On Wed, Jul 16, 2008 at 3:52 PM, Ralf Gerlich <[EMAIL PROTECTED]> wrote:
> No, the question is not really about taxidraw, but about genapts. It
> seems like genapts adds threshold markings (e.g. pa_threshold.rgb) to
> runways, which according apt.dat should have only visual markings.
> According to FAA AC 150/5340-1H (which is mentioned in rwy_visual.cxx),
> visual markings do not include threshold markings. According to that
> same sourcefile, you are the author of these functions.
>
> Did I miss something about that AC or is there a specific reason why
> threshold markings are included nevertheless in gen_visual_rwy?
>
It's been a long time but I believe the original intent of the code is that
precision and non-precision runways should have threshold markings, while
visual runways should not have them. By my best recollection, this is how
the code was designed and by my reading of the code, that is the way it
still works.
Do you have an example airport where this is broken?
Regards,
Curt.
--
Curtis Olson: http://baron.flightgear.org/~curt/
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
