185
edits
AI Traffic: Difference between revisions
m
→Tools: spelling, capitalization
m (→Putting it all together: Including a traffic file: capitalize proper name, fix spelling mistakes, other minor fixes) |
m (→Tools: spelling, capitalization) |
||
| Line 233: | Line 233: | ||
== Tools == | == Tools == | ||
One major motivation for introducing the | One major motivation for introducing the Traffic Manager II file format is to make it easier for FlightGear users to contribute to the traffic database. To further motivate this, some tools are currently in development that aim to make user interaction even easier. Although most of these tools are not ready for public use yet, it is probably worth mentioning some of these developments. First of all, the custom scenery project is working on extending their scenemodel database to store traffic. A web based front end will allow users to enter their favorite flight, and thus collect an extensive amount of traffic data. Users will be able to download the collected results and place the downloaded files in their traffic directory or get it via Terrasync. | ||
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 | 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. The most important of these scripts can be found in the FlightGear source package under scripts/perl/traffic/. | ||
Creating AI traffic files this way is easy. First, you need to define the aircraft for each fleet (data taken from the June 2010 | Creating AI traffic files this way is easy. First, you need to define the aircraft for each fleet (data taken from the June 2010 Malaysian project): | ||
###HOMEP RegNo TypeCode Type AirLine Livery Offset Radius FltType Perf.Class Heavy Model | ###HOMEP RegNo TypeCode Type AirLine Livery Offset Radius FltType Perf.Class Heavy Model | ||
| Line 268: | Line 268: | ||
- The last entry in each line (A/C type) should correspond to the ''combination'' of the '''TypeCode''' and '''Airline''' entries in the aircraft sections. | - The last entry in each line (A/C type) should correspond to the ''combination'' of the '''TypeCode''' and '''Airline''' entries in the aircraft sections. | ||
The resulting table can now easily be converted to | The resulting table can now easily be converted to XML output by running the conf2xml.pl (conv2xml.pl - check) script. | ||
For Operating Systems of the Unix family, simply run conf2xml.pl from the directory where you unpacked the trafficdata.zip archive: | For Operating Systems of the Unix family, simply run conf2xml.pl from the directory where you unpacked the trafficdata.zip archive: | ||
| Line 284: | Line 284: | ||
When the script encounters an error, it will stop prematurely. | When the script encounters an error, it will stop prematurely. | ||
The [[AI Schedule | The [[AI Schedule Manager]] is a GUI based application that uses a database backend to store and perform operations on flights, fleets and aircraft for airlines. | ||
== Ground networks == | == Ground networks == | ||