Closed skadakar closed 2 years ago
This is a wintak specific issue and can be solved by changing your windows installation to use English language instead of your local language. Might not be worth spending time on, but it's still a issue I think one should survive. Maybe fire off a message informing the user.
So I did a little bit of research on this. According to this[1], it seems that GPS coordinates should use a period for the decimal place, regardless of locale. This would indicate that the bug is with WinTAK -- though I'm not sure where to file a bug report.
I could add some special logic to handle this edge case, but I'm rather hesitant, as it's a little complicated to handle correctly, and I'd prefer to keep the codebase simple.
In the future, one of the features I'm looking to add is a plugin framework that can execute pre-processing on the incoming data. A plugin could be written to look for (and correct) locale specific separator formats. I think that is the best place for such a feature to go.
For now, though... are you and your users able to work around this ok? If not, I can provide you a little patch, if you'd like to run your own fork until the plugin framework is established!
1 - https://ux.stackexchange.com/questions/85702/localizing-coordinates
Just a validating opinion, I view this as a client issue and not something that taky should try to solve. GPS coordinate should not use localized decimal indicators.
ERROR:
COT part that creates the problem:
<track course="0,00000000" speed="0,00000000"/>