<html>
<head>
</head>
<body style="font-variant: normal; line-height: normal; font-family: Comic Sans MS; margin-left: 4px; margin-right: 4px; margin-bottom: 1px; font-weight: normal; margin-top: 4px; font-style: normal; font-size: 12pt">
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">Steve,</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">Hmmm, good point on the Copyright thing, I suppose it's complicating things, but you could use a KEYWORD / function in the Mapfiles to enforce the stamping, or hide such layers from a [toggle_layer] listing.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">It's sometimes easier to predict (or assume) that certain layers should be on by default. In a GeoMoose configuration, the data owners/custodians can have their own publication controls, and they will have their preferences for default layers, for particular users, this may work very well for them, but other (unpredicted) users, may want/need to display things in different combinations of layers in their view of the world.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">I've been a long (LONG) time user of the CGI model for MapServer, even building my own image generator before ever moving to using MapServer. The CGI methods for me just seem easier and less verbose to use, and much quicker to implement on the fly, especially when I have control of everything from front to back. Some WMS queries are optional, so not all capabilities that a CGI approach would afford are necessarily available via WMS all the time. The thread was aimed at making things more flexible overall, not just more complicated.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">Templates work very well, and look like they will work for the layer listing too (I thought about this before sending the questions). Lastly, since MapServer is in the mix, I can combine CGI with WMS calls as well. I may need to run the request through some proxy, but then I have even more control over things, A WMS+ service if you will.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">My parting thought on this, would be, if this is truly seen as a cumbersome or time consuming thing to add to mapserver, should some review of current capabilities be performed to see what redundant capabilities might be removable from MapServer since they are now available via other means, like WMS, or at the very least, implement/convert them to a WMS like call.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">I prefer to keep both products/services in their own sand boxes, and apply the best capabilities list to each, but maybe I'm missing something at the big(ger) picture level.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">:c)</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">bobb</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br>
>>> Stephen Woodbridge <woodbri@swoodbridge.com> wrote:<br> </p>
<table style="margin-left: 15px; margin-right: 0; margin-bottom: 0; margin-top: 0; font-size: 1em" bgcolor="#f3f3f3" border="0">
<tr>
<td>
<div style="padding-left: 7px; border-left: solid 1px #050505">
<p style="margin-top: 0; margin-bottom: 0">
I do not think this would be a good idea because it would allow a user<br>to turn off say a copyright layer for instance.<br><br>I think it is better to plan out your application to turn things on that<br>you want on as Steve suggests.<br><br>So while I do you the CGI even in OpenLayers over the WMS, mostly<br>because I learned it first and partly because WMS just makes it too easy<br>for unwanted users to pull maps, I am somewhat inclined to think the WMS<br>is the better way to go if you want all the capabilities of WMS. What is<br>your rationale for adding a all this stuff to the CGI? Does working it<br>through the template system meet your needs?<br><br>Inquiring minds want to know :)<br><br>Best regards,<br>   -Steve W<br><br>On 2/1/2011 10:54 PM, Lime, Steve D (DNR) wrote:<br>> 1) If your interface is smart enough to explicitly turn the<br>> centerlines off why wouldn't you just set STATUS OFF in the mapfile<br>> and explicitly turn them on? I think the REQUIRES parameter is a<br>> better means of triggering this auto-off capability in any regard.<br>><br>> 2) You might already be able to do the layer list using the<br>> [toggle_layers] tag. It returns a space delimited list of layers that<br>> can be toggled. It's available in any query/browse template so I<br>> imagine you could craft a URL that runs quickly to access them that<br>> way... Just a thought.<br>><br>> Steve ________________________________________ From:<br>> mapserver-dev-bounces@lists.osgeo.org<br>> [mapserver-dev-bounces@lists.osgeo.org] On Behalf Of Bob Basques<br>> [Bob.Basques@ci.stpaul.mn.us] Sent: Tuesday, February 01, 2011 2:43<br>> PM To: MapServer Dev Mailing List Subject: [mapserver-dev] A thought<br>> about a CGI parameter add,   basically a switch for turning a default<br>> layer off.<br>><br>> All,<br>><br>><br>> Is this doable?<br>><br>><br>> Was wondering about a mechanism to turn a DEFAULT layer off via CGI,<br>> something like "layers=-centerlines", where the negative sign ( - )<br>> would be used to indicate that a default layer should NOT be drawn<br>> for a CGI request.<br>><br>><br>> In short terms, could adding a negative sign ( - ) to the front of a<br>> layer name to NOT draw that layer be easily implemented in the CGI<br>> calls?<br>><br>><br>> WARNING:  If the above is possible, the next question would be to get<br>> a list of the layers that are available in a MAPFILE (like<br>> GetCapabilities) for drawing.  And don't say use WMS, otherwise you<br>> should get rid of the LEGEND generation in MapServer too, since that<br>> can be done via WMS as well.  :c)   I also have an inkling that<br>> having the ability to poll the mapfile for the layers available might<br>> be an interesting capability to add in that would allow for some<br>> interesting user GUI elements to be built around.<br>><br>><br>> ---------<br>><br>><br>> Here is my use case (if needed):<br>><br>><br>> Say I have a centerline file of a street network for a map, and then<br>> add in a Aerial photo background, I want to turn the centerlines off,<br>> but keep the labels as an overlay.  Both the centerlines and the<br>> labels are on by default at the mapfile.<br>><br>><br>> Thanks<br>><br>><br>> bobb<br>><br>><br>><br>> _______________________________________________ mapserver-dev mailing<br>> list mapserver-dev@lists.osgeo.org<br>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br><br>
</p>
</div>
</td>
</tr>
</table>
</body>
</html>