In GCP environment, Search queries created by the CRS Conversion Services V3, have some issue, because of which failure are seen while using CRS Conversion V3 service
POST https://preship.gcp.gnrg-osdu.projects.epam.com/api/crs/converter/v3/convert Body
{ "fromCRS": "odesprod:reference-data--CoordinateReferenceSystem:BoundProjected:EPSG::29193_EPSG::1867:", "toCRS": "odesprod:reference-data--CoordinateReferenceSystem:Geographic2D:EPSG::4326:", "points": [ { "x": 697339.525, "y": 7239989.403, "z": 0 } ] }
Response { "code": 400, "message": "record not found: odesprod:reference-data--CoordinateReferenceSystem:BoundProjected:EPSG::29193_EPSG::1867/" }
We do find the two following records in GCP/Preship environment, using the Search API odesprod:reference-data--CoordinateReferenceSystem:BoundProjected:EPSG::29193_EPSG::1867 (SAD69 UTM Zone 23S) odesprod:reference-data--CoordinateReferenceSystem:Geographic2D:EPSG::4326 for WGS84
The collection to test can be found here https://community.opengroup.org/osdu/platform/testing/-/blob/master/Postman%20Collection/18_CICD_Setup_CRSConversionAPI/CRS%20Conversion%20Service%20V3.skip_postman_collection.json
Some details about this issue can also be found here #353 (closed)