Ticket #2420 (closed defect: fixed)
WFS w/ PostGIS backend: missing map extent causes queries to fail
|Reported by:||dougrenwick||Owned by:||pramsey|
|Severity:||normal||Keywords:||wfs, extent, postgis, filter|
|Cc:||dmorissette, assefa, hobu|
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.