European Commission logo
INSPIRE Community Forum

Separate WFS endpoint for each dataset in TN - one dataset per GetCapabilities response - how to do it?

  • General

    The INSPIRE Community Forum is now part of the INSPIRE helpdesk system, based on GitHub (https://github.com/INSPIRE-MIF), so please start there any new discussions.

    The current platform will remain available in read only mode in its current form and URL address until 31/01/2021, then its content will be archived and then published in a different URL which will be announced when it becomes available.

Dear TN implementers,

I would like to ask for a help in providing INSPIRE direct download service for TN data using OGC WFS. In Slovakia we currently have the following "single" endpoint:

https://zbgisws.skgeodesy.sk/inspire_transport_networks_wfs/service.svc/get?service=WFS&request=GetCapabilities

which operatesOn 20 featureTypes as tn-a:AerodromeArea, tn-c:CablewayLink, tn_ra:RailwayArea, tn-ro:RoadArea, etc. each linking to a single INSPIRE dataset metadata record.

The question is whether this is not against the requirement 52 of having one dataset per GetCapabilities response.

If yes, how should data provider do it correctly, provide a separate endpoint for each featureType, separate endpoint for each application schema (tn-ro, tn-ra, tn-a).

Thank you in advance for sharing your experiences in implementing direct download service based on WFS for TN data.

And also, is there any definition of a INSPIRE dataset and its relation to WFS featureType. Could not find definition of INSPIRE dataset anywhere (incl. INSPIRE registry - glossary, TG for download service, etc...)

Tomas