WFS w/ PostGIS backend: missing map extent causes queries to fail

[dougrenwick]

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.

[sdlime]

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

[pramsey]

Patched at r7624. Crappy fix pending postgis driver re-write.