You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: