On 1/15/03 at 6:20 PM Bernie Bright wrote:
>On Wed, 15 Jan 2003 01:45:30 +
>"David Luff" <[EMAIL PROTECTED]> wrote:
>
>[snip]
>
>> ... FWIW I'm currently writing a
>> program to allow the laying out of a logical taxiway and parking place
>> network for AI planes to follow over an image of Fli
Jon Stockill writes:
> > Then, late, you can specify rules for which ones get included or
> > excluded in a build (i.e. the DAFIF KSFO and the X-Plane KSFO are
> > treated as different, mutually-exclusive airports).
>
> Hmmm It seems like that's just putting off the problem - but it woul
David Luff writes:
> Yes, the x-plane way really screws the rendering up now that yellow
> lines are added. However, the amount of work that has gone into
> specifying the taxiways and aprons at major airports must be *huge*
> - it would take a long time to replicate it with a better system.
On Tue, 14 Jan 2003, David Megginson wrote:
> Then, late, you can specify rules for which ones get included or
> excluded in a build (i.e. the DAFIF KSFO and the X-Plane KSFO are
> treated as different, mutually-exclusive airports).
Hmmm It seems like that's just putting off the problem - but
On Tue, 14 Jan 2003, David Megginson wrote:
> We also have fields for this information in the current default.apt
> data, but they don't seem to be filled in.
Some of the UK ones certainly are.
EGNM for example.
--
Jon Stockill
[EMAIL PROTECTED]
__
On Wed, 15 Jan 2003 01:45:30 +
"David Luff" <[EMAIL PROTECTED]> wrote:
[snip]
> ... FWIW I'm currently writing a
> program to allow the laying out of a logical taxiway and parking place
> network for AI planes to follow over an image of Flightgear's rendered taxi
> and runways by clicking on
David Luff writes:
>
> I believe his intention/achievement
> is to allow the editing of scenery superimposed over calibrated maps or
> ariel photos, which would ease the task of getting the aprons/taxiways etc
> in the right place.
I can heartily reccomend two OpenSource packages for doing this
On 1/14/03 at 8:11 PM David Megginson wrote:
>For now, let's just get all the airports in. The way that X-Plane
>implements taxiways is just horrible -- aprons are just wide taxiways,
>for example, and taxiways are always rectangles run together. Perhaps
>we'll be able to think of a better system
David Luff writes:
> Yep, here's my stats from the program I ran to compare the databases when I
> imported the atis data:
>
> *** STATS ***
> 9873 airports in DAFIF
> 16937 airports in default.apt
> 1384 airports had K added to match default.apt
Also note that the Alaska and Hawaii airpo
On 1/15/03 at 12:39 AM Jon Stockill wrote:
>On the subject of runways - I've been working on the database today.
>
>I can import and export the xplane database, and have some code which
>parses the DAFIFT data, and compares it with the existing database,
>however:
>
>1. Not all airfields in the xp
Jon Stockill writes:
> I can import and export the xplane database, and have some code which
> parses the DAFIFT data, and compares it with the existing database,
> however:
>
> 1. Not all airfields in the xplane database are in DAFIF
> 2. Not all DAFIF airfields are in xplane
> therefore
David Luff writes:
> >David Luff writes:
> >> and I'd have thought that displaced thesholds and the arrows
> >> pointing to them would have to be pretty high on the list of
> >> features that would be expected to make it in.
> >
> >Do we actually have these in our airport data? If so (or if
On Tue, 14 Jan 2003, David Luff wrote:
> Got it. The Dafif has separate landing and takeoff distances for each
> direction of each runway, and on the airports/runways I've looked at (in
> the UK) these seem to correspond to the displaced thresholds. To be quite
> honest I never realised one cou
On 1/14/03 at 4:10 PM Curtis L. Olson wrote:
>David Luff writes:
>> and I'd have thought that displaced thesholds and the arrows
>> pointing to them would have to be pretty high on the list of
>> features that would be expected to make it in.
>
>Do we actually have these in our airport data? If s
14 matches
Mail list logo