Defective US CUB Airspace and TFR files

All,

Unfortunately, I have discovered a significant defect in my software that creates CUB airspace and TFR files for my website and the Soaring Turnpoint Exchange. The defect could cause incorrect information to be displayed when using the files. Affected files include all airspace and TFR files downloaded from my website (www.soaringdata.info) or from the Soaring Turnpoint Exchange since January 21, 2019. If you are using any of these, please discard it and download a replacement copy created today or later.

Corrected files and file generation logic has already been implemented on my website. It may take John a little time to generate replacements on the Turnpoint Exchange for individual sites.

For anyone interested in the specifics of the defect: a duplicate point filter was coded incorrectly, resulting in polygons that were not properly closed. How this might affect display of the airspace is somewhat unpredictable. For example, desktop SeeYou often tolerates the problem, but it occasionally causes missing or incorrect display of metadata such as the airspace name and vertical limits.

Thanks to Jim Staniforth, whose report led to the discovery of the underlying issue.

Apologies!

Lynn Alley
"2KA"

On Monday, October 5, 2020 at 6:22:11 PM UTC-4, 2KA wrote:
Unfortunately, I have discovered a significant defect in my software...

Thanks Lynn for all your efforts,
and for tracking down and fixing rare problems.
Much appreciated by all of us!
Best Regards, Dave

Good save,
thanks

2KA wrote on 10/5/2020 3:22 PM:
All,

Unfortunately, I have discovered a significant defect in my software that creates CUB airspace and TFR files for my website and the Soaring Turnpoint Exchange. The defect could cause incorrect information to be displayed when using the files. Affected files include all airspace and TFR files downloaded from my website (www.soaringdata.info) or from the Soaring Turnpoint Exchange since January 21, 2019. If you are using any of these, please discard it and download a replacement copy created today or later.

Corrected files and file generation logic has already been implemented on my website. It may take John a little time to generate replacements on the Turnpoint Exchange for individual sites.

For anyone interested in the specifics of the defect: a duplicate point filter was coded incorrectly, resulting in polygons that were not properly closed. How this might affect display of the airspace is somewhat unpredictable. For example, desktop SeeYou often tolerates the problem, but it occasionally causes missing or incorrect display of metadata such as the airspace name and vertical limits.

Thanks to Jim Staniforth, whose report led to the discovery of the underlying issue.

Apologies!

I never saw any errors, but I'm glad to hear I won't see any.

--
Eric Greenwell - Washington State, USA (change ".netto" to ".us" to email me)
- "A Guide to Self-Launching Sailplane Operation"
https://sites.google.com/site/motorg...ad-the-guide-1

And just to be clear, it is only SeeYou CUB formatted airspace and TFR files that are affected. Other formats including OpenAir, Tim Newport-Peace Special Use Airspace, and Nadler NDB, etc. are all OK.

L.

2KA wrote on 10/5/2020 9:23 PM:
And just to be clear, it is only SeeYou CUB formatted airspace and TFR files that are affected. Other formats including OpenAir, Tim Newport-Peace Special Use Airspace, and Nadler NDB, etc. are all OK.

L.

Ah, I missed that, and that's why I didn't see any errors: I use NP-SUA and OpenAir.

--
Eric Greenwell - Washington State, USA (change ".netto" to ".us" to email me)
- "A Guide to Self-Launching Sailplane Operation"
https://sites.google.com/site/motorg...ad-the-guide-1

Lynn --

Thank you very much for all your work and attention to details

Best

Jim Garrison
AE

Lynn, could this explain phantom airspace warning I was getting in my LX9000 using your CUB airspace files? I was getting alert that I am inside class B/C Airspace’s that were at least 10 miles away. This happened with more than one airspace, always in the same areas. I assumed it was LX9000 bug, but the LXNav folks never identified the issue.
in any case, thanks for identifying and fixing the issue and many thanks for your service.

Ramy

Ramy,

Absolutely, it could explain your phantom warning. It is exactly the kind of thing that could happen. You should definitely try an updated file and see if the problem goes away. I think it is very likely.

Lynn