FlightGear wiki - User contributions [en]

Flightplan XML formats

2021-10-10T20:48:27Z

Psnarf: correct mis-matched tags - flaps and gear down

FlightGear use a few different '''flightplan XML formats''' stored in property-list xml files. Due to different needs the flightplans used in the route manager and AI scenarios and have different formats.

== AI flightplans ==
{{see also|AI Scenarios#Flightplans and Their Waypoints|AI groundvehicles#The flightplan}}

These flightplans contain only waypoints. By tying an AI flightplan to an AI model in a scenario xml file, an AI scenario will be created.

=== Waypoint tags ===
Each waypoint can contain the following tags:
{| class="wikitable"
! Tag !! Type !! Use !! Remarks
|-
| <code><name></code> || string || Waypoint name || The last waypoint use <code>EOF</code>, or if the AI model is to be deleted <code>END</code>.
|-
| <code><lat></code> || double || Latitude, decimal degrees ||
|-
| <code><lon></code> || double || Longitude, decimal degrees ||
|-
| <code><alt></code> || double || Altitude above mean sea level, feet ||
|-
| <code><crossat></code> || double || Crossing altitude, feet ||
|-
| <code><ktas></code> || double || True air speed, knots ||
|-
| <code><on-ground></code> || bool || Set to <code>true</code> or <code>1</code> if on ground

Set to <code>false</code> or <code>0</code> if in air or in a tunnel
|
|-
| <code><gear-down></code> || double || <code>true</code> for gear down

<code>false</code> for gear up
| Or any number between 0 and 1
|-
| <code><flaps-down></code> || double || <code>true</code> for flaps down

<code>false</code> for flaps up
| Or any number between 0 and 1
|}

=== Example ===
<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<PropertyList>
<flightplan>
<wpt>
<name>First!</name>
<lat>53.6762</lat>
<lon>-1.39984</lon>
<alt>1000</alt>
<ktas>120</ktas>
<on-ground>false</on-ground>
<gear-down>1</gear-down>
<flaps-down>0.25</flaps-down>
</wpt>
...
<wpt>
<name>END</name>
</wpt>
</flightplan>
</PropertyList>
</syntaxhighlight>

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

Route manager waypoints are a bit more complex, for starters they contain departure and destination information and not just one type of waypoint.

Note that the first and last waypoint are the departure and destination airports.

There is also support for Level-D 767 SID:s and STAR:s in FlightGear.

=== Departure and destination tags ===
{| class="wikitable"
! Tag !! Type !! Use !! Remarks
|-
| <code><airport></code> || string || The ICAO identifier of the airport ||
|-
| <code><sid></code> || string || Any available SID ||
|-
| <code><star></code> || string || Any available STAR ||
|-
| <code><transition></code> || string || ||
|-
| <code><runway></code> || string || Departure or destination runway ||
|}

=== Waypoint types and tags ===
{| class="wikitable"
! Tag !! Type !! Use !! Remarks
|-
| <code><type></code> || string || Type of waypoint. Either <code>runway</code>, <code>navaid</code> or <code>offset-navaid</code> ||
|-
| <code><alt-restrict></code> || string || ||
|-
| <code><altitude-ft></code> || double || Altitude in feet ||
|-
| <code><ident></code> || string || If <code><type></code> is
: <code>runway</code>: The departure or destination airport's runway number. Accompanied in the waypoint by the <code><icao></code> tag.
: <code>navaid</code>: Any significant point along the route. Both airports, navaids and fixes.
: <code>offset-navaid</code>: An point offset from a navaid by a bearing and distance. Note that true bearings are used here.
|
|-
| <code><icao></code> || string || ICAO code of an airport || Used only if <code><type></code> is <code>runway</code>
|-
| <code><lon></code> || double || Longitude of the waypoint in decimal degrees ||
|-
| <code><lat></code> || double || Latitude of the waypoint in decimal degrees ||
|-
| <code><radial-deg></code> || double || True bearing from a navaid, fix or airport || {{inote|Radials on charts are magnetic!}}
|-
| <code><distance-nm></code> || double || Distance from a navaid, fix or airport ||
|}

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

<PropertyList>
<version type="int">2</version>
<departure>
<airport type="string">KOAK</airport>
<sid type="string">(none)</sid>
<runway type="string">29</runway>
</departure>
<destination>
<airport type="string">KSJC</airport>
<star type="string">(none)</star>
<transition type="string"></transition>
<runway type="string">11</runway>
</destination>
<route>
<wp>
<type type="string">runway</type>
<departure type="bool">true</departure>
<generated type="bool">true</generated>
<ident type="string">29</ident>
<icao type="string">KOAK</icao>
</wp>
<wp n="1">
<type type="string">offset-navaid</type>
<alt-restrict type="string">at</alt-restrict>
<altitude-ft type="double">7500</altitude-ft>
<ident type="string">SFO</ident>
<lon type="double">-122.3738889</lon>
<lat type="double">37.61947222</lat>
<radial-deg type="double">88.22972768</radial-deg>
<distance-nm type="double">16</distance-nm>
</wp>
<wp n="2">
<type type="string">navaid</type>
<alt-restrict type="string">at</alt-restrict>
<altitude-ft type="double">10000</altitude-ft>
<ident type="string">MISON</ident>
<lon type="double">-121.890306</lon>
<lat type="double">37.496806</lat>
</wp>
<wp n="3">
<type type="string">runway</type>
<arrival type="bool">true</arrival>
<generated type="bool">true</generated>
<ident type="string">11</ident>
<icao type="string">KSJC</icao>
</wp>
</route>
</PropertyList>
</syntaxhighlight>

== Using the flightplans in FlightGear ==
=== Through the route manager ===
{{main article|Route manager}}

=== For AI models ===
{{main article|AI Systems#AI Models}}

== Related content ==
=== Wiki articles ===
* [[Howto:Add procedures to the route manager]]
* [[AI Systems]]
* [[Howto:Create a flightplan]] – Contains no information whatsoever on using flightplans in FlightGear though.
* [[AI Traffic#An example of a traffic file]] – Not flightplans per see as they only cover cruise altitude and departure and destination airport.
* [[List of Nasal extension functions#flightplan()]]
* [[Nasal Flightplan]]
* [[PropertyList XML File]]
* [[UFO from the 'White Project' of the UNESCO]]

=== Source code ===
==== AI flightplans ====
* {{flightgear source|src/AIModel/AIFlightPlan.hxx}}
* {{flightgear source|src/AIModel/AIFlightPlan.cxx}}
* {{flightgear source|src/Navaids/FlightPlan.hxx}}
* {{flightgear source|src/Navaids/FlightPlan.cxx}}

==== Route manager flightplans ====
* {{flightgear source|src/Autopilot/route_mgr.hxx}}
* {{flightgear source|src/Autopilot/route_mgr.cxx}}

[[Category:XML]]
[[Category:AI Traffic]]
[[Category:Autoflight]]

Talk:Boeing 787-8 Dreamliner: Operating manual and checklists

2021-10-03T00:44:08Z

Psnarf:

An obvious question to this aircraft (following the checklist) is where is the Parking Brake?! And how do we know if it is set or not? ~BlueRain

Upper-case 'B' toggles it. The message on the co-pilot side always reads Parking Brake Set. Like most aircraft, they are in various stages of development. Someone might volunteer to test each aircraft and report what works and what is left to do. Recall folks work on Flight Gear in their spare time, much like a hobby. An obvious question to all aircraft is who is going to volunteer to do what needs to be done. [[User:Psnarf|Psnarf]] ([[User talk:Psnarf|talk]]) 00:43, 3 October 2021 (UTC)

Talk:A380 Tutorial

2021-09-29T02:05:56Z

Psnarf: Add current database info

Hello to everyone!
I can only download the SID/STAR by paying a fee (of course I did not, I want to fly free!)
My experience depends on this tutorial, which seems to be old- because I can not find the top-button called SID/STAR on this website. Is anybody of you able to find a good website, where we can download the SID/STAR for free, so that we can change this article :)
bye for now
EDDM08R

UPDATE:

I found a website:
http://www.findthatfile.com/search-11288382-hZIP/winrar-winzip-download-lds767-aio-individual-xml-airports-zip.htm

WHAT DO YOU THINK?

=-=-=-=-=-=-=-=
UPDATE 09/28/21
FlightAware.com has current free Stars, IAP, DP plates.

I use the following to generate an fgfs flight plan, get the Airport Diagram to fill in the Radio NAV/DME, get the Departure/Arrival plates for the fix names and altitudes for the approach to line up with the runway, which I look up and add to the .fgfs plan with a text editor. The Launcher tries to generate that info, but current plates are a safer choice to program the autopilot for landing.
# https://flightplandatabase.com
# https://flightaware.com - Enter the airport, download the Diagram, IFR Departure and Arrival plates
# https://airportguide.com/search/airspace-fix-search/
[[User:Psnarf|Psnarf]] ([[User talk:Psnarf|talk]]) 02:05, 29 September 2021 (UTC)

Talk:Boeing 787-8 Dreamliner

2021-08-20T04:55:13Z

Psnarf: /* Typographical suggestion */ new section

= Rate of growth :-) =
If this continues to grow at this pace, it might be better to split off some parts to separate sub pages, or possibly even create a new "787" sub portal. For example, the checklists and tutorials could be moved at some point. So that it's hopefully becoming easier to navigate all the documentation we have here. Any thoughts/comments?--[[User:Hooray|Hooray]] 09:12, 23 February 2012 (EST)
::Sure, Atm I'll put the things here and we'll discuss how we should split it... ~[[User:Omega1174|Omega95]]
::: From a usability POV, I would suggest to use a "tabbed" layout, with things split into distinct categories (systems overview, tutorials, checklists, CDU reference). --[[User:Hooray|Hooray]] 12:32, 25 February 2012 (EST)

In-line with the previous contributor.. I suggest to split into two pages. 787-8 development and a 787-8 [[AFM]] [[User:PH-JBO|PH-JBO]] 12:18, 29 February 2012 (EST)

:::: It might be a good idea to add a template to all related pages, so that we have a good navigation layout (tabs). --[[User:Hooray|Hooray]] 10:05, 7 March 2012 (EST)

== Aircraft of the Month ==

I suggest to link with the newsletter. [[User:PH-JBO|PH-JBO]] 11:24, 1 March 2012 (EST)

== Typographical suggestion ==

"Landing Gear Chokes" might be spelled "Landing Gear Chocks".

Talk:Flight planning

2021-08-06T21:50:41Z

Psnarf: /* https://flightplandatabase.com */ new section

== https://flightplandatabase.com ==

Just enter your departure/arrival airports, this site generates routes, waypoints, weather en route (temperature, winds, satellite clouds and precipitation), Metar/TAF for both airports, preferred runways depending upon the weather, Navaids. Of course, the official up-to-date charts add more realism, practice for pilot training, but for someone just learning FlightGear, it gets me off the ground.