Tuno wrote:
Thanks 2KA, I'd love to see your source code for the airport turnpoint
stuff. You can find my e-addy at justsoar.com.

I've completed a program that takes a Cambridge turnpoint file (for
boundaries) and outputs (1) a new version of the same file padded with
all APT entries not closer than a mile to any turnpoint already in the
file, (2) a separate file of the same format with all APT entries in
the same boundary, and (3) a SeeYou (.cup) file with all APT entries
as turnpoints. The last one is nice to load in SeeYou and do whatever
with from there.

The entire APT file creates a file with 13520 turnpoints. And that's
facility type = "AIRPORT" or "GLIDERPORT" only.

Interesting that Turf Soaring (Pleasant Valley Airport) is listed as
an airport and not a gliderport.

Lots of info available to plop into the "Description" field. CTAF and
runway idents?

My priorities are *runway width*, and then 100LL availability (I fly a
motorglider). Here's how John L. does it in the CU cup description:

"RLD, RW width: 100, Fuel: 100LL"

He puts the main airport frequency in the cup Frequency box, and it
would be *very* useful to have the ATIS/AWOS frequency in the description.

--
Eric Greenwell - Washington State, USA
* Change "netto" to "net" to email me directly
* "Transponders in Sailplanes" http://tinyurl.com/y739x4
* "A Guide to Self-launching Sailplane Operation" at www.motorglider.org