Opened 23 years ago
Closed 16 years ago
#45 closed enhancement (wontfix)
multiple query layers
Reported by: | Owned by: | sdlime | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | MapServer CGI | Version: | 4.1 |
Severity: | minor | Keywords: | |
Cc: |
Description
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
Change History (3)
comment:2 by , 21 years ago
Status: | new → assigned |
---|---|
Version: | 4.0 → 4.1 |
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...
comment:3 by , 16 years ago
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
sdlime describes a workaround which is acceptable
Note:
See TracTickets
for help on using tickets.