<br><div><span class="gmail_quote">2006/11/16, Daniel Morissette <<a href="mailto:dmorissette@mapgears.com">dmorissette@mapgears.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Frank Warmerdam wrote:<br>><br>> I think if the wcs service is listed but the layer is not a raster layer,<br>> or does not have DUMP TRUE set, then an error should be emitted explaining<br>> the problem.<br>>
<br><br>An option could be to emit a <!-- WARNING ... --> comment in the<br>GetCapabilities when this layer is being processed. At least for WMS and<br>WFS, WARNINGs in GetCapabilities are used this way to report several
<br>potential config issues or missing pieces of info.<br><br>> I also think there should be an "all" option indicating that a layer<br>> should be made visible to all *applicable* services.<br>><br><br>
Or a way to make 'all' the default? For instance, we could allow setting<br>"ows_service" "wms, wfs" in the WEB metadata, and this value would be<br>inherited by default by all layers unless they have their own
<br>ows_service metadata. This way if you want to include 20 layers and<br>exclude only one or two you can do it easily without having to set<br>ows_service on all layers in the mapfile.</blockquote><div><br>Daniel,<br><br>
I like the idea of seting ows_service in the WEB to default to all layers unless ows_service is specified in a specify layer.<br><br>Although, this idea does not cover bug 300 about the output of "geometry". <br>
<br>I first thought of "ows_service" as a way to turn a layer on and off and in bug 300 Doug Cate talks about "Outputs attribute fields (with our without) the geometry". I think we would need another metadata for this matter something like "ows_service_geometry".
<br><br>Right now, I am willing to start writting code for ows_service metadata. For the "geometry" case I would prefer to postpone it until I get to know MapServer code better. <br><br>Denis<br><br><br></div>
<br></div><br>