Support #3816

RO: While testing compliant WFS, linkage checker is reporting "Unable to obtain a Spatial Object reported" even if the requests sent to the server are correctly resolved

Added by Maxim Iurie 6 months ago. Updated 6 months ago.

Status:NewStart date:30 Jan 2020
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Linkage Checker
Target version:-
Submitting Organisation:Essensys Software Knowledge-Base relevant?:Yes
Proactive:Yes Keyword #1:
Country:RO - Romania Keyword #2:
Originating UI: Keyword #3:

Description

We assume that there is an issue with the testing of WFS services.

We seek guidance if the issue is not in the linckage checker validator or a confirmation that there is an issue in the linckage checker validator

How to test:

Link to data set metdata: https://inspire.meteoromania.ro/WIGOS/MD-DS

Link to view service metdata: https://inspire.meteoromania.ro/WIGOS/MD-WMS

Link to download service metdata: https://inspire.meteoromania.ro/WIGOS/MD-WFS

 

The result of the test can be found here:

https://inspire-geoportal.ec.europa.eu/resources/sandbox/INSPIRE-71fd794a-436b-11ea-8318-0050563f01ec_20200130-151854/

Metadata files for the Data set, view and download service are reported 100% compliant.

Interoperability is reported 100% compliant for the dataset and for the view service.

Interoperability is reported 50% compliant for the download service (WFS) as can be seen here:

https://inspire-geoportal.ec.europa.eu/resources/sandbox/INSPIRE-71fd794a-436b-11ea-8318-0050563f01ec_20200130-151854/download/services/1/resourceLocator1/download/services/1/resourceReport/

 

The linkage checker validator is reporting Unable to obtain a Spatial Object 20 times.

We looked in the log files and the requests that are sent from the linkage cheker (IP: 139.191.1.236) between 2020-01-30T14:19:00.619Z - 2020-01-30T14:19:30.21Z where the following:

