James Turner writes: > Anyway, I think I'll start working on reading in the raw DAFIFT data > instead of the existing data in Navaids/, and then worry about > supporting compressed forms of the data once I have the basics working. > And now I have airways data to play with!
For navaids, the DAFIFT is probably the best choice, especially since it's updated every few weeks (we'll be the most up-to-date sim out there); we just need to confirm that there's nothing extra in the FAA data. We could start with just the following files: NAV.TXT: 1.5MB uncompressed, 570K compressed. WPT.TXT: 8.5MB uncompressed, 2.9MB compressed. Those are quite reasonable sizes, considering that they include full data for 11,192 navaids and 72,549 waypoints/intersections. I agree that not all fields are needed, but the majority seem useful. I notice that the range for most non-US navaids is down as "unknown". For anyone who wants to look, you can import the DAFIFT files straight into a spreadsheet; here's the current ZIP: http://164.214.2.62/dafif/dafif_0301_ed7/DAFIFT.ZIP All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
