117
edits
Line 349: | Line 349: | ||
The '''<flights>''' section is slightly more complex than the aircraft definition itself, because it has a few nested levels. The following keywords should be specified: | The '''<flights>''' section is slightly more complex than the aircraft definition itself, because it has a few nested levels. The following keywords should be specified: | ||
* '''<flight>''' All the relevant parameter should be specified between the '''<flight></flight>''' keywords. | |||
'''<flight>''' All the relevant parameter should be specified between the '''<flight></flight>''' keywords. | * '''<callsign>''' The airline callsign used for ATC. If this is an airline flight it should be combination of the airline callsign (e.g. '''KLM''' for KLM, or '''Springbok''' for South African Airways), and the flight number (e.g. '''KLM0605''', or '''Springbok0033'''). | ||
* '''<fltrules>''' Can be ''IFR'' or ''VFR''. This is required or use in ATC, but currently not used. This is likely to change, however. | |||
'''<callsign>''' The airline callsign used for ATC. If this is an airline flight it should be combination of the airline callsign (e.g. '''KLM''' for KLM, or '''Springbok''' for South African Airways), and the flight number (e.g. '''KLM0605''', or ''' | * '''<departure>''' Definition of the departure airport. This section should contain the '''<port>''' and '''<time>''' keywords. | ||
* '''<cruise-alt>''' Cruising altitude for this flight. This is a bit of a simplyfication from the real world, where aircraft usually don't stay at the same cruise altitude throughout the flight. This behavior will probably also change in future versions. | |||
'''<fltrules>''' Can be ''IFR'' or ''VFR''. This is required or use in ATC, but currently not used | * '''<arrival>''' Same as '''<departure>''', but now defining the port of arrival. | ||
* '''<repeat>''' Repeat period. This can be either the keyword ''WEEK'', or a number followed by ''Hr''. ''WEEK'' means that the whole schedule repeats itself on a weekly basis. ''Hr'' means that the whole schedule repeats after the number of hours specified directly before it (e.g. ''24Hr'' means that the schedule repeats after 24 hours). | |||
'''<departure>''' Definition of the departure airport. This section should contain the '''<port>''' and '''<time>''' keywords. | * '''<port>''' This should be the international ICAO airport code. This keyword should be specified only within the '''<departure>''' or '''<arrival>''' sections. As far as I know, here it should still be in upper case, although the FlightGear command line currently also supports lower case ICAO codes. | ||
* '''<time>''' Used to specify the '''<departure>''' or '''<arrival>''' time. The format of this string is ''hour:minute:second''. Notice that departure day is optional and is specifically intended to be used in combination with a weekly repeating schedule. When used in combination with other schedules, results may be unpredicatble. Times should be in UTC. Weekdays start at sunday (0) and end at saturday (6). | |||
'''<cruise-alt>''' Cruising altitude for this flight. This is a bit of a simplyfication from the real world, where aircraft usually don't stay at the same cruise altitude throughout the flight. This behavior will probably also change in future versions. | |||
'''<arrival>''' Same as '''<departure>''', but now defining the port of arrival. | |||
'''<repeat>''' Repeat period. This can be either the keyword ''WEEK'', or a number followed by ''Hr''. ''WEEK'' means that the whole schedule repeats itself on a weekly basis. ''Hr'' means that the whole schedule repeats after the number of hours specified directly before it (e.g. ''24Hr'' means that the schedule repeats after 24 hours). | |||
'''<port>''' This should be the international ICAO airport code. This keyword should be specified only within the '''<departure>''' or '''<arrival>''' sections. As far as I know, here it should still be in upper case, although the FlightGear command line currently also supports lower case ICAO codes. | |||
'''<time>''' Used to specify the '''<departure>''' or '''<arrival>''' time. The format of this string is ''hour:minute:second''. Notice that departure day is optional and is specifically intended to be used in combination with a weekly repeating schedule. When used in combination with other schedules, results may be unpredicatble. Times should be in UTC. Weekdays start at sunday (0) and end at saturday (6). | |||
== Putting it all together: Including a traffic file == | == Putting it all together: Including a traffic file == |
edits