Opened 16 years ago
Closed 16 years ago
#2420 closed defect (fixed)
WFS w/ PostGIS backend: missing map extent causes queries to fail
| Reported by: | dougrenwick | Owned by: | pramsey |
|---|---|---|---|
| Priority: | normal | Milestone: | 5.2 release |
| Component: | MapServer CGI | Version: | 5.0 |
| Severity: | normal | Keywords: | wfs, extent, postgis, filter |
| Cc: | dmorissette, assefa, hobu |
Description
Description: I have set up a WFS server using Mapserver, with PostGIS as the backend data. I have not set a EXTENT in my mapfile, nor set the wfs_extent metadata. The result is that no WFS filter will ever match any features.
Analysis: The generated PosrGIS query always includes a intersection clause with BOX3D(extent) and if no extent is specified, this is BOX3D(-1 -1, -1 -1) As such, a extent is effecively required.
Suggestion: If no extent is given, omit the BOX3D() intersection test entirely. This should save some CPU time on the server, as well as solving this bug-like behavior.
Change History (4)
comment:1 by , 16 years ago
| Cc: | added |
|---|---|
| Status: | new → assigned |
comment:2 by , 16 years ago
| Milestone: | 5.0.1 release → 5.2 release |
|---|
comment:3 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
comment:4 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Patched at r7624. Crappy fix pending postgis driver re-write.
Note:
See TracTickets
for help on using tickets.
CC'ing a few others... What do you guys think? This is probably not just limited to PostGIS or WFS so I would wager mode=itemquery CGI calls also fail in a similar fashion as do other drivers. As such, it doesn't feel like a 5.0 fix but rather 5.2.
Steve