search

gopeg / issues-barriers

A series of recommendations will be formulated based on the experience gained in activities 1 through 3. The recommendations will be presented to and discussed with stakeholders and the broader open data community with the aim of presenting both the recommendations and feedback in a report.
0 stars 0 forks source link

Access data in other CRSes than EPSG:4326 via OGC API #13

Closed MayteTDGeograma closed 1 year ago

MayteTDGeograma commented 2 years ago

The only EPSG available for the publication of data through OGC API is 4326, while the INSPIRE compliance reference system is EPSG 4258.

It would be desirable, to improve the usability of the OGC API, to speed up the possibility of using EPSG 4258 in this application

sMorrone commented 1 year ago

INSPIRE is "evolving", meaning that (once the new INSPIRE IR have been officially published, which should be shortly) the CRS list will be updated allowing for more EPSG codes e.g., the Member States will be allowed to deliver also in their own National CRSs, if these have been previously approved by the MIG and published in the (upcoming) INSPIRE CRS registry - find more details at https://github.com/INSPIRE-MIF/helpdesk/blob/main/crs.md

rociorj commented 1 year ago

We found the same issue for the Pop Wildfire use case. Thank you for the information on how the issue of reference systems will evolve within ISNPIRE. In the meantime, in our use case we have solved this by publishing the datasets in the system that supports OGC API Features, EPSG: 4326

sMorrone commented 1 year ago

An additional note: the Good Practice "OGC API – Features as an INSPIRE download service" explicitly mentions that "NOTE 1 The Web API shall return collections and features in the default OAPIF coordinate reference system (WGS 84 longitude and latitude). However, the enclosure link for bulk download could still provide access to a data set in a different CRS. "