Hi James,
James Turner wrote:
>
> On 27 Oct 2009, at 23:58, Martin Spott wrote:
>
>> Thanks for pointing out ! I'm going to investigate and comment as soon
>> as my (spare) time permits,
>
> Just to add, Anders and I discussed my loading code on IRC, and it's
> definitely possible I am mis-interpreting some of the values in
> threshold.xml - especially relating to the displaced threshold value.
According to the AptNav specs, the displaced threshold "is included in
implied runway length". To me it looks like, in contrast, you are
adding the displaced threshold to the given runway length, which is not
required here.
>From my experience I'd say, simply ignore the displaced threshold for
startup position calculations - I suspect this is the way it has been
in FlightGear all the time. The way I learnt it, the startup run starts
at the beginning of the entire runway, anyway, no matter if they have a
displaced threshold or not.
This is different from the stopway/blastway which typically is not
readily prepared (cleaned and checked) for aircraft movements.
To my understanding there's just a little offset in startup direction
added to the runway center endpoint at the startup position
calculations to make sure that all aircraft wheels are getting situated
onto the tarmac.
Best regards,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