service=WFS&version=2.0.0&request=GetCapabilities
request=GetCapabilities&service=WFS&AcceptVersions=2.0.0
typenames=ef:EnvironmentalMonitoringNetwork&REQUEST=DescribeFeatureType&VERSION=2.0.0&SERVICE=WFS&namespaces=xmlns(ef,http://inspire.ec.europa.eu/schemas/ef/4.0)
typenames=ef:EnvironmentalMonitoringFacility&REQUEST=DescribeFeatureType&VERSION=2.0.0&SERVICE=WFS&namespaces=xmlns(ef,http://inspire.ec.europa.eu/schemas/ef/4.0)
typenames=ef:EnvironmentalMonitoringNetwork&REQUEST=DescribeFeatureType&VERSION=2.0.0&SERVICE=WFS&namespaces=xmlns(ef,http://inspire.ec.europa.eu/schemas/ef/4.0)
typenames=ef:EnvironmentalMonitoringFacility&REQUEST=DescribeFeatureType&VERSION=2.0.0&SERVICE=WFS&namespaces=xmlns(ef,http://inspire.ec.europa.eu/schemas/ef/4.0)
REQUEST=ListStoredQueries&VERSION=2.0.0&SERVICE=WFS
REQUEST=DescribeStoredQueries&VERSION=2.0.0&SERVICE=WFS&STOREDQUERY_ID=http://inspire.ec.europa.eu/operation/download/GetSpatialDataSet
request=GetFeature&Language=eng&CRS=http://www.opengis.net/def/crs/EPSG/0/3035&DataSetIdNamespace=https://inspire.meteoromania.ro/&service=WFS&count=10&STOREDQUERY_ID=http://inspire.ec.europa.eu/operation/download/GetSpatialDataSet&version=2.0.0&DataSetIdCode=WIGOS/MD-DS
request=GetFeature&Language=eng&DataSetIdNamespace=https://inspire.meteoromania.ro/&service=WFS&count=10&STOREDQUERY_ID=http://inspire.ec.europa.eu/operation/download/GetSpatialDataSet&version=2.0.0&DataSetIdCode=WIGOS/MD-DS
request=GetFeature&Language=eng&CRS=urn:ogc:def:crs:EPSG::4326&DataSetIdNamespace=https://inspire.meteoromania.ro/&service=WFS&count=10&STOREDQUERY_ID=http://inspire.ec.europa.eu/operation/download/GetSpatialDataSet&version=2.0.0&DataSetIdCode=WIGOS/MD-DS
typenames=ef:EnvironmentalMonitoringFacility&request=GetFeature&service=WFS&count=10&version=2.0.0&namespaces=xmlns(ef,)
typenames=ef:EnvironmentalMonitoringNetwork&request=GetFeature&service=WFS&count=10&version=2.0.0&namespaces=xmlns(ef,)

All of them were returned from IP 10.255.10.101 with ResponseStatus 200 and Failed is FALSE. So all requests returned the expected results in the expected MIME Type.

GetCapabilities, ListStoredQuerries and DescribeStroedQuerries requests were returned with MIME type "application/xml" as XML files (.xml).

DescribeFeatureType and GetFeature requests were returned with MIME type "application/gml+xml; version=3.2" as XML files (.xml). According to IANA for this MIME Type the files can be provided as .gml or as .xml for usage in Windows environment, both beeing correct.

 

Manually it can be tested that all the above requests are returning correct results. For example:

https://inspire.meteoromania.ro/WIGOS/WFS?request=GetFeature&Language=eng&CRS=http://www.opengis.net/def/crs/EPSG/0/3035&DataSetIdNamespace=https://inspire.meteoromania.ro/&service=WFS&count=10&STOREDQUERY_ID=http://inspire.ec.europa.eu/operation/download/GetSpatialDataSet&version=2.0.0&DataSetIdCode=WIGOS/MD-DS

 

Same error Unable to obtain a Spatial Object is reported for all valid WFS services that we tested. For example the same behavior can be observed for the datasets from Malta.

Links to test:

Link to data set metdata: https://msdi.data.gov.mt/geonetwork/srv/eng/csw?service=CSW&request=GetRecordById&version=2.0.2&outputSchema=http://www.isotc211.org/2005/gmd&elementSetName=full&id=4cc79d52-f58e-4a95-ba42-a8e8426b22d2

Link to view service metdata: https://msdi.data.gov.mt/geonetwork/srv/eng/csw?service=CSW&request=GetRecordById&version=2.0.2&outputSchema=http://www.isotc211.org/2005/gmd&elementSetName=full&id=37569840-7c18-49da-bac5-f730491591e4

Link to download service metdata: https://msdi.data.gov.mt/geonetwork/srv/eng/csw?service=CSW&request=GetRecordById&version=2.0.2&outputSchema=http://www.isotc211.org/2005/gmd&elementSetName=full&id=4394b124-6cd1-46d4-bd86-53ecd15a82f5

Results of this test can be seen here: https://inspire-geoportal.ec.europa.eu/resources/sandbox/INSPIRE-bd6944f6-41da-11ea-8318-0050563f01ec_20200128-153032/

 

We were not able to identify in the INSPIRE Geoportal a single WFS service for which the Limkage cheker validator would not report Unable to obtain a Spatial Object even if we tested quite many. It should be noted that at least ProxyBrowser, even if it is not an official tool, is reporting the WFS services from Malta with "no issues" as can be seen if "no issues" would be selected while accessing this link:

https://inspire-geoportal.ec.europa.eu/proxybrowser/#fq=degreeOfConformity%3Aconformant&fq=implementationSpecification%3A%22iso%2019142%2Fwfs%202.0%22&fq=-resourceReportResourceLocator%3A%5B*%20TO%20*%5D&q=*%3A*

 

Hope this will help to find the issue in the Linkage Checker in relation to datasets served trough WFS 2.0. If the source code of the Linkage checker is available, please share it as we can also look to spot the error.

If there is a real problem with the datasets served trough WFS that are triggering corectly the error Unable to obtain a Spatial Object than please let us know.

 

Best regards,

Iurie Maxim

 

History

#1 Updated by Maxim Iurie 6 months ago

The above links were changed:

 

Instead of:

 

Link to data set metdata according to version 2.0 of the TG: https://inspire.meteoromania.ro/WIGOS/MD-DS

Link to view service metdata according to version 2.0 of the TGhttps://inspire.meteoromania.ro/WIGOS/MD-WMS

Link to download service metdata according to version 2.0 of the TGhttps://inspire.meteoromania.ro/WIGOS/MD-WFS

 

should be used now:

 

Link to data set metdata according to version 1.3 of the TG: https://geoportal.meteoromania.ro/WIGOS/MD-DS

Link to view service metdata according to version 1.3 of the TG: https://geoportal.meteoromania.ro/WIGOS/MD-WMS

Link to download service metdata according to version 1.3 of the TG: https://geoportal.meteoromania.ro/WIGOS/MD-WFS

 

Also available in: Atom PDF