The coordinates were properly embedded in the JSON data.
ETO-09 did not process the coordinates.
JSON data for the error setup looks like:
"ciim_mapLat": "37.69265467",
"ciim_mapLon": "-121.78917017",
JSON data for correct setup looks like:
"ciim_mapLat": "37.670500",
"ciim_mapLon": "-121.889667",
It's hard to say exactly as the EmComm-Training team (https://emcomm-training.org/) does not officially support PAT, so it's a challenge to get a final say what the issue is. It's BELIEVED to be a decimal point error, that the parsing script fails when the data exceeds 8 digits total.
I have no ability to directly reproduce the failure, as I don't have access to the mapping tool and requests for more information have not yet been answered from the feedback team.
This came up during the Great Shakeout event.
The coordinates were properly embedded in the JSON data. ETO-09 did not process the coordinates. JSON data for the error setup looks like: "ciim_mapLat": "37.69265467", "ciim_mapLon": "-121.78917017",
JSON data for correct setup looks like: "ciim_mapLat": "37.670500", "ciim_mapLon": "-121.889667",
It's hard to say exactly as the EmComm-Training team (https://emcomm-training.org/) does not officially support PAT, so it's a challenge to get a final say what the issue is. It's BELIEVED to be a decimal point error, that the parsing script fails when the data exceeds 8 digits total.
You can see the finally parsed data here, with no LAT/LON data present. https://www.google.com/maps/d/u/0/viewer?ll=-0.0010887102554818172%2C0.09456875691506106&z=15&mid=12c3Qk5cOcB9RBHNWUF7PVMX9Ztk5WS4
I have no ability to directly reproduce the failure, as I don't have access to the mapping tool and requests for more information have not yet been answered from the feedback team.