Add layername based GetCapabilities Filtering
---------------------------------------------
Key: GEOS-3829
URL: http://jira.codehaus.org/browse/GEOS-3829
Project: GeoServer
Issue Type: Wish
Environment: Java
Reporter: Tisham Dhar
Assignee: Andrea Aime
Priority: Minor
Some deployments get large in terms of number of layers available. In these
cases getcapabilities parsing can become a real pain especially on the client
side and if the code is not well written. In my particular case, worldwind
reparses the whole WMS getcapability to create each WMSLayer for display which
is very wasteful and can be trying on the user's patience.
OMAR implements a catalogue like system where the default getcapability returns
an index layer encompassing the total extent of all layers. Subsequent
getcapability requests can be made with the "layers" parameter to obtain a cut
down version of getcapabilities containing only the mentioned layers. This is
very non-standard behaviour and should only be avaialable in a special
catalogue mode.
Here is sample OMAR capability request. Note OMAR is a Groovy/Grails layer on
top of Mapserver.
http://hypersphere.telascience.org/omar-2.0/ogc/wms?request=GetCapabilities&layers=322
--
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
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
