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
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
Curtis L. Olson writes:
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. :-(
We have to decide on the authority of each data point individually.
Anything that we get from the DAFIF
David Megginson writes:
We have to decide on the authority of each data point individually.
Anything that we get from the DAFIF or FAA data should stand as-is,
for example. For Robin Peel's data, we should fix things only when
there is a known problem.
The problem is that in my spot
Curtis L. Olson writes:
I don't know if either DAFIF or FAA could be considered
authoritative.
I'd consider FAA authoritative for U.S. airports, and DAFIF for other
countries, again, until proven otherwise.
I'm guessing that when an ILS is installed, someone goes out and
stands at the
