AI Traffic: Difference between revisions

Jump to navigation Jump to search

AI Traffic (view source)

Revision as of 20:03, 23 January 2009

89 bytes removed ,  23 January 2009
no edit summary
No edit summary
Line 158: Line 158:
* '''<radius>''' An estimate of the aircraft's size. This is mainly used at airports for gate assignments.
* '''<radius>''' An estimate of the aircraft's size. This is mainly used at airports for gate assignments.
* '''<flighttype>''' In the near future, this keyword will be used for runway assignments, so that general aviation, commercial, and military traffic will use different runways if that is part of the airport's operational procedures. This line is also used for gate assignments and should be one of the following:
* '''<flighttype>''' In the near future, this keyword will be used for runway assignments, so that general aviation, commercial, and military traffic will use different runways if that is part of the airport's operational procedures. This line is also used for gate assignments and should be one of the following:
** '''ga''' (general aviation),  
** '''ga'''           (general aviation),  
** '''cargo''' (cargo)
** '''cargo'''         (cargo)
** '''gate''' (commercial passenger traffic)  
** '''gate'''         (commercial passenger traffic)  
** In addtion, it is expected that a '''mil''' value will be valid sometime soon.
** '''mil-fighter'''  (military fighter)
** '''mil-cargo'''     (military transport)
* '''<performance-class>''' This line is used to determine the performance characteristics of AI aircraft. This should match one of the performance classes that are predefined in FlightGear. Currently, the following performance classes are supported:
* '''<performance-class>''' This line is used to determine the performance characteristics of AI aircraft. This should match one of the performance classes that are predefined in FlightGear. Currently, the following performance classes are supported:
** '''light_aircraft''' (prop driven single or twin),
** '''light_aircraft''' (prop driven single or twin),
Line 240: Line 241:
Secondly, the author of the traffic manager code has written some scripts, mainly for private use,  that will allow one to input the flight data into a simple text format and then convert the resulting text file to xml. These scrips are not available yet, because they haven't been tested well enough for general use, but that is likely to change in the not too distant future.  
Secondly, the author of the traffic manager code has written some scripts, mainly for private use,  that will allow one to input the flight data into a simple text format and then convert the resulting text file to xml. These scrips are not available yet, because they haven't been tested well enough for general use, but that is likely to change in the not too distant future.  


'''Documentation updated until here.'''
 
= Ground networks =
= Ground networks =


Line 246: Line 247:


For example, see the ground network for EHAM, which is found in <tt>data/Airports/AI/EHAM/parking.xml</tt>. See the end of this page for a small  
For example, see the ground network for EHAM, which is found in <tt>data/Airports/AI/EHAM/parking.xml</tt>. See the end of this page for a small  
excerpt from this file. It should be noted that current development work is planned that aims to move these files from the base package to the scenery repository, so that ground network information and the physical layout of the airport can be updated in parallel. Once this is done, the new location / name for the file will be [fg-scenery]/Airports/[ICAO1]/[ICAO2]/[ICA03]/[ICAO].groundnetwork.xml. Here [ICAO] stands for the 4 letter ICAO code of the airport in question, and [ICAO1], [ICAO2], and [ICAO3] for the first to third letter of this code. This move is expected to be finished in the Winter/Spring of 2009.
excerpt from this file. It should be noted that current development work is planned that aims to move these files from the base package to the scenery repository, so that ground network information and the physical layout of the airport can be updated in parallel. Once this is done, the new location / name for the file will be [fg-scenery]/Airports/[ICAO1]/[ICAO2]/[ICA03]/[ICAO].ground-network.xml. Here [ICAO] stands for the 4 letter ICAO code of the airport in question, and [ICAO1], [ICAO2], and [ICAO3] for the first to third letter of this code. This move is expected to be finished in the Winter/Spring of 2009.


== A technical perspective ==  
== A technical perspective ==  
Line 261: Line 262:
segments to link the startup location and the taxiways together. Parkings and  
segments to link the startup location and the taxiways together. Parkings and  
AI nodes have the following parameters:  
AI nodes have the following parameters:  
* index (unique, consecutively numbered id)
* '''index     (unique, consecutively numbered id)
* lat (position in latitude)
* '''lat'''    (position in latitude)
* lon (position in longitude)
* '''lon'''    (position in longitude)
* name (name as found on airport charts: e.g. D23, or C1).  
* '''name'''  (name as found on airport charts: e.g. D23, or C1).  
* number


The name parameter is currently used by flightgear only for the Parking names.  will be used in future ATC, but AINode names will probably not be used except for some specific internal functions.
airlineCodes= list any (comma separated) ICAO airline codes here to specify
which airlines are allowed here.
* pushBack (used to determine whether departing aircraft can make left or right
turns after pushback


In addition, each parking has a number of additional parameters:
In addition, each parking has a number of additional parameters:
* '''type:''' specifies what type of aircraft can use this parking bay: Valid values for this parameter are: ''cargo, gate'' (=usually intermediate to heavy airline traffic), ''ramp'' (=usually smaller regional jets and commuter aircraft), ''ga'' (=general aviation), and ''mil'' (=military). See the description of the '''<flighttype>''' parameter in the traffic pattern description above for a comparison.
* '''type:''' specifies what type of aircraft can use this parking bay. See the description of the '''<flighttype>''' parameter in the traffic pattern description above for a comparison. Valid values for this parameter are:  
* '''number:''' Currently unused, and likely to be removed.
** '''ga'''           (general aviation),  
* '''heading:''' the heading the aircraft parked in this bay.
** '''cargo'''        (cargo)
*'''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.
** '''gate'''         (commercial passenger traffic)  
** '''mil-fighter'''  (military fighter)
** '''mil-cargo'''     (military transport)
 
 
* '''number:''' Currently used in combination with the <name> parameter to determine the full name of the gate.
* '''heading:''' The heading at which the aircraft are parked in this bay.
*'''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.
*'''pushBack:''' Currently unused.
*'''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, this simulating being pushed back.
 
'''Documentation updated until here.'''


Finally, the taxiway segments contain three parameters.  
Finally, the taxiway segments contain three parameters.  
Durk
117

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/10474"

Navigation menu