Mercator bug appears still present?

@fhoueto.amz

CC - @marneson ; @debasisc ; @gehrmann ; josh townsend

• Can you clarify whether this bug (Mercator 180E longitude wraparound for a local map projection issue) is supposed to have been fixed or not in AWS M13 pre-ship? My understanding from Josh Townsend was that with the update of SIS this now should work. Is AWS Convert pre-ship using the latest SIS library?

My understanding was that M13 was using the latest SIS and that should have resolved the Mercator bug.

However, following request still gives wrong answer.

M13 pre-ship AWS testing on 2022-08-30 showed the bug is still present for Mercator with request:

{
  "fromCRS" : "osdu:reference-data--CoordinateReferenceSystem:Geographic2D:EPSG::4326:",
  "toCRS" : "osdu:reference-data--CoordinateReferenceSystem:Projected:EPSG::3994:",
  "points" : [ {
    "x" : -179.0,
    "y" : -35,
    "z" : 0
  } ]
}

This returns

{
    "successCount": 1,
    "points": [
        {
            "x": -2.3473716646826036E7,
            "y": -3128534.7348073535,
            "z": 0.0
        }
    ],
    "operationsApplied": [
        "conversion from GCS_WGS_1984 to WGS_1984_Mercator_41; 1 points converted"
    ]
}

but the x should be some positive value around +7,000,000 or so and not around negative -20,000,000 as returned.