Curtis L. Olson writes:
The one area to be careful of is airports, runways, and taxiways of
course. I'd hate to lose a lot of the hand edited data from X-Plane
for airports that aren't available in DAFIFT (and for all the
taxiways.)
Agreed -- we should stick to ILS, navaids, and fixes
Curtis L. Olson writes:
That might be the thing to do. Fixes are something I'd have no
hesitation to switching to DAFIFT format.
We should also consider whether we want to compress the DAFIFT files.
They take much more disk space uncompressed, but presumably CVS
updates would be
On Friday, February 21, 2003, at 02:12 pm, David Megginson wrote:
We should also consider whether we want to compress the DAFIFT files.
They take much more disk space uncompressed, but presumably CVS
updates would be significantly faster, since they would exchange only
deltas (or does the
James Turner writes:
On Friday, February 21, 2003, at 02:12 pm, David Megginson wrote:
We should also consider whether we want to compress the DAFIFT files.
They take much more disk space uncompressed, but presumably CVS
updates would be significantly faster, since they would exchange
On Fri, 21 Feb 2003, David Megginson wrote:
Curtis L. Olson writes:
The one area to be careful of is airports, runways, and taxiways of
course. I'd hate to lose a lot of the hand edited data from X-Plane
for airports that aren't available in DAFIFT (and for all the
taxiways.)
On Fri, 21 Feb 2003, David Megginson wrote:
Curtis L. Olson writes:
That might be the thing to do. Fixes are something I'd have no
hesitation to switching to DAFIFT format.
We should also consider whether we want to compress the DAFIFT files.
They take much more disk space
Jon Stockill writes:
We should also consider whether we want to compress the DAFIFT files.
They take much more disk space uncompressed, but presumably CVS
updates would be significantly faster, since they would exchange only
deltas (or does the whole file come anyway?).
AIUI you'd get
Jon Stockill writes:
On Fri, 21 Feb 2003, David Megginson wrote:
Curtis L. Olson writes:
The one area to be careful of is airports, runways, and taxiways of
course. I'd hate to lose a lot of the hand edited data from X-Plane
for airports that aren't available in DAFIFT (and for
Jon Stockill writes:
AIUI you'd get the whole file if it was compressed, because it's a binary
file, where you'd just get diffs if it's left as text.
I was pretty sure that that was the case, as well, but I'm concerned
that sometimes CVS sends the whole file anyway. Are there any CVS
Jon Stockill writes:
The problem you have in using different sources for ILS and runways is
that the two may not always line up.
As far as I know, Robin takes the ILS positions from published sources
rather than manually tweaking them to line up with his runways.
All the best,
David
--
I'm currently checking new files Navaids/default.nav.gz and
Navaids/default.fix.gz into the base package. These are generated
directly from DAFIF files (I've checked in my Perl scripts as well),
so they will be easy to keep up to date. The navaids file is a
moderate improvement, adding a couple
David,
In the spirit of keeping code separate from data, would it make sense
to put the scripts somewhere in the source tree? Maybe scripts/ or
src/Navaids/?
Curt.
David Megginson writes:
I'm currently checking new files Navaids/default.nav.gz and
Navaids/default.fix.gz into the base
Curtis L. Olson writes:
David,
In the spirit of keeping code separate from data, would it make sense
to put the scripts somewhere in the source tree? Maybe scripts/ or
src/Navaids/?
I should also say this really cool to be able to incorporate this data
directly. In terms of fixes though
Curtis L. Olson writes:
In the spirit of keeping code separate from data, would it make sense
to put the scripts somewhere in the source tree? Maybe scripts/ or
src/Navaids/?
Sure -- I just dumped them there for now. Someone suggested earlier
that we should modify FlightGear to read the
Curtis L. Olson writes:
I should also say this really cool to be able to incorporate this data
directly. In terms of fixes though 72000 is an insane amount. For
anyone wanting to actaully draw these on a map, there is going to have
to be some sort of data reduction strategy. Does the
David Megginson writes:
Sure -- I just dumped them there for now. Someone suggested earlier
that we should modify FlightGear to read the DAFIFT format directly,
and I think that's a good idea; at that point, the scripts would be
obsolete.
I think this is a great idea ... that makes it easier
David Megginson writes:
Different intersections and fixes server different purposes: the ones
around KSFO are probably parts of various instrument approaches, and
we would need most or all of them to simulate ATC or an
approach-certified GPS. Just around Ottawa TCA, we have quite a few
17 matches
Mail list logo
