[Geoserver-users] Changed Axis Ordering with WFS 1.1.0 Filtering using URN-Projections and SRS styles documentation

Bernhard_Kiselka · January 16, 2014, 9:20am

Hi List!

I upgraded from GeoServer 2.1.3 to 2.4.2 and experienced the following problems:

1) Changed Axis Ordering with WFS 1.1.0 Filtering using URN-Projections

Worked and works only in GeoServer 2.1.3: Provide coordinates as latitude/longitude (y/x)
Example:
http://localhost:8080/geoserver/ows?service=wfs&version=1.1.0&request=getfeature&typeName=EDGE&filter=<Filter xmlns:ogc="http://www.opengis.net/ogc" xmlns:gml="http://www.opengis.net/gml"><BBOX><PropertyName>SHAPE</PropertyName><gml:Envelope srsName="urn:x-ogc:def:crs:EPSG:31258"><gml:lowerCorner>167426 524877</gml:lowerCorner><gml:upperCorner>167573 525122</gml:upperCorner></gml:Envelope></BBOX></Filter>

Works only GeoServer 2.4.2: Provide coordinates as longitude/latitude (x/y)
Example:
http://localhost:8080/geoserver/ows?service=wfs&version=1.1.0&request=getfeature&typeName=EDGE&filter=<Filter xmlns:ogc="http://www.opengis.net/ogc" xmlns:gml="http://www.opengis.net/gml"><BBOX><PropertyName>SHAPE</PropertyName><gml:Envelope srsName="urn:x-ogc:def:crs:EPSG:31258"><gml:lowerCorner>524877 167426</gml:lowerCorner><gml:upperCorner>525122 167573</gml:upperCorner></gml:Envelope></BBOX></Filter>

The GeoServer 2.1.3 behaviour is documented here
http://docs.geoserver.org/stable/en/user/services/wfs/basics.html#axis-ordering
but GeoServer 2.4.2 shows a wrong behaviour.
Shall I file a JIRA-Ticket?

My solution (I would say a work-around):
Works with both GeoServer versions: Provide coordinates as longitude/latitude (x/y), but use srsName EPSG:31258 instead of urn:x-ogc:def:crs:EPSG:31258
http://localhost:8080/geoserver/ows?service=wfs&version=1.1.0&request=getfeature&typeName=EDGE&filter=<Filter xmlns:ogc="http://www.opengis.net/ogc" xmlns:gml="http://www.opengis.net/gml"><BBOX><PropertyName>SHAPE</PropertyName><gml:Envelope srsName="EPSG:31258"><gml:lowerCorner>524877 167426</gml:lowerCorner><gml:upperCorner>525122 167573</gml:upperCorner></gml:Envelope></BBOX></Filter>

2) SRS styles not documented (may be linked to 1)
The documentation
http://docs.geoserver.org/stable/en/user/webadmin/services/WFS.html
does not match GeoServer 2.4.2:
Documented is (and has been in GeoServer 2.1.3): Normal, XML, URN
The list of SRS styles is now in GeoServer 2.4.2: EPSG Code, OGC HTTP URL, OGC Experimental URN, OGC URN, OGC HTTP URI
What's the matching?
(Shall I file a JIRA-Ticket?)

Cheers,
Bernhard

Andrea_Aime4 · January 16, 2014, 9:52am

On Thu, Jan 16, 2014 at 10:20 AM, Bernhard Kiselka <
bernhard.kiselka@anonymised.com> wrote:

Hi List!

I upgraded from GeoServer 2.1.3 to 2.4.2 and experienced the following
problems:

1) Changed Axis Ordering with WFS 1.1.0 Filtering using URN-Projections

Worked and works only in GeoServer 2.1.3: Provide coordinates as
latitude/longitude (y/x)
Example:

http://localhost:8080/geoserver/ows?service=wfs&version=1.1.0&request=getfeature&typeName=EDGE&filter=<Filter
xmlns:ogc="http://www.opengis.net/ogc" xmlns:gml="
http://www.opengis.net/gml"><BBOX><PropertyName>SHAPE</PropertyName><gml:Envelope
srsName="urn:x-ogc:def:crs:EPSG:31258"><gml:lowerCorner>167426
524877</gml:lowerCorner><gml:upperCorner>167573
525122</gml:upperCorner></gml:Envelope></BBOX></Filter>

Works only GeoServer 2.4.2: Provide coordinates as longitude/latitude (x/y)
Example:

http://localhost:8080/geoserver/ows?service=wfs&version=1.1.0&request=getfeature&typeName=EDGE&filter=<Filter
xmlns:ogc="http://www.opengis.net/ogc" xmlns:gml="
http://www.opengis.net/gml"><BBOX><PropertyName>SHAPE</PropertyName><gml:Envelope
srsName="urn:x-ogc:def:crs:EPSG:31258"><gml:lowerCorner>524877
167426</gml:lowerCorner><gml:upperCorner>525122
167573</gml:upperCorner></gml:Envelope></BBOX></Filter>

According to http://www.epsg-registry.org/ 32258 is a strange beast, it's a
projected coordinate system whose axis
order is north/east.
So it seems that GeoServer 2.1.3 had it right, and GeoServer 2.4.2 is not
working as it is supposed to.
Wondering, we have now a old EPSG database, the error might be in there, or
in the code that is handling the axis order.
Yes, please file a report

The GeoServer 2.1.3 behaviour is documented here

http://docs.geoserver.org/stable/en/user/services/wfs/basics.html#axis-ordering
but GeoServer 2.4.2 shows a wrong behaviour.
Shall I file a JIRA-Ticket?

My solution (I would say a work-around):
Works with both GeoServer versions: Provide coordinates as
longitude/latitude (x/y), but use srsName EPSG:31258 instead of
urn:x-ogc:def:crs:EPSG:31258

http://localhost:8080/geoserver/ows?service=wfs&version=1.1.0&request=getfeature&typeName=EDGE&filter=<Filter
xmlns:ogc="http://www.opengis.net/ogc" xmlns:gml="
http://www.opengis.net/gml"><BBOX><PropertyName>SHAPE</PropertyName><gml:Envelope
srsName="EPSG:31258"><gml:lowerCorner>524877
167426</gml:lowerCorner><gml:upperCorner>525122
167573</gml:upperCorner></gml:Envelope></BBOX></Filter>

2) SRS styles not documented (may be linked to 1)
The documentation
http://docs.geoserver.org/stable/en/user/webadmin/services/WFS.html
does not match GeoServer 2.4.2:
Documented is (and has been in GeoServer 2.1.3): Normal, XML, URN
The list of SRS styles is now in GeoServer 2.4.2: EPSG Code, OGC HTTP URL,
OGC Experimental URN, OGC URN, OGC HTTP URI
What's the matching?
(Shall I file a JIRA-Ticket?)

Please do

Cheers
Andrea

--
== Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information ==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------