Jorge Van Hemelryck writes:

> On Mon, 01 Mar 2004 13:55:43 +0000
> David Luff wrote:
> 
> > This should now be fixed.  The cause of the problem was that LFMI and LFMY
> > have a common tower frequency (122.1), but the commlist code was returning
> > the first in-range match rather the closest match when initialising the
> > tower, resulting in logical inconsistencies.  I guess that none of the
> > airports I originally tested the code at share a frequency with any of
> > their neighbours.
> 
> Actually, it's one of the common NATO frequencies. These are usually
> listed as Tower frequencies, but used mostly as Ground control. As LFMI
> and LFMY are both military airfields, they share this frequency, but of
> course they have many others as well (including UHF frequencies). If you
> like, I can check which frequencies are to be used by civilian aircraft
> there. Who maintains these files ?
> 

Currently the frequencies listed for LFMI and LFMY are:

LFMI:
Tower 122.1
Tower 123.6
Tower 257.8
Tower 356.32

LFMY:
Tower 122.1
Tower 135.15
Tower 141.25
Tower 257.8
Tower 275.45

I generated them from the DAFIF data, you (and others) can send corrections, additions 
and clarifications to me and I'll store them and apply them each time the files are 
regenerated.  So far I've only generated tower and ATIS frequencies, so I don't know 
if any of the listed tower frequencies would also be in the DAFIF data as ground as 
well.  As for which frequencies would be most likely to be used by civilian traffic, 
that's rather a can of worms at the moment.  Each airport in Robin Peel's data should 
be flagged either military or civil, but at the moment it appears that they are all 
listed as civil.  In the case of mixed use airports (or military airports that allow 
civilian traffic) I'm not sure how to store the information regarding which 
frequencies are most likely to be used for civilian traffic etc.  Eventually I think 
that each airport will have a corresponding xml file with things like tower closing 
times, preferred circuit directions and runways etc, and other stuff like preferred 
frequencies for a given use could go into it, but it's not implemented yet.

Cheers - Dave

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

Reply via email to