Hi!

Ok, here we go...

I've written a little (very ugly coded) C-prog to convert the apt.dat.gz data to default.* files. (and some even more awful bash scripts...)

see http://gw.orson.at/~orson/linux/FlightGear/

But not all COMM-codes are translated to default.* files.

Here a list:

apt.dat.gz conversion details:
50      ATIS/ASOS       -> default.atis
51      CTAF/UNICOM     -> not mapped (don't know where to put :))
52      CLNC/DEL        -> not mapped (don't know where to put :))
53      GROUND          -> default.ground
54      TOWER           -> default.tower
55      APPROACH        -> default.approach
56      DEPARTURE       -> default.approach (in lack of a default.departure)

INFO: As the apt.dat.gz only stores freqencys in this format xxx.xx but the default.* files somehow need the "_real_" frequency, they get automagically converted to 0.025 Frequency-steps (123.12 -> 123.125 / 123.57 -> 123.575)

Hope this is somehow sane...

My scripts also re-added the existing Freq-Data for airports contained in the old default.atis/default.tower which a not presen in the new/converted ones.

The "ready4use" generated new default.* files (apt.dat.gz of CVS/HEAD used)
you can find at:
http://gw.orson.at/~orson/linux/FlightGear/apt.dat-ATC.default-convert/default.approach
http://gw.orson.at/~orson/linux/FlightGear/apt.dat-ATC.default-convert/default.atis
http://gw.orson.at/~orson/linux/FlightGear/apt.dat-ATC.default-convert/default.ground
http://gw.orson.at/~orson/linux/FlightGear/apt.dat-ATC.default-convert/default.tower

Feel free to test the newly generated ATC/default files... and to extend the "convert-program" for your needs :)

PS: if you "build" it on your own edit the PATHSETTINGS file to your /PATH/TO/apt.dat.gz and /PATH/TO/ATCDIR

then use:
make clean
make run

and hopefully everything works and u have "new" default.* files in the current directory.

Maybe someone finds it useful...

Greetings,
  Juergen

David Luff wrote:

On 08/04/2005 at 11:10 Melchior FRANZ wrote:


* David Luff -- Friday 08 April 2005 10:46:

The ATIS and tower lists should be reasonably complete, since they're
generated from the DAFIF, as is Robin's data.  He might well have a

number

of user additions / corrections in there though.

That would explain it. At least there are a few Austrian international airports for which $FG_ROOT/Airports/apt.dat.gz has an ATIS frequncy, but $FG_ROOT/ATC/default.atis has not: examples: LOWL, LOWG, LOWK, which is almost half of our international airports. Same problem for default.tower

I assume that the reason why there are two separated databases at all
is only that apt.dat.gz is rather new,


Yes, the older airport data formats had no ATC freq data when I first came
to need it, so I just created the default.atis etc files out of necessity.


and that the long-term goal is
to read all information from there?


It would seem to make sense - your examples above indicate that the
coverage would probably be a lot better outside of the US.

Cheers - Dave



This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.


_______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d

-- -- Diese Message wurde erstellt mit freundlicher Unterstuetzung eines freilaufenden Pinguins aus artgerechter Freilandhaltung. Sie ist garantiert frei von Microsoftschen Viren. ------------------------------------------------------------------------------ May the pig be with you! *oink* email: orson aet orson.at ------------------------------------------------------------------------------

_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to