Allow to limit the list of available CRS's in WMS GetCapabilities
-----------------------------------------------------------------
Key: GEOS-1830
URL: http://jira.codehaus.org/browse/GEOS-1830
Project: GeoServer
Issue Type: Improvement
Components: Configuration, WMS
Affects Versions: 1.6.3
Reporter: Gabriel Roldán
Assignee: Gabriel Roldán
Fix For: 1.6.3
The WMS capabilities document currently exposes the list of all the geoserver
supported CRS's.
That means 3900+ elements of the type {{<SRS>EPSG:2588</SRS>}}, which, by one
side, kills most javascript based WMS clients when trying to parse the
GetCapabilities document. And by the other hand it makes sense for an
installation to expose those CRS codes that make sense for the actual data
being served.
This issue though, is not meant to actually limit the list of CRS's geoserver
can operate with, but to just limit the list of exposed ones. So if a request
is made over a supported CRS that is not listed in the capabilities document,
it should keep working anyways.
Also, a very basic user interface configuration element shall be included, so
its not that hard for users to specify the list of CRS's. This may be as simple
as a text area in which to write a comma separated list of epsg codes to expose.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
