MapServer as WFS 1.1.0 does NOT support correct axis order

[jachym]

I need to render WFS 1.1.0 layer and I'm testing it with shp2img with following syntax:

shp2img -m mapfile.map -e 14.9948950985 50.8659873396 15.2607258548 51.0177787275 -l "ccss:Flood2010_transport_roads" -all_debug 5

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

[jachym]

According to http://mapserver.org/ogc/#axis-orientation-in-wfs-1-1, it should work.

[mko]

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.

[jachym]

Yesterday, I had a look into the code, and I think, there mapserver does not check, if WFS 1.1 axis order should be used or not.

See ​http://lists.osgeo.org/pipermail/mapserver-dev/2011-December/011785.html

[jachym]

Anyone? I think, this is important feature, that MapServer - WFS-Client behaviour is consistant to the server implementation.

[jachym]

Patch, wich seems to solve the problem

[jachym]

The problem is solved in #4228 in a more complex way.