Nabble - eogeo

Re: WMS TIME and ELEVATION through XML POST

2009-12-15T13:21:05Z

Alessio Fabiani wrote:
> I'm trying to build up a WMS GetMap request XML encoded and post it trhough
> HTTP POST to the server, but actually I'm not able to find a way to specify
> also the TIME and ELEVATION parameters into the XML request.
>
> Also the GetMap XSD seems not allowing to do that. The only possible way
> might be specifying the parameters through the SLD filter but actually I
> would like to query raster layers and cannot figure out how to do that.
>
> Can someone please give me some pointers and delucidations on this issue?

To the best of my knowledge, the situation is this. Very little
attention has been paid to the XML encodings of the various requests in
the latest versions of the WMS specifications, and thus what exists is
not necessary complete or consistent with the HTTP GET versions of the
requests. Thus, the only real way to include the TIME and ELEVATION
parameters in an XML-encoded GetMap request is to use a vendor- or
project-specific extension to the GetMap schema.

The next version of the WMS specification (currently being developed)
will hopefully remedy this situation.

---
Keith Pomakis <pomakis@...>
Senior Software Developer, CubeWerx Inc.
15 rue Gamelin, Gatineau, Québec J8Y 3B5
Phone: 819-771-8303 x202, FAX: 819-771-8388
_______________________________________________
wms-dev mailing list
wms-dev@...
http://lists.eogeo.org/mailman/listinfo/wms-dev

From forum: eogeo - wms-dev

WMS TIME and ELEVATION through XML POST

2009-12-15T07:47:20Z

Hello all,

I'm trying to build up a WMS GetMap request XML encoded and post it trhough HTTP POST to the server, but actually I'm not able to find a way to specify also the TIME and ELEVATION parameters into the XML request.

Also the GetMap XSD seems not allowing to do that. The only possible way might be specifying the parameters through the SLD filter but actually I would like to query raster layers and cannot figure out how to do that.

Can someone please give me some pointers and delucidations on this issue?

Thank you very much.

Regards,

Alessio.

-------------------------------------------------------
Eng. Alessio Fabiani
Founder / CTO GeoSolutions S.A.S.
Via Carignoni 51
55041 Camaiore (LU)
Italy

phone: +39 0584 983027
fax: +39 0584 983027
mob: +39 349 8227000

http://www.geo-solutions.it
http://geo-solutions.blogspot.com
-------------------------------------------------------

_______________________________________________
wms-dev mailing list
wms-dev@...
http://lists.eogeo.org/mailman/listinfo/wms-dev

From forum: eogeo - wms-dev

Re: Best practices for securing WMS?

2009-11-16T09:19:03Z

Jon,

The OGC has started an "Authentication Interoperability Experiment" to address just this issue - and develop a Best Practice for Authentication on WMS. The first use case is HTTP Authentication.

I encourage you to get engaged if possible. An initial announcement on the effort is here -

http://www.opengeospatial.org/pressroom/pressreleases/1073

Please do not hesitate to contact me if you any questions, or if I may help in any way.

Regards,

Jeff

Today's Topics:

1. Best practices for securing WMS? (Jon Blower)

2. Re: Best practices for securing WMS? (Horst Wessel (Moskito))

----------------------------------------------------------------------

Message: 1

Date: Mon, 16 Nov 2009 15:29:51 +0000

From: Jon Blower <jdb@...>

Subject: [wms-dev] Best practices for securing WMS?

To: wms-dev@...

Message-ID:

<2bb6ee950911160729t5b21674fj68038147c50ddcbe@...>

Content-Type: text/plain; charset=ISO-8859-1

Hi all,

I'm in a project in which we are considering providing WMS access to

secure datasets. We're at the early stages of researching how best to

do this (or even whether we really need to do this at all) but I was

wondering if anyone has developed any best practices in this area?

We'd probably be looking at some fairly lightweight authentication on

the WMS server. I know some WMS clients support HTTP Basic

authentication, but this has to be done over HTTPS to protect

passwords. Digest authentication over plain HTTP is another

possibility. Client-side certificates are another, although rather

more complex for the client and unlikely to be supported in many WMS

clients.

We'd also like the access control to be fairly fine-grained, i.e.

potentially with different permissions on each layer. We develop the

WMS server in question so we have control of any server-side code that

might be needed.

Thanks in advance for any help.

Jon

Dr Jon Blower

Technical Director, Reading e-Science Centre

Environmental Systems Science Centre

University of Reading

Harry Pitt Building, 3 Earley Gate

Reading RG6 6AL. UK

Tel: +44 (0)118 378 5213

Fax: +44 (0)118 378 6413

j.d.blower@...

http://www.nerc-essc.ac.uk/People/Staff/Blower_J.htm

------------------------------

Message: 2

Date: Mon, 16 Nov 2009 23:16:03 +0700

From: "Horst Wessel (Moskito)" <horst.wessel@...>

Subject: Re: [wms-dev] Best practices for securing WMS?

To: "Jon Blower" <jdb@...>, <wms-dev@...>

Message-ID: <58412A6E333D4CA2815BB4C609438061@DELLPC>

Content-Type: text/plain; format=flowed; charset="iso-8859-1";

reply-type=original

Hello all,

we until now have implemented HTTP Basic Auth for the Moskito GIS Webserver.

We do http normally, as the security in most cases is Ok. There are 2

solution for the password query. It can be done by assess to the map or by

queriing a special page for login. As soon, as this page has been accessed,

all other pages from the same server get user and password as well.

After login, we can control detailed reaction on WMS-GetFeatureinfo and

layers. If interested, please take a look at www.cantho.iwrm.vn for an

impression. This solution is easy to use and medium secure.

Hope this helps

Horst

Moskito GIS

horst.wessel@...

----- Original Message -----

From: "Jon Blower" <jdb@...>

To: <wms-dev@...>

Sent: Monday, November 16, 2009 10:29 PM

Subject: [wms-dev] Best practices for securing WMS?

> Hi all,

> I'm in a project in which we are considering providing WMS access to

> secure datasets. We're at the early stages of researching how best to

> do this (or even whether we really need to do this at all) but I was

> wondering if anyone has developed any best practices in this area?

> We'd probably be looking at some fairly lightweight authentication on

> the WMS server. I know some WMS clients support HTTP Basic

> authentication, but this has to be done over HTTPS to protect

> passwords. Digest authentication over plain HTTP is another

> possibility. Client-side certificates are another, although rather

> more complex for the client and unlikely to be supported in many WMS

> clients.

> We'd also like the access control to be fairly fine-grained, i.e.

> potentially with different permissions on each layer. We develop the

> WMS server in question so we have control of any server-side code that

> might be needed.

> Thanks in advance for any help.

> Jon

> --

> Dr Jon Blower

> Technical Director, Reading e-Science Centre

> Environmental Systems Science Centre

> University of Reading

> Harry Pitt Building, 3 Earley Gate

> Reading RG6 6AL. UK

> Tel: +44 (0)118 378 5213

> Fax: +44 (0)118 378 6413

> j.d.blower@...

> http://www.nerc-essc.ac.uk/People/Staff/Blower_J.htm

> _______________________________________________

> wms-dev mailing list

> wms-dev@...

> http://lists.eogeo.org/mailman/listinfo/wms-dev

------------------------------

_______________________________________________

wms-dev mailing list

wms-dev@...

http://lists.eogeo.org/mailman/listinfo/wms-dev

End of wms-dev Digest, Vol 43, Issue 1

**************************************

_______________________________________________
wms-dev mailing list
wms-dev@...
http://lists.eogeo.org/mailman/listinfo/wms-dev

From forum: eogeo - wms-dev

Re: Best practices for securing WMS?

2009-11-16T08:16:03Z

Hello all,

we until now have implemented HTTP Basic Auth for the Moskito GIS Webserver.
We do http normally, as the security in most cases is Ok. There are 2
solution for the password query. It can be done by assess to the map or by
queriing a special page for login. As soon, as this page has been accessed,
all other pages from the same server get user and password as well.

After login, we can control detailed reaction on WMS-GetFeatureinfo and
layers. If interested, please take a look at www.cantho.iwrm.vn for an
impression. This solution is easy to use and medium secure.

Hope this helps

Horst
Moskito GIS
horst.wessel@...

----- Original Message -----
From: "Jon Blower" <jdb@...>
To: <wms-dev@...>
Sent: Monday, November 16, 2009 10:29 PM
Subject: [wms-dev] Best practices for securing WMS?

