117
edits
AI Traffic: Difference between revisions
Jump to navigation
Jump to search
→A technical perspective
No edit summary |
|||
| Line 281: | Line 281: | ||
*'''radius:''' A value used to determine whether the aircaft will fit in this bay: see also the description of the '''<radius>''' parameter in the traffic pattern description above. FlightGear uses a standard list of [[aircraft radii]] for gate assignment. | *'''radius:''' A value used to determine whether the aircaft will fit in this bay: see also the description of the '''<radius>''' parameter in the traffic pattern description above. FlightGear uses a standard list of [[aircraft radii]] for gate assignment. | ||
*'''airlineCodes:''' a comma-separated list of ICAO airline codes used to indicate which airlines should park here. Leave this field blank if you want any aircraft to park here. | *'''airlineCodes:''' a comma-separated list of ICAO airline codes used to indicate which airlines should park here. Leave this field blank if you want any aircraft to park here. | ||
*'''pushBackRoute:''' A number that refers to another node in the network. In a correctly configured network, the AI aircraft will taxi to this node in reverse, | *'''pushBackRoute:''' A number that refers to another node in the network. In a correctly configured network, the AI aircraft will taxi to this node in reverse, thus simulating being pushed back. See the documentation for the PushBack hold point type below. | ||
''' | Taxiway nodes contain two additional parameters: | ||
* '''isOnRunway'''' A logical value that is 1 when the node is on the runway, or 0 otherwise | |||
* '''holdPointType''' Describes wether the current point should be considered a holding point. This parameter can have the following values: | |||
** '''none''' No holding point | |||
** '''normal''' A regular holding point. This point should be placed just before the runway entrance / exit points, so that traffic will not enter the runway before receiving clearance to enter the runway. Note that support for this type of holding point is not implemented yet, but should appear sometime during 2009. | |||
** '''CAT II/III''' A special holding point for IFR conditions. Currently not supported yet. | |||
** '''PushBack''' A push back hold point type. Each parking can be connected to maximally one push back point, connected through a series of push back routes. Note that a push back point is optional, but that there can maximally only be one connected to each gate. | |||
Finally, the taxiway segments contain three parameters. | Finally, the taxiway segments contain three parameters. | ||
* '''begin''' | * '''begin''' The id of the parking or AINode where this segment starts | ||
* '''end''' | * '''end''' The id of the parking or AINode where this segment ends | ||
* '''name''' | * '''IsPushBackRoute''' a logical value. Should be one if the current segment is part of a route connecting a gate to a push back hold point, or 0 otherwise. | ||
* '''name''' Name of the taxiway. | |||
== Creating a ground network, a practical approach == | == Creating a ground network, a practical approach == | ||