EpsgManifestGenerator for custom entities (WKT and names)
discussion 2022-01-17
Operators have a requirement to add custom CRS, CT and BoundCRSs to OSDU geodetic reference data.
[populating-OSDUgeodetic-reference-data.docx](/uploads/5f046d69bf1c152e6c6041d228a40d16/populating-OSDUgeodetic-reference-data.docx)Operators with an in-house GeoRepository would point EpsgManifestGenerator to it in order to overwrite the OSDU data. Such database would contain Operator defined CRS, CT, and BoundCRSs.
Several changes described in the attached (outdated) have been implemented (in particular the "id" and ability to generate reference data from a list). As of 2022-01-17 there are 2 unresolved items bundled in this issue:
1. The ability for an operator to put in a naming convention for BoundCRSs. (More generically, for any CRS or CT - the main issue is that Operators will have naming conventions for BoundCRSs that should be used in OSDU.
2. Creation of WKT. Ideally the WKT is created dynamically from parameters stored in the database and not from hardcoded information to avoid mistakes - but mainly to enable WKT for custom entities.
This issue was discussed in the geomatics workstream with Phil (XOM), Sigrid (Equinor), Bert (Shell), Josh (BP) and Jin (Chevron).
For the first issue, a NameAlias could perhaps be used, but that solution is not understood and still requires a mechanism to generate reference data such that end users in OSDU applications see the desired CRS names. The easier solution appears to be that the an output name is added to the script/input file so that this name is written.
For the second issue, several approaches have lightly been discussed but nobody in the Geomatics workstream knows of a clear and easy method to generate this WKT in ESRI style. (a) EPSG GeoRepository does not generate this "ESRI flavor" - it can output OGC/ISO WKT1 and WKT2. Some attempts were made to output ESRI methods and parameters but that is not fully compliant even with a simple LCC1 method because it uses a naming system only. (b) gdal or other utilities (e.g., epsg.io) appear to be able to generate ESRI WKT. However it is not clear to us what utility can do this, nor what license is required for this and if OSDU would accept that. (c) An ESRI web service might be able to somehow export ESRI WKT - this would need to be checked but seemed unlikely; (d) a geospatial open source developer may know the answer and be able to code this, i.e., by extending the EpsgManifestGenerator.py script to retrieve the method and parameters, then use that to define a spatial reference object, and then export that as ESRI WKT which essentially can be converted to what is required for OSDU PersistenReference.
Discussion on 27-Aug-2021 Need some kind of translator from common format such as WKT