CRS convert v3 openapi doc
"swagger" like documentation checked at: https://community.opengroup.org/osdu/platform/system/reference/crs-conversion-service/-/blob/master/docs/v3/api_spec/crs_converter_openapi.json
record id for geodetic data: https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/blob/353-Usage-Guide/Guides/Chapters/04-FrameOfReference.md#4-frame-of-reference
-
The main issue is that the examples do not follow the record id style agreed in OSDU. -
- Currently it says like "fromCRS": "osdu:reference-data--CoordinateReferenceSystem:BoundCRS::osdu::fromcrsConvert23031024:"
-
- But is agreed like "fromCRS": "osdu:reference-data--CoordinateReferenceSystem:BoundProjected:EPSG::26715_EPSG::15851:"
-
The /v3/convert example has the same CRS as input and output in the request, and the response indicates nothing was done. This is a bad example and should show an actual conversion (there are many examples provided in the excel file for convert testing - pick any with EPSG codes). -
The /v3/convertGeoJson has a property "toUnitZ" and "UnitZ" in AnyCrsfeaturecollection. The example is using "ms". That is bad example because it is a time and not a length. it should be like "m" or "metre" or whatever OSDU uses for "meter" (I guess "m" though I do not know the OSDU standard for UoM "id"). The response suggests that a conversion from ft to m was executed, but it seems unlikely that the request was executed because it says "ms" (milliseconds I presume). -
The /v3/convertTrajectory shows unit "ms". As above, this should be ft or m for the measured distances and cannot be a length unit. -
Where does the help/documentation of Convert/v3 endpoints explain that record id OR persistent string can be input? If it is not there it should be added or how is a programmer to know what the inputs can be? Ideally with an example, but I do not know if multiple examples can be shown or comments can be added.