On Apr 8, 2010, at 1:29 PM, David Megginson wrote:

> On Thu, Apr 8, 2010 at 11:32 AM, Peter Brown
> <smoothwater...@adelphia.net> wrote:
> 
>> David, yes, as I have as well.  The localizer for 33 as you listed above is 
>> on a 326 heading per the approach plate, but the mpmap shows ILS data as the 
>> runway heading in degrees - as if for users to use as the ILS data.  I'm not 
>> sure what the 342 in the navaid file is referring to unless it's 
>> elevation?... elev. is 335, course is 326.  (ref: 
>> http://flightaware.com/resources/airport/BTV/IAP/ILS_DME+RWY+33/pdf)
> 
> The plates give the heading in degrees magnetic; the data file gives
> it in degrees true.  That's still a degree off (BTV is 15W, IIRC), but
> it's pretty close, and nav.data.gz may be based on old data.
> 
> 
> All the best,
> 
> 
> David
> 

I see.  So that brings us back to magnetic vs true, as I was originally 
referring to.  But, that's somewhat irrevelant as it _appears_ the mpmap is 
sourcing the data from the actual runway placement.  My opinion is there should 
be an data file with the correct info to be displayed, and it seems logical for 
it to be the navaid file, but we'd need to add a line if they want to keep the 
true heading.

Thanks,
Peter
------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to