... | @@ -143,9 +143,9 @@ See [issue 52](https://community.opengroup.org/osdu/platform/system/reference/cr |
... | @@ -143,9 +143,9 @@ See [issue 52](https://community.opengroup.org/osdu/platform/system/reference/cr |
|
* 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.
|
|
* 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).
|
|
* 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).
|
|
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).
|
|
* 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)
|
|
* Gap: `convertTrajectory` does not allow interpolation on a specific MD (which is needed to get the TVD for a log at a given MD that is not in the survey).
|
|
* Gap: `convertTrajectory` does not allow interpolation on a specific MD (which is needed to get the TVD for a log at a given MD that is not in the survey). See [issue 29](https://gitlab.opengroup.org/osdu/subcommittees/ea/projects/geomatics/home/-/issues/29)
|
|
* Gap: `CRS Convert` has no endpoint for Bin Grid squaring, deriving p6 parameters, and conversion. Such checks (if the grid is square, and derive the parameters from the corners) should be part of the seismic ingest workflow which then would need such endpoint to be developed.
|
|
* Gap: `CRS Convert` has no endpoint for Bin Grid squaring, deriving p6 parameters, and conversion. Such checks (if the grid is square, and derive the parameters from the corners) should be part of the seismic ingest workflow which then would need such endpoint to be developed. See [issue 27](https://gitlab.opengroup.org/osdu/subcommittees/ea/projects/geomatics/home/-/issues/27)
|
|
* Gap: `CRS Convert` has no endpoint that directly returns the point scale factor and grid convergence at a given location. `ConvertTrajectory` can be called with a dummy call to obtain these.
|
|
* Gap: `CRS Convert` has no endpoint that directly returns the point scale factor and grid convergence at a given location. `ConvertTrajectory` can be called with a dummy call to obtain these. See [issue 29](https://gitlab.opengroup.org/osdu/subcommittees/ea/projects/geomatics/home/-/issues/29)
|
|
* Gap: `CRS Convert` cannot execute a direct transformation between CRS A and CRS B, it requires a pivot (through WGS 84).
|
|
* Gap: `CRS Convert` cannot execute a direct transformation between CRS A and CRS B, it requires a pivot (through WGS 84).
|
|
See [Issue #15 Converter Service](https://community.opengroup.org/osdu/platform/system/reference/crs-conversion-service/-/issues/15). |
|
See [Issue #15 Converter Service](https://community.opengroup.org/osdu/platform/system/reference/crs-conversion-service/-/issues/15). Also see [issue 34](https://gitlab.opengroup.org/osdu/subcommittees/ea/projects/geomatics/home/-/issues/34) |