Discussion Area

This area serves for discussing changes, additions, etc. Feel free to contribute, but maintain the overall structure.

Issue: Update registry definitions with correct xlink location

Description

 change
  http://schemas.opengis.net/xlink/1.0.0/xlinks.xsd
 to
  http://www.w3.org/1999/xlink.xsd

based on http://www.opengeospatial.org/blog/1597. OGC xlinks.xsd was removed 2012-07-21.

Outstanding questions per PeterBaumann:
  • How would that affect CRS version numbering?
    • Possibly no version change similar to the schema.
  • How about the EPSG database contents? the next OGP release will overwrite changes. Or just change the OGC/ branch?

-- KevinStegemoller - 03 Nov 2017

Discussion

tbd

Resolution

tbd

Issue: Some WMS 1.3 CRSs contain dangling references, as per OGC specification

Description

In November 2017, the CRSs defined in WMS 1.3 have been added to the resolver. However, CRS1, AUTO42001:99:8888, AUTO42002:99:8888, AUTO42003:99:8888, AUTO42004:99:8888, AUTO42005:99 contain dangling references:

because their gml files contain elements which point to non-existing EPSG CRSs.
  • in CRS1: MapCS and ComputerDisplay don't exist. They are referenced as follows:
    <cartesianCS xlink:href=http://www.opengis.net/def/cs/OGC/1.3/MapCS/>
    <imageDatum xlink:href=http://www.opengis.net/def/datum/OGC/1.0/ComputerDisplay/>
  • in AUTO42001/99/8888: AutoUniversalTransverseMercatorConversion doesn't exist, but it is referenced as follows:
    <conversion xlink:href= [[http://www.opengis.net/def/coordinateOperation/OGC/1.3/AutoUniversalTransverseMercatorConversion/99/8888]["http://www.opengis.net/def/coordinateOperation/OGC/1.3/AutoUniversalTransverseMercatorConversion/99/8888"]]/>

Discussion

tbd

Resolution

tbd
Topic revision: r3 - 04 Nov 2017, PeterBaumann
 

This site is powered by FoswikiCopyright © 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