SE: Failing download services
|Status:||Closed||Start date:||05 Dec 2019|
|Submitting Organisation:||Lantmäteriet||Knowledge-Base relevant?:||No|
|Country:||SE - Sweden||Keyword #2:|
|Originating UI:||Keyword #3:|
We are failing to make WFS downloadservices published.
Below are our Analysis on one of the services published.
Below are the three links to dataset, viewservice and download service metadata
The Resourceidentfier for the dataset is: 1eb016c8-f362-42c0-b7a8-e34650396110
The download service that is referenced from C above is a WFS at URL:
The capabilities in above this URL contains following reference to the dataset through the spatialdatasetIdentifier element
The capabilities also have following FeatureType definition
When checking this resource in the linkage checker we get following results
The linkage checker informs something in the download service is not ok.
When viewing the evaluation report we see one failed aspect
When inspecting details on the download service
It complains about the Describe Feature type request
The URL to that request is
and the response for the feature type we are inspecting is.
We can also inspect this layer in QGIS
What should we do to find more details that could be a problem.
We have some doubts on some isssues that we though think is ok
It is ok to have mutiple online links for a download services, at least one should be a valid Inspire Network service
It is ok to let multiple datasetets be accessed though a single WFS endpoint. Even if TG Req 52 says its not allowed the dicussions last year and when inspecting existing services on Inspire Geoportal we can see WFS-services that gices access to Multiple datasets
What shall we change ??
#1 Updated by Michael Östling 8 months ago
I got some feedback from Bart Verbeeck (BE), on that in the DescribeFeatureType-response we have
Schemalocation that is behind the firewall. Thanks Bart !
Can this be the reason for our download service is not accepted in harvesting console?
It would be really, really good if there where a complete list of the controls that are done in the harvesting console.
For checking conformance its really good to see what clauses in regulation and Technical guidelines that are passed
But for validating errors it would actually be much easier to see the actual error-messages.
#2 Updated by Michael Östling 3 months ago
- Status changed from New to Closed
We have still not got any feedback on this issue, but we do anyhow close this ticket to create new tickets
with updates with new links since URLs to metadata and services may have been changes since ticket was created.