Re: [Flightgear-devel] Missing ATIS frequencies in apt.dat. Was: Help with shared VOR/ATIS frequencies. Was Time to divorce X-plane??

[Torsten D. <To...@t3...>]

Am 15.05.14 22:55, schrieb John Denker:
> Previous versions of apt.dat knew about this ... but this
> information does not seem to appear in the current version.
> I have no idea when this changed, or why.
Right, this commit removed the nav atis frequencies.

/commit 2c3363951a547c2e5a40376876874b1fe014b69f//
//Author: Christian Schmitt <ch...@il...>//
//Date:   Fri Dec 13 23:51:33 2013 +0100//
//
//    Update *.dat files to 2013.10 state to match new terrain//
/
Chris, do you know what happened?
> 1) Make sure FGFS can handle voice on nav frequencies
>
> 2a) In the short run, to facilitate testing, patch a few
>    examples into apt.dat
>
> 2b) In the longer run, find a systematic way to obtain
>   reliable data.
>
> 3) Creeping feature:
>
>   As we have discussed before, ideally the ATIS feature
>   should not be built into the radios.  This is particularly
>   obvious in a multiplayer environment.  There should be
>   a separate ATC process that generates the ATIS broadcast.
>   Then the radio just has to receive it.  The idea is that
>   everybody in the vicinity should hear the /same/ ATIS.
>   You don't want different players getting different instructions
>   as to runway-in-use.
Yes. That's why I refactored the ATIS code and this is how it works now.
The classes building the ATIS are still in the commradio.cxx source 
file, but can easily be moved into separate files and used from anywhere 
else.
I'll try to add spoken ATIS to the navradio before the feature freeze 
and hope we get apt.dat fixed, too.
>
>   The aforementioned ATC process should also handle things
>   like reversible ILS, tower-controlled runway lights, pilot-
>   controlled runway lights, et cetera.
That's another story.
>
>   Given that people are busy revamping the ATIS code, it
>   might be timely to think again about the big picture.

Thinking,
Torsten
>