Am Mittwoch 22 Dezember 2004 22:58 schrieb Roy Vegard Ovesen: > On Wednesday 22 December 2004 22:43, David Megginson wrote: > > On Wed, 22 Dec 2004 22:22:58 +0200, Paul Surgeon <[EMAIL PROTECTED]> > > wrote: > > > I really feel that FG should have a built in flight planner of some > > > sort. All the basic navaid data is already in FG we just need some way > > > of displaying > > > > What's not in FlightGear, like the actual airways, is in the DAFIF (as > > long as it lasts). > > There is the data/Navaids/awy.dat.gz file that I guess contains the > airways. AFAIK it's not used by FlightGear, but it could of course be used > by Atlas.
Thats right. But some data is also missing I guess (e.g. one way restrictions). The format is relatively easy. Every line contains an airway segment. The first 3 values per line are the data for the starting fix (name, lat, lon). The next 3 the same for the endpoint fix. I'm not completely sure about the last 4 columns in the file. The last one is most probably the name of the airway. The seventh seems to be some kind of classification with values 1 or 2 (High/Low Enroute?). The other two being heading(?) and flight level(?) Can anyone confirm this? I've written a custom python app, which uses that data to draw "enroute charts". It shows NDB's, VOR's, Fixes, Airways and Airports. Because of it's "quickly hacked together in a weekend" status it is extremely picky about the users it is friendly to ;-) (you have to change code to set coordinates, it doesn't really zoom, ...) If anyone is interested just mail me, I'm happy to share. But beware, it's definitely ALPHA code. Thomas _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
