AI Traffic: Difference between revisions

Jump to navigation Jump to search
Line 579: Line 579:
= Runway Usage Configuration =  
= Runway Usage Configuration =  


ICAO.rwyuse.XML dictates which runway(s) should be used for AI take off and which ones accept AI landings. These instructions are organised in multiple sets (or configurations) and ordered by preference of use.
ICAO.rwyuse.xml dictates which runway(s) should be used for AI take off and which ones accept AI landings. These instructions are organised in multiple sets (or configurations) and ordered by preference of use.


Schedules can be defined so different runway configurations can be used at different time of the day. Different Sets can also be applied to the General Aviation and Commercial traffic.
Schedules can be defined so different runway configurations can be used at different time of the day. Different Sets can also be applied to the General Aviation and Commercial traffic.
Line 598: Line 598:
The < time > table defines the hours of activation for a particular Schedule. Each schedule contains a 'Pattern' ie a fixed number of runways allocated to either take off or landing).
The < time > table defines the hours of activation for a particular Schedule. Each schedule contains a 'Pattern' ie a fixed number of runways allocated to either take off or landing).


For instance, at EHAM, the commercial "inbound" schedule is active from 06:20 to 08h30 UTC, at a time where there is more inbound than outbound traffic and the airport needs to allocate more runways to landing than to take off.
For instance, at EHAM, the commercial "inbound" schedule is active from 06:20 to 08:30 UTC, at a time where there is more inbound than outbound traffic and the airport needs to allocate more runways to landing than to take off.


<syntaxhighlight lang="xml">
<syntaxhighlight lang="xml">
Line 629: Line 629:
</syntaxhighlight>
</syntaxhighlight>


Shall wind conditions prevent the use of this configuration (Tailwind or Crosswind values exeeding the ones defined in <wind> above), the next set (or “column”) will apply ie 24 for take-offs, and 18R + 18C for landings.
Shall wind conditions prevent the use of this configuration (Tailwind or Crosswind values exceeding the ones defined in <wind> above), the next set (or “column”) will apply ie 24 for take-offs, and 18R + 18C for landings.


Again, if wind conditions prevent this configuration use, the next set will be used (18L for take-offs, 18R and 18C for landing).
Again, if wind conditions prevent this configuration use, the next set will be used (18L for take-offs, 18R and 18C for landing).
Line 638: Line 638:


[https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAMbEsE46ontK4G43zmrEqLEk%3D8ZK5sQ-vxZup%3DNjpaUDgb-ASw%40mail.gmail.com/#msg37166996 Source from Durk post in Devel]
[https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAMbEsE46ontK4G43zmrEqLEk%3D8ZK5sQ-vxZup%3DNjpaUDgb-ASw%40mail.gmail.com/#msg37166996 Source from Durk post in Devel]


= Model Animation =
= Model Animation =
1,376

edits

Navigation menu