Improper parsing of LAT/LON data by Winlink clients for PAT users.

[Rebootkid]

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.

[Rebootkid]

Looks like the challenge is that Winlink added a "Header" value in both the embedded XML as well as the mail headers.

Example in the XML attachment: 47.537315N, 122.238852W (GPS)
Example in the mail headers: X-Location: 47.537315N, 122.238852W (GPS)

[martinhpedersen]

Hi,

Can you provide some more details regarding the template used and the expected XML structure for the attachment?

Thank you.

[martinhpedersen]

@Rebootkid - Can you please share the template and example of expected XML structure?

The X-Location header is on my TODO list, but I need more information to implement it:

1. When should it be added?
2. What's the exact format?
3. Pointer to docs would be great, if WDT have released any.

And for the XML attachment, I need an example template to work with and the exact format expected.

Thanks!