[Flightgear-devel] DAFIFT navids

[James Turner]

Sorry to muck people (esp David, by the sound of it) around, but I have 'live' DAFIFT importing working in my local tree (for about 3 weeks now), I've just been holding off submitting while I did more testing. I've had to extend the Nav types and APIs slightly, to cope with multiple fixes / intersections, and a few other things. So far I'm reading the WPT, NAV and ATS files, about to move on to the ARPT files. I only read a few fields right now but extracting more is trivial. BTW, if we read the DAFIFT ARPT data, do we still need metakit for anything? Reading the DAFIFT files is surprisingly fast, even using brutal, non-indexed schemes (I run through every line in the 18mb airway file each time I instantiate an airway, and the performance seems fine, I expected it be crushingly slow....)

I can get the NAV and WPT stuff over to Curt / David today if there is interest, but the ATS (airway) stuff depends on my FGRoute classes (and there's quite a few of them) which is still in flux (though it's getting there). Of course, if anyone wants to give me CVS access, I could do this development on a branch :-P

Anyway, the other relevant point (I suppose) is that my current impl is backwards compatible, it will still read default.nav and default.fix. So I think it's fairly safe to go in. Any comments either way?

H&H
James

--
You whine like a mule. You are still alive!


_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel