Jump to: navigation, search

Flightplan XML formats

108 bytes added, 15:07, 15 August 2013
Header cleanup: No real need for the Property-list header, it's already implied by the ingress
FlightGear can use '''flightplans''' stored in property-list xml files. Due to having different needs the flightplans used in the route manager and the ones used in AI scenarios have different formats.
== Property-list format ===== AI Flightplans =flightplans ==
:''See also [[AI Scenarios#Flightplans and Their Waypoints]].''
These flightplans contain only waypoints.
==== Waypoint tags ====
Each waypoint can contain the following tags:
* <tt>'''<name>'''</tt> - Waypoint name, if it is the last waypoint use EOF or, if you want the AI model deleted, END.
* <tt>'''<flaps-down>'''</tt> - True for flaps down, false for flaps up, or 0 to 1
==== Example ====
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
=== Route manager flightplans ===
:''See also [[Route manager#Defining a Route]].''
There are in FlightGear support for Level-D 767 SIDs and STARs.
==== Departure and destination tags ====
* <tt>'''<airport type="string">'''</tt> - The ICAO identifier of the airport
* <tt>'''<sid type="string">'''</tt> - Any available SID
* <tt>'''<runway type="string">'''</tt> - Departure or destination runway
==== Waypoint types and tags ====
* <tt>'''runway'''</tt> - The runway end on the departure and destination airports. Accompanied by the <icao> tag.
* <tt>'''navaid'''</tt> - Any significant point along the route. Both airports, navaids and fixes.
* <tt>'''<distance-nm type="double">'''</tt> -
=== Example ===
<syntaxhighlight lang="xml">
<?xml version="1.0"?>

Navigation menu