CRS convert now requires closing colon in m13 preship for record id
When convert by record id was implemented in v3 the following worked (April 30, 2022):
{
"fromCRS": "osdu:reference-data--CoordinateReferenceSystem:BoundGeographic2D:EPSG::4208_EPSG::15754",
"toCRS": "osdu:reference-data--CoordinateReferenceSystem:Geographic2D:EPSG::4326",
"points" : [ {
"x" : -45.0,
"y" : -25,
"z" : 0
} ]
}
In AWS pre-ship M13 testing only the following works:
{
"fromCRS": "osdu:reference-data--CoordinateReferenceSystem:BoundGeographic2D:EPSG::4208_EPSG::15754:",
"toCRS": "osdu:reference-data--CoordinateReferenceSystem:Geographic2D:EPSG::4326:",
"points" : [ {
"x" : -45.0,
"y" : -25,
"z" : 0
} ]
}
The difference is that a colon appears to be needed at the end of the record id.
-
Can you please comment if this is intended or a (new) requirement or an accident? The swagger documentation does show it with terminating colon; I just had never used it and that worked fine seemingly.
Note that the record id as returned by the Catalog service does not have the closing colon, e.g., the following is returned by that service:
"createUser": "serviceprincipal@testing.com",
"id": "osdu:reference-data--CoordinateReferenceSystem:Geographic2D:EPSG::4158"
}
],
"totalCount": 1
},
"query": "data.ID: \"Geographic2D:EPSG::4158\""
}
A normal use case would be that someone fetches a list of CRSs, then picks one, then passes on the "id". It seems awkward that the colon needs to be appended manually.
Edited by Bert Kampes