search

opengeospatial / ets-wfs20

Executable Test Suite for WFS 2.0
Other
9 stars 11 forks source link

Unexpected @srsName value on element srsName #277

Open CeciliaPH opened 1 month ago

CeciliaPH commented 1 month ago

Describe the bug When validating our service https://www.ign.es/wfs-inspire/ngbe?request=GetCapabilities&service=WFS

We receive this error. Simple WFS (1 error). OGC TEAM Engine reported a failed test: Unexpected @srsName value on element srsName expected [http://www.opengis.net/def/crs/EPSG/0/4326] but found [urn:ogc:def:crs:EPSG:6.3:4326]

We don't understand where this error comes from. If you make the individual requests there is no way that the servers returns [urn:ogc:def:crs:EPSG:6.3:4326]. We would like to understand where this urn style string is coming from.

Thanks,

Cecilia

To Reproduce https://www.ign.es/wfs-inspire/ngbe?REQUEST=GetFeature&SERVICE=WFS&VERSION=2.0.0&COUNT=10&TYPENAMES=ns41:NamedPlace&SRSName=http://www.opengis.net/def/crs/EPSG/0/4326

https://www.ign.es/wfs-inspire/ngbe?REQUEST=GetFeature&SERVICE=WFS&VERSION=2.0.0&COUNT=10&TYPENAMES=ns41:NamedPlace&SRSName=http://www.opengis.net/def/crs/EPSG/0/25830

dstenger commented 1 month ago

Thank you for reporting. We will do further investigation.

CeciliaPH commented 1 month ago

We made further investigation and discovered that is something that happens when you retrieve data by a POST request. If you ask via REST request the data retrieved should be correct. We are using deegree 3 to serve this data. May be is an internal parameter that changes the srsName while using POST. Does the petition need to be POST to accomplish the requirement?

bpross-52n commented 1 month ago

@CeciliaPH I can confirm your findings, the incorrect EPSG code is returned from the server when requesting using POST. When the service supports POST requests, this will be tested. However, POST is not mandatory for WFS 2.0 services, see Chapter 6.4 of the WFS 2.0 standard.

CeciliaPH commented 1 month ago

Hi Benjamin,

We are really interested in complete the tests successfully. If the test is successful in GET, we understand that validator should not raise an error. We wonder which should be the next steps, as this issue is in Waiting in CITE.

Best regards,

dstenger commented 1 month ago

Hi @CeciliaPH, The unexpected srsName is produced by your service when requested via POST. Thus, the error seems to be on the service side. Can you please check that? The request sent by TEAM Engine should be correct. @bpross-52n Can you please share the exact request which is leading to the response with the unexpected srsName?

CeciliaPH commented 1 month ago

Exactly, the srsName is produced by deegree 3. There is something intern that changes de srsName style, to the one with urn. Any way, using GET it works properly, but engine uses POST.

This is the kind of post request that raises the error. (any petition would, as the software changes de srsName style) https://www.ign.es/wfs-inspire/ngbe?