Test of CRS /v3/convert (Bert tests summary and findings/questions)
To: @fhoueto.amz @kogliny @spencer CC: @gehrmann @sjtomlinson
@kogliny : Following is first test of v3/convert
-
Can the service be on at night and in weekend? -
Can the token access time be made longer than 3600. Is there an issue to set it to a week or so? Suddenly at 8PM (Houston) on Saturday I get 401 Access denied, User not authorized. Then again around 8:20PM I needed to get a new token. -
I cannot find the documentation of the CRS Convert service. -
By reverse engineering confirm that /v3/convert/ accepts both record id and persistent string. Please confirm this is the design for convert. -
The return has full machine precision. Is there an easy way to round this to 10 dp for geographic and 5 for projected? (implementation TBD if easily doable without performance loss; the given dp are at 10 um level or better). -
returned numbers can be scientific. They should always be formatted in decimal format for CRS convert service. Undesired is for example "x": -1.7543083738224965E7. Coordinates are <-100e6, +100e6> and decimal is best in my view (I do not expect larger than 100,000,000 for a coordinate but often in the 10MM range. -
test custom CRS by WKT for TM for expected correct result. -
"y" : .5 not -.5 do not work. This may be normal but it should be documented that number input requires "the whole" (number before the decimal point. I tested the input coordinates do not require a decimal point. I tested also (0,0,0) which gave NaN but probably due to Transverse Mercator in the SIS lib going out of range. -
test storing a custom CRS -
it seems I can store a BoundProjected referencing a SourceCRS and unit that is not in the database. Isn't there record validation? -
Created record version is not like "1" but some crazy number. How does this work (how to start from EpsgManifestGenerator at 1 and increment?) "recordIdVersions": [ "osdu:reference-data--CoordinateReferenceSystem:Geographic2D:EPSG::4326:1651368973685309" -
test custom CRS "by id" for same result as above. -
test for multiple points in the request.
(end of testing /v3/convert).