This page aims at collecting usability issues related to the use of INSPIRE data reported through TC discussions. The issue 'Status' reports whether the issue has currently been solved or not.

This page is read-only,  should you have any news on the Status of reported issues, or should you want to report a new issue, please post a relevant discussion on the Cluster.

I will update this page accordingly when relevant. 

Use of the ‘http’ encoding for Coordinate Reference System identifiers 

The use of the 'http' encoding for Coordinate Reference System  (e.g. "http://www.opengis.net/def/crs/EPSG/0/3035”) is an INSPIRE TG Requirement. In all the INSPIRE Data Specifications, it is stated "These Technical Guidelines propose to use the http URIs provided by the Open Geospatial Consortium as coordinate reference system identifiers”.

When validating INSPIRE datasets,the INSPIRE Validator rises an error if an encoding different than ''http (e.g. ''urn' encoding) is used to provide CRS information.

In the TC discussion https://themes.jrc.ec.europa.eu/discussion/view/109106/fyi-interpreted-coordinate-order-flipped-in-gml-files-with-uri-format-srsname  two issues are mentioned with reference to the use of the ‘http’ encoding for CRS.  

Here follows description of the issues and their current Status.

• INSPIRE GML datasets using the http encoding are displayed incorrectly in some GIS environments, e.g. QGIS. Responsible for this behaviour is the GDAL library (before version 2.1.2) not respecting the coordinate order (northing, easting) for http CRS, thus causing problems to all software tools using it, either directly or indirectly ( QGIS for example) when consuming INSPIRE GML data.

      Status: solved

This issue has been solved with new versions of GDAL library and the http encoding for CRS can be safely used e.g. in QGIS (v2.18 and above).

• http URI encoding for CRS not supported by deegree software tool

when ingesting a GML dataset conforming to INSPIRE CRS http encoding, deegree rises an error. Therefore it is necessary to use e.g. the urn encoding -  see https://github.com/deegree/deegree3/issues/711

Status: solved

this issue has been fixed in v.3.4.6 (stable)