Closed dylanbuli closed 14 years ago
Hmm - I'm not so sure this is a good idea. I think the various WPT file formats specify the units as meters. Do you have an example of a file that was not correctly parsed? If so, can you attach it to the bug?
On more investigation, it looks like the soaring way point databases from the Waypoint Exchange depend on the area. In the US they are in feet, in the Alps, its in meters. So obeying the preference during import might make sense (if there is no other indication of standard used in the .wpt.) http://soaringweb.org/TP/NA.html#CO http://soaringweb.org/TP/Alps_out
This site might be useful for WPT examples for you too.
Thank you for the report Dylan. I looked at the files and finally found a spec for CompeGPS and Oziexplorer format files - they both call for feet, so that's what I'll start using. For the legacy simple wpt format, those seem to be in meters both in Europe and the US. Please let me know how this works out for you.
Fixed in .81, thanks!
When importing a WPT with altitude in feet, Gaggle will always assume that it is in meters. Perhaps use the preference when there are no units specified.