[Geoserver-users] SRS advertised in capabilities document (with possible funding)??

GeoServer GeoServer User
1

Hi,

WMS side is handled already. By default the long SRS/CRS list is advertised but it can be made shorter. Try http://demo.opengeo.org/geoserver/wms?service=WMS&version=1.3.0&request=GetCapabilities

However, you are right with WFS and Geoserver advertises only DefaultSRS http://demo.opengeo.org/geoserver/wms?service=WFS&version=1.1.0&request=GetCapabilities

It would be useful to have a short OtherSRS if WFS clients could make a selection list based on that. WFS 1.0.0 standard supports only default SRS so there is no place for OtherSRS in GetCapabilities with that version so we must be talking about WFS >= 1.1.0.

I believe that WFS standard mandates that what is advertised in the GetCapabilities must be usable. I think it is compliant that Geoserver offers a support for using other SrsNames in WFS 1.1.0 and also in WFS 1.0.0 even this possibility is not advertised in GetCapabilities. But as I said, having an OtherSRS list would be an improvement. Are you after a common list for the whole WFS service or a per feature type setting for OtherSRS?

-Jukka Rahkonen-

________________________________
Brent Wood wrote:

This has been discussed before, but I'm not aware of any solution.

Several WMS/WFS client applications present users with a list of available SRS determined from the capabilities document - if there are no alternatives listed, then only the default SRS is available.

Geoserver does NOT provide the list of supported SRS in the capabilities doc (which I think makes it non-compliant with the spec? eg: 7.2.4.6.7 of the WMS spec)

I'm aware of earlier discussions that including some 5000 CRS's in every layer creates a bloated document & I agree in principle.

However, to solve one of the problems we have encountered in our migration fom mapserver to Geoserver, is it possible to allow Geoserver to advertise specified CRS's in the capabilities document? So the admin menu lets some CRS's be identified & selected to be so advertised. This would not preclude unadvertised CRS's being supported as well, but I think does address this issue.

If this is considered viable, I have access to some funding which could pay for it to be implemented.

2

Hi Jukka,

Thanks for your response.

For our needs, a common list for all layers provided by the service would be adequate, but a per feature type would be ideal, and ensure the best level of interoperability.

The particular use case is for clients harvesting copies of datasets via WFS 1.1.0 for local institutional caches - at present they are downloading in the default CRS, then locally reprojecting. We’d like to be able to advertise locally relevant CRS’s to enable server side reprojection.

With WMS, the long list is perhaps overkill, and again, being able to identify a shorter list of relevant SRS’s would be useful (I don’t think you can select a short lis at present?). The long list includes many inappropriate (useless) CRS’s - for example I understand you get offered Antarctic Polar SRS’s even if you data is equatorial or Arctic, just because Geoserver “can do it”

Ideally (I think - but open to debate) the admin UI would allow a list of advertised SRS’s to be selected, and whether they are advertised per feature class or globally is also selectable.

Depending on the cost, I may be able to fund this enhancement.

Thanks again,

Brent Wood

From: Rahkonen Jukka jukka.rahkonen@anonymised.com
To: “geoserver-users@lists.sourceforge.net” geoserver-users@anonymised.com.sourceforge.net
Sent: Thursday, November 14, 2013 6:58 PM
Subject: Re: [Geoserver-users] SRS advertised in capabilities document (with possible funding)??

Hi,

WMS side is handled already. By default the long SRS/CRS list is advertised but it can be made shorter. Try http://demo.opengeo.org/geoserver/wms?service=WMS&version=1.3.0&request=GetCapabilities

However, you are right with WFS and Geoserver advertises only DefaultSRS http://demo.opengeo.org/geoserver/wms?service=WFS&version=1.1.0&request=GetCapabilities

It would be useful to have a short OtherSRS if WFS clients could make a selection list based on that. WFS 1.0.0 standard supports only default SRS so there is no place for OtherSRS in GetCapabilities with that version so we must be talking about WFS >= 1.1.0.

I believe that WFS standard mandates that what is advertised in the GetCapabilities must be usable. I think it is compliant that Geoserver offers a support for using other SrsNames in WFS 1.1.0 and also in WFS 1.0.0 even this possibility is not advertised in GetCapabilities. But as I said, having an OtherSRS list would be an improvement. Are you after a common list for the whole WFS service or a per feature type setting for OtherSRS?

-Jukka Rahkonen-

Brent Wood wrote:

This has been discussed before, but I’m not aware of any solution.

Several WMS/WFS client applications present users with a list of available SRS determined from the capabilities document - if there are no alternatives listed, then only the default SRS is available.

Geoserver does NOT provide the list of supported SRS in the capabilities doc (which I think makes it non-compliant with the spec? eg: 7.2.4.6.7 of the WMS spec)

I’m aware of earlier discussions that including some 5000 CRS’s in every layer creates a bloated document & I agree in principle.

However, to solve one of the problems we have encountered in our migration fom mapserver to Geoserver, is it possible to allow Geoserver to advertise specified CRS’s in the capabilities document? So the admin menu lets some CRS’s be identified & selected to be so advertised. This would not preclude unadvertised CRS’s being supported as well, but I think does address this issue.

If this is considered viable, I have access to some funding which could pay for it to be implemented.

DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

3

Hi,

The limited SRS list for WMS is set with the config utility in the Services - WMS page. I can see that documentation http://docs.geoserver.org/stable/en/user/webadmin/services/WMS.html#service-metadata lags behind and is missing also some other options. You'd better to install Geoserver and check the page
http://localhost:8080/geoserver/web/?wicket:bookmarkablePage=:org.geoserver.wms.web.WMSAdminPage

It will be up to you and whoever you will contract to deside if OtherSRS list will affect the whole WFS service or each feature type separately. Have a look at the UI pages and think where would you like to see this new config option.

-Jukka Rahkonen-

________________________________
Brent Wood wrote:

Hi Jukka,

Thanks for your response.

For our needs, a common list for all layers provided by the service would be adequate, but a per feature type would be ideal, and ensure the best level of interoperability.

The particular use case is for clients harvesting copies of datasets via WFS 1.1.0 for local institutional caches - at present they are downloading in the default CRS, then locally reprojecting. We'd like to be able to advertise locally relevant CRS's to enable server side reprojection.

With WMS, the long list is perhaps overkill, and again, being able to identify a shorter list of relevant SRS's would be useful (I don't think you can select a short lis at present?). The long list includes many inappropriate (useless) CRS's - for example I understand you get offered Antarctic Polar SRS's even if you data is equatorial or Arctic, just because Geoserver "can do it"

Ideally (I think - but open to debate) the admin UI would allow a list of advertised SRS's to be selected, and whether they are advertised per feature class or globally is also selectable.

Depending on the cost, I may be able to fund this enhancement.

Thanks again,

  Brent Wood

________________________________
From: Rahkonen Jukka <jukka.rahkonen@anonymised.com>
To: "geoserver-users@lists.sourceforge.net" <geoserver-users@anonymised.comrge.net>
Sent: Thursday, November 14, 2013 6:58 PM
Subject: Re: [Geoserver-users] SRS advertised in capabilities document (with possible funding)??

Hi,

WMS side is handled already. By default the long SRS/CRS list is advertised but it can be made shorter. Try http://demo.opengeo.org/geoserver/wms?service=WMS&version=1.3.0&request=GetCapabilities

However, you are right with WFS and Geoserver advertises only DefaultSRS http://demo.opengeo.org/geoserver/wms?service=WFS&version=1.1.0&request=GetCapabilities

It would be useful to have a short OtherSRS if WFS clients could make a selection list based on that. WFS 1.0.0 standard supports only default SRS so there is no place for OtherSRS in GetCapabilities with that version so we must be talking about WFS >= 1.1.0.

I believe that WFS standard mandates that what is advertised in the GetCapabilities must be usable. I think it is compliant that Geoserver offers a support for using other SrsNames in WFS 1.1.0 and also in WFS 1.0.0 even this possibility is not advertised in GetCapabilities. But as I said, having an OtherSRS list would be an improvement. Are you after a common list for the whole WFS service or a per feature type setting for OtherSRS?

-Jukka Rahkonen-

________________________________
Brent Wood wrote:

This has been discussed before, but I'm not aware of any solution.

Several WMS/WFS client applications present users with a list of available SRS determined from the capabilities document - if there are no alternatives listed, then only the default SRS is available.

Geoserver does NOT provide the list of supported SRS in the capabilities doc (which I think makes it non-compliant with the spec? eg: 7.2.4.6.7 of the WMS spec)

I'm aware of earlier discussions that including some 5000 CRS's in every layer creates a bloated document & I agree in principle.

However, to solve one of the problems we have encountered in our migration fom mapserver to Geoserver, is it possible to allow Geoserver to advertise specified CRS's in the capabilities document? So the admin menu lets some CRS's be identified & selected to be so advertised. This would not preclude unadvertised CRS's being supported as well, but I think does address this issue.

If this is considered viable, I have access to some funding which could pay for it to be implemented.

------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@anonymised.comrge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-users