TWC Updates on John Deere Case for IBM Support

The customer (John Deere, Co) reported this issue over 115 days ago; we have yet to provide a fix/solution. The problem stems from the method and inconsistent results of the data using HOD - Direct APIs through an automated systems and the response result do not match. The client’s investigation turned out the following: It turned out that when their automated systems (written in python) queried the HOD - Direct API, it was percent-encoding the comma character within the geocode, while manually querying the API using a raw ascii (non encoded) comma. The HOD - Direct API returns different results depending on if the comma character was percent encoded or not (defect).

EIS Support/Hod Dev summary of the investigation:
This appears to be the TWC API gateway has logic to round the lat and lon values in the geocode parameter to two decimal places. (@penfeldt confirmed – no longer with IBM). However, there is an apparent bug or oversight in that logic — when the geocode parameter is urlencoded in xx.xxx%2Cyy.yyy format, the rounding does not happen and the string is passed as is to IBM’s gateway (APIc). The reason that the customer is seeing different results with the two different formats is because of the rounding, the requested point gets mapped to a different nearest neighbor grid point. HoD Dev feels strongly this is a bug on TWC side, which is why this was escalated to TWC to help address this problem.
Here are the client's examples of the problematic APIs:
Curl "https://api.weather.com/v3/wx/hod/r1/direct?apiKey=$API_KEY&startDateTime=20240403T06Z&endDateTime=20240403T07Z&format=json&units=e&compact=false&products=precip1Hour&geocode=41.451,-90.121&weighted=false"
Would return:
[{"requestedLatitude":41.45,"requestedLongitude":-90.12,"latitude":41.42857142857142,"longitude":-90.13185133865619,"gridpointId":"9zrgsvzfztkw8","validTimeUtc":"2024-04-03T06:20:00+0000","precip1Hour":0.03}]
While
curl "https://api.weather.com/v3/wx/hod/r1/direct?apiKey=$API_KEY&startDateTime=20240403T06Z&endDateTime=20240403T07Z&format=json&units=e&compact=false&products=precip1Hour&geocode=41.451%2C-90.121&weighted=false"
would return:
[{"requestedLatitude":41.451,"requestedLongitude":-90.121,"latitude":41.47252747252747,"longitude":-90.13185133865619,"gridpointId":"9zrguvzfzxkw8","validTimeUtc":"2024-04-03T06:20:00+0000","precip1Hour":0.02}]