Ron Jensen > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:flightgear- > [EMAIL PROTECTED] On Behalf Of > Sent: 02 June 2006 04:29 > To: FlightGear developers discussions > Subject: Re: [Flightgear-devel] fgmap navaids > > On Fri, 2006-06-02 at 11:04 +1000, Pigeon wrote: > > > The only thing that I'm missing now is TACAN. It > > > would be really great (and a slight improvement on Atlas) if the TACAN > > > channel for a suitably equipped airfield was shown. > > > > I have just noticed I have sorta misinterpreted some of the nav data > > regarding TACAN, i.e. at the moment all the TACAN are missing on the > > map. I will look into this soon. And perhaps I shall ask you or Vivian > > on IRC later on about any specifics I needed to know. > > > > Can we get TACAN channel assignments fixed while you're at it? > Currently the TACAN system assigns random, bogus channels that don't > jive with the real world nav data. I had a simple fix but Vivian > thought it was a 'hack'. >
I'm more than willing to be corrected on this one, but my understanding is as follows: A VORTAC station has 3 frequencies in RL - TACAN, VOR, and DME. In FG nav.dat only the VOR and DME are held. Thus it is a fix in the case of VORTAC to misalign the TACAN channel/frequency pairing to the VOR frequency in stead of the TACAN frequency. Unfortunately, there are other stations in the world which are TACAN only, which seem to have the correct TACAN frequency assigned: Flesland TACAN is one such example. Thus we fix the VORTAC at the expense of the TACAN. The correct fix is to modify nav.dat to show all 3 frequencies for the VORTAC stations. As I say, I think this is the case ... Vivian _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
