Replacement for DAFIF Airspace Data

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?

2NO

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

If you want the runway width, do you also want the lengths and widths
of all runways at the airport? (can do, as well as the fuel)

Neither ATIS nor AWOS freqs are in the NASR's APT table -- UNICOMs and
CTAFs only.

Hopefully the NFD will have all the freqs we see on the charts.
(They're supposed to add comm frequencies sometime in 2008.)

2NO

2KA wrote:

Please do add the airport turnpoint list to turnpoint.com. I'll send
over some of my source code for comparison, so you can see how I
handle things like unique short name generation.

Speaking of name generation...

I'm probably telling you stuff you know already, but there is the
problem of airports with identical names. I fly from Richland airport in
Washington state, but there are Richland airports in MO, NY, and WI.
John Leibacher solved that for the airport databases he generated by
appending the state name to airports names that weren't unique: Richland
WA, Richland MO, etc.

If you use small turnpoint areas, it may not be problem, but I put the
entire USA into SeeYou, and I typically use large portions of it in
SeeYou mobile, like WA, OR, ID, MT, or WA, OR, ID, northern CA and NV.

--
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