CRS Resolver Maintenance and History

This page hosts announcements, pending requests, as well as maintenance history for the CRS resolver. -- PeterBaumann - 06 Mar 2017

Note: With decision by Scott Simmons, OGC CTO, on 2017-03-06 the CRS.DWG is no longer authoritative decision maker on CRS maintenance. Currently, OGC-NA is the authoritative decision body. Contact the CRS resolver (cf. landing page for email address) for any inquiry.

Request: recommend use of secore.rasdaman.org instead of opengis.net for CRSs

  • requestor: Gobe Hobona, chair, OGC-NA
  • Background: Since the redirect of the EPSG/ branch to IOGP (see below) it has turned out that the IOGP resolver operates slightly differently. Specifically, it offers only "shallow" CRS definitions instead of the "deep" CRS definitions returned by SECORE. (which continues operating all other CRS-related branches). Consequently, information is missing from such CRS definitions in the XML code. Any tool attempting to resolve may break, such as when trying to retrieve the axisLabels attribute required for resolution of OGC CRS URLs. In practice, this means that the EPSG/ branch (served via IOGP) behaves differently from all other CRS-related branches (still served by SECORE) which reportedly causes severe tool clashes, aggravated by the fact that these often run in unsuervised mode. Therefore, OGC-NA recommends to point all CRS URLs directly to SECORE, e.g., http://secore.rasdaman.org/def/crs/EPSG/0/4326 .

-- PeterBaumann - 12 Nov 2019

Request: redirect EPSG/0/ branch to IOGP server

-- PeterBaumann - 12 Nov 2019

Request: add CRS84

  • requestor: Simon Cox, CSIRO (initially reported 2016-04-07 by Raphaël Troncy)

Please add http://www.opengis.net/def/crs/OGC/1.3/CRS84 It should respond with the contents from https://github.com/opengeospatial/OGC-NA/files/1406084/CRS84.xml.txt

The source for the definition is in http://portal.opengeospatial.org/files/?artifact_id=30575 OGC 07-092r3, transitively from Annex B of WMS 1.3.

Since Simon Cox could not find the equivalent of CRS84 in the EPSG database, he interprets that it implies CS 6424, instead of CS 6422 which is used in EPSG 4326. So to create XML for CRS84, just clone the definition for EPSG 4326, substitute 6424 in place of 6422 and adjust the annotations. See CRS84.xml.txt for the outcome.

-- KevinStegemoller - 23 Oct 2017
Topic revision: r5 - 13 Nov 2019, PeterBaumann
This site is powered by FoswikiThe information you supply is used for OGC purposes only. We will never pass your contact details to any third party without your prior consent.
If you enter content here you are agreeing to the OGC privacy policy.

Copyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding OGC Public Wiki? Send feedback