Opened 4 years ago

Closed 4 years ago

#157 closed defect (wontfix)

SetSpatialFilter() does not seem to be called when using the OGR-driver for WFS Client 2.0

Reported by: LarsOttosson Owned by: Jeff McKenna
Priority: minor Milestone: 3.2.6 release
Component: MS4W - Base Version: 3.2.5
Keywords: Cc:
Blocked By: Blocking:

Description

I built a WFS server site on some Oracle data and another WMS site using the WFS layers in the first site (version=2.0.0) using the OGR WFS driver. It works but was slow as dough and when I checked the serverlogs I can see that the BBOX constraint given in the WMS call were not used in the calls to the underlying Oracle database (EXTENT from the mapfile is used).

It seems like SetSpatialFilter() (se http://www.gdal.org/drv_wfs.html) is not called in this case.

I can use external WFS 2.0 sources fine and I can call the WFS server from QGIS the expected spatial filter is used.

Change History (2)

comment:1 by Jeff McKenna, 4 years ago

This doesn't sound like an issue specific to MS4W. Can you test this outside of MS4W?

The only thing I can add here is that Oracle layers require that the EXTENT parameter is set at the LAYER level in the mapfile, when using OGC services. If you did that already, maybe you can ask about this on either the GDAL-dev mailing list since you are using the OGR WFS driver (subscribe at https://lists.osgeo.org/mailman/listinfo/gdal-dev/), or on the MapServer-users list (https://lists.osgeo.org/listinfo/mapserver-users).

comment:2 by Jeff McKenna, 4 years ago

Resolution: wontfix
Status: newclosed

No feedback. Closing.

(new release: MS4W 3.2.6 release https://ms4w.com/download.html

Note: See TracTickets for help on using tickets.