A BBOX-Filter axis order problem in WFS 1.1.0

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

A BBOX-Filter axis order problem in WFS 1.1.0

Christian Seewald
Hello,

I am using GeoServer version 2.0.1. I am having a problem in WFS 1.1.0 with axis ordering in a BBOX filter (also tried 2.1 RC 3, same problem).

A WFS 1.1.0 capable map client issues an http-POST GetFeature request, including a spatial constraint:

<wfs:GetFeature service="WFS" version="1.1.0"
	outputFormat="text/xml; subtype=gml/3.1.1" xmlns:wfs="http://www.opengis.net/wfs">
	<wfs:Query typeName="gk:waterlevels" xmlns:gk="http://gkinfo.wsv.de">
		<ogc:Filter xmlns:ogc="http://www.opengis.net/ogc">
			<ogc:BBOX>
				<ogc:PropertyName>the_geom</ogc:PropertyName>
				<gml:Envelope srsName="EPSG:4326" xmlns:gml="http://www.opengis.net/gml">
					<gml:lowerCorner>49.97894409826496 4.19131460613648</gml:lowerCorner>
					<gml:upperCorner>53.33055446943188 15.843890646710745</gml:upperCorner>
				</gml:Envelope>
			</ogc:BBOX>
		</ogc:Filter>
	</wfs:Query>
</wfs:GetFeature>

These coordinates are central european, the ordering is northing/easting. The response contains no features at all. If I reverse those coordinates within each corner, all features are delivered.

<ogc:BBOX>
  <ogc:PropertyName>the_geom</ogc:PropertyName>
  <gml:Envelope srsName="EPSG:4326" xmlns:gml="http://www.opengis.net/gml">
    <gml:lowerCorner>4.19131460613648 49.97894409826496</gml:lowerCorner>
    <gml:upperCorner>15.843890646710745 53.33055446943188</gml:upperCorner>
  </gml:Envelope>
</ogc:BBOX>

I presume the error lies with GeoServer, since all positions within a GetFeature response are encoded with Northing/Easting in WFS 1.1.0 for EPSG 4326, so I believe the BBOX in a request should be the same.

If this problem cannot be remedied, is there an easy way to disable WFS 1.1.0 in GeoServer? This means a version=1.1.0 request must be illegal and the default Capabilites document must be in 1.0.0 format.

I played arround with a few config files including a spring application context file, but I did not manage to disable it.

Any help is really appreciated!!