Direct WFS 2.0 Test - Spatial Filter (invalid Geometry Operand)

[Dnoack49]

Dear all,

when validating this WFS
https://inspire.brandenburg.de/services/el_gmklinien_wfs?request=GetCapabilities&service=WFS
with both, the productive and the staging instance of the TEAM-Engine the following error is thrown in the spatial filter class:

The test report: Test Session Results_gmk.pdf

Apparently the test is applied to a property that has no geometry value anyway:

we assume that this is a bug of the validator?

kind regards

[dstenger]

Thank you for reporting.

POST https://inspire.brandenburg.de/services/el_gmklinien_wfs

<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs/2.0" count="10" service="WFS"
                version="2.0.0">
   <wfs:Query xmlns:ns55="http://inspire.ec.europa.eu/schemas/el-vec/4.0"
              typeNames="ns55:BreakLine">
      <fes:Filter xmlns:fes="http://www.opengis.net/fes/2.0">
         <fes:BBOX>
            <fes:ValueReference xmlns:tns="http://www.opengis.net/gml/3.2">tns:description</fes:ValueReference>
            <gml:Envelope xmlns:gml="http://www.opengis.net/gml/3.2" srsName="urn:ogc:def:crs:EPSG::25833">
               <gml:lowerCorner>237458.16 5684616.44</gml:lowerCorner>
               <gml:upperCorner>484567.86 5941605.03</gml:upperCorner>
            </gml:Envelope>
         </fes:BBOX>
      </fes:Filter>
   </wfs:Query>
</wfs:GetFeature>

is the request sent by the test suite. The response is a 500 with an HTML with non closing meta element. Thus, the error message is correct here.

However, we have to clarify why a BBOX filter is applied on fes:description. This might be a bug in the test suite.

[bpross-52n]

@Dnoack49 The test does use a property that has no geometry value on purpose to provoke an ExceptionReport with 400 or 403 HTTP status code. There was some discussion about this specific test see here, but the decision was to keep it in thet test suite.