Some soarindata.info bug fixes (US)

[2KA]

I noticed one or two users that had problems when their CUP turnpoint file contained tasks that used numbered turnpoints. In one example, the turnpoint file started with "01Beloit-WI". Any tasks using that turnpoint (or any other numbered one) would get messed up. That issue has been corrected, so anyone experiencing that may wish to try again.

I also noted that in some cases the KML airspace files generated as companions to airport information had errors, such that Google Earth would not read them. That issue has also been fixed.

I updated airspace and airport information earlier this week, including the new definition for the Atlanta Class B. Spring soaring has already started in many US locations, so its a great time to update the airport and airspace info in your glide computer. All the required information is always free at http://www.soaringdata.info.

Happy Downloading!

Lynn Alley
"2KA"

[CLewis95]

On Friday, March 8, 2013 12:40:45 PM UTC-6, 2KA wrote:
> I noticed one or two users that had problems when their CUP turnpoint file contained tasks that used numbered turnpoints. In one example, the turnpoint file started with "01Beloit-WI". Any tasks using that turnpoint (or any other numbered one) would get messed up. That issue has been corrected, so anyone experiencing that may wish to try again.
>
>
>
> I also noted that in some cases the KML airspace files generated as companions to airport information had errors, such that Google Earth would not read them. That issue has also been fixed.
>
>
>
> I updated airspace and airport information earlier this week, including the new definition for the Atlanta Class B. Spring soaring has already started in many US locations, so its a great time to update the airport and airspace info in your glide computer. All the required information is always free at http://www.soaringdata.info.
>
>
>
> Happy Downloading!
>
>
>
> Lynn Alley
>
> "2KA"

That was me Lynn! :)
Can you describe in more detail the problem you saw? .. I looked and do not see any issues with the tasks in the output I received.

Thanks,
Curt - 95

[2KA]

As I mentioned above, the problem involved numbered turnpoints. In the input file, the example turnpoint was "01Beloit-WI". In the output file, a space would have been added after the number: "01 Beloit-WI". This would disconnect the turnpoint from any tasks that used the original format.

You can see problems like this by checking the log file that is produced as part of the query. It is a good idea to have a look at the log to see if anything unexpected happened.

Thanks for using soaringdata.info!

L.