M13-Release-Notes.md

@@ -138,8 +138,8 @@ See [Issue #46 Converter Service](https://community.opengroup.org/osdu/platform/
   * `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. 
+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: 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).