On Apr 8, 2010, at 4:09 PM, Martin Spott wrote: > Peter Brown wrote: > >> 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. > > .... or from the navaids. > >> 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. > > "They" are certainly going to keep the true heading in the navaid file, > because the magnetic heading is changing permanently and therefore is a > moving target. The navaids collection is meant to place the navaids at > their proper location in an unambiguous way - which obviously is the > true heading. > > BTW, feel free to use this service if your're looking for slightly more > complete airfield data: > > > http://mapserver.flightgear.org/ms?Service=WFS&Version=1.0.0&request=GetFeature&Typename=apt_airfield&MaxFeatures=1&Filter=<Filter><PropertyIsEqualTo><PropertyName>icao</PropertyName><Literal>KBTV</Literal></PropertyIsEqualTo></Filter> > > .... still processing. > > Cheers, > Martin. > --
I have no reason to take it out, but I see no reason to not compile a list of approach plate data that the mpmap can retrieve usable data from either, if you don't want to add it to the navaids file. Is there any reason not to? Peter ------------------------------------------------------------------------------ Download Intel® 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
