While testing the CRS Conversion V3 in AWS Platform Validation environment found the following issue.
Using the storage API was able to create the CRS record, but then when referencing that record during performing the trajectory data conversion, one gets the error message with status 400 Bad Request. { "code": 400, "reason": "Error getting record", "message": "An unexpected error occurred when getting record: " }
It appears it is not able to read the created record. crs-storage-conversion.postman_collection.json
Also sometimes while executing the request for the first time, one gets 500 Internal server message, but then when one executes the request the second time it is successful. It is not a particular request, it is random.
Note I am able to access all the reference data using the STORAGE and SEARCH API
e.g.
curl --location --request POST 'https://sp221718.forumtesting.osdu.aws/api/search/v2/query'
--header 'Content-Type: application/json'
--header 'data-partition-id: osdu'
--header 'Authorization: Bearer eyJraWQiOiJRV3RKSUxz...VA9dA'
--data-raw '{
"kind": "osdu:wks:reference-data--CoordinateReferenceSystem:1.0.0",
"query": "id: "osdu:reference-data--CoordinateReferenceSystem:BoundCRS::osdu::toCRStrajectory23031024""
}
'
curl --location --request POST 'https://sp221718.forumtesting.osdu.aws/api/search/v2/query'
--header 'Content-Type: application/json'
--header 'data-partition-id: osdu'
--header 'Authorization: Bearer eyJraWQiOiJRV3RKSUxz...VA9dA'
--data-raw '{
"kind": "osdu:wks:reference-data--UnitOfMeasure:1.0.0",
"query": "id: "osdu:reference-data--UnitOfMeasure:ms""
}
'