Flightplan XML formats: Difference between revisions

m
Header cleanup: No real need for the Property-list header, it's already implied by the ingress
(Extending)
m (Header cleanup: No real need for the Property-list header, it's already implied by the ingress)
Line 1: Line 1:
FlightGear can use '''flightplans''' stored in property-list xml files.
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 ==
=== AI Flightplans ===
:''See also [[AI Scenarios#Flightplans and Their Waypoints]].''
:''See also [[AI Scenarios#Flightplans and Their Waypoints]].''


These flightplans contain only waypoints.
These flightplans contain only waypoints.


==== Waypoint tags ====
=== Waypoint tags ===
Each waypoint can contain the following 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>'''<name>'''</tt> - Waypoint name, if it is the last waypoint use EOF or, if you want the AI model deleted, END.
Line 19: Line 18:
* <tt>'''<flaps-down>'''</tt> - True for flaps down, false for flaps up, or 0 to 1
* <tt>'''<flaps-down>'''</tt> - True for flaps down, false for flaps up, or 0 to 1


==== Example ====
=== Example ===
<syntaxhighlight lang="xml">
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<?xml version="1.0"?>
Line 42: Line 41:
</syntaxhighlight>
</syntaxhighlight>


=== Route manager flightplans ===
== Route manager flightplans ==
:''See also [[Route manager#Defining a Route]].''
:''See also [[Route manager#Defining a Route]].''


Line 51: Line 50:
There are in FlightGear support for Level-D 767 SIDs and STARs.
There are in FlightGear support for Level-D 767 SIDs and STARs.


==== Departure and destination tags ====
=== Departure and destination tags ===
* <tt>'''<airport type="string">'''</tt> - The ICAO identifier of the airport
* <tt>'''<airport type="string">'''</tt> - The ICAO identifier of the airport
* <tt>'''<sid type="string">'''</tt> - Any available SID
* <tt>'''<sid type="string">'''</tt> - Any available SID
Line 58: Line 57:
* <tt>'''<runway type="string">'''</tt> - Departure or destination runway
* <tt>'''<runway type="string">'''</tt> - Departure or destination runway


==== Waypoint types and tags ====
=== Waypoint types and tags ===
* <tt>'''runway'''</tt> - The runway end on the departure and destination airports. Accompanied by the <icao> tag.
* <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>'''navaid'''</tt> - Any significant point along the route. Both airports, navaids and fixes.
Line 73: Line 72:
* <tt>'''<distance-nm type="double">'''</tt> -  
* <tt>'''<distance-nm type="double">'''</tt> -  


=== Example ===
<syntaxhighlight lang="xml">
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<?xml version="1.0"?>