You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While researching #165, i ran into the following challenge:
In some feeds in the netherlands data-publishers have decided to put the same dataset in multiple formats online, to facilitate ease-of-reuse. An example is here: http://services.rce.geovoorziening.nl/www/download/data/Rijksmonumenten_nl.xml
In that scenario would I have to add to URL element twice in the opensearch description, for each of the available formats? Having a unique url per format? That would cause problems if some of the datasets are exposed in less or more formats then other datasets in the same service.
Based on this template: <Url type="application/zip" rel="results" template="https://www.nationaalgeoregister.nl:/geonetwork/opensearch/dut/download?spatial_dataset_identifier_code={inspire_dls:spatial_dataset_identifier_code?}&spatial_dataset_identifier_namespace={inspire_dls:spatial_dataset_identifier_namespace?}&crs={inspire_dls:crs?}&language={language?}&q={searchTerms?}"/>
with Accept header application/zip. The validator expects that the service response Content-Type equals the media-type from the GetSpatialDataset URL. But the service returns a XML document.
While researching #165, i ran into the following challenge:
In some feeds in the netherlands data-publishers have decided to put the same dataset in multiple formats online, to facilitate ease-of-reuse. An example is here: http://services.rce.geovoorziening.nl/www/download/data/Rijksmonumenten_nl.xml
In that scenario would I have to add to URL element twice in the opensearch description, for each of the available formats? Having a unique url per format? That would cause problems if some of the datasets are exposed in less or more formats then other datasets in the same service.
testreport:
http://inspire-sandbox.jrc.ec.europa.eu/etf-webapp/v2/TestRuns/EID6af4d855-4d6c-4532-9506-b86e207ac25c.html
The text was updated successfully, but these errors were encountered: