Skip to content

Fix TNO/Volve CRS reference data

TNO/Volve test data repo contains 3 reference data manifests that are not desired because they do not follow the standard record id agreement. Additionally they are not BoundCRSs and use schema version 1.0.0 and not 1.1.0. Meanwhile OSDU comes "out of the box" with distributed set of standard CRSs. The objective of this issue is to

  • Replace any CRS id referenced in the (thousands of) Well and Wellbore TNO/Volve to use the standard "out of the box" CRSs (per table below).
  • Remove the local CRS reference data manifests in the TNO/Volve repo because they won't be needed anymore (i.e., the Well and Wellbore manifest will point to the OSDU distributed CRSs).

The OSDU CRS record id standard is described at:https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/blob/master/Guides/Chapters/04-FrameOfReference.md?ref_type=heads#4331-record-id-dataid-for-coordinatereferencesystem

The standard CRS reference data included with a OSDU distribution are contained in file CRS_CT.json at https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/blob/master/ReferenceValues/Manifests/reference-data/LOCAL/CRS_CT.json?ref_type=heads

Detailed analysis:

There are 3 files with local reference data: The letters A,B,C are referenced in the below table.

Volve/TNO 1.0.0 bogus string (record id)

Count in TNO/Volve manifests

 Replace in (Well and Wellbore) data manifests with proper record id

Comment
A,C osdu:reference-data--CoordinateReferenceSystem:23031 12000+ osdu:reference-data--CoordinateReferenceSystem:BoundProjected:EPSG::23031_EPSG::1311

23031 is ED50/UTM31N; We should confirm where the data is.  Namely 1311 is valid in specific area and if this would be northern Norway it would not be correct.

See below 23031024 is a different CT valid in Norway.  I assumed the TNO data is in North Sea near Netherlands.

Note: 23031 is a normal CRS, not BoundCRS. But in OSDU the standard is to use BoundCRS to ingest data, so we best fix the test data and assign a BoundCRS to the original coordinates.  The normalizer on ingest is then able to compute the WGS 84 coordinates. (and WGS 84 should not be in the input manifest ingested).

We can confirm the CT by checking the WGS 84 coordinates.
A osdu:reference-data--CoordinateReferenceSystem:4230 osdu:reference-data--CoordinateReferenceSystem:BoundGeographic2D:EPSG::4230_EPSG::1311 4230 is ED50, base of above. Bound the same to CT 1311 (common offshore in North Sea)
A osdu:reference-data--CoordinateReferenceSystem:4979 0 (confirmed) osdu:reference-data--CoordinateReferenceSystem:Geographic2D:EPSG::4979

WGS 84 3D.   Cannot be used by data. (I cannot believe that; it should only referenced in 4326).  We should be OK to simply delete it from Volve reference data.
A osdu:reference-data--CoordinateReferenceSystem:4978 0 (confirmed) osdu:reference-data--CoordinateReferenceSystem:Geographic2D:EPSG::4978

WGS 84 Geocentric.   Cannot be used by data. (I cannot believe that; it should only referenced in 4979).  We should be OK to simply delete it from Volve reference data.
A osdu:reference-data--CoordinateReferenceSystem:4326 many osdu:reference-data--CoordinateReferenceSystem:Geographic2D:EPSG::4326

WGS 84 2D.  Not bound.
B osdu:reference-data--CoordinateReferenceSystem:WGS%2084

0

(confirmed)

 osdu:reference-data--CoordinateReferenceSystem:Geographic2D:EPSG::4326

Violates current OSDU record id standard (space not allowed).  Since it is not used, we can simply delete it from the local reference data .json, or let the issue resolve itself when that file is deleted out of this repo. If used, replace it with 4326 same as above (WGS 84 2D)
B osdu:reference-data--CoordinateReferenceSystem:23031024 osdu:reference-data--CoordinateReferenceSystem:BoundProjected:EPSG::23031_EPSG::1613

024 is the variant for CT EPSG::1613 which is valid in Norway offshore, South of 62N.

https://epsg.org/transformation_1613/ED50-to-WGS-84-24.html
B,C osdu:reference-data--CoordinateReferenceSystem:MSL osdu:reference-data--CoordinateReferenceSystem:Vertical:EPSG::5714

_MSL height _https://epsg.org/crs_5714/MSL-height.html
C osdu:reference-data--CoordinateReferenceSystem:5709 osdu:reference-data--CoordinateReferenceSystem:Vertical:EPSG::5709

5709 is NAP height (Dutch onshore vertical)
C osdu:reference-data--CoordinateReferenceSystem:23095 osdu:reference-data--CoordinateReferenceSystem:BoundProjected:EPSG::23095_EPSG::1311 ED50 / TM 5 NE used in NLD with CT 1311 generally
C osdu:reference-data--CoordinateReferenceSystem:23032 osdu:reference-data--CoordinateReferenceSystem:BoundProjected:EPSG::23032_EPSG::1311 ED50/UTM32N. Several CTs used. 1311, 1133, 1612, 1613, 1627, 1631, 1810 depending on area.
C osdu:reference-data--CoordinateReferenceSystem:25831 osdu:reference-data--CoordinateReferenceSystem:BoundProjected:EPSG::25831_EPSG::1149

ETRS89 / UTM zone 31N [1149_25831]
C osdu:reference-data--CoordinateReferenceSystem:28992 osdu:reference-data--CoordinateReferenceSystem:BoundProjected:EPSG::28992_EPSG::1672 Amersfoort/RD New used in NLD with CT 1672
C osdu:reference-data--CoordinateReferenceSystem:4230 See above – first check if there is data in TNO with 4230 or if this is just a dependency for defining ED50 / UTM (projected CRS which points to 4230 geographic). If 4230 is used in data records, then we need to use the same CT as used in the BoundProjected here for the BoundGeographic

Example manifests for a Well and Wellbore (search e.g., for AsIngestedCoordinates in data SpatialLocation):

Edited by Bert Kampes