Changes between Version 3 and Version 4 of HidingLayersInOGCWebServices

Timestamp:

Feb 26, 2009, 11:23:56 AM (15 years ago)

Author:

mko

Comment:

--

HidingLayersInOGCWebServices

@@ -34 +34 @@
  3. One may want to offer a given layer via WMS but not via WFS (or any combination of services). In other words, we need the ability to select in which OGC services a given layer is exposed.
 
- 4. ...
+ 4. The [http://mapserver.org/faq.html#how-do-i-add-a-copyright-notice-on-the-corner-of-my-map copyright notice] shall not appear in the GetCapabilities output and shall not be queryable.
  
  5. ...
@@ -42 +42 @@
 === Solution 1 ===
 
-...
+Disable each request type per service. The metadata section of the layer object could be extended by a key {{{[service]_disable_request}}}. Each request type listet in this key will not be processed for the given service. The value {{{all}}} will disable a service completely. Examples:
+{{{
+    wfs_disable_request 'all'
+    wms_disable_request 'getcapabilities getfeatureinfo'
+}}}
+
+The docs must contain clear warnings about the behaviour of the feature, esp. the value 'all' and OGC compability.
 
 === Solution 2 ===