> Hi all,
>
> I'm in a project in which we are considering providing WMS access to
> secure datasets. We're at the early stages of researching how best to
> do this (or even whether we really need to do this at all) but I was
> wondering if anyone has developed any best practices in this area?
>
> We'd probably be looking at some fairly lightweight authentication on
> the WMS server. I know some WMS clients support HTTP Basic
> authentication, but this has to be done over HTTPS to protect
> passwords. Digest authentication over plain HTTP is another
> possibility. Client-side certificates are another, although rather
> more complex for the client and unlikely to be supported in many WMS
> clients.
>
> We'd also like the access control to be fairly fine-grained, i.e.
> potentially with different permissions on each layer. We develop the
> WMS server in question so we have control of any server-side code that
> might be needed.
>
> Thanks in advance for any help.
>
> Jon
>
> --
> Dr Jon Blower
> Technical Director, Reading e-Science Centre
> Environmental Systems Science Centre
> University of Reading
> Harry Pitt Building, 3 Earley Gate
> Reading RG6 6AL. UK
> Tel: +44 (0)118 378 5213
> Fax: +44 (0)118 378 6413
> j.d.blower@...
> http://www.nerc-essc.ac.uk/People/Staff/Blower_J.htm
> _______________________________________________
> wms-dev mailing list
> wms-dev@...
> http://lists.eogeo.org/mailman/listinfo/wms-dev
>
>

_______________________________________________
wms-dev mailing list
wms-dev@...
http://lists.eogeo.org/mailman/listinfo/wms-dev

From forum: eogeo - wms-dev

Best practices for securing WMS?

2009-11-16T07:29:51Z

Hi all,

I'm in a project in which we are considering providing WMS access to
secure datasets. We're at the early stages of researching how best to
do this (or even whether we really need to do this at all) but I was
wondering if anyone has developed any best practices in this area?

We'd probably be looking at some fairly lightweight authentication on
the WMS server. I know some WMS clients support HTTP Basic
authentication, but this has to be done over HTTPS to protect
passwords. Digest authentication over plain HTTP is another
possibility. Client-side certificates are another, although rather
more complex for the client and unlikely to be supported in many WMS
clients.

We'd also like the access control to be fairly fine-grained, i.e.
potentially with different permissions on each layer. We develop the
WMS server in question so we have control of any server-side code that
might be needed.

Thanks in advance for any help.

Jon

--
Dr Jon Blower
Technical Director, Reading e-Science Centre
Environmental Systems Science Centre
University of Reading
Harry Pitt Building, 3 Earley Gate
Reading RG6 6AL. UK
Tel: +44 (0)118 378 5213
Fax: +44 (0)118 378 6413
j.d.blower@...
http://www.nerc-essc.ac.uk/People/Staff/Blower_J.htm
_______________________________________________
wms-dev mailing list
wms-dev@...
http://lists.eogeo.org/mailman/listinfo/wms-dev

From forum: eogeo - wms-dev

Display WMS layer within Openlayers when STATUS set to ON

2009-10-26T04:28:48Z

Hi, I have been struggling with this problem for a while now.

My WMS layer will only display if STATUS is set to DEFAULT within the mapfile. If status is set to ON, i get following error message within OL Map window. "WMSLoadGetMapParams(): WMS Server Error". What am i missing to call the layer within openlayers? The reason i want it set to ON is i eventually want to have several layers and call them for a particular zoom level.

My Code is as follows:

      var bounds = new OpenLayers.Bounds(0, 0, 660046, 1229782);
      var map, layer1, layer2;
      var options = { maxExtent: bounds, maxResolution: 1000, numZoomLevels: 10};



      function init(){
          map = new OpenLayers.Map('map', options);

      layer1 = new OpenLayers.Layer.WMS("OpenLayers WMS",
      "http://localhost/cgi-bin/mapserv.exe?map=c:/ms4w/apps/openlayers-2.8/data/uk2.map", { layers: "250" },
      {gutter: 15});

      map.addLayer(layer1);
      map.zoomToMaxExtent();

And my mapfile looks as follows:

NAME UK1
PROJECTION
    'proj=longlat'
    'ellps=WGS84'
    'datum=WGS84'
    'no_defs'
    ''
    END
    SIZE 1600 1200
    IMAGECOLOR -1 -1 -1
    IMAGETYPE JPEG
    SHAPEPATH "http://localhost/openlayers/data/"
    #QGIS
    #EXTENT -837824 -111116 1677552 1232884
    #Port Talbot
    #EXTENT 272000 187000 278000 193000
    #UK
    EXTENT 0 0 660046 1240000
    UNITS METERS


WEB
   TEMPLATE "http://localhost/openlayers/examples/uktest.html"
   LOG "\ms4w\tmp\ms_tmp\log.txt"
      IMAGEPATH "\ms4w\tmp\ms_tmp\"
      IMAGEURL "/ms_tmp/"
      METADATA
  'wms_title' "map"
        'wms_onlineresource' "http://127.0.0.1./cgi-bin/mapserv?map=uk2.map"
      END

END

LAYER

    NAME "250"
    METADATA
      '250' "wms_demo"
    END
    STATUS DEFAULT
    TYPE raster
    TILEINDEX "250K"
    TILEITEM "Location"
    PROJECTION
  'proj=longlat'
  'ellps=WGS84'
  'datum=WGS84'
  'no_defs'
  ''
    END
    CLASS
      STYLE
       COLOR 0 0 0
      END
      LABEL
       COLOR 0 0 0
       SIZE SMALL
      END

    END

Thanks for any help in advance

_______________________________________________
wms-dev mailing list
wms-dev@...
http://lists.eogeo.org/mailman/listinfo/wms-dev

From forum: eogeo - wms-dev

Re: Georss.org = Attack Site (Firefox)

2009-10-14T05:42:55Z

I'm on it. Wordpress needs to be upgraded.

On Wednesday, October 14, 2009, Andrew Turner <ajturner@...> wrote:

> I'm on it. Wordpress needs to be upgraded.
>
> (via mobile)
>
> On Oct 14, 2009, at 6:44 AM, "Mathias Richter" <saith@...> wrote:
>
>
> Hello list,
>
>
>
> my firefox 3.5 browser says, that georss.org is an “Suspected Attack Site!”. Who can solve this problem?
>
>
>
> Greetings,
>
> saith
>
> _______________________________________________
> georss mailing list
> georss@...
> http://lists.eogeo.org/mailman/listinfo/georss
>
>

--
Andrew Turner
mobile: 248.982.3609
andrew@...
http://highearthorbit.com

http://geocommons.com Helping build the Geospatial Web
Introduction to Neogeography - http://oreilly.com/catalog/neogeography
_______________________________________________
georss mailing list
georss@...
http://lists.eogeo.org/mailman/listinfo/georss

Nabble - eogeo

Re: WMS TIME and ELEVATION through XML POST

WMS TIME and ELEVATION through XML POST

Re: Best practices for securing WMS?

Re: Best practices for securing WMS?

Best practices for securing WMS?

Display WMS layer within Openlayers when STATUS set to ON

Re: Georss.org = Attack Site (Firefox)

Georss.org = Attack Site (Firefox)

Re: [Geowanking] openARML augmented Reality Markuplanguage ~ extended KML?

Re: [Geowanking] openARML augmented Reality Markuplanguage ~ extended KML?

Re: [Geowanking] openARML augmented Reality Markuplanguage ~ extended KML?

Re: [Geowanking] openARML augmented Reality Markuplanguage ~ extended KML?

Re: [Geowanking] openARML augmented Reality Markup language ~ extended KML?

Re: [Geojson] openARML augmented Reality Markup language ~ extended KML?

Re: openARML augmented Reality Markup language ~ extended KML?

openARML augmented Reality Markup language ~ extended KML?

Re: Yet another flavor of GeoRSS?

Re: Yet another flavor of GeoRSS?

Re: simple 3D geocode for AR

Re: Yet another flavor of GeoRSS?

Re: Yet another flavor of GeoRSS?

Re: Yet another flavor of GeoRSS?

Re: Yet another flavor of GeoRSS?

Re: Yet another flavor of GeoRSS?

Re: Yet another flavor of GeoRSS?

Yet another flavor of GeoRSS?

GeoRSS in Twitter API

Re: [Geowanking] [Geojson] simple 3D geocode for AR

Re: [Geowanking] [Geojson] simple 3D geocode for AR

Re: [Geowanking] [Geojson] simple 3D geocode for AR

Re: [Geowanking] [Geojson] simple 3D geocode for AR

Re: [Geowanking] [Geojson] simple 3D geocode for AR

Re: [Geowanking] [Geojson] simple 3D geocode for AR

Re: [Geowanking] [Geojson] simple 3D geocode for AR

Re: [Geowanking] [Geojson] simple 3D geocode for AR