David Megginson writes: > Curtis L. Olson writes: > > > Modified Files: > > default.ils.gz > > Log Message: > > Align all the approaches I could automatically match up to runways. > > Where we have exact data on the lat/lon of the localizer and GS, we > should use it, and fix our airport data if there's a discrepancy; > where we're just guessing, of course, we should do the > auto-correction.
The problem is that I have two data sets both providing "exact" locations for the localizer and both disagreeing significantly on the position and orientation. :-( Our runway data is really out of date and most of which is of unknown quality/origin. We *really* need to get our airport database updated from recent DAFIFT/FAA data first. Then we will have a better idea if our localizer positions are reasonable and we can come up with a better solution auto-aligning (or not) the localizers (or the runways.) Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities curt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
