Bug #2238

Task #2214: MIWP-8 (D) Integrate metadata for interoperability into the Metadata TG.

Inconsistency on CRS metadata

Added by Michael Lutz almost 6 years ago. Updated almost 6 years ago.

Status:ProposedStart date:24 Oct 2014
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

We discovered an inconsistency on the guidelines for CRS metadata in the data specifications template. In section 6 (on CRS), it says the following: > These Technical Guidelines propose to use the http URIs provided by the Open Geospatial Consortium as coordinate reference system identifiers (see identifiers for the default CRSs below). These are based on and redirect to the definition in the EPSG Geodetic Parameter Registry (http://www.epsg-registry.org/). > > *TG requirement* The identifiers listed in Table x shall be used for referring to the coordinate reference systems used in a data set. > > NOTE CRS identifiers may be used e.g. in: > * data encoding, > * data set and service metadata, and > * requests to INSPIRE network services > > *Table x. http URIs for the default coordinate reference systems* > (...) In section 8, in the CRS metadata example, however, the CRS short name (rather than the http URI) and "INSPIRE RS registry" (rather than some id for the EPSG registry, e.g. http://www.epsg-registry.org/) is used:

  
     
       
         
           ETRS89-LAEA
         
         
           INSPIRE RS registry
         
       
     
   
 
We should agree on what code and code space to use (preferably the EPSG http URIs as suggested in section 6) and then update the example for the CRS MD element accordingly.

Related issues

Related to 2016.3 Validation & conformity - Task #2239: CRS guidance and validation Submitted 24 Oct 2014

History

#1 Updated by Alex Ramage almost 6 years ago

I have posted something similar on the MIWP-05 workspace as the metadata validator seem to be rejecting well know CRS url's - for example EPSG-04326. Cross reference https://ies-svn.jrc.ec.europa.eu/issues/2239

#2 Updated by Angelo Quaglia almost 6 years ago

The Validator 2 currently sticks to the following list and expects the full HTTP URI (to be used as code of the RS_Identifier element while the codespace is not checked): http://inspire-geoportal.ec.europa.eu/documentation/legal-and-tgs/ds/INSPIRE_DataSpecification_AD_v3.1/?zoomToText=TG%20Requirement%202 The Validator 2 will likely be extended to recognize compound codes like in the OGC CRS name type specification (https://portal.opengeospatial.org/files/?artifact_id=53819), which in section 9 has a specification for compound CRS, e.g. Example 2 The URI for combining the CRSs EPSG 4269 (NAD83) and EPSG 5713 (Canadian Geodetic Vertical Datum of 1928), adding in height, is: http://www.opengis.net/def/crs-compound?1=http://www.opengis.net/def/crs/EPSG/0/4269&2=http://www.opengis.net/def/crs/EPSG/0/5713 In addition the Validation 2 will accept WGS 84 (the full HTTP URI) if the bounding box spans the whole world.

Also available in: Atom PDF