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
In the log, you can see, that the axis order of BBOX parameter in the WFS GetFeature request does NOT have correct axis order, and so, no data are returned:
Author: mko Date: 2011/12/16 - 08:51
Due to the fact that not all eosg codes between 4000 and 5000 have inverted axes, we should use msIsAxisInverted() instead. It does check against a static list of epsg codes included in mapaxisorder.h and generated from the epsg database.
Reporter: jachym
Date: 2011/12/08 - 23:01
I need to render WFS 1.1.0 layer and I'm testing it with shp2img with following syntax:
In the log, you can see, that the axis order of BBOX parameter in the WFS GetFeature request does NOT have correct axis order, and so, no data are returned:
http://briseide01.ingr.briseide.eu:8080/geoserver/ows?&REQUEST=GetFeature&VERSION=1.1.0&SERVICE=WFS&TYPENAME=ccss:Flood2010_transport_roads&BBOX=14.9948950985,50.8089676554,15.2607258548,51.0747984117
when swaped the coordinates manually, data are returned correctly
http://briseide01.ingr.briseide.eu:8080/geoserver/ows?&REQUEST=GetFeature&VERSION=1.1.0&SERVICE=WFS&TYPENAME=ccss:Flood2010_transport_roads&BBOX=50.8089676554,14.9948950985,51.0747984117,15.2607258548
Mapfile attached
The text was updated successfully, but these errors were encountered: