Skip to content

Changes

Page history
Update M13 Release Notes authored by Debasis Chatterjee's avatar Debasis Chatterjee
Hide whitespace changes
Inline Side-by-side
M13-Release-Notes.md
View page @ e5c3893d
......@@ -140,7 +140,7 @@ See [Issue #46 Converter Service](https://community.opengroup.org/osdu/platform/
* Known issue: incorrectly adds meters to feet and feet to meters if the unit of the projected CRS is in the one and the Measured Depths are in the other.
See [issue 52](https://community.opengroup.org/osdu/platform/system/reference/crs-conversion-service/-/issues/52).
* Gap: there is no option to compute a wellpath without applying a correction for map projection point scale factor. See [issue 29](https://gitlab.opengroup.org/osdu/subcommittees/ea/projects/geomatics/home/-/issues/29)
* Known issue: All CoordinateTransformations stored in OSDU must be “to WGS 84”. It is not guaranteed that the generated reference data satisfies this because it is not checked. Geodetic reference data loaded to OSDU are OK, and in general transformations are 99.99% defined as such in the EPSG Database, but EpsgManifestGenerator does not check for this.
* Known issue: All CoordinateTransformations stored in OSDU must be “to WGS 84”. It is not guaranteed that the generated reference data satisfies this because it is not checked. Geodetic reference data loaded to OSDU are OK, and in general transformations are 99.99% defined as such in the EPSG Database, but EpsgManifestGenerator does not check for this. See [issue 44](https://gitlab.opengroup.org/osdu/subcommittees/ea/projects/geomatics/home/-/issues/44)
* Known issue: Convert does not return continuous Eastings when converting latitude, longitude to a local projected CRS that spans the antimeridian (the 180d meridian), e.g., for a seismic line from 179E to 179W. This has no impact unless such local projection would be used (which is uncommon).
See [Issue #49 Converter Service](https://community.opengroup.org/osdu/platform/system/reference/crs-conversion-service/-/issues/49).
* Known issue: Convert custom WKT for a grid file Transformation expects parameter name expected by SIS is "Latitude and longitude difference file" for NTv2 method (and similar for NADCON and vertical models). EpsgManifestGenerator and the underlying database do not typically contain the correct file names. Hence, any custom WKT for transformations that are not implicitly defined by the EPSG code and stored in the Apache SIS library will not work. This is a low priority/low value, because in general Operators will not create NTv2 custom files (there is a small risk a new transform is defined by EPSG that is intended to be used, but before SIS is updated). See [issue 39](https://gitlab.opengroup.org/osdu/subcommittees/ea/projects/geomatics/home/-/issues/39)
......