confused by STATUS ON/OFF purpose
Nathan Vander Wilt
nathan.vanderwilt at ORIONNETWORKSOLUTIONS.COM
Wed Oct 17 12:57:30 PDT 2007
Yes, that explains what I was seeing. I added your response as a
comment to http://mapserver.gis.umn.edu/docs/faq/default_vs_on_vs_off/
faq_view
thanks much,
-natevw
On Oct 17, 2007, at 12:42 PM, Steve Lime wrote:
> With regards to the CGI. It turns everything off that is not
> "STATUS DEFAULT" off so all layers start from the same state (e.g.
> off) and must be explicitly requested to be drawn or query. That
> common state made (at least in my mind) implementations easier. I
> mean, if a layer "lakes" started ON the doing layer=lakes would
> turn it OFF. So I wanted to remove the ambiguity of a starting state.
>
> So, from the CGI point of view if it's not a default layer then
> consider it off and you must request it. Does that help?
>
> Steve
>
>>>> Nathan Vander Wilt <nathan.vanderwilt at ORIONNETWORKSOLUTIONS.COM>
>>>> 10/17/07 1:48 PM >>>
> I'm trying to figure out what a layer's "STATUS" really means. I get
> DEFAULT -- basically, the layer is on no matter what. But in
> practice, I'm not seeing the difference between ON and OFF.
>
> http://mapserver.gis.umn.edu/docs/faq/default_vs_on_vs_off has a
> promising description, but doesn't seem accurate either.
>
> When I query layers=all, I get layers with both ON and OFF status,.
> When I omit layer/layers from my query entirely, I don't get any ON
> images, just DEFAULT ones.
>
> What CGI query will return the layers with ON or DEFAULT set, but no
> OFF layers?
>
> thanks,
> -natevw
>
More information about the MapServer-users
mailing list