On 04/07/2010 07:06 PM, Peter Brown wrote: > Perhaps this has been brought up before, but I see that the ILS > "beam" data for each airport on the mpmap is derived from the runway > alignment (as verified in taxidraw).
That sounds like a problem. > This doesn't allow for magnetic > deviation, and therefore all the course headings are incorrect. That is the wrong way to think about the problem. This is basically a geodesy problem. It should be worked using true headings, true lat/lon, et cetera. The question of magnetic variation should never come up in this context. > I have not looked at the 850 airport format, but is there a way in > any of the apt.dat or nav data to specify ILS approach data > accurately? The navaid data is accurate. The 830 and 850 formats are equivalently accurate. > Or is this a question for Pigeon, to see about using a > different data list? There is no need for that. The existing nav.dat data is plenty good enough. The existing FGFS code handles this correctly, except in the case of "reversible ILS" installations. Perhaps mpmap could just clone this code. Also, the code to handle reversible ILSs in a reasonable way exists in the sport model. It has been available for many months, as previously discussed. Let me know if you are interested. Or take a look at http://gitorious.org/~jsd/fg/sport-model/commits/sport This is an issue for more than 20% of all ILS installations in the US and UK ... and more than 10% worldwide. ------------------------------------------------------------------------------ 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
