Predefined WFS ETS fails on AutoConfigure WFS-GetNumber of Feautures in DB #904
-
|
Dears, While testing this WFS By checking the request sent by ETF <ows:AllowedValues>
<ows:Value>GML32</ows:Value>
<ows:Value>GML32+ZIP</ows:Value>
<ows:Value>application/gml+xml; version=3.2</ows:Value>
<ows:Value>GML3</ows:Value>
<ows:Value>GML3+ZIP</ows:Value>
<ows:Value>text/xml; subtype=gml/3.1.1</ows:Value>
<ows:Value>GML2</ows:Value>
<ows:Value>GML2+ZIP</ows:Value>
<ows:Value>text/xml; subtype=gml/2.1.2</ows:Value>
<ows:Value>GEOJSON</ows:Value>
<ows:Value>GEOJSON+ZIP</ows:Value>
<ows:Value>ESRIGEOJSON</ows:Value>
<ows:Value>ESRIGEOJSON+ZIP</ows:Value>
<ows:Value>KML</ows:Value>
<ows:Value>application/vnd.google-earth.kml xml</ows:Value>
<ows:Value>application/vnd.google-earth.kml+xml</ows:Value>
<ows:Value>KMZ</ows:Value>
<ows:Value>application/vnd.google-earth.kmz</ows:Value>
<ows:Value>SHAPE+ZIP</ows:Value>
<ows:Value>CSV</ows:Value>
<ows:Value>CSV+ZIP</ows:Value>
</ows:AllowedValues>and the one ETF used is not advertised. If you instead use https://arc.sazp.sk/arcgis/services/tazobny_odpad/ulozisko__pd3801/MapServer/WFSServer?OUTPUTFORMAT=GML32&REQUEST=GetFeature&RESULTTYPE=hits&SERVICE=WFS&TYPENAMES=PD3801_Extractive_waste:ULOZISKO_VSETKY&VERSION=2.0.0<wfs:FeatureCollection xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:wfs="http://www.opengis.net/wfs/2.0" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:PD3801_Extractive_waste="https://arc.sazp.sk/arcgis/services/tazobny_odpad/ulozisko__pd3801/MapServer/WFSServer" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" timeStamp="2020-02-27T21:07:31Z" numberMatched="455" numberReturned="0" xsi:schemaLocation="http://www.opengis.net/wfs/2.0 http://schemas.opengis.net/wfs/2.0/wfs.xsd http://www.opengis.net/gml/3.2 http://schemas.opengis.net/gml/3.2.1/gml.xsd https://arc.sazp.sk/arcgis/services/tazobny_odpad/ulozisko__pd3801/MapServer/WFSServer https://arc.sazp.sk/arcgis/services/tazobny_odpad/ulozisko__pd3801/MapServer/WFSServer?service=wfs%26version=2.0.0%26request=DescribeFeatureType"> </wfs:FeatureCollection>Could you please clarify why this ETS assertion uses OUTPUTFORMAT parameter value which is not advertised in the Capabilities of the service? The URL to ETF report is here: http://inspire.ec.europa.eu/validator/v2/TestRuns/EIDc230f334-6be6-4d09-b49f-afbbc249d8ef.html#EID8867f704-0170-1000-3737-56b08aaa553cThank you, ` |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
|
Hello Tomas, Indeed it seems that the request made by the ETF validator is not correct. It should require the features with the following MIME type: "aplication/gml+xml; version=3.2" according to Technical Guidelines that requiers features to be provided in GML 3.2 and according to IANA (https://www.iana.org/assignments/media-types/application/gml+xml). And "aplication/gml+xml; version=3.2" is present in the GetCapabilities response. In any case "text/xml; subtype=gml/3.2" should not be correct for GetFeatures request. Neither "application/gml+xml; subtype=3.2" should not be correct if consulting IANA at https://www.iana.org/assignments/media-types/application/gml+xml. But I think you should look in more details to the GetCapabilities response as there are some more issues and I think that the error you get is from another reason. The error you mention indicates that the validator is not able to get the number of available feature types (not the number of features of each feature type). And most probably this is due to the GetCapabilities document that is not complete or incorrect. According to the WFS standard 2.0.0/2.0.2 the MIME type for GetCapabilities request shall include the value ”text/xml” and may include other MIME types as well. The WFS 2.0.2 standard can be consulted here: http://docs.opengeospatial.org/is/09-025r2/09-025r2.html Below an extract on the topic:
Unfortunately the service tested does not include ”text/xml”. It should look like this:
And your service looks like this and is missing AcceptFormats and Sections parameters for GetCapabilities request:
You may find an example of a WFS that is passing the ETF tests: https://inspire.meteoromania.ro/WIGOS/WFS?service=WFS&request=GetCapabilities The issues that are reported by the validator for the above service are fake and they were already communicated and are treated by the development team. You may look at it and compare to your implementation. Regarding FeatureTypes, your GetCapabilities document looks like this:
while an example that is passing the test looks like this:
"PD3801_Extractive_waste:" is not a correct prefix for an INSPIRE data theme. INSPIRE prefixes and schemas are found here: https://inspire.ec.europa.eu/schemas/ Most probably the error message provided by the validator should be different and the OUTPUTFORMAT parameter of the GetFeatures request should be changed into "aplication/gml+xml; version=3.2". Hope it helps, |
Beta Was this translation helpful? Give feedback.
-
|
Most probably your data is falling under Production and Industrial Facilities Data Theme. Technical Guideline is here: INSPIRE schema is here: Prefix would be then "pf". Seems like your GetCapabilities document is listing Features instead of listing FeatureTypes. You will have only one feature type and that would be "pf:ProductionAndIndustrialFacilities" |
Beta Was this translation helpful? Give feedback.
-
|
@carlospzurita are there any updates related to the issue that the validator is not requesting the features with "aplication/gml+xml; version=3.2" MIME type, according to Technical Guidelines that requires features to be provided in GML 3.2 and according to IANA (https://www.iana.org/assignments/media-types/application/gml+xml)? |
Beta Was this translation helpful? Give feedback.
-
|
@klimeto The media types encircled in red are not listed in IANA
For geojson media type, the correct syntax is found here https://www.iana.org/assignments/media-types/application/geo+json Entire list of accepted media types are found here: https://www.iana.org/assignments/media-types/media-types.xhtml None of those encircled in red are listed in IANA. While testing against predefined WFS it shows this error
The error is due to this declaration, while it should be application/gml+xml; version=3.2
as it is declared here Once this error will be fixed the WFS will be able to provide the features and the mentioned error will disappear as well: Just paste the link indicated in the error message in any browser (https://arc.sazp.sk/arcgis/services/tazobny_odpad/ulozisko__pd3801/MapServer/WFSServer?#PROJECT#ENDPT.GETFEATURE.GET=%23Project%23endpt.GetFeature.Get&NAMESPACES=xmlns%28PD3801_Extractive_waste%2Chttps%3A%2F%2Farc.sazp.sk%2Farcgis%2Fservices%2Ftazobny_odpad%2Fulozisko__pd3801%2FMapServer%2FWFSServer%29&OUTPUTFORMAT=text%2Fxml%3B+subtype%3Dgml%2F3.2&REQUEST=GetFeature&RESULTTYPE=hits&SERVICE=WFS&TYPENAMES=PD3801_Extractive_waste%3AULOZISKO_VSETKY&VERSION=2.0.0) and will show
The request is made based on this declaration not based on this declaration This is quite similar to https://github.com/inspire-eu-validation/community/issues/29 @carlospzurita This can be marked as discussion. The validator provides all the necessary information for the user to fix the issue. |
Beta Was this translation helpful? Give feedback.
-
|
Dear @klimeto, do you still have this kind of issue? Have you tried to follow the instructions provided by iuriemaxim to solve the problem? |
Beta Was this translation helpful? Give feedback.
-
|
Did ESRI fixed this issue? Probably relevant for the subject: |
Beta Was this translation helpful? Give feedback.
@klimeto The media types encircled in red are not listed in IANA
For geojson media type, the correct syntax is found here https://www.iana.org/assignments/media-types/application/geo+json
Entire list of accepted media types are found here: https://www.iana.org/assignments/media-types/media-types.xhtml
None of those encircled in red are listed in IANA.
While testing against predefined WFS it shows this error
The error is due to this declaration, while it should be application/gml+xml; version=3.2
as it is declared here
Once this error will be fixed the WFS will be able to provide the features and the mentioned error will disappear as well:
Just paste the link indicated in the error me…