Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiple query layers #45

Closed
mapserver-bot opened this issue Apr 3, 2012 · 3 comments
Closed

multiple query layers #45

mapserver-bot opened this issue Apr 3, 2012 · 3 comments

Comments

@mapserver-bot
Copy link

Reporter: rich@greenwoodmap.com
Date: 2001/09/18 - 01:25
Trac URL: http://trac.osgeo.org/mapserver/ticket/45

This is a feature suggestion. It would be nice to allow more than one query 
layer. This functionality would be akin to MapInfo and ArcView in that a layer 
can be in various states: on/off, selectable/not-selectable, etc. As it stands 
now, mapserver accepts a single qlayer, or else all layers with a template 
within their class are queried if not qlayer is specified. I am suggesting sort 
of a middle ground.

This feature could be added in conjunction with GROUP, or maybe with a 
new �qlayers� similar to the existing layer and layers.

Thanks,
Rich
@mapserver-bot
Copy link
Author

Author: dmorissette
Date: 2003/07/01 - 04:20

Steve, should we mark this as a post 4.0 enhancement or is this already done?

@mapserver-bot
Copy link
Author

Author: sdlime
Date: 2003/07/01 - 07:05

Post 4.0. It's not done, not too hard but not trivial either. That said there is
a work around. The easiest way would be to store layers that could be queried in
a second mapfile and then reference that mapfile when querying and just use the
normal layer parameter. I'll change to 4.1 and assign it to myself...

@mapserver-bot
Copy link
Author

Author: pramsey
Date: 2008/04/09 - 19:12
sdlime describes a workaround which is acceptable

@ghost ghost assigned sdlime Apr 5, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants