Opened 8 years ago
Closed 8 years ago
#2739 closed defect (wontfix)
QUERYMAPFEATURES does not respect REQUESTDATA when using FEATUREFILTER instead of GEOMETRY
| Reported by: | jng | Owned by: | jng |
|---|---|---|---|
| Priority: | high | Milestone: | 3.0 |
| Component: | Rendering Service | Version: | 2.5.0 |
| Severity: | critical | Keywords: | |
| Cc: | External ID: |
Description
The QUERYMAPFEATURES operation does not respect REQUESTDATA when FEATUREFILTER (ie. selection XML) is passed instead of GEOMETRY. It will always return the updated selection XML
Change History (3)
comment:1 by , 8 years ago
| Priority: | low → high |
|---|---|
| Severity: | trivial → critical |
| Version: | → 2.5.0 |
comment:2 by , 8 years ago
| Version: | 2.5.0 |
|---|
comment:3 by , 8 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
| Version: | → 2.5.0 |
Note:
See TracTickets
for help on using tickets.
It doesn't respect the geometry because when LAYERATTRIBUTEFILTER is not passed in, it defaults to 3 (include selectable and visible layers). If passing selection XML, it may contain selected features that cause the omission to happen (and the false appearance of REQUESTDATA not being respected).
To prevent this, client applications should include a LAYERATTRIBUTEFILTER of 0, which will disable all layer candidate filtering, and allow the REQUESTDATA to be respected.