You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reporter: jratike80 Date: 2012/01/25 - 09:55 Trac URL:http://trac.osgeo.org/mapserver/ticket/4166
WFS GetFeature request with OGC BBOX filter fails if shapefile is accessed through the native Mapserver native method. With OGR access the recuest is successful.
This can be tested with the attached shapefile and mapfile by toggling the access type by commenting/uncommenting the following lines.
#CONNECTIONTYPE OGR
#CONNECTION "d:\ms4w\data\bbox_test.shp"
DATA "d:\ms4w\data\bbox_test.shp"
The POST request that shows the difference for me is this
BBOX and POST does work with Mapserver 7.0 with both native shp connection and with OGR shapefile driver. The mapfile that is included in the bbox_test.zip needs some editing for making it to work with MS 7.0, for example the EXTENT must now cover the data. When I wrote the ticket for MS 5.x or 6.x wrong extent had no effect. This extent is good:
EXTENT 279470.988034 6695663.439659 280666.936409 6696825.670338
Reporter: jratike80
Date: 2012/01/25 - 09:55
Trac URL: http://trac.osgeo.org/mapserver/ticket/4166
WFS GetFeature request with OGC BBOX filter fails if shapefile is accessed through the native Mapserver native method. With OGR access the recuest is successful.
This can be tested with the attached shapefile and mapfile by toggling the access type by commenting/uncommenting the following lines.
The POST request that shows the difference for me is this
The practical consequence is that Geoserver cannot cascade this WFS layer if it is configured to use the native shapefile access.
The text was updated successfully, but these errors were encountered: