-
-
Notifications
You must be signed in to change notification settings - Fork 364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tileindex Layer and WMS Get Capabilities. #1952
Comments
|
Author: dnadeau |
|
Author: jmckenna "...For many clients who have an application mapfile AND a serve-through-wms requirement for their data I have to make a copy of the mapfile and remove certain layers that shouldn't be served through WMS...I wish there was a magical "wms_exclude_layers" metadata item that we could set." |
|
Author: dnadeau I did not set "wms_exclude_layers" metadata but ows_service if you set this METADATA in the LAYER or WEB section to "none" no layer will be displayed in the GetCapabilities request. This is working only for WMS at this point. i.e. I found the discussion thread about this on MPASERVER-DEV mailing list. |
|
Author: mko related discussion thread: related tickets: |
|
Author: dmorissette |
|
Author: bj Any comment from a dev would be helpful gain momentum here. bj |
|
Author: assefa |
|
Author: dmorissette |
|
attachment http://trac.osgeo.org/mapserver/attachment/ticket/1952/mapwms.patch : |
|
attachment http://trac.osgeo.org/mapserver/attachment/ticket/1952/mapwms.c.patch : |
|
attachment http://trac.osgeo.org/mapserver/attachment/ticket/1952/ms540b1-hidden-layers.patch : |
Reporter: dnadeau@pop600.gsfc.nasa.gov
Date: 2006/10/31 - 17:01
Trac URL: http://trac.osgeo.org/mapserver/ticket/1952
When a client perform a Get Capabilities, all "tileindex" layers should not be
displayed. WMS clients may try to get data from this layer and the request will
fail.
Can we add a STATUS flag to hide some layers from a Get Capability request?
Here is an example where the first layer should not be displayed in a Get Capability request.
The text was updated successfully, but these errors were encountered: