M13-Release-Notes.md

@@ -34,6 +34,11 @@ For detailed services that are included in this release, please refer to [M13 ta
   * `E&O`
   * <span dir="">`Apache SIS`</span>
   * `CRS Conversion`
+    * The Convert service can now handle Operator defined Transformations between geodetic datums, i.e., a PersistableReference using WKT using GEOGTRAN. Previously the EPSG code was extracted from the PR and used. If that code did not exist in the Apache SIS library then no transformation would be executed. Now the WKT is parsed and used if the given code cannot be found in the Apache SIS library.
+See [Issue #46 Converter Service](https://community.opengroup.org/osdu/platform/system/reference/crs-conversion-service/-/issues/46).
+    * The EpsgManifestGenerator script has been updated to dynamically generate WKT (PersistableReferences) for CRS and CT entities not in the Esri lookup files.
+
+  * `CRS Catalog`
     * **POST CRS and POST CT**
       * Change default search limit to a large value (10000)
       * Add includeDeprecated (exclude InactiveIndicator: true)
@@ -99,3 +104,23 @@ For detailed services that are included in this release, please refer to [M13 ta
 ### Deprecation Notice
 
 ## Known Issues/Gaps
+- `Core and Helper Services`
+  * `Storage`
+  * `File`
+  * `Search`
+    * Known issue: a search for UOM by record id using query “osdu:reference-data--UnitOfMeasure:ft:” returns ft[US] and ft[GC] units.  A query for "osdu:reference-data--UnitOfMeasure:ft[US]" does not work and neither does "unitZ": "osdu:reference-data--UnitOfMeasure:ft%5BUS%5D"
+  * `Indexer Queue`
+  * `CRS Conversion V3` 
+    * `ConvertTrajectory` 
+       * 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 [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. 
+    * 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). 
+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).
+    * 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: `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 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` 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).