Subject: Re: [Mapserver-dev] New QUERYABLE true/false layer parameter?
Date: Fri, 25 Apr 2003 14:00:38 -0500
From: "Steve Lime" <steve.lime@dnr.state.mn.us>
To: <morissette@dmsolutions.ca>, <mapserver-dev@lists.gis.umn.edu>
It would be cleaner certainly, I'm not sure of how big a change that
would be
though. The query functions all reference the msIsLayerQueryable (or
whatever
it's called function) so that's where the change would have to be made
so that
template would have the same meaning. The CGI code would have to be
checked
to make sure that TEMPLATE is used as a test rather then the above
function.
Steve
>>> Daniel Morissette <morissette@dmsolutions.ca> 04/23/03 03:54PM >>>
Steve, and all,
Since we are breaking with the past in many ways with this upcoming
release, perhaps now would be a good time to fix another annoying
issue:
the lack of a QUERYABLE flag in layer and class definitions.
I understand the logic and historical reasons behind the use of
TEMPLATE
to trigger queryability in the context of the mapserv CGI, but these
days there are lots of MapScript applications that end up having to
set
TEMPLATE "ttt" in their layer definitions just to make the layers
queryable, this is really not intuitive and sounds clunky when we have
to explain to a new user why things are this way. There are also WMS
client layers that end up setting TEMPLATE "ttt" to indicate that the
layer on the remote server is queryable... we're very far from the
initial TEMPLATE idea.
What would you think of adding a QUERYABLE parameter to the LAYER and
CLASS definitions that dictates whether a layer is queryable or not?
For mapserv CGI applications, the TEMPLATE value would still be
required, if TEMPLATE is not set for a queryable class or layer then
the
mapserv CGI would return an error.
Daniel
