Rick Ansell [EMAIL PROTECTED] wrote:
[...] Then merge in data from X-Plane adding any
missing airports and any taxiway data ... taking care to avoid
airports that might still be in the X-Plane data set but have since
been plowed under by progress.
It might be worth doing something other than
The scripting process proposed is exactly what I do to generate the X-Plane
data from the DAIF source:
- Identify airports in the X-Plane database that are not in the DAFIF data.
- Add this X-Plane data to the DAFIF airport/runway data.
- Then add all the X-Plane taxiway data to airports sourced
James Turner wrote:
Sorry to muck people (esp David, by the sound of it) around, but I have
'live' DAFIFT importing working in my local tree (for about 3 weeks
now), I've just been holding off submitting while I did more testing.
Anyway, the other relevant point (I suppose) is that my
James Turner writes:
Sorry to muck people (esp David, by the sound of it) around, but I have
'live' DAFIFT importing working in my local tree (for about 3 weeks
now), I've just been holding off submitting while I did more testing.
I've had to extend the Nav types and APIs slightly, to
On Friday, February 21, 2003, at 02:27 pm, David Megginson wrote:
1. For VORs, we're interested in the slaved magnetic variation; you
can always ignore the actual one, since we calculate that inside
FlightGear anyway.
Already done
2. Entries for TACANs have only a channel, not a
James Turner writes:
2. Entries for TACANs have only a channel, not a paired VHF
frequency. By trial and error, I've figured out how to get the VHF
(I think):
snipped scary conversion
Err, I'm not sure this is correct. the VORTACs have an explicit
frequency as well as a
David Megginson writes:
On the contrary, I will be thrilled to remove this from my TODO list
and to throw out my Perl scripts. Before I do that, I'll mention a
few gotchas I found in the NAV file and how I dealt with them:
1. For VORs, we're interested in the slaved magnetic variation; you
James Turner writes:
Supporting new types is trivial. I would greatly prefer to switch the
airport data over too, simply for consistency in the data set. Can
anyone establish what (if anything we would lose by doing so?)
The DAFIFT doesn't have taxiway data. Beyond that, it would be
On Friday, February 21, 2003, at 03:23 pm, Curtis L. Olson wrote:
The DAFIFT doesn't have taxiway data. Beyond that, it would be
interesting to compare the X-Plane data set vs. DAFIFT to see what
airport X-Plane has that are not in DAFIFT. Much of the X-Plane data
is hand entered, especially
James Turner writes:
On Friday, February 21, 2003, at 03:23 pm, Curtis L. Olson wrote:
The DAFIFT doesn't have taxiway data. Beyond that, it would be
interesting to compare the X-Plane data set vs. DAFIFT to see what
airport X-Plane has that are not in DAFIFT. Much of the X-Plane data
Curtis L. Olson [EMAIL PROTECTED] wrote:
This may work ok. But, yes it will be additional effort to merge the
data, eliminate duplicates, resolve errors and discrepancies, etc.
X-Plane is continually upgrading their taxiway data, so it might be
nice to have a script that will start with
Martin Spott writes:
I think merging this stuff has been on Robin's TODO for quite some
time - but he did not manag to to it because apparently this
requires a huge amound of manual editing,
A simple either/or merge is manageable -- probably a day's work. The
trick is to apply some
12 matches
Mail list logo
