[mapserver-dev] again: wfs 1.1.0 and axis order, ticket with patch

Jachym Cepicky jachym.cepicky at gmail.com
Wed Mar 7 08:14:42 EST 2012


after some discussion with some of you, I've created patch for the "WFS
1.1.0 axis order issue"


Doing some investigation, I have come to this conclusion:

* WFS client should respect axis order or used SRS for the BBOX
parameter (MapServer does not)

* WFS client should be aware of, in which SRS the data will come, and
assume in some cases, the data do have "inverted" axis order (currently,
it is assumed, that returned data have *always* x,y order)

* WFS  server should use default SRS for the BBOX parameter, if NONE was
specified in the request

I hope, everything is explained in the ticket. The patch is not big, it
affects 1 file more (mapwfslayer.c) and 3 others only on single lines or

I would like to ask someone for review and in the case, it's fine,
please add this to mapserver-trunk, so mapserver 6.2 can have propper
WFS 1.1.0 client implementation (the server issues is not that big).



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
Url : http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20120307/26a5c8cd/signature.bin

More information about the mapserver-dev mailing list