86
edits
No edit summary |
|||
Line 9: | Line 9: | ||
== | == Traffic Files Location == | ||
Traffic patterns are stored in data files in extended markup language (.xml) format. The actual location of these files are version dependent. | Traffic patterns are stored in data files in extended markup language (.xml) format. The actual location of these files are version dependent. | ||
* FlightGear 0.9.x : <tt>[[$FG ROOT]]/Traffic/</tt> | |||
<tt>[[$FG ROOT]]/Traffic/</tt> | * FlightGear 1.0 : <tt>[[$FG ROOT]]/AI/Aircraft/</tt> | ||
* FlightGear 1.9.0 and subsequent versions : <tt>[[$FG ROOT]]/AI/Traffic/</tt> | |||
FlightGear 1.9.0 | |||
<tt>[[$FG ROOT]]/AI/Traffic/</tt> | |||
Traffic is organised by Operator in subfolders, using the initial of the operator's ICAO designator. For example, traffic for United Airlines is stored under <tt>[[$FG ROOT]]/AI/Traffic/U/UAL.xml | |||
A new traffic file format was introduced with FlightGear 1.9.0, referred to as "Traffic Manager II" format (TM-II), in which aircraft and flights are no longer directly coupled, leading to more flexibility. | |||
Each traffic pattern is built around two entities: Aircraft and Flights. Before discussing the details, lets start by exploring these two concepts a little further. | Each traffic pattern is built around two entities: Aircraft and Flights. Before discussing the details, lets start by exploring these two concepts a little further. | ||
edits