Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Way point files with no elevation data for turn points do not load #21

Open
Nimbus2 opened this issue Jan 19, 2016 · 0 comments
Open

Way point files with no elevation data for turn points do not load #21

Nimbus2 opened this issue Jan 19, 2016 · 0 comments

Comments

@Nimbus2
Copy link

Nimbus2 commented Jan 19, 2016

There are a lot of way point files on the Worldwide Soaring Turnpoint Exchange in SeeYou cup format that do not have elevation data for the turnpoints. This causes the way point files to not be loaded.

Example of a turn point from a cup file that doesn't load in proSoar:
"Bakerville","BAK",ZA,2558.467S,02605.483E,,1,,,,"Turn Point, Road T Junction"

Adding any elevation fixes the problem:
"Bakerville","BAK",ZA,2558.467S,02605.483E,0m,1,,,,"Turn Point, Road T Junction"

In the absence of an elevation for the turn point, most soaring applications will calculate the elevation based on an elevation model. If an elevation exists in the way point file it will override the internal calculation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant