FlightGear wiki - User contributions [en]

Talk:757/767 Autopilot and autothrottle

2017-11-27T21:22:24Z

Tikibar: /* Merge */

== Merge ==
Suggest it be merged. No need for two wiki pages.
I'm willing to do it.
[[User:Legoboyvdlp|Legoboyvdlp]] ([[User talk:Legoboyvdlp|talk]]) 17:49, 31 October 2017 (EDT)

The 757 and current FGADDON version of the 767 both use exactly the same AP. I thought, rather than duplicate this section in each article, have a separate article for the howto on their shared AP system. That said, I forgot all about the article till now. It needs a little finishing still.
[[User:Tikibar|Tikibar]] ([[User talk:Tikibar|talk]]) 16:22, 27 November 2017 (EST)

Howto:Animated jetways (Type 1)

2017-02-24T18:48:11Z

Tikibar: /* Compatible airports and aircraft */

'''Animated jetways''' are dynamic {{Wikipedia|jetway}} models that connect to your aircraft when you are pulled up at a gate. [[FlightGear]] boasts the most advanced animated jetways in the flight simulator market, beating those of Microsoft Flight Simulator and X-Plane in features — a testament to the flexibility of FlightGear. This article describes how to obtain and use the jetways and interface them with aircraft and scenery.

== Compatible airports and aircraft ==
This section lists the airports having animated jetways, as well as the aircraft and AI aircraft supporting them, as of September 2015.

The compatible airports are:
* [[London Gatwick Airport]] (EGKK)*
* [[Amsterdam Airport Schiphol]] (EHAM)
* Denver International Airport (KDEN)*
* Las Vegas McCarran International Airport (KLAS)*
* [[San Francisco International Airport]] (KSFO)
* Ted Stevens Anchorage International Airport (PANC)*
''<nowiki>*</nowiki> indicates the jetways for this airport were auto-converted and do not have gate numbers.''

The aircraft supporting animated jetways are:
* [[Boeing 717]]
* [[Boeing 747-8i]]
* [[Boeing 757-200]] and -300
* [[Boeing 767-300]]/ER
* [[Boeing 777-200ER]]
* [[Bombardier CRJ700]]
* [[McDonnell Douglas MD-11]]

The [[Interactive traffic|AI aircraft]] supporting animated jetways are:
* [[Airbus A319]]
* [[Airbus A320]]
* [[Airbus A321]]
* [[Boeing 737]]
* [[Boeing 747-400]]
* [[McDonnell Douglas MD-80]]

The {{fgdata file|Models/Airport/Jetway/generic.xml|t=generic jetway model}} in FGData is broken, but there is [http://scenemodels.flightgear.org/app.php?c=Models&a=view&id=2211 a repaired version in the TerraSync scenery repository].

== Obtaining and installing ==
FlightGear 2.4.0 and later include the animated jetway system. Nothing extra has to be installed.

== Using the jetways ==
# Start FlightGear in any compatible aircraft. Make sure to have animated jetways enabled (AI->Jetway->EnableAnimatedJetways and View->RenderingOptions->AnimatedJetways)
# Fly (or spawn) to any airport equipped with animated jetways. You can tell if a jetway is animated by pressing {{key press|Ctrl|C}}; if the polygons are highlighted in yellow, then it is animated.
{{note|Ensure you have the latest scenery from [[TerraSync]] so you do not get conflicts between animated and static jetways.}}
<ol start="3">
<li>Taxi up to an animated jetway and park near it, then click it. If your aircraft is supported and parked well enough, the jetway will extend, rotate, and connect.</li>
</ol>

== Adding support in aircraft ==
# Open up the main model of your aircraft in your favorite 3D modeling software (such as [[Blender]]).
# Move the model around to account for any offsets you have in the main model file, then get the coordinates of the door.
[[File:Animated-jetway-tutorial.jpg]]
<ol start="3">
<li>Add the following code in your aircraft's -set.xml (remember to merge the tags properly):</li>
</ol>
<syntaxhighlight language="xml">
<sim>
<model>
<door>
<position-x-m type="float">X-M</position-x-m>
<position-y-m type="float">Y-M</position-y-m>
<position-z-m type="float">Z-M</position-z-m>
<jetway-hood-deg type="float">HOOD-DEG</jetway-hood-deg>
</door>
</model>
</sim>
</syntaxhighlight>
: where <tt>X-M</tt>, <tt>Y-M</tt>, and <tt>Z-M</tt> are the X/Y/Z coordinates of the door in meters and <tt>HOOD-DEG</tt> is the jetway hood rotation amount. To specify more doors, just add more door elements.
<ol start="4">
<li>Add the following code into your XML model file to enable the jetways to connect to your aircraft over the [[multiplayer]] network:</li>
</ol>
<syntaxhighlight language="xml">
<nasal>
<load>
var model = cmdarg();
model.getNode("door[0]/position-x-m", 1).setValue(X-M);
model.getNode("door[0]/position-y-m", 1).setValue(Y-M);
model.getNode("door[0]/position-z-m", 1).setValue(Z-M);
model.getNode("door[0]/jetway-hood-deg", 1).setValue(HOOD-DEG);
</load>
</nasal>
</syntaxhighlight>
: Again, replace <tt>X-M</tt>, <tt>Y-M</tt>, <tt>Z-M</tt> and <tt>HOOD-DEG</tt> with their respective values. To add more doors, duplicate the last four lines of [[Nasal]] code and replace <tt>[0]</tt> with <tt>[1]</tt> or <tt>[2]</tt>.

=== Adding support in AI aircraft ===
Follow the steps for regular aircraft above, but only add in the Nasal code.

== Adding support in scenery ==
=== Placing jetways ===
# Launch FlightGear in your favorite aircraft, such as the [[Bluebird]].
{{note|You ''cannot'' use the [[UFO]] because its scenery editing function will interfere with the jetway editor.}}
<ol start="2">
<li>Go to {{menu item|AI|Jetway Settings}} and tick the '''Enable jetway editor''' checkbox, then click the {{button|Open Editor}} button.
[[File:Animated-jetway-editor.jpg]]
<li>With the editor enabled, click anywhere on the ground to place an animated jetway, which will flash to indicate it is selected. The jetway editor is similar to the UFO scenery model editor. You can {{key press|Alt}}+click on the terrain to move the current selected jetway. {{key press|Ctrl}}+click selects the jetway closest to the click position (the new jetway will flash to indicate it is selected). {{key press|Shift}}+click deselects the current jetway.</li>
</ol>

: The dialog is used to adjust the selected jetway. The top sliders adjust position and orientation and the bottom ones adjust the jetway itself. The offsets that the bottom sliders control can be used to model jetways that are in obscure configurations. The dropdown menus at the very bottom of the dialog control various properties of the jetway, such as the model, gate number, airline sign and door number. The following models are available:
:* Generic
:* Glass
:* [[EHAM]] gate
:* [[EHAM]] 747 gate

<ol start="4">
<li>When you are finished editing your airport jetway layout, click the {{button|Export}} button. A jetway definition file will be created and written to <tt>$FG_HOME/Export/ICAO.xml</tt>, where <tt>ICAO</tt> is the ICAO code of the nearest airport. (The exact location of this file is printed to the console window.) This file should be [[FlightGear Scenery Database#Contribute|submitted to TerraSync]].</li>
</ol>

=== Auto-converting static/obsolete jetways ===
{{WIP}}

== Future development ==
{{See also|AI Jetway Objects}}
Ryan A Young, the original developer of the animated jetway code, is planning to rewrite it as a C++ subsystem. This would bring several advantages:
* some hacks in the current [[Nasal]] code would be removed, and the system would be faster and more reliable;
* the model files could be streamlined and the jetways could be automatically placed on the ground, irrespective of the employed scenery;
* performance could be improved by letting the user decide how many jetways would be rendered;
* they could be integrated with AI traffic.<ref>{{cite web
| url = http://sourceforge.net/p/flightgear/mailman/message/34725917/
| title = <nowiki>[Flightgear-devel] Animated jet bridges redux</nowiki>
| author = <nowiki>Ryan A Young</nowiki>
| date = Dec 29th, 2015
}}</ref>

== Related content ==
* [[Ramp Marshall]]
* {{forumref|title=The animated jetway project|t=8728|f=5}}

{{Appendix}}

[[Category:Scenery]]
[[Category:Scenery enhancement]]

List of developed airports

2017-02-14T02:43:45Z

Tikibar: /* List of airports */

This is an incomplete '''list of developed airports''' in the FlightGear [[TerraSync]] scenery.

Airports can be listed here if these two conditions are fulfilled:
* At least one building or [[Signs|taxi signs]] have been placed
* Objects are represented in the [[FlightGear Scenery Database]].

Every improvement listed here should be possible to download using TerraSync. These improvements will also be included in the next [[World Scenery]] release.

__TOC__

== For airport developers ==
If you are currently developing an airport, please feel free to add it to [[Airports under construction]]. For a list of currently ongoing scenery related projects, please check out [[Current Scenery Projects]].

== List of airports ==
The ICAO codes link to the FlightGear mapserver, which - among other things - contains information about the current status of the [[FlightGear Scenery Database]]. On a map, you will see:
* The current airport layout with runways, taxiways and aprons
* Red dots: static objects in the scenery database made especially for this airport
* Dark red dots: shared models in the scenery database placed at this airport
* Green dots: [[Signs|taxi signs]] placed at the airport

{{inote|You can sort the table by clicking one of the [[File:Sort none.gif]] symbols in the row headers.}}

{| class="wikitable sortable" border="0" cellspacing="0"
|-
! ICAO !! Name !! Country !! Continent !! class="unsortable" | Comment

|-
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 EDDC] || [[Dresden Airport]] || Germany || Europe || Fully modeled with tower, terminal, animated hangars etc.

|-
| [https://scenery.flightgear.org/map/?lon=8.56293&lat=50.03795&z=13 EDDF] || [[Frankfurt am Main Airport]] || Germany || Europe || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique scycrapers downtown

|-
| EDDG || [[Münster Osnabrück]] || Germany || Europe || 1 static + 100 shared objects

|-
| EDDH || [[Hamburg Airport]] || Germany || Europe || Fully modeled, plus unique buildings downtown

|-
| [https://scenery.flightgear.org/map/?lon=13.40379&lat=52.47502&z=13 EDDI] ||[[Berlin Tempelhof Airport]] || Germany || Europe || Fully modeled

|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf Airport]] || Germany || Europe || Fully modeled, many shared objects

|-
| [https://scenery.flightgear.org/map/?lon=11.78609&lat=48.35378&z=13 EDDM] || [[Munich Airport]] || Germany || Europe || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=12.23603&lat=51.42262&z=13 EDDP] || [[Leipzig/Halle Airport]] || Germany || Europe || Fully modelled with [[Signs]]

|-
| EDDS || [[Stuttgart Airport]] || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=13.28992&lat=52.55917&z=13 EDDT] || [[Berlin Tegel Airport]] || Germany || Europe || Tower, terminals, [[Signs]] and unique buildings downtown

|-
| EDFB || Reichelsheim Airport || Germany || Europe || Tower done

|-
| EDFM || [[Mannheim City Airport]] || Germany || Europe || Basic models of tower, terminals and hangars

|-
| [https://scenery.flightgear.org/map/?lon=10.71706&lat=53.80496&z=13 EDHL] || [[Lübeck Blankensee Airport]] || Germany || Europe || Almost complete, home of the [[Piper PA34-200T Seneca II|Seneca]] used to model the FlightGear version. A modified tile is available at [http://www.t3r.de/fg/scenery/ Torsten's scenery site]

|-
| [https://scenery.flightgear.org/map/?lon=7.16278&lat=50.76767&z=13 EDKB] || [[Bonn-Hangelar Airport]] || Germany || Europe ||

|-
| EDLW || [[Flughafen Dortmund]] || Germany || Europe || Fully modelled

|-
| EDVE || [[Braunschweig Airport]] || Germany || Europe || Fully modelled

|-
| EEKE || Kuressaare Airport || Estonia || Europe ||

|-
| EETN || Lennart Meri Tallinn Airport || Estonia || Europe ||

|-
| EETU || Tartu Airport || Estonia || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=25.04487&lat=60.25318&z=13 EFHF] || Helsinki-Malmi Airport || Finland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=24.95253&lat=60.3206&z=13 EFHK] || Helsinki-Vantaa Airport || Finland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=22.26281&lat=60.51412&z=13 EFTU] || Turku Airport || Finland || Europe || Tower and terminal modelled

|-
| EGFF || Cardiff Airport || United Kingdom || Europe || One building: British Airways Maintenance Facility

|-
| EGGP || Liverpool John Lennon Airport || United Kingdom || Europe ||

|-
| EGGW || London Luton Airport || United Kingdom || Europe ||

|-
| EGKA || Shoreham Airport || United Kingdom || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-0.19224&lat=51.14869&z=13 EGKK] || [[London Gatwick]] || United Kingdom || Europe || Complete and fully modeled to highest level of detail with day and night textures; AI parking and ground network

|-
| [https://scenery.flightgear.org/map/?lon=-0.46095&lat=51.47139&z=13 EGLL] || London Heathrow Airport || United Kingdom || Europe || Basic development only

|-
| EGPH || Edinburgh Airport || United Kingdom || Europe || Tower, terminal, park deck, and some shared models

|-
| [https://scenery.flightgear.org/map/?lon=1.28469&lat=52.67713&z=13 EGSH] || Norwich Airport || United Kingdom || Europe ||

|-
| EH01 || [[VU University Medical Center]] || Netherlands || Europe || Complete hospital building including on-roof heli platform.

|-
| [https://scenery.flightgear.org/map/?lon=4.75487&lat=52.31296&z=13 EHAM] || [[Amsterdam Airport Schiphol]] || Netherlands || Europe || Fully modeled, bussiest AI airport currently

|-
| EHEH || Eindhoven Airport || Netherlands || Europe || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=5.51885&lat=52.45717&z=13 EHLE] || [[Lelystad Airport]] || Netherlands || Europe || Fully modeled

|-
| EHVK || [[Volkel Air Base]] || Netherlands || Europe || Shelters and detailed airport layout.

|-
| EIDW || [[Dublin Airport]] || Ireland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=6.11017&lat=62.56037&z=13 ENAL] || Ålesund Airport || Norway || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=6.10949&lat=61.83027&z=13 ENSD] || Sandane Airport || Norway || Europe ||

|-
| ENVA || Trondheim Værnes Airport || Norway || Europe ||

|-
| ESGP || Göteborg Airport || Sweden || Europe || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=-106.60912&lat=35.04021&z=13 KABQ] || Albuquerque Sunport Airport, NM || USA || America || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=-84.42809&lat=33.63672&z=13 KATL] || [[Hartsfield - Jackson Atlanta International Airport]], GA || USA || America || Terminal modeled

|-
| [https://scenery.flightgear.org/map/?lon=-81.4629595&lat=41.0421187&z=13 KAKR] || [[Akron-Fulton International Airport]], OH || USA || America || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=-81.43676804&lat=40.91510112&z=13 KCAK] || Akron-Canton Regional Airport, OH || USA || America || Fully modelled

|-
| KAUS || Austin-Bergstrom Airport, TX || USA || America ||

|-
| KBOS || Boston Logan || USA || America || Tower, Terminals done

|-
| KFNT || Bishop Intl, MI || USA || America || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=-76.66833&lat=39.17535&z=13 KBWI] || Baltimore-Washington International, MD || USA || America || Terminal modeled with jetways, parking garage, support buildings and [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lat=37.9858289&lon=-122.05529346000002&z=15 KCCR] || Buchanan Field Airport, Concord, CA || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-76.92254&lat=38.98062&z=13 KCGS] || College Park Airport, MD || USA || America ||

|-
| KCVG || Cincinnati/Northern Kentucky International Airport, KY || USA || America || Terminals, Concourses, Towers, Signs, DHL Hub, and Other Buildings (Almost Fully Modeled)

|-
| KDCA || Reagan National Airport, VA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-104.67318&lat=39.86166&z=13 KDEN] || [[Denver_International_Airport|Denver Airport, CO]] || USA || America || One terminal modelled

|-
| KDTW || Detroit Metropolitan Wayne County Airport, MI || USA || America || Basic development only

|-
| KFHR || Friday Harbor Airport, WA || USA || America ||

|-
| KIND || Indianapolis Airport, IN || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-90.07589&lat=32.31118&z=13 KJAN] || Jackson-Evers Airport, MS || USA || America ||

|-
| KJFK || [[John F. Kennedy International Airport]], NY || USA || America ||

|-
| KLAS || Las Vegas McCarran Airport, NV || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-118.40809&lat=33.9425&z=13 KLAX] || [[Los Angeles International Airport]], CA || USA|| America || Fully modeled

|-
| KLSV || [[Nellis Air Force Base]], NV || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-109.4667&lat=47.04924&z=13 KLWT] || Lewistown Municipal Airport, MT || USA || America ||

|-
| KMCI || Kansas City Airport, MO || USA || America || Basic development only

|-
| KMPI || Mariposa-Yosemite Airport, CA || USA || America || Hangars and FBO.

|-
| KMTN || Martin State Airport, MD || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-117.69181&lat=35.68565&z=13 KNID] || China Lake Naval Air Weapons Station, CA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.04918&lat=37.4162&z=13 KNUQ] || Moffett Federal Airfield, CA || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-122.22062&lat=37.7214&z=13 KOAK] || [[Oakland International Airport]], CA || USA || America || Realistic terminal, currently undergoing maintenance

|-
| KORD || Chicago [[O'Hare International Airport]], IL || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-88.55704&lat=43.98436&z=13 KOSH] || Wittman Regional Airport, Oshkosh, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-75.12398&lat=38.31045&z=13 KOXB] || Ocean City Municipal Airport, MD || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.59751&lat=45.58871&z=13 KPDX] || Portland Airport, OR || USA || America ||

|-
| KPHX || Phoenix Sky Harbor Airport, AZ || USA || America ||

|-
| KRNO || Reno/Tahoe Airport, NV || USA || America ||

|-
| KSEA || [[Seattle-Tacoma International Airport]], WA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.3749&lat=37.61897&z=13 KSFO] || [[San Francisco International Airport]], CA || USA || America || FlightGear's default airport, terminal buildings, airport lights and airport train.

|-
| KSLC || Salt Lake City International Airport, UT || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lat=33.80112251&lon=-118.34134126&z=15 KTOA] || Zamperini Field, Torrance, CA || USA || America || Fully modeled

|-
| KXTA || Edwards Airforce Base Detachment 3 (Homey Airport, or Area 51), NV || USA || America || Fully Modelled

|-
| KVUO || Pearson Field Airport, Vancouver, WA || USA || America ||

|-
| LDSP || Split Airport || Croatia || Europe || Basic development only

|-
| LEBB || Bilbao || Spain || Europe || Fully modeled

|-
| LEMD || Madrid - Barajas || Spain || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-3.19889&lat=47.32611&z=13 LFEA] || Belle-Ile || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.10167&lat=47.48139&z=13 LFEQ] || Quiberon || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.66479&lat=48.05247&z=13 LFES] || Guiscriff Scaër || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=2.35465&lat=49.04626&z=13 LFFE] || Enghien Moisselles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=4.8264&lat=45.25226&z=13 LFLR] || Saint Rambert d'Albon Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 LFMA] || Aix - Les Milles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=0.08816&lat=49.53404&z=13 LFOH] || Le Havre Octeville Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=5.36736&lat=43.50499&z=13 LFPG] || Charles de Gaulle International Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.60632&lat=48.89629&z=13 LFPH] || Chelles Le Pin Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.622793&lat=48.822237&z=13 LFPL] || Lognes Emerainville Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.359443&lat=48.72551&z=13 LFPO] || Paris-Orly Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.073197&lat=48.810622&z=13 LFPZ] || St-Cyr-l’École Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=-4.41785&lat=48.44413&z=13 LFRB] || Brest Bretagne Airport || France || Europe || Modeled airport with static models

|-
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRL] || Lanvéoc Naval Air Base || France || Europe || Airport fitted with shared models (for helos and training)

|-
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=-4.167981&lat=47.97553&z=13 LFRQ] || Quimper || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.816762&lat=48.601247&z=13 LFRU] || Morlaix || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-2.736754&lat=47.717558&z=13 LFRV] || Vannes || France || Europe || Airport fitted with shared models

|-
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFRH] || Lorient - Bretagne Sud || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFSB] || [[EuroAirport Basel-Mulhouse-Freiburg|Basel Mulhouse]] || Switzerland || Europe || Nice modelling of Terminal.

|-
| LILN || Venegono Airport || Italy || Europe || Developed airport

|-
| LILQ || Massa Cinquale Airport || Italy || Europe ||

|-
| LILV || Valbrembo Airport || Italy || Europe ||

|-
| LIMC || Milano-Malpensa Airport || Italy || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=9.70741&lat=45.66952&z=13 LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=9.27521&lat=45.44776&z=13 LIML] || [[LIML|Milano-Linate Airport]] || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=7.36789&lat=45.73857&z=13 LIMW] || Aosta Airport || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=14.26&lat=50.100833&z=13 LKPR] || [[Václav Havel Airport Prague]] (Ruzyne) || Czech Republic || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=11.34397&lat=47.26023&z=13 LOWI] || [[Innsbruck Airport]] || Austria || Europe ||

|-
| LROP || Bucharest Otopeni || Romania || Europe ||

|-
| LSGG || Geneve (Cointrin) Airport || Switzerland || Europe || Fully Modelled. OSM2city available on https://github.com/FGMEMBERS-SCENERY/LSGG-fg-CustomScenery

|-
| LSGS || Sion Airport || Switzerland || Europe || Basic development only

|-
| LSZB || Bern-Belp Airport || Switzerland || Europe || Basic development only

|-
| PANC || Ted Stevens Anchorage International Airport || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=136.80541&lat=34.85841&z=13 RJGG] || [[Chūbu Centrair International Airport]] || Japan || Asia || Detailed airport buildings, taxiway layout and customized terrain.

|-
| [https://scenery.flightgear.org/map/?lon=139.78114&lat=35.5533&z=13 RJTT] || [[Tokyo Haneda International Airport]] || Japan || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=126.45051&lat=37.46909&z=13 RKSI] || Seoul Incheon Airport || South Korea || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=121.01349&lat=14.51024&z=13 RPLL] || Manila Aquino Airport || Philippines || Asia || Tower and three large terminals

|-

| SAEZ || Aeropuerto Internacional Ministro Pistarini || Argentina || America || Several static buildings

|-

| [[SVMI]] || Aeropuerto Internacional Simon Bolivar || Venezuela || America || Several static buildings

|-

| TAPA || V.C. Bird Intl Airport || Antigua and Barbuda || America ||

|-
| TDPD || Melville Hall Airport || Dominica || America ||

|-
| TFFF || Martinique Aimé Césaire International Airport || Martinique, France || America ||

|-
| TFFG || Grand Case Airport || St. Maarten, Netherlands || America ||

|-
| TIST || Cyril E. King Airport || US Virgin Islands || America ||

|-
| TJSJ || Luis Muñoz Marín International Airport || Puerto Rico || America ||

|-
| TKPK || Robert L. Bradshaw International Airport || St. Kitts || America ||

|-
| TNCM || [[Princess Juliana International Airport]] || St. Maarten, Netherlands || America || Fully modeled, customized terrain

|-
| TNCS || Juancho E. Yrausquin Airport || Saba || America || Fully modeled

|-
| TQPF || Clayton J. Lloyd International Airport || Anguilla || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-49.17201&lat=-25.53101&z=13 SBCT] || Afonso Pena International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-46.65768&lat=-23.62558&z=13 SBSP] || Congonhas Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-46.46864&lat=-23.43351&z=13 SBGR] || Guarulhos International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-48.54304&lat=-27.6685&z=13 SBFL] || Hercílio Luiz International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| SKRG || Jose Maria Cordoba International Airport, Rionegro, Antioquia || Colombia || South America || Fully Modelled

|-
| VIDP || Indira Gandhi International Airport || India || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=89.42272&lat=27.39994&z=13 VQPR] || [[Paro Airport]] || Bhutan || Asia || Terminal, Buildings, Refernce Points and other POIs

|-
| [https://scenery.flightgear.org/map/?lon=91.50917&lat=27.25961&z=13 VQ10] || [[Yongphulla Airport]] || Bhutan || Asia || Terminal, some other Buildings

|-
| [https://scenery.flightgear.org/map/?lon=113.9183&lat=22.308&z=13 VHHH] || Hong Kong International Airport || Hong Kong || Asia || Terminals, control towers, some other buildings

|-
| [https://scenery.flightgear.org/map/?lon=-81.41707414&lat=41.15689289&z=13 1G3] || Kent State University Airfield, OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-81.76281774&lat=41.13448335&z=13 1G5] || [[Medina Municipal Airport]], OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-81.24620281&lat=41.20973295&z=13 29G] || Portage Co, OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-90.13769&lat=43.83872&z=13 82C] || Mauston-New Lisbon Union Airport, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-89.02545&lat=44.50485&z=13 68C] || Iola Central County Airport, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-123.00815977&lat=43.93009927&z=13 77S] || Hobby Field, Creswell, OR || USA || America || Nearly complete: Hangars (one accidently missing), fuel pump, GA aircraft, cars, trees, bushes (shared models)

|}

== Authors ==

Airports by HerbyW in Yakutia, Irkutsk and Krasnoyarsk:
UIBB UEEE UEST UEMS UEBN UEBT UEWD UEMA UERR UEMT UEEA UEMU UIII UITT UEBB UEVV UENW UEMO UERL UERT UEMH UERO UERP UNAA UIUN UENN UIBV UNCC UEMJ

Airports by D-ABBA:
EDXW,EDFE,EDGS,EDFQ,EDFH,EDFL,EDFO,ED03

Airports by [[User:Laserman]]:
EDDG,EDLM,EDLB,EDLK,EDLN,EDLV,EDLW,LJLJ,LJAJ,LJSG,LJCE,LJPZ

== External links ==
* [http://iveze.nl/fgmap/ Builtup airports in Flightgear] – Interactive world map by KL-666. ''See also related forum topic [http://forum.flightgear.org/viewtopic.php?f=5&t=23613 Map of airports with buildings in terrasync].''

{{Suggested}}

[[Category:Lists]]
[[Category:Airports]]

List of developed airports

2017-02-14T02:42:18Z

Tikibar: /* List of airports */

This is an incomplete '''list of developed airports''' in the FlightGear [[TerraSync]] scenery.

Airports can be listed here if these two conditions are fulfilled:
* At least one building or [[Signs|taxi signs]] have been placed
* Objects are represented in the [[FlightGear Scenery Database]].

Every improvement listed here should be possible to download using TerraSync. These improvements will also be included in the next [[World Scenery]] release.

__TOC__

== For airport developers ==
If you are currently developing an airport, please feel free to add it to [[Airports under construction]]. For a list of currently ongoing scenery related projects, please check out [[Current Scenery Projects]].

== List of airports ==
The ICAO codes link to the FlightGear mapserver, which - among other things - contains information about the current status of the [[FlightGear Scenery Database]]. On a map, you will see:
* The current airport layout with runways, taxiways and aprons
* Red dots: static objects in the scenery database made especially for this airport
* Dark red dots: shared models in the scenery database placed at this airport
* Green dots: [[Signs|taxi signs]] placed at the airport

{{inote|You can sort the table by clicking one of the [[File:Sort none.gif]] symbols in the row headers.}}

{| class="wikitable sortable" border="0" cellspacing="0"
|-
! ICAO !! Name !! Country !! Continent !! class="unsortable" | Comment

|-
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 EDDC] || [[Dresden Airport]] || Germany || Europe || Fully modeled with tower, terminal, animated hangars etc.

|-
| [https://scenery.flightgear.org/map/?lon=8.56293&lat=50.03795&z=13 EDDF] || [[Frankfurt am Main Airport]] || Germany || Europe || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique scycrapers downtown

|-
| EDDG || [[Münster Osnabrück]] || Germany || Europe || 1 static + 100 shared objects

|-
| EDDH || [[Hamburg Airport]] || Germany || Europe || Fully modeled, plus unique buildings downtown

|-
| [https://scenery.flightgear.org/map/?lon=13.40379&lat=52.47502&z=13 EDDI] ||[[Berlin Tempelhof Airport]] || Germany || Europe || Fully modeled

|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf Airport]] || Germany || Europe || Fully modeled, many shared objects

|-
| [https://scenery.flightgear.org/map/?lon=11.78609&lat=48.35378&z=13 EDDM] || [[Munich Airport]] || Germany || Europe || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=12.23603&lat=51.42262&z=13 EDDP] || [[Leipzig/Halle Airport]] || Germany || Europe || Fully modelled with [[Signs]]

|-
| EDDS || [[Stuttgart Airport]] || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=13.28992&lat=52.55917&z=13 EDDT] || [[Berlin Tegel Airport]] || Germany || Europe || Tower, terminals, [[Signs]] and unique buildings downtown

|-
| EDFB || Reichelsheim Airport || Germany || Europe || Tower done

|-
| EDFM || [[Mannheim City Airport]] || Germany || Europe || Basic models of tower, terminals and hangars

|-
| [https://scenery.flightgear.org/map/?lon=10.71706&lat=53.80496&z=13 EDHL] || [[Lübeck Blankensee Airport]] || Germany || Europe || Almost complete, home of the [[Piper PA34-200T Seneca II|Seneca]] used to model the FlightGear version. A modified tile is available at [http://www.t3r.de/fg/scenery/ Torsten's scenery site]

|-
| [https://scenery.flightgear.org/map/?lon=7.16278&lat=50.76767&z=13 EDKB] || [[Bonn-Hangelar Airport]] || Germany || Europe ||

|-
| EDLW || [[Flughafen Dortmund]] || Germany || Europe || Fully modelled

|-
| EDVE || [[Braunschweig Airport]] || Germany || Europe || Fully modelled

|-
| EEKE || Kuressaare Airport || Estonia || Europe ||

|-
| EETN || Lennart Meri Tallinn Airport || Estonia || Europe ||

|-
| EETU || Tartu Airport || Estonia || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=25.04487&lat=60.25318&z=13 EFHF] || Helsinki-Malmi Airport || Finland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=24.95253&lat=60.3206&z=13 EFHK] || Helsinki-Vantaa Airport || Finland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=22.26281&lat=60.51412&z=13 EFTU] || Turku Airport || Finland || Europe || Tower and terminal modelled

|-
| EGFF || Cardiff Airport || United Kingdom || Europe || One building: British Airways Maintenance Facility

|-
| EGGP || Liverpool John Lennon Airport || United Kingdom || Europe ||

|-
| EGGW || London Luton Airport || United Kingdom || Europe ||

|-
| EGKA || Shoreham Airport || United Kingdom || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-0.19224&lat=51.14869&z=13 EGKK] || [[London Gatwick]] || United Kingdom || Europe || Complete and fully modeled to highest level of detail with day and night textures; AI parking and ground network

|-
| [https://scenery.flightgear.org/map/?lon=-0.46095&lat=51.47139&z=13 EGLL] || London Heathrow Airport || United Kingdom || Europe || Basic development only

|-
| EGPH || Edinburgh Airport || United Kingdom || Europe || Tower, terminal, park deck, and some shared models

|-
| [https://scenery.flightgear.org/map/?lon=1.28469&lat=52.67713&z=13 EGSH] || Norwich Airport || United Kingdom || Europe ||

|-
| EH01 || [[VU University Medical Center]] || Netherlands || Europe || Complete hospital building including on-roof heli platform.

|-
| [https://scenery.flightgear.org/map/?lon=4.75487&lat=52.31296&z=13 EHAM] || [[Amsterdam Airport Schiphol]] || Netherlands || Europe || Fully modeled, bussiest AI airport currently

|-
| EHEH || Eindhoven Airport || Netherlands || Europe || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=5.51885&lat=52.45717&z=13 EHLE] || [[Lelystad Airport]] || Netherlands || Europe || Fully modeled

|-
| EHVK || [[Volkel Air Base]] || Netherlands || Europe || Shelters and detailed airport layout.

|-
| EIDW || [[Dublin Airport]] || Ireland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=6.11017&lat=62.56037&z=13 ENAL] || Ålesund Airport || Norway || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=6.10949&lat=61.83027&z=13 ENSD] || Sandane Airport || Norway || Europe ||

|-
| ENVA || Trondheim Værnes Airport || Norway || Europe ||

|-
| ESGP || Göteborg Airport || Sweden || Europe || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=-106.60912&lat=35.04021&z=13 KABQ] || Albuquerque Sunport Airport, NM || USA || America || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=-84.42809&lat=33.63672&z=13 KATL] || [[Hartsfield - Jackson Atlanta International Airport]], GA || USA || America || Terminal modeled

|-
| [https://scenery.flightgear.org/map/?lon=-81.4629595&lat=41.0421187&z=13 KAKR] || [[Akron-Fulton International Airport]], OH || USA || America || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=-81.43676804&lat=40.91510112&z=13 KCAK] || Akron-Canton Regional Airport, OH || USA || America || Fully modelled

|-
| KAUS || Austin-Bergstrom Airport, TX || USA || America ||

|-
| KBOS || Boston Logan || USA || America || Tower, Terminals done

|-
| KFNT || Bishop Intl, MI || USA || America || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=-76.66833&lat=39.17535&z=13 KBWI] || Baltimore-Washington International, MD || USA || America || Terminal modeled with jetways, parking garage, support buildings and [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lat=37.9858289&lon=-122.05529346000002&z=15 KCCR] || Buchanan Field Airport, Concord, CA || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-76.92254&lat=38.98062&z=13 KCGS] || College Park Airport, MD || USA || America ||

|-
| KCVG || Cincinnati/Northern Kentucky International Airport, KY || USA || America || Terminals, Concourses, Towers, Signs, DHL Hub, and Other Buildings (Almost Fully Modeled)

|-
| KDCA || Reagan National Airport, VA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-104.67318&lat=39.86166&z=13 KDEN] || [[Denver_International_Airport|Denver Airport, CO]] || USA || America || One terminal modelled

|-
| KDTW || Detroit Metropolitan Wayne County Airport, MI || USA || America || Basic development only

|-
| KFHR || Friday Harbor Airport, WA || USA || America ||

|-
| KIND || Indianapolis Airport, IN || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-90.07589&lat=32.31118&z=13 KJAN] || Jackson-Evers Airport, MS || USA || America ||

|-
| KJFK || [[John F. Kennedy International Airport]], NY || USA || America ||

|-
| KLAS || Las Vegas McCarran Airport, NV || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-118.40809&lat=33.9425&z=13 KLAX] || [[Los Angeles International Airport]], CA || USA|| America || Fully modeled

|-
| KLSV || [[Nellis Air Force Base]], NV || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-109.4667&lat=47.04924&z=13 KLWT] || Lewistown Municipal Airport, MT || USA || America ||

|-
| KMCI || Kansas City Airport, MO || USA || America || Basic development only

|-
| KMPI || Mariposa-Yosemite Airport, CA || USA || America || Hangars and FBO.

|-
| KMTN || Martin State Airport, MD || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-117.69181&lat=35.68565&z=13 KNID] || China Lake Naval Air Weapons Station, CA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.04918&lat=37.4162&z=13 KNUQ] || Moffett Federal Airfield, CA || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-122.22062&lat=37.7214&z=13 KOAK] || [[Oakland International Airport]], CA || USA || America || Realistic terminal, currently undergoing maintenance

|-
| KORD || Chicago [[O'Hare International Airport]], IL || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-88.55704&lat=43.98436&z=13 KOSH] || Wittman Regional Airport, Oshkosh, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-75.12398&lat=38.31045&z=13 KOXB] || Ocean City Municipal Airport, MD || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.59751&lat=45.58871&z=13 KPDX] || Portland Airport, OR || USA || America ||

|-
| KPHX || Phoenix Sky Harbor Airport, AZ || USA || America ||

|-
| KRNO || Reno/Tahoe Airport, NV || USA || America ||

|-
| KSEA || [[Seattle-Tacoma International Airport]], WA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.3749&lat=37.61897&z=13 KSFO] || [[San Francisco International Airport]], CA || USA || America || FlightGear's default airport, terminal buildings, airport lights and airport train.

|-
| KSLC || Salt Lake City International Airport, UT || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lat=33.80112251&lon=-118.34134126&z=15 KTOA] || Zamperini Field, CA || USA || America || Fully modeled

|-
| KXTA || Edwards Airforce Base Detachment 3 (Homey Airport, or Area 51), NV || USA || America || Fully Modelled

|-
| KVUO || Pearson Field Airport, Vancouver, WA || USA || America ||

|-
| LDSP || Split Airport || Croatia || Europe || Basic development only

|-
| LEBB || Bilbao || Spain || Europe || Fully modeled

|-
| LEMD || Madrid - Barajas || Spain || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-3.19889&lat=47.32611&z=13 LFEA] || Belle-Ile || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.10167&lat=47.48139&z=13 LFEQ] || Quiberon || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.66479&lat=48.05247&z=13 LFES] || Guiscriff Scaër || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=2.35465&lat=49.04626&z=13 LFFE] || Enghien Moisselles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=4.8264&lat=45.25226&z=13 LFLR] || Saint Rambert d'Albon Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 LFMA] || Aix - Les Milles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=0.08816&lat=49.53404&z=13 LFOH] || Le Havre Octeville Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=5.36736&lat=43.50499&z=13 LFPG] || Charles de Gaulle International Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.60632&lat=48.89629&z=13 LFPH] || Chelles Le Pin Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.622793&lat=48.822237&z=13 LFPL] || Lognes Emerainville Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.359443&lat=48.72551&z=13 LFPO] || Paris-Orly Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.073197&lat=48.810622&z=13 LFPZ] || St-Cyr-l’École Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=-4.41785&lat=48.44413&z=13 LFRB] || Brest Bretagne Airport || France || Europe || Modeled airport with static models

|-
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRL] || Lanvéoc Naval Air Base || France || Europe || Airport fitted with shared models (for helos and training)

|-
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=-4.167981&lat=47.97553&z=13 LFRQ] || Quimper || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.816762&lat=48.601247&z=13 LFRU] || Morlaix || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-2.736754&lat=47.717558&z=13 LFRV] || Vannes || France || Europe || Airport fitted with shared models

|-
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFRH] || Lorient - Bretagne Sud || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFSB] || [[EuroAirport Basel-Mulhouse-Freiburg|Basel Mulhouse]] || Switzerland || Europe || Nice modelling of Terminal.

|-
| LILN || Venegono Airport || Italy || Europe || Developed airport

|-
| LILQ || Massa Cinquale Airport || Italy || Europe ||

|-
| LILV || Valbrembo Airport || Italy || Europe ||

|-
| LIMC || Milano-Malpensa Airport || Italy || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=9.70741&lat=45.66952&z=13 LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=9.27521&lat=45.44776&z=13 LIML] || [[LIML|Milano-Linate Airport]] || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=7.36789&lat=45.73857&z=13 LIMW] || Aosta Airport || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=14.26&lat=50.100833&z=13 LKPR] || [[Václav Havel Airport Prague]] (Ruzyne) || Czech Republic || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=11.34397&lat=47.26023&z=13 LOWI] || [[Innsbruck Airport]] || Austria || Europe ||

|-
| LROP || Bucharest Otopeni || Romania || Europe ||

|-
| LSGG || Geneve (Cointrin) Airport || Switzerland || Europe || Fully Modelled. OSM2city available on https://github.com/FGMEMBERS-SCENERY/LSGG-fg-CustomScenery

|-
| LSGS || Sion Airport || Switzerland || Europe || Basic development only

|-
| LSZB || Bern-Belp Airport || Switzerland || Europe || Basic development only

|-
| PANC || Ted Stevens Anchorage International Airport || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=136.80541&lat=34.85841&z=13 RJGG] || [[Chūbu Centrair International Airport]] || Japan || Asia || Detailed airport buildings, taxiway layout and customized terrain.

|-
| [https://scenery.flightgear.org/map/?lon=139.78114&lat=35.5533&z=13 RJTT] || [[Tokyo Haneda International Airport]] || Japan || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=126.45051&lat=37.46909&z=13 RKSI] || Seoul Incheon Airport || South Korea || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=121.01349&lat=14.51024&z=13 RPLL] || Manila Aquino Airport || Philippines || Asia || Tower and three large terminals

|-

| SAEZ || Aeropuerto Internacional Ministro Pistarini || Argentina || America || Several static buildings

|-

| [[SVMI]] || Aeropuerto Internacional Simon Bolivar || Venezuela || America || Several static buildings

|-

| TAPA || V.C. Bird Intl Airport || Antigua and Barbuda || America ||

|-
| TDPD || Melville Hall Airport || Dominica || America ||

|-
| TFFF || Martinique Aimé Césaire International Airport || Martinique, France || America ||

|-
| TFFG || Grand Case Airport || St. Maarten, Netherlands || America ||

|-
| TIST || Cyril E. King Airport || US Virgin Islands || America ||

|-
| TJSJ || Luis Muñoz Marín International Airport || Puerto Rico || America ||

|-
| TKPK || Robert L. Bradshaw International Airport || St. Kitts || America ||

|-
| TNCM || [[Princess Juliana International Airport]] || St. Maarten, Netherlands || America || Fully modeled, customized terrain

|-
| TNCS || Juancho E. Yrausquin Airport || Saba || America || Fully modeled

|-
| TQPF || Clayton J. Lloyd International Airport || Anguilla || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-49.17201&lat=-25.53101&z=13 SBCT] || Afonso Pena International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-46.65768&lat=-23.62558&z=13 SBSP] || Congonhas Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-46.46864&lat=-23.43351&z=13 SBGR] || Guarulhos International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-48.54304&lat=-27.6685&z=13 SBFL] || Hercílio Luiz International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| SKRG || Jose Maria Cordoba International Airport, Rionegro, Antioquia || Colombia || South America || Fully Modelled

|-
| VIDP || Indira Gandhi International Airport || India || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=89.42272&lat=27.39994&z=13 VQPR] || [[Paro Airport]] || Bhutan || Asia || Terminal, Buildings, Refernce Points and other POIs

|-
| [https://scenery.flightgear.org/map/?lon=91.50917&lat=27.25961&z=13 VQ10] || [[Yongphulla Airport]] || Bhutan || Asia || Terminal, some other Buildings

|-
| [https://scenery.flightgear.org/map/?lon=113.9183&lat=22.308&z=13 VHHH] || Hong Kong International Airport || Hong Kong || Asia || Terminals, control towers, some other buildings

|-
| [https://scenery.flightgear.org/map/?lon=-81.41707414&lat=41.15689289&z=13 1G3] || Kent State University Airfield, OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-81.76281774&lat=41.13448335&z=13 1G5] || [[Medina Municipal Airport]], OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-81.24620281&lat=41.20973295&z=13 29G] || Portage Co, OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-90.13769&lat=43.83872&z=13 82C] || Mauston-New Lisbon Union Airport, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-89.02545&lat=44.50485&z=13 68C] || Iola Central County Airport, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-123.00815977&lat=43.93009927&z=13 77S] || Hobby Field, Creswell, OR || USA || America || Nearly complete: Hangars (one accidently missing), fuel pump, GA aircraft, cars, trees, bushes (shared models)

|}

== Authors ==

Airports by HerbyW in Yakutia, Irkutsk and Krasnoyarsk:
UIBB UEEE UEST UEMS UEBN UEBT UEWD UEMA UERR UEMT UEEA UEMU UIII UITT UEBB UEVV UENW UEMO UERL UERT UEMH UERO UERP UNAA UIUN UENN UIBV UNCC UEMJ

Airports by D-ABBA:
EDXW,EDFE,EDGS,EDFQ,EDFH,EDFL,EDFO,ED03

Airports by [[User:Laserman]]:
EDDG,EDLM,EDLB,EDLK,EDLN,EDLV,EDLW,LJLJ,LJAJ,LJSG,LJCE,LJPZ

== External links ==
* [http://iveze.nl/fgmap/ Builtup airports in Flightgear] – Interactive world map by KL-666. ''See also related forum topic [http://forum.flightgear.org/viewtopic.php?f=5&t=23613 Map of airports with buildings in terrasync].''

{{Suggested}}

[[Category:Lists]]
[[Category:Airports]]

List of developed airports

2017-02-13T23:17:50Z

Tikibar: Add link for KCCR and KTOA maps

This is an incomplete '''list of developed airports''' in the FlightGear [[TerraSync]] scenery.

Airports can be listed here if these two conditions are fulfilled:
* At least one building or [[Signs|taxi signs]] have been placed
* Objects are represented in the [[FlightGear Scenery Database]].

Every improvement listed here should be possible to download using TerraSync. These improvements will also be included in the next [[World Scenery]] release.

__TOC__

== For airport developers ==
If you are currently developing an airport, please feel free to add it to [[Airports under construction]]. For a list of currently ongoing scenery related projects, please check out [[Current Scenery Projects]].

== List of airports ==
The ICAO codes link to the FlightGear mapserver, which - among other things - contains information about the current status of the [[FlightGear Scenery Database]]. On a map, you will see:
* The current airport layout with runways, taxiways and aprons
* Red dots: static objects in the scenery database made especially for this airport
* Dark red dots: shared models in the scenery database placed at this airport
* Green dots: [[Signs|taxi signs]] placed at the airport

{{inote|You can sort the table by clicking one of the [[File:Sort none.gif]] symbols in the row headers.}}

{| class="wikitable sortable" border="0" cellspacing="0"
|-
! ICAO !! Name !! Country !! Continent !! class="unsortable" | Comment

|-
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 EDDC] || [[Dresden Airport]] || Germany || Europe || Fully modeled with tower, terminal, animated hangars etc.

|-
| [https://scenery.flightgear.org/map/?lon=8.56293&lat=50.03795&z=13 EDDF] || [[Frankfurt am Main Airport]] || Germany || Europe || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique scycrapers downtown

|-
| EDDG || [[Münster Osnabrück]] || Germany || Europe || 1 static + 100 shared objects

|-
| EDDH || [[Hamburg Airport]] || Germany || Europe || Fully modeled, plus unique buildings downtown

|-
| [https://scenery.flightgear.org/map/?lon=13.40379&lat=52.47502&z=13 EDDI] ||[[Berlin Tempelhof Airport]] || Germany || Europe || Fully modeled

|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf Airport]] || Germany || Europe || Fully modeled, many shared objects

|-
| [https://scenery.flightgear.org/map/?lon=11.78609&lat=48.35378&z=13 EDDM] || [[Munich Airport]] || Germany || Europe || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=12.23603&lat=51.42262&z=13 EDDP] || [[Leipzig/Halle Airport]] || Germany || Europe || Fully modelled with [[Signs]]

|-
| EDDS || [[Stuttgart Airport]] || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=13.28992&lat=52.55917&z=13 EDDT] || [[Berlin Tegel Airport]] || Germany || Europe || Tower, terminals, [[Signs]] and unique buildings downtown

|-
| EDFB || Reichelsheim Airport || Germany || Europe || Tower done

|-
| EDFM || [[Mannheim City Airport]] || Germany || Europe || Basic models of tower, terminals and hangars

|-
| [https://scenery.flightgear.org/map/?lon=10.71706&lat=53.80496&z=13 EDHL] || [[Lübeck Blankensee Airport]] || Germany || Europe || Almost complete, home of the [[Piper PA34-200T Seneca II|Seneca]] used to model the FlightGear version. A modified tile is available at [http://www.t3r.de/fg/scenery/ Torsten's scenery site]

|-
| [https://scenery.flightgear.org/map/?lon=7.16278&lat=50.76767&z=13 EDKB] || [[Bonn-Hangelar Airport]] || Germany || Europe ||

|-
| EDLW || [[Flughafen Dortmund]] || Germany || Europe || Fully modelled

|-
| EDVE || [[Braunschweig Airport]] || Germany || Europe || Fully modelled

|-
| EEKE || Kuressaare Airport || Estonia || Europe ||

|-
| EETN || Lennart Meri Tallinn Airport || Estonia || Europe ||

|-
| EETU || Tartu Airport || Estonia || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=25.04487&lat=60.25318&z=13 EFHF] || Helsinki-Malmi Airport || Finland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=24.95253&lat=60.3206&z=13 EFHK] || Helsinki-Vantaa Airport || Finland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=22.26281&lat=60.51412&z=13 EFTU] || Turku Airport || Finland || Europe || Tower and terminal modelled

|-
| EGFF || Cardiff Airport || United Kingdom || Europe || One building: British Airways Maintenance Facility

|-
| EGGP || Liverpool John Lennon Airport || United Kingdom || Europe ||

|-
| EGGW || London Luton Airport || United Kingdom || Europe ||

|-
| EGKA || Shoreham Airport || United Kingdom || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-0.19224&lat=51.14869&z=13 EGKK] || [[London Gatwick]] || United Kingdom || Europe || Complete and fully modeled to highest level of detail with day and night textures; AI parking and ground network

|-
| [https://scenery.flightgear.org/map/?lon=-0.46095&lat=51.47139&z=13 EGLL] || London Heathrow Airport || United Kingdom || Europe || Basic development only

|-
| EGPH || Edinburgh Airport || United Kingdom || Europe || Tower, terminal, park deck, and some shared models

|-
| [https://scenery.flightgear.org/map/?lon=1.28469&lat=52.67713&z=13 EGSH] || Norwich Airport || United Kingdom || Europe ||

|-
| EH01 || [[VU University Medical Center]] || Netherlands || Europe || Complete hospital building including on-roof heli platform.

|-
| [https://scenery.flightgear.org/map/?lon=4.75487&lat=52.31296&z=13 EHAM] || [[Amsterdam Airport Schiphol]] || Netherlands || Europe || Fully modeled, bussiest AI airport currently

|-
| EHEH || Eindhoven Airport || Netherlands || Europe || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=5.51885&lat=52.45717&z=13 EHLE] || [[Lelystad Airport]] || Netherlands || Europe || Fully modeled

|-
| EHVK || [[Volkel Air Base]] || Netherlands || Europe || Shelters and detailed airport layout.

|-
| EIDW || [[Dublin Airport]] || Ireland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=6.11017&lat=62.56037&z=13 ENAL] || Ålesund Airport || Norway || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=6.10949&lat=61.83027&z=13 ENSD] || Sandane Airport || Norway || Europe ||

|-
| ENVA || Trondheim Værnes Airport || Norway || Europe ||

|-
| ESGP || Göteborg Airport || Sweden || Europe || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=-106.60912&lat=35.04021&z=13 KABQ] || Albuquerque Sunport Airport, NM || USA || America || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=-84.42809&lat=33.63672&z=13 KATL] || [[Hartsfield - Jackson Atlanta International Airport]], GA || USA || America || Terminal modeled

|-
| [https://scenery.flightgear.org/map/?lon=-81.4629595&lat=41.0421187&z=13 KAKR] || [[Akron-Fulton International Airport]], OH || USA || America || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=-81.43676804&lat=40.91510112&z=13 KCAK] || Akron-Canton Regional Airport, OH || USA || America || Fully modelled

|-
| KAUS || Austin-Bergstrom Airport, TX || USA || America ||

|-
| KBOS || Boston Logan || USA || America || Tower, Terminals done

|-
| KFNT || Bishop Intl, MI || USA || America || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=-76.66833&lat=39.17535&z=13 KBWI] || Baltimore-Washington International, MD || USA || America || Terminal modeled with jetways, parking garage, support buildings and [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lat=37.9858289&lon=-122.05529346000002&z=15 KCCR] || Buchanan Field Airport, CA || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-76.92254&lat=38.98062&z=13 KCGS] || College Park Airport, MD || USA || America ||

|-
| KCVG || Cincinnati/Northern Kentucky International Airport, KY || USA || America || Terminals, Concourses, Towers, Signs, DHL Hub, and Other Buildings (Almost Fully Modeled)

|-
| KDCA || Reagan National Airport, VA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-104.67318&lat=39.86166&z=13 KDEN] || [[Denver_International_Airport|Denver Airport, CO]] || USA || America || One terminal modelled

|-
| KDTW || Detroit Metropolitan Wayne County Airport, MI || USA || America || Basic development only

|-
| KFHR || Friday Harbor Airport, WA || USA || America ||

|-
| KIND || Indianapolis Airport, IN || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-90.07589&lat=32.31118&z=13 KJAN] || Jackson-Evers Airport, MS || USA || America ||

|-
| KJFK || [[John F. Kennedy International Airport]], NY || USA || America ||

|-
| KLAS || Las Vegas McCarran Airport, NV || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-118.40809&lat=33.9425&z=13 KLAX] || [[Los Angeles International Airport]], CA || USA|| America || Fully modeled

|-
| KLSV || [[Nellis Air Force Base]], NV || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-109.4667&lat=47.04924&z=13 KLWT] || Lewistown Municipal Airport, MT || USA || America ||

|-
| KMCI || Kansas City Airport, MO || USA || America || Basic development only

|-
| KMPI || Mariposa-Yosemite Airport, CA || USA || America || Hangars and FBO.

|-
| KMTN || Martin State Airport, MD || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-117.69181&lat=35.68565&z=13 KNID] || China Lake Naval Air Weapons Station, CA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.04918&lat=37.4162&z=13 KNUQ] || Moffett Federal Airfield, CA || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-122.22062&lat=37.7214&z=13 KOAK] || [[Oakland International Airport]], CA || USA || America || Realistic terminal, currently undergoing maintenance

|-
| KORD || Chicago [[O'Hare International Airport]], IL || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-88.55704&lat=43.98436&z=13 KOSH] || Wittman Regional Airport, Oshkosh, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-75.12398&lat=38.31045&z=13 KOXB] || Ocean City Municipal Airport, MD || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.59751&lat=45.58871&z=13 KPDX] || Portland Airport, OR || USA || America ||

|-
| KPHX || Phoenix Sky Harbor Airport, AZ || USA || America ||

|-
| KRNO || Reno/Tahoe Airport, NV || USA || America ||

|-
| KSEA || [[Seattle-Tacoma International Airport]], WA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.3749&lat=37.61897&z=13 KSFO] || [[San Francisco International Airport]], CA || USA || America || FlightGear's default airport, terminal buildings, airport lights and airport train.

|-
| KSLC || Salt Lake City International Airport, UT || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lat=33.80112251&lon=-118.34134126&z=15 KTOA] || Zamperini Field, CA || USA || America || Fully modeled

|-
| KXTA || Edwards Airforce Base Detachment 3 (Homey Airport, or Area 51), NV || USA || America || Fully Modelled

|-
| KVUO || Pearson Field Airport, Vancouver, WA || USA || America ||

|-
| LDSP || Split Airport || Croatia || Europe || Basic development only

|-
| LEBB || Bilbao || Spain || Europe || Fully modeled

|-
| LEMD || Madrid - Barajas || Spain || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-3.19889&lat=47.32611&z=13 LFEA] || Belle-Ile || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.10167&lat=47.48139&z=13 LFEQ] || Quiberon || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.66479&lat=48.05247&z=13 LFES] || Guiscriff Scaër || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=2.35465&lat=49.04626&z=13 LFFE] || Enghien Moisselles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=4.8264&lat=45.25226&z=13 LFLR] || Saint Rambert d'Albon Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 LFMA] || Aix - Les Milles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=0.08816&lat=49.53404&z=13 LFOH] || Le Havre Octeville Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=5.36736&lat=43.50499&z=13 LFPG] || Charles de Gaulle International Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.60632&lat=48.89629&z=13 LFPH] || Chelles Le Pin Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.622793&lat=48.822237&z=13 LFPL] || Lognes Emerainville Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.359443&lat=48.72551&z=13 LFPO] || Paris-Orly Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.073197&lat=48.810622&z=13 LFPZ] || St-Cyr-l’École Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=-4.41785&lat=48.44413&z=13 LFRB] || Brest Bretagne Airport || France || Europe || Modeled airport with static models

|-
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRL] || Lanvéoc Naval Air Base || France || Europe || Airport fitted with shared models (for helos and training)

|-
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=-4.167981&lat=47.97553&z=13 LFRQ] || Quimper || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.816762&lat=48.601247&z=13 LFRU] || Morlaix || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-2.736754&lat=47.717558&z=13 LFRV] || Vannes || France || Europe || Airport fitted with shared models

|-
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFRH] || Lorient - Bretagne Sud || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFSB] || [[EuroAirport Basel-Mulhouse-Freiburg|Basel Mulhouse]] || Switzerland || Europe || Nice modelling of Terminal.

|-
| LILN || Venegono Airport || Italy || Europe || Developed airport

|-
| LILQ || Massa Cinquale Airport || Italy || Europe ||

|-
| LILV || Valbrembo Airport || Italy || Europe ||

|-
| LIMC || Milano-Malpensa Airport || Italy || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=9.70741&lat=45.66952&z=13 LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=9.27521&lat=45.44776&z=13 LIML] || [[LIML|Milano-Linate Airport]] || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=7.36789&lat=45.73857&z=13 LIMW] || Aosta Airport || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=14.26&lat=50.100833&z=13 LKPR] || [[Václav Havel Airport Prague]] (Ruzyne) || Czech Republic || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=11.34397&lat=47.26023&z=13 LOWI] || [[Innsbruck Airport]] || Austria || Europe ||

|-
| LROP || Bucharest Otopeni || Romania || Europe ||

|-
| LSGG || Geneve (Cointrin) Airport || Switzerland || Europe || Fully Modelled. OSM2city available on https://github.com/FGMEMBERS-SCENERY/LSGG-fg-CustomScenery

|-
| LSGS || Sion Airport || Switzerland || Europe || Basic development only

|-
| LSZB || Bern-Belp Airport || Switzerland || Europe || Basic development only

|-
| PANC || Ted Stevens Anchorage International Airport || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=136.80541&lat=34.85841&z=13 RJGG] || [[Chūbu Centrair International Airport]] || Japan || Asia || Detailed airport buildings, taxiway layout and customized terrain.

|-
| [https://scenery.flightgear.org/map/?lon=139.78114&lat=35.5533&z=13 RJTT] || [[Tokyo Haneda International Airport]] || Japan || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=126.45051&lat=37.46909&z=13 RKSI] || Seoul Incheon Airport || South Korea || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=121.01349&lat=14.51024&z=13 RPLL] || Manila Aquino Airport || Philippines || Asia || Tower and three large terminals

|-

| SAEZ || Aeropuerto Internacional Ministro Pistarini || Argentina || America || Several static buildings

|-

| [[SVMI]] || Aeropuerto Internacional Simon Bolivar || Venezuela || America || Several static buildings

|-

| TAPA || V.C. Bird Intl Airport || Antigua and Barbuda || America ||

|-
| TDPD || Melville Hall Airport || Dominica || America ||

|-
| TFFF || Martinique Aimé Césaire International Airport || Martinique, France || America ||

|-
| TFFG || Grand Case Airport || St. Maarten, Netherlands || America ||

|-
| TIST || Cyril E. King Airport || US Virgin Islands || America ||

|-
| TJSJ || Luis Muñoz Marín International Airport || Puerto Rico || America ||

|-
| TKPK || Robert L. Bradshaw International Airport || St. Kitts || America ||

|-
| TNCM || [[Princess Juliana International Airport]] || St. Maarten, Netherlands || America || Fully modeled, customized terrain

|-
| TNCS || Juancho E. Yrausquin Airport || Saba || America || Fully modeled

|-
| TQPF || Clayton J. Lloyd International Airport || Anguilla || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-49.17201&lat=-25.53101&z=13 SBCT] || Afonso Pena International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-46.65768&lat=-23.62558&z=13 SBSP] || Congonhas Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-46.46864&lat=-23.43351&z=13 SBGR] || Guarulhos International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-48.54304&lat=-27.6685&z=13 SBFL] || Hercílio Luiz International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| SKRG || Jose Maria Cordoba International Airport, Rionegro, Antioquia || Colombia || South America || Fully Modelled

|-
| VIDP || Indira Gandhi International Airport || India || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=89.42272&lat=27.39994&z=13 VQPR] || [[Paro Airport]] || Bhutan || Asia || Terminal, Buildings, Refernce Points and other POIs

|-
| [https://scenery.flightgear.org/map/?lon=91.50917&lat=27.25961&z=13 VQ10] || [[Yongphulla Airport]] || Bhutan || Asia || Terminal, some other Buildings

|-
| [https://scenery.flightgear.org/map/?lon=113.9183&lat=22.308&z=13 VHHH] || Hong Kong International Airport || Hong Kong || Asia || Terminals, control towers, some other buildings

|-
| [https://scenery.flightgear.org/map/?lon=-81.41707414&lat=41.15689289&z=13 1G3] || Kent State University Airfield, OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-81.76281774&lat=41.13448335&z=13 1G5] || [[Medina Municipal Airport]], OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-81.24620281&lat=41.20973295&z=13 29G] || Portage Co, OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-90.13769&lat=43.83872&z=13 82C] || Mauston-New Lisbon Union Airport, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-89.02545&lat=44.50485&z=13 68C] || Iola Central County Airport, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-123.00815977&lat=43.93009927&z=13 77S] || Hobby Field, Creswell, OR || USA || America || Nearly complete: Hangars (one accidently missing), fuel pump, GA aircraft, cars, trees, bushes (shared models)

|}

== Authors ==

Airports by HerbyW in Yakutia, Irkutsk and Krasnoyarsk:
UIBB UEEE UEST UEMS UEBN UEBT UEWD UEMA UERR UEMT UEEA UEMU UIII UITT UEBB UEVV UENW UEMO UERL UERT UEMH UERO UERP UNAA UIUN UENN UIBV UNCC UEMJ

Airports by D-ABBA:
EDXW,EDFE,EDGS,EDFQ,EDFH,EDFL,EDFO,ED03

Airports by [[User:Laserman]]:
EDDG,EDLM,EDLB,EDLK,EDLN,EDLV,EDLW,LJLJ,LJAJ,LJSG,LJCE,LJPZ

== External links ==
* [http://iveze.nl/fgmap/ Builtup airports in Flightgear] – Interactive world map by KL-666. ''See also related forum topic [http://forum.flightgear.org/viewtopic.php?f=5&t=23613 Map of airports with buildings in terrasync].''

{{Suggested}}

[[Category:Lists]]
[[Category:Airports]]

List of developed airports

2017-02-13T09:30:05Z

Tikibar: /* List of airports */Added modeled airports (KCCR, KTOA) to the list.

This is an incomplete '''list of developed airports''' in the FlightGear [[TerraSync]] scenery.

Airports can be listed here if these two conditions are fulfilled:
* At least one building or [[Signs|taxi signs]] have been placed
* Objects are represented in the [[FlightGear Scenery Database]].

Every improvement listed here should be possible to download using TerraSync. These improvements will also be included in the next [[World Scenery]] release.

__TOC__

== For airport developers ==
If you are currently developing an airport, please feel free to add it to [[Airports under construction]]. For a list of currently ongoing scenery related projects, please check out [[Current Scenery Projects]].

== List of airports ==
The ICAO codes link to the FlightGear mapserver, which - among other things - contains information about the current status of the [[FlightGear Scenery Database]]. On a map, you will see:
* The current airport layout with runways, taxiways and aprons
* Red dots: static objects in the scenery database made especially for this airport
* Dark red dots: shared models in the scenery database placed at this airport
* Green dots: [[Signs|taxi signs]] placed at the airport

{{inote|You can sort the table by clicking one of the [[File:Sort none.gif]] symbols in the row headers.}}

{| class="wikitable sortable" border="0" cellspacing="0"
|-
! ICAO !! Name !! Country !! Continent !! class="unsortable" | Comment

|-
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 EDDC] || [[Dresden Airport]] || Germany || Europe || Fully modeled with tower, terminal, animated hangars etc.

|-
| [https://scenery.flightgear.org/map/?lon=8.56293&lat=50.03795&z=13 EDDF] || [[Frankfurt am Main Airport]] || Germany || Europe || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique scycrapers downtown

|-
| EDDG || [[Münster Osnabrück]] || Germany || Europe || 1 static + 100 shared objects

|-
| EDDH || [[Hamburg Airport]] || Germany || Europe || Fully modeled, plus unique buildings downtown

|-
| [https://scenery.flightgear.org/map/?lon=13.40379&lat=52.47502&z=13 EDDI] ||[[Berlin Tempelhof Airport]] || Germany || Europe || Fully modeled

|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf Airport]] || Germany || Europe || Fully modeled, many shared objects

|-
| [https://scenery.flightgear.org/map/?lon=11.78609&lat=48.35378&z=13 EDDM] || [[Munich Airport]] || Germany || Europe || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=12.23603&lat=51.42262&z=13 EDDP] || [[Leipzig/Halle Airport]] || Germany || Europe || Fully modelled with [[Signs]]

|-
| EDDS || [[Stuttgart Airport]] || Germany || Europe || Fully modelled based on Shared-Models, incl. [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=13.28992&lat=52.55917&z=13 EDDT] || [[Berlin Tegel Airport]] || Germany || Europe || Tower, terminals, [[Signs]] and unique buildings downtown

|-
| EDFB || Reichelsheim Airport || Germany || Europe || Tower done

|-
| EDFM || [[Mannheim City Airport]] || Germany || Europe || Basic models of tower, terminals and hangars

|-
| [https://scenery.flightgear.org/map/?lon=10.71706&lat=53.80496&z=13 EDHL] || [[Lübeck Blankensee Airport]] || Germany || Europe || Almost complete, home of the [[Piper PA34-200T Seneca II|Seneca]] used to model the FlightGear version. A modified tile is available at [http://www.t3r.de/fg/scenery/ Torsten's scenery site]

|-
| [https://scenery.flightgear.org/map/?lon=7.16278&lat=50.76767&z=13 EDKB] || [[Bonn-Hangelar Airport]] || Germany || Europe ||

|-
| EDLW || [[Flughafen Dortmund]] || Germany || Europe || Fully modelled

|-
| EDVE || [[Braunschweig Airport]] || Germany || Europe || Fully modelled

|-
| EEKE || Kuressaare Airport || Estonia || Europe ||

|-
| EETN || Lennart Meri Tallinn Airport || Estonia || Europe ||

|-
| EETU || Tartu Airport || Estonia || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=25.04487&lat=60.25318&z=13 EFHF] || Helsinki-Malmi Airport || Finland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=24.95253&lat=60.3206&z=13 EFHK] || Helsinki-Vantaa Airport || Finland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=22.26281&lat=60.51412&z=13 EFTU] || Turku Airport || Finland || Europe || Tower and terminal modelled

|-
| EGFF || Cardiff Airport || United Kingdom || Europe || One building: British Airways Maintenance Facility

|-
| EGGP || Liverpool John Lennon Airport || United Kingdom || Europe ||

|-
| EGGW || London Luton Airport || United Kingdom || Europe ||

|-
| EGKA || Shoreham Airport || United Kingdom || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-0.19224&lat=51.14869&z=13 EGKK] || [[London Gatwick]] || United Kingdom || Europe || Complete and fully modeled to highest level of detail with day and night textures; AI parking and ground network

|-
| [https://scenery.flightgear.org/map/?lon=-0.46095&lat=51.47139&z=13 EGLL] || London Heathrow Airport || United Kingdom || Europe || Basic development only

|-
| EGPH || Edinburgh Airport || United Kingdom || Europe || Tower, terminal, park deck, and some shared models

|-
| [https://scenery.flightgear.org/map/?lon=1.28469&lat=52.67713&z=13 EGSH] || Norwich Airport || United Kingdom || Europe ||

|-
| EH01 || [[VU University Medical Center]] || Netherlands || Europe || Complete hospital building including on-roof heli platform.

|-
| [https://scenery.flightgear.org/map/?lon=4.75487&lat=52.31296&z=13 EHAM] || [[Amsterdam Airport Schiphol]] || Netherlands || Europe || Fully modeled, bussiest AI airport currently

|-
| EHEH || Eindhoven Airport || Netherlands || Europe || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=5.51885&lat=52.45717&z=13 EHLE] || [[Lelystad Airport]] || Netherlands || Europe || Fully modeled

|-
| EHVK || [[Volkel Air Base]] || Netherlands || Europe || Shelters and detailed airport layout.

|-
| EIDW || [[Dublin Airport]] || Ireland || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=6.11017&lat=62.56037&z=13 ENAL] || Ålesund Airport || Norway || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=6.10949&lat=61.83027&z=13 ENSD] || Sandane Airport || Norway || Europe ||

|-
| ENVA || Trondheim Værnes Airport || Norway || Europe ||

|-
| ESGP || Göteborg Airport || Sweden || Europe || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=-106.60912&lat=35.04021&z=13 KABQ] || Albuquerque Sunport Airport, NM || USA || America || Basic development only

|-
| [https://scenery.flightgear.org/map/?lon=-84.42809&lat=33.63672&z=13 KATL] || [[Hartsfield - Jackson Atlanta International Airport]], GA || USA || America || Terminal modeled

|-
| [https://scenery.flightgear.org/map/?lon=-81.4629595&lat=41.0421187&z=13 KAKR] || [[Akron-Fulton International Airport]], OH || USA || America || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=-81.43676804&lat=40.91510112&z=13 KCAK] || Akron-Canton Regional Airport, OH || USA || America || Fully modelled

|-
| KAUS || Austin-Bergstrom Airport, TX || USA || America ||

|-
| KBOS || Boston Logan || USA || America || Tower, Terminals done

|-
| KFNT || Bishop Intl, MI || USA || America || Fully modelled

|-
| [https://scenery.flightgear.org/map/?lon=-76.66833&lat=39.17535&z=13 KBWI] || Baltimore-Washington International, MD || USA || America || Terminal modeled with jetways, parking garage, support buildings and [[Signs]]

|-
| KCCR || Buchanan Field Airport, CA || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-76.92254&lat=38.98062&z=13 KCGS] || College Park Airport, MD || USA || America ||

|-
| KCVG || Cincinnati/Northern Kentucky International Airport, KY || USA || America || Terminals, Concourses, Towers, Signs, DHL Hub, and Other Buildings (Almost Fully Modeled)

|-
| KDCA || Reagan National Airport, VA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-104.67318&lat=39.86166&z=13 KDEN] || [[Denver_International_Airport|Denver Airport, CO]] || USA || America || One terminal modelled

|-
| KDTW || Detroit Metropolitan Wayne County Airport, MI || USA || America || Basic development only

|-
| KFHR || Friday Harbor Airport, WA || USA || America ||

|-
| KIND || Indianapolis Airport, IN || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-90.07589&lat=32.31118&z=13 KJAN] || Jackson-Evers Airport, MS || USA || America ||

|-
| KJFK || [[John F. Kennedy International Airport]], NY || USA || America ||

|-
| KLAS || Las Vegas McCarran Airport, NV || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-118.40809&lat=33.9425&z=13 KLAX] || [[Los Angeles International Airport]], CA || USA|| America || Fully modeled

|-
| KLSV || [[Nellis Air Force Base]], NV || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-109.4667&lat=47.04924&z=13 KLWT] || Lewistown Municipal Airport, MT || USA || America ||

|-
| KMCI || Kansas City Airport, MO || USA || America || Basic development only

|-
| KMPI || Mariposa-Yosemite Airport, CA || USA || America || Hangars and FBO.

|-
| KMTN || Martin State Airport, MD || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-117.69181&lat=35.68565&z=13 KNID] || China Lake Naval Air Weapons Station, CA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.04918&lat=37.4162&z=13 KNUQ] || Moffett Federal Airfield, CA || USA || America || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-122.22062&lat=37.7214&z=13 KOAK] || [[Oakland International Airport]], CA || USA || America || Realistic terminal, currently undergoing maintenance

|-
| KORD || Chicago [[O'Hare International Airport]], IL || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-88.55704&lat=43.98436&z=13 KOSH] || Wittman Regional Airport, Oshkosh, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-75.12398&lat=38.31045&z=13 KOXB] || Ocean City Municipal Airport, MD || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.59751&lat=45.58871&z=13 KPDX] || Portland Airport, OR || USA || America ||

|-
| KPHX || Phoenix Sky Harbor Airport, AZ || USA || America ||

|-
| KRNO || Reno/Tahoe Airport, NV || USA || America ||

|-
| KSEA || [[Seattle-Tacoma International Airport]], WA || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-122.3749&lat=37.61897&z=13 KSFO] || [[San Francisco International Airport]], CA || USA || America || FlightGear's default airport, terminal buildings, airport lights and airport train.

|-
| KSLC || Salt Lake City International Airport, UT || USA || America ||

|-
| KTOA || Zamperini Field, CA || USA || America || Fully modeled

|-
| KXTA || Edwards Airforce Base Detachment 3 (Homey Airport, or Area 51), NV || USA || America || Fully Modelled

|-
| KVUO || Pearson Field Airport, Vancouver, WA || USA || America ||

|-
| LDSP || Split Airport || Croatia || Europe || Basic development only

|-
| LEBB || Bilbao || Spain || Europe || Fully modeled

|-
| LEMD || Madrid - Barajas || Spain || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=-3.19889&lat=47.32611&z=13 LFEA] || Belle-Ile || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.10167&lat=47.48139&z=13 LFEQ] || Quiberon || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.66479&lat=48.05247&z=13 LFES] || Guiscriff Scaër || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=2.35465&lat=49.04626&z=13 LFFE] || Enghien Moisselles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=4.8264&lat=45.25226&z=13 LFLR] || Saint Rambert d'Albon Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=13.76716&lat=51.13277&z=13 LFMA] || Aix - Les Milles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=0.08816&lat=49.53404&z=13 LFOH] || Le Havre Octeville Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=5.36736&lat=43.50499&z=13 LFPG] || Charles de Gaulle International Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.60632&lat=48.89629&z=13 LFPH] || Chelles Le Pin Airport || France || Europe || Fully modeled, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.622793&lat=48.822237&z=13 LFPL] || Lognes Emerainville Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.359443&lat=48.72551&z=13 LFPO] || Paris-Orly Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=2.073197&lat=48.810622&z=13 LFPZ] || St-Cyr-l’École Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [https://scenery.flightgear.org/map/?lon=-4.41785&lat=48.44413&z=13 LFRB] || Brest Bretagne Airport || France || Europe || Modeled airport with static models

|-
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRL] || Lanvéoc Naval Air Base || France || Europe || Airport fitted with shared models (for helos and training)

|-
| [https://scenery.flightgear.org/map/?lon=-4.15167&lat=48.53014&z=13 LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]

|-
| [https://scenery.flightgear.org/map/?lon=-4.167981&lat=47.97553&z=13 LFRQ] || Quimper || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.816762&lat=48.601247&z=13 LFRU] || Morlaix || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-2.736754&lat=47.717558&z=13 LFRV] || Vannes || France || Europe || Airport fitted with shared models

|-
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFRH] || Lorient - Bretagne Sud || France || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=-3.439579&lat=47.760964&z=13 LFSB] || [[EuroAirport Basel-Mulhouse-Freiburg|Basel Mulhouse]] || Switzerland || Europe || Nice modelling of Terminal.

|-
| LILN || Venegono Airport || Italy || Europe || Developed airport

|-
| LILQ || Massa Cinquale Airport || Italy || Europe ||

|-
| LILV || Valbrembo Airport || Italy || Europe ||

|-
| LIMC || Milano-Malpensa Airport || Italy || Europe ||

|-
| [https://scenery.flightgear.org/map/?lon=9.70741&lat=45.66952&z=13 LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=9.27521&lat=45.44776&z=13 LIML] || [[LIML|Milano-Linate Airport]] || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=7.36789&lat=45.73857&z=13 LIMW] || Aosta Airport || Italy || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=14.26&lat=50.100833&z=13 LKPR] || [[Václav Havel Airport Prague]] (Ruzyne) || Czech Republic || Europe || Fully modeled

|-
| [https://scenery.flightgear.org/map/?lon=11.34397&lat=47.26023&z=13 LOWI] || [[Innsbruck Airport]] || Austria || Europe ||

|-
| LROP || Bucharest Otopeni || Romania || Europe ||

|-
| LSGG || Geneve (Cointrin) Airport || Switzerland || Europe || Fully Modelled. OSM2city available on https://github.com/FGMEMBERS-SCENERY/LSGG-fg-CustomScenery

|-
| LSGS || Sion Airport || Switzerland || Europe || Basic development only

|-
| LSZB || Bern-Belp Airport || Switzerland || Europe || Basic development only

|-
| PANC || Ted Stevens Anchorage International Airport || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=136.80541&lat=34.85841&z=13 RJGG] || [[Chūbu Centrair International Airport]] || Japan || Asia || Detailed airport buildings, taxiway layout and customized terrain.

|-
| [https://scenery.flightgear.org/map/?lon=139.78114&lat=35.5533&z=13 RJTT] || [[Tokyo Haneda International Airport]] || Japan || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=126.45051&lat=37.46909&z=13 RKSI] || Seoul Incheon Airport || South Korea || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=121.01349&lat=14.51024&z=13 RPLL] || Manila Aquino Airport || Philippines || Asia || Tower and three large terminals

|-

| SAEZ || Aeropuerto Internacional Ministro Pistarini || Argentina || America || Several static buildings

|-

| [[SVMI]] || Aeropuerto Internacional Simon Bolivar || Venezuela || America || Several static buildings

|-

| TAPA || V.C. Bird Intl Airport || Antigua and Barbuda || America ||

|-
| TDPD || Melville Hall Airport || Dominica || America ||

|-
| TFFF || Martinique Aimé Césaire International Airport || Martinique, France || America ||

|-
| TFFG || Grand Case Airport || St. Maarten, Netherlands || America ||

|-
| TIST || Cyril E. King Airport || US Virgin Islands || America ||

|-
| TJSJ || Luis Muñoz Marín International Airport || Puerto Rico || America ||

|-
| TKPK || Robert L. Bradshaw International Airport || St. Kitts || America ||

|-
| TNCM || [[Princess Juliana International Airport]] || St. Maarten, Netherlands || America || Fully modeled, customized terrain

|-
| TNCS || Juancho E. Yrausquin Airport || Saba || America || Fully modeled

|-
| TQPF || Clayton J. Lloyd International Airport || Anguilla || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-49.17201&lat=-25.53101&z=13 SBCT] || Afonso Pena International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-46.65768&lat=-23.62558&z=13 SBSP] || Congonhas Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-46.46864&lat=-23.43351&z=13 SBGR] || Guarulhos International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| [https://scenery.flightgear.org/map/?lon=-48.54304&lat=-27.6685&z=13 SBFL] || Hercílio Luiz International Airport || Brazil || South America || 3D Fully modeled - Download [http://djrick1.wix.com/grupofgbr/aeroportos#!__aeroportos Site Group FGBR]

|-
| SKRG || Jose Maria Cordoba International Airport, Rionegro, Antioquia || Colombia || South America || Fully Modelled

|-
| VIDP || Indira Gandhi International Airport || India || Asia ||

|-
| [https://scenery.flightgear.org/map/?lon=89.42272&lat=27.39994&z=13 VQPR] || [[Paro Airport]] || Bhutan || Asia || Terminal, Buildings, Refernce Points and other POIs

|-
| [https://scenery.flightgear.org/map/?lon=91.50917&lat=27.25961&z=13 VQ10] || [[Yongphulla Airport]] || Bhutan || Asia || Terminal, some other Buildings

|-
| [https://scenery.flightgear.org/map/?lon=113.9183&lat=22.308&z=13 VHHH] || Hong Kong International Airport || Hong Kong || Asia || Terminals, control towers, some other buildings

|-
| [https://scenery.flightgear.org/map/?lon=-81.41707414&lat=41.15689289&z=13 1G3] || Kent State University Airfield, OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-81.76281774&lat=41.13448335&z=13 1G5] || [[Medina Municipal Airport]], OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-81.24620281&lat=41.20973295&z=13 29G] || Portage Co, OH || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-90.13769&lat=43.83872&z=13 82C] || Mauston-New Lisbon Union Airport, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-89.02545&lat=44.50485&z=13 68C] || Iola Central County Airport, WI || USA || America ||

|-
| [https://scenery.flightgear.org/map/?lon=-123.00815977&lat=43.93009927&z=13 77S] || Hobby Field, Creswell, OR || USA || America || Nearly complete: Hangars (one accidently missing), fuel pump, GA aircraft, cars, trees, bushes (shared models)

|}

== Authors ==

Airports by HerbyW in Yakutia, Irkutsk and Krasnoyarsk:
UIBB UEEE UEST UEMS UEBN UEBT UEWD UEMA UERR UEMT UEEA UEMU UIII UITT UEBB UEVV UENW UEMO UERL UERT UEMH UERO UERP UNAA UIUN UENN UIBV UNCC UEMJ

Airports by D-ABBA:
EDXW,EDFE,EDGS,EDFQ,EDFH,EDFL,EDFO,ED03

Airports by [[User:Laserman]]:
EDDG,EDLM,EDLB,EDLK,EDLN,EDLV,EDLW,LJLJ,LJAJ,LJSG,LJCE,LJPZ

== External links ==
* [http://iveze.nl/fgmap/ Builtup airports in Flightgear] – Interactive world map by KL-666. ''See also related forum topic [http://forum.flightgear.org/viewtopic.php?f=5&t=23613 Map of airports with buildings in terrasync].''

{{Suggested}}

[[Category:Lists]]
[[Category:Airports]]

User:Tikibar

2016-04-27T08:25:59Z

Tikibar:

Tikibar's real name is John. He works on the following aircraft:
* Boeing 747-8, both Intercontinental and Freighter ([https://github.com/dogsaysmoo/747-8i/archive/master.zip development version], change folder name to "747-8i")
* Boeing 757-200 and 757-300 ([https://github.com/dogsaysmoo/757-200/archive/master.zip development version], change folder name to "757-200")
* Boeing 767-300 and 767-300ER ([https://github.com/dogsaysmoo/767-300/archive/master.zip development version], change folder name to "767-300")
* McDonnell Douglas MD-11 and MD-11F ([https://github.com/dogsaysmoo/md-11/archive/master.zip development version], change folder name to "MD-11")
He is also preparing:
* [[757/767 Autopilot and Autothrottle|Boeing 757/767 Autopilot and Autothrottle]]

757/767 Autopilot and autothrottle

2016-04-27T08:21:22Z

Tikibar: Explanation of the controls for the autopilot system found on the Boeing 757 and 767 models.

This page is a work in progress. For now, there's some text explaining what the buttons all do. In time, labeled images will be added to complement the text. Hang on.

# A/T ARM – Switch must be in the up position to turn on the autothrottle.
# THR – Push to activate the autothrottle in thrust-hold mode. If no thrust mode is selected, the current thrust will be maintained. If a thrust mode is selected, the preset thrust for that mode will be maintained. If TO thrust mode is selected, the A/T can be activated in THR mode on the ground. THR is inhibited for other thrust modes below 200 ft agl. If AP is in V/S or ALT HOLD mode and A/T is in SPD mode, pressing the THR button will set the A/T to THR mode and the AP will adjust pitch to hold speed at the current thrust.
# SPD – Push to activate autothrottle in speed-by-thrust mode. A/T cannot be activated in this mode below 200 ft agl. If AP is in V/S or ALT HOLD mode and A/T is in SPD mode, pressing the SPD button will set the A/T to THR mode and the AP will adjust pitch to hold speed at the current thrust.
# IAS/MACH selector – switch between IAS and Mach A/T modes.
# A/T adjustment knob – in IAS mode, adjusts target speed in increments of 1 kt; in Mach mode, adjusts target mach in increments of 0.001 mach.
# LNAV – Follow the flight plan specified in the route manager. Note: a minimum of two (2) points must be specified in the route manager for LNAV to work properly. The departure and arrival airports are sufficient. “INVALID ROUTE” will appear on the EICAS display if fewer than two points are specified. When using LNAV mode with closely spaced waypoints and frequent turns (such as the end phase of RNAV STAR), monitor your speed closely. Flying too fast can cause you to miss waypoints and may lead to unpredictable AP behavior.
# VNAV – Hold and change altitudes as specified in the route manager flight plan. Altitude changes are executed by activating FLCH mode. Note: VNAV only looks ahead to the next waypoint. It does not control vertical speed or pitch angle, and therefore is not equipped to properly manage the climb and descent phases of the flight. When VNAV activates FLCH mode, target altitude cannot be changed until system returns to VNAV mode.
# FLCH – Speed in the A/T display window is maintained by adjusting pitch. If autothrottle is active, A/T mode changes to THR. Thrust mode is set to CLB if climbing more than 3000 feet, otherwise thrust mode is set to CON. If descending, thrust mode is set to IDLE. A/T mode changes to SPD within 500 feet the target altitude. Mode automatically changes to ALT HOLD within 50 feet the target altitude. Pressing the SPD button while in FLCH mode sets the A/T to speed with thrust mode and the maximum climb/descend rate to +-1000 fpm. Mode automatically changes to ALT HOLD within 50 feet the target altitude.
# HDG knob – Change target magnetic heading in increments of 1 degree. (Use left and middle mouse buttons on the edge of the knob or use the mouse scroll wheel to rotate).
# HDG SEL – Turn to and hold the target magnetic heading. (Left click the middle of the knob).
# BANK LIMIT Knob – AP bank angle limiter (Auto, 5, 10, 15, 20, 25, 30 deg). Note: If BANK LIMIT is set to “Auto,” the aircraft will not turn at speeds greater than 0.86 mach.
# HDG HOLD – Hold the current heading.
# VERT SPD wheel – Adjust the vertical speed when in V/S mode in increments of 100 fpm.
# VS/FPA – Activate V/S mode at the current vertical speed (rounded to the nearest 100 fpm). Mode automatically changes to ALT HOLD when the target altitude is reached.
# ALT knob – Adjust the target altitude in increments of 100 feet.
# ALT HOLD – Hold the current altitude (rounded to the nearest 100 feet).
# LOC – Arms and activates LOC lateral mode to follow VOR radials or localizer approach paths.
# APP – Arms and activates G/S mode to follow ILS glideslope path. Also arms and activates LOC mode.
# CMD – Turns the Autopilot on and off. AP cannot be activated below 200 ft agl. (Press any of the three CMD buttons).
# DISENGAGE – Deactivates and disables all autoflight functions (both Autopilot and Autothrottle). When this switch is open, the pattern shown below appears on the panel. Autoflight functions cannot operate until this switch is closed.
# TO/GA – Select Take Off thrust mode if aircraft is on the ground, or Go Around thrust mode if airborne.
# CLB – Select Climb thrust mode
# 1 and 2 – Reduced thrust for TO and CLB thrust modes.
# CON – Select maximum continuous thrust mode.
# CRZ – Select cruise thrust mode.

Howto:Animated jetways (Type 1)

2016-04-27T08:05:18Z

Tikibar: /* Using the jetways */

'''Animated jetways''' are dynamic {{Wikipedia|jetway|noicon=1}} models that connect to your aircraft when you are pulled up at a gate. [[FlightGear]] boasts the most advanced animated jetways in the flight simulator market, beating those of Microsoft Flight Simulator and X-plane in features — a testament to the flexibility of FlightGear. This article describes how to obtain and use the jetways and interface them with aircraft and scenery.

== Current state (09/2015) ==
At the moment only KSFO has this kind of jetways. see <code>Airports/K/S/F/KSFO.jetways.xml</code> using {{fgdata file|Models/Airport/Jetway/generic.xml|t=$FG_ROOT/Models/Airport/Jetway/generic.xml}}

generic.xml in fgdata is still broken, but there is a repaired Version in terrrasync: http://scenemodels.flightgear.org/app.php?c=Models&a=view&id=2211

== Future Development ==
{{FGCquote
|1= I don't know if anyone remembers the Nasal-based animated jetway code I wrote a few years ago, but I'd like to rewrite it as a clean-sheet C++ subsystem. I want to eliminate the truly atrocious Nasal hacks I used in the initial implementation and make the whole thing faster and more reliable. My objectives as of now are, 1) Implement a new FGJetwayManager subsystem to replace the existing code in jetways.nas. (I have not yet decided what to do with jetways_edit.nas - it might be fixed up instead of outright replaced.) 2) Streamline the jetway model files in fgdata. I want to do away with the generic.airline.<XYZ>.xml files because they're unnecessary clutter. The C++ code can deal with these cases. 3) As for the jetway definition files themselves (<airport>.jetways.xml), the only change I'd like to make is deprecating the "elevation-m" property for each jetway, which is currently relative to the surrounding scenery, including buildings and AI craft (due to the Nasal API). Instead, I propose fixing all jetways to the ground. Rationale: The current method is unreliable (see sunken jetways at KSFO) and I can't imagine a situation when you would need a floating jetway. 4) Performance optimiations - much of this would come from plain superior code, but I also plan to introduce a user preference for "jetway density." That is, you can choose to spawn between 0 to 100% of all jetways defined for an airport. This allows the user to reduce the overhead from rendering and animating all those jetway objects (which is probably the biggest bottleneck besides the current Nasal implementation). This is what FSX does. 5) Potential idea - integration with AI traffic. So that when AI airliners park at their gates, jetways will extend to meet them. The current Nasal code makes an attempt at this, but it's very hacky and unreliable. While I think this is a cool idea, I don't want to interfere with anyone's work on the AI subsystem. I would greatly appreciate any ideas and comments on my proposal, as well as some pointers and tips on getting started with core development. :-)
|2= {{cite web
| url = http://sourceforge.net/p/flightgear/mailman/message/34725917/
| title = <nowiki>[Flightgear-devel] Animated jet bridges redux</nowiki>
| author = <nowiki>Ryan A Young</nowiki>
| date = Dec 29th, 2015
}}
}}

== Obtaining and installing ==

Versions of FlightGear later than June 17, 2011 (so 2.4.0 and onwards) include the animated jetway system. Nothing extra has to be installed.

== Using the jetways ==

Start FlightGear in any animated jetway-compatible aircraft. Currently, these include the following:
* [[Boeing 717]] (separate download) (support available in Git)
* [[Boeing 747-8i]]
* [[Boeing 757-200]] and -300
* [[Boeing 767-300]]/ER
* [[Boeing 777-200ER]] (separate download)
* [[Bombardier CRJ700]]

Fly (or spawn) to any airport equipped with animated jetways. Ensure you have the latest scenery from [[TerraSync]], so you don't get conflicts between animated and static jetways! At the moment, the following airports are animated jetway-compatible:
* [[London Gatwick Airport]] (EGKK)*
* [[Amsterdam Airport Schiphol]] (EHAM)
* Denver International Airport (KDEN)*
* Las Vegas McCarran International Airport (KLAS)*
* [[San Francisco International Airport]] (KSFO)
* Ted Stevens Anchorage International Airport (PANC)*
''<nowiki>*</nowiki> - Indicates the jetways for this airport were auto-converted and do not have gate numbers''

You can tell if a jetway is animated by pressing Ctrl-C. If the polygons are highlighted in yellow, then it's animated.

Taxi up to an animated jetway and park near it. Click it, and if your aircraft is supported and parked well enough, the jetway will extend, rotate, and connect.

== Adding support in aircraft ==

Open up your aircraft's main model in your favorite 3d modeling software (the author prefers [[Blender]]). Move the model around to account for any offsets you have in the main model file. Then get the coordinates of the door.

[[File:Animated-jetway-tutorial.jpg]]

Now add the following code in your aircraft's -set.xml (remember to merge the tags properly):

<syntaxhighlight language="xml">
<sim>
<model>
<door>
<position-x-m type="float">X-M</position-x-m>
<position-y-m type="float">Y-M</position-y-m>
<position-z-m type="float">Z-M</position-z-m>
<jetway-hood-deg type="float">HOOD-DEG</jetway-hood-deg>
</door>
</model>
</sim>
</syntaxhighlight>

Where '''X-M''', '''Y-M''', and '''Z-M''' are the X/Y/Z coordinates of the door in meters and '''HOOD-DEG''' is the jetway hood rotation amount. To specify more doors, just add more door elements.

Finally, add the following code into your XML model file. It enables the jetways to connect to your aircraft over the [[multiplayer]] network.

<nasal>
<load>
var model = cmdarg();
model.getNode("door[0]/position-x-m", 1).setValue(X-M);
model.getNode("door[0]/position-y-m", 1).setValue(Y-M);
model.getNode("door[0]/position-z-m", 1).setValue(Z-M);
model.getNode("door[0]/jetway-hood-deg", 1).setValue(HOOD-DEG);
</load>
</nasal>

Again, replace '''X-M''', '''Y-M''', '''Z-M''', and '''HOOD-DEG''' with their respective values. To add more doors, duplicate the last 4 lines of [[Nasal]] code and replace <tt>[0]</tt> with <tt>[1]</tt> or <tt>[2]</tt>.

=== Adding support in AI aircraft ===

Follow the steps for regular aircraft above, but only add in the Nasal code.

=== jetway-enabled AI Aircraft (9/2015) ===
<pre>
AI/Aircraft/A319/A319-main.xml
AI/Aircraft/A320/A320-main.xml
AI/Aircraft/737/737-main.xml
AI/Aircraft/MD80/MD80-main.xml
AI/Aircraft/A321/A321-main.xml
AI/Aircraft/747-400/747-400-main.xml
</pre>

== Adding support in scenery ==

=== Placing jetways ===

Launch FlightGear in your favorite aircraft. The author uses the [[Bluebird]]. You ''cannot'' use the [[UFO]] because its scenery-editing function will interfere with the jetway editor. Go to AI > Jetway Settings and tick the "Enable jetway editor" checkbox. Then click the "Open Editor" button.

[[File:Animated-jetway-editor.jpg]]

With the editor enabled, click anywhere on the ground to place an animated jetway, which will flash to indicate it is selected. The jetway editor is similar to the UFO's scenery model editor. You can Alt-click on the terrain to move the current selected jetway. Ctrl-click selects the jetway closest to the click position (the new jetway will flash to indicate it's selected). Shift-click deselects the current jetway.

The dialog is used to adjust the selected jetway. The top sliders adjust position and orientation, and the bottom ones adjust the jetway itself. The offsets that the bottom sliders control can be used to model jetways that are in obscure configurations. The drop-down menus at the very bottom of the dialog control various properties of the jetway, such as the model, gate number, airline sign, and door number. At the moment, the following models are available:

* Generic
* Glass
* [[EHAM]] gate
* [[EHAM]] 747 gate

When you are finished editing your airport jetway layout, click the "Export" button. A jetway definition file will be created and written to <tt>$FG_HOME/Export/ICAO.xml</tt>, where <tt>ICAO</tt> is the ICAO code of the nearest airport. (The exact location of this file is printed to the console window.) This file should be submitted to Terrasync (see [[FlightGear Scenery Database#Contribute]]).

=== Auto-converting static/obsolete jetways ===

{{WIP}}

== Related content ==
=== FlightGear wiki ===
* [[Ramp Marshall]]

=== Forum topics ===
* [http://forum.flightgear.org/viewtopic.php?f=5&t=8728 The animated jetway project]

[[Category:Scenery]]
[[Category:Scenery enhancement]]

Airliner development status

2016-04-05T07:37:40Z

Tikibar: /* Boeing 747 */

The Airliner Development Statuses were previously managed by Skyop in the forum but due to no response there, I created this page. Here, you don't have to go asking someone to change an airliner's status, you can do this yourself.

= Airbus Industries =
== Airbus A300 ==
* Airbus A300-B2 - {{alds|stalled}}
* Airbus A300-B4 - {{alds|stalled}}
* [[Airbus A300-600]] - {{alds|active}}
* [[Airbus A300-600ST]] - {{alds|abandoned}}

== Airbus A310 ==
* Airbus A310-200 - {{alds|not started}}
* [[Airbus A310-300]] - {{alds|active}}

== Airbus A320 ==
* [[A320-family]]
** Airbus A318-100 - {{alds|stable}}
** Airbus A318-200 - {{alds|stable}}
** Airbus A319-100 - {{alds|stable}}
** Airbus A319-200 - {{alds|stable}}
** Airbus A320-100 - {{alds|stable}}
** Airbus A320-200 - {{alds|stable}}
** Airbus A321-100 - {{alds|stable}}
** Airbus A321-200 - {{alds|stable}}

* [[Airbus A320neo|A320neo]]
** Airbus A319neo - {{alds|active}}
** Airbus A320neo - {{alds|active}}
** Airbus A321neo - {{alds|active}}

== Airbus A330 ==
* [[Airbus A330-200]] - {{alds|stable}}, continued by Artix and the Project 300 Dev Team
* Airbus A330-200F - {{alds|not started}}
* [[Airbus A330-300]] - {{alds|stable}}

== Airbus A340 ==
* Airbus A340 - {{alds|not started}}
* [[Airbus A340|Airbus A340-300]] - {{alds|stalled}}
* [[Airbus A340|Airbus A340-500]] - {{alds|active}}
* [[Airbus A340-600]] - {{alds|active}}

== Airbus A350 ==
* Airbus A350-800 -{{alds|not started}}
* Airbus A350-900 - {{alds|stable}}
* Airbus A350-1000 -{{alds|not started}}

== Airbus A380 ==
* [[Airbus A380|Airbus A380-800]] - {{alds|active}}
* Airbus A380-900 - {{alds|not started}}

= Avions Transportation Regional =
== ATR-42 ==
* ATR-42-200 - {{alds|not started}}
* ATR-42-300 - {{alds|not started}}
* ATR-42-500 - {{alds|stalled}}
* ATR-42-600 - {{alds|stalled}}

== ATR-72 ==
* [[ATR 72-500|ATR-72-500]] - {{alds|stalled}}
* ATR-72-600 - {{alds|stalled}}

= Boeing Commercial Airplanes =
== Boeing 707 ==
* [[Boeing 707]]
** Boeing 707-100 - {{alds|not started}}
** Boeing 707-200 - {{alds|not started}}
** Boeing 707-300 - {{alds|abandoned}}
* Boeing 720 - {{alds|not started}}

== Boeing 717 ==
* [[Boeing 717|Boeing 717-200]] - {{alds|stalled}}

== Boeing 727 ==
* Boeing 727-100 - {{alds|not started}}
* Boeing 727-200 - {{alds|stable}}, {{alds|active}} by [[user:it0uchpods]] http://www.github.com/FGMEMBERS/727-230

== Boeing 737 ==
* Boeing 737-100 - {{alds|abandoned}}
* Boeing 737-200 - {{alds|abandoned}}
* [[Boeing 737-300]] - {{alds|stalled}}
* [[Boeing 737-400]] - {{alds|stalled}}
* [[Boeing 737-500]] - {{alds|stalled}}
* Boeing 737NG models - {{alds|active}} by [[user:zakalawe]]
* [[Boeing 737-7 MAX]] - {{alds|not started}}
* [[Boeing 737-8 MAX]] - {{alds|not started}}
* [[Boeing 737-9 MAX]] - {{alds|not started}}

== Boeing 747 ==
* [[Boeing 747-100]] - {{alds|abandoned}}
* [[Boeing 747-200]] - {{alds|abandoned}}
* Boeing 747-300 - {{alds|not started}}
* [[Boeing 747-400]] - {{alds|stable}}
* [[Boeing 747-8i]] - {{alds|active}}
* Boeing 747-8F - {{alds|active}}
* Boeing 747SP - {{alds|active}} by [[user:it0uchpods]] http://www.github.com/it0uchpods/747SP

== Boeing 757 ==
* [[Boeing 757-200]] - {{alds|stable}}
* Boeing 757-300 - {{alds|stable}}

== Boeing 767 ==
* Boeing 767-200 - {{alds|not started}}
* [[Boeing 767-300]] - {{alds|active}}
* [[Boeing 767-300F]] - {{alds|active}}
* Boeing 767-400 - {{alds|not started}}

== Boeing 777 ==
* [[Boeing 777-200]] - {{alds|stable}}
* [[Boeing 777-300]] - {{alds|stable}}
* Boeing 777-8X - {{alds|not started}}
* Boeing 777-9X - {{alds|not started}}

== Boeing 787 ==
* [[Boeing 787-8]] - {{alds|stable}}
* Boeing 787-9 - {{alds|stable}}

= Bombardier Aerospace =
== Dash 7 ==
* Dash 7-100 - {{alds|abandoned}}

== Dash 8 ==
* Dash 8-300 - {{alds|abandoned}}
* Dash 8-Q400 - {{alds|active}}

== Canadair Regional Jets ==
* [[CRJ-200|CRJ200]] - {{alds|active}}
* CRJ700 - {{alds|stable}}
* [[CRJ-900|CRJ900]] - {{alds|stable}}
* CRJ1000 - {{alds|stable}}

== CSeries ==
* CS100 - {{alds|stalled}}
* CS300 - {{alds|stalled}}

= Douglas Aircraft Company =
== DC-1 ==
* DC-1 - {{alds|not started}}

== DC-2 ==
* DC-2 - {{alds|abandoned}}

== DC-3 ==
* DC-3 - {{alds|stable}}

== DC-4 ==
* DC-4 - {{alds|not started}}

== DC-5 ==
* DC-5 - {{alds|not started}}

== DC-6 ==
* DC-6 - {{alds|stable}}

== DC-7 ==
* DC-1 - {{alds|not started}}

== DC-8 ==
* DC-8-10 - {{alds|not started}}
* DC-8-20 - {{alds|not started}}
* DC-8-30 - {{alds|not started}}
* DC-8-40 - {{alds|not started}}
* DC-8-50 - {{alds|not started}}
* DC-8-60 - {{alds|stable}}
* DC-8-70 - {{alds|stable}}

== DC-9 ==
* DC-9-10 - {{alds|not started}}
* DC-9-20 - {{alds|not started}}
* DC-9-30 - {{alds|stalled}} by [[user:it0uchpods]] http://www.github.com/FGMEMBERS-NONGPL/DC-9-32
* DC-9-40 - {{alds|not started}}

== DC-10 ==
* DC-10-10 - {{alds|not started}}
* DC-10-20 - {{alds|not started}}
* DC-10-30 - {{alds|stable}}
* DC-10-40 - {{alds|not started}}

= Embraer Manufacturers =
== Embraer 120 Series ==
* EMB120 - {{alds|not started}}
* EMB125 - {{alds|not started}}
* EMB140 - {{alds|not started}}
* EMB145 - {{alds|abandoned}}

== Embraer E-jet Series ==
* ERJ170 - {{alds|stable}}
* ERJ175 - {{alds|stable}}
* ERJ190 - {{alds|stable}}
* ERJ195 - {{alds|stable}}
* Legacy - {{alds|not started}}

= Fokker Aero-structures =
== Fokker F27 ==
* Fokker F27 - {{alds|not started}}

== Fokker 50 ==
* [[Fokker 50]] - {{alds|abandoned}}

== Fokker 60 ==
* Fokker 60 - {{alds|not started}}

== Fokker 70 ==
* [[Fokker 70]] - {{alds|abandoned}}

== Fokker 100 ==
* [[Fokker 100]] - {{alds|abandoned}}

= Lockheed Corporation =
== Lockheed 1049H ==
* L1049H - {{alds|stable}}

== Lockheed L1011 ==
* L1011-1 - {{alds|not started}}
* L1011-100 - {{alds|not started}}
* L1011-200 - {{alds|not started}}
* L1011-500 - {{alds|abandoned}}

= McDonnell Douglas =

== MD-10 ==
* MD-10-10 - {{alds|stable}}, {{alds|active}} by [[user:it0uchpods]] http://www.github.com/it0uchpods/MD-10-10
* MD-10-30 - {{alds|abandoned}}
== MD-11 ==
* [[MD-11]] - {{alds|stable}}, {{alds|active}} by [[user:it0uchpods]] http://www.github.com/FGMEMBERS/MD-11

== MD-80 ==
* MD-81 - {{alds|abandoned}}
* MD-82 - {{alds|abandoned}}
* MD-83 - {{alds|abandoned}}
* MD-87 - {{alds|not started}}
* MD-88 - {{alds|stable}}, {{alds|active}} by [[user:it0uchpods]] http://www.github.com/it0uchpods/MD-88

== MD-90 ==
* MD-90 - {{alds|active}} by [[user:it0uchpods]] http://www.github.com/it0uchpods/MD-90

[[Category:Aircraft enhancement]]

Airliner development status

2016-04-05T07:35:39Z

Tikibar: /* Boeing 747 */

The Airliner Development Statuses were previously managed by Skyop in the forum but due to no response there, I created this page. Here, you don't have to go asking someone to change an airliner's status, you can do this yourself.

= Airbus Industries =
== Airbus A300 ==
* Airbus A300-B2 - {{alds|stalled}}
* Airbus A300-B4 - {{alds|stalled}}
* [[Airbus A300-600]] - {{alds|active}}
* [[Airbus A300-600ST]] - {{alds|abandoned}}

== Airbus A310 ==
* Airbus A310-200 - {{alds|not started}}
* [[Airbus A310-300]] - {{alds|active}}

== Airbus A320 ==
* [[A320-family]]
** Airbus A318-100 - {{alds|stable}}
** Airbus A318-200 - {{alds|stable}}
** Airbus A319-100 - {{alds|stable}}
** Airbus A319-200 - {{alds|stable}}
** Airbus A320-100 - {{alds|stable}}
** Airbus A320-200 - {{alds|stable}}
** Airbus A321-100 - {{alds|stable}}
** Airbus A321-200 - {{alds|stable}}

* [[Airbus A320neo|A320neo]]
** Airbus A319neo - {{alds|active}}
** Airbus A320neo - {{alds|active}}
** Airbus A321neo - {{alds|active}}

== Airbus A330 ==
* [[Airbus A330-200]] - {{alds|stable}}, continued by Artix and the Project 300 Dev Team
* Airbus A330-200F - {{alds|not started}}
* [[Airbus A330-300]] - {{alds|stable}}

== Airbus A340 ==
* Airbus A340 - {{alds|not started}}
* [[Airbus A340|Airbus A340-300]] - {{alds|stalled}}
* [[Airbus A340|Airbus A340-500]] - {{alds|active}}
* [[Airbus A340-600]] - {{alds|active}}

== Airbus A350 ==
* Airbus A350-800 -{{alds|not started}}
* Airbus A350-900 - {{alds|stable}}
* Airbus A350-1000 -{{alds|not started}}

== Airbus A380 ==
* [[Airbus A380|Airbus A380-800]] - {{alds|active}}
* Airbus A380-900 - {{alds|not started}}

= Avions Transportation Regional =
== ATR-42 ==
* ATR-42-200 - {{alds|not started}}
* ATR-42-300 - {{alds|not started}}
* ATR-42-500 - {{alds|stalled}}
* ATR-42-600 - {{alds|stalled}}

== ATR-72 ==
* [[ATR 72-500|ATR-72-500]] - {{alds|stalled}}
* ATR-72-600 - {{alds|stalled}}

= Boeing Commercial Airplanes =
== Boeing 707 ==
* [[Boeing 707]]
** Boeing 707-100 - {{alds|not started}}
** Boeing 707-200 - {{alds|not started}}
** Boeing 707-300 - {{alds|abandoned}}
* Boeing 720 - {{alds|not started}}

== Boeing 717 ==
* [[Boeing 717|Boeing 717-200]] - {{alds|stalled}}

== Boeing 727 ==
* Boeing 727-100 - {{alds|not started}}
* Boeing 727-200 - {{alds|stable}}, {{alds|active}} by [[user:it0uchpods]] http://www.github.com/FGMEMBERS/727-230

== Boeing 737 ==
* Boeing 737-100 - {{alds|abandoned}}
* Boeing 737-200 - {{alds|abandoned}}
* [[Boeing 737-300]] - {{alds|stalled}}
* [[Boeing 737-400]] - {{alds|stalled}}
* [[Boeing 737-500]] - {{alds|stalled}}
* Boeing 737NG models - {{alds|active}} by [[user:zakalawe]]
* [[Boeing 737-7 MAX]] - {{alds|not started}}
* [[Boeing 737-8 MAX]] - {{alds|not started}}
* [[Boeing 737-9 MAX]] - {{alds|not started}}

== Boeing 747 ==
* [[Boeing 747-100]] - {{alds|abandoned}}
* [[Boeing 747-200]] - {{alds|abandoned}}
* Boeing 747-300 - {{alds|not started}}
* [[Boeing 747-400]] - {{alds|stable}}
* [[Boeing 747-8i]] - {{alds|active}}
* [[Boeing 747-8F]] - {{alds|active}}
* Boeing 747SP - {{alds|active}} by [[user:it0uchpods]] http://www.github.com/it0uchpods/747SP

== Boeing 757 ==
* [[Boeing 757-200]] - {{alds|stable}}
* Boeing 757-300 - {{alds|stable}}

== Boeing 767 ==
* Boeing 767-200 - {{alds|not started}}
* [[Boeing 767-300]] - {{alds|active}}
* [[Boeing 767-300F]] - {{alds|active}}
* Boeing 767-400 - {{alds|not started}}

== Boeing 777 ==
* [[Boeing 777-200]] - {{alds|stable}}
* [[Boeing 777-300]] - {{alds|stable}}
* Boeing 777-8X - {{alds|not started}}
* Boeing 777-9X - {{alds|not started}}

== Boeing 787 ==
* [[Boeing 787-8]] - {{alds|stable}}
* Boeing 787-9 - {{alds|stable}}

= Bombardier Aerospace =
== Dash 7 ==
* Dash 7-100 - {{alds|abandoned}}

== Dash 8 ==
* Dash 8-300 - {{alds|abandoned}}
* Dash 8-Q400 - {{alds|active}}

== Canadair Regional Jets ==
* [[CRJ-200|CRJ200]] - {{alds|active}}
* CRJ700 - {{alds|stable}}
* [[CRJ-900|CRJ900]] - {{alds|stable}}
* CRJ1000 - {{alds|stable}}

== CSeries ==
* CS100 - {{alds|stalled}}
* CS300 - {{alds|stalled}}

= Douglas Aircraft Company =
== DC-1 ==
* DC-1 - {{alds|not started}}

== DC-2 ==
* DC-2 - {{alds|abandoned}}

== DC-3 ==
* DC-3 - {{alds|stable}}

== DC-4 ==
* DC-4 - {{alds|not started}}

== DC-5 ==
* DC-5 - {{alds|not started}}

== DC-6 ==
* DC-6 - {{alds|stable}}

== DC-7 ==
* DC-1 - {{alds|not started}}

== DC-8 ==
* DC-8-10 - {{alds|not started}}
* DC-8-20 - {{alds|not started}}
* DC-8-30 - {{alds|not started}}
* DC-8-40 - {{alds|not started}}
* DC-8-50 - {{alds|not started}}
* DC-8-60 - {{alds|stable}}
* DC-8-70 - {{alds|stable}}

== DC-9 ==
* DC-9-10 - {{alds|not started}}
* DC-9-20 - {{alds|not started}}
* DC-9-30 - {{alds|stalled}} by [[user:it0uchpods]] http://www.github.com/FGMEMBERS-NONGPL/DC-9-32
* DC-9-40 - {{alds|not started}}

== DC-10 ==
* DC-10-10 - {{alds|not started}}
* DC-10-20 - {{alds|not started}}
* DC-10-30 - {{alds|stable}}
* DC-10-40 - {{alds|not started}}

= Embraer Manufacturers =
== Embraer 120 Series ==
* EMB120 - {{alds|not started}}
* EMB125 - {{alds|not started}}
* EMB140 - {{alds|not started}}
* EMB145 - {{alds|abandoned}}

== Embraer E-jet Series ==
* ERJ170 - {{alds|stable}}
* ERJ175 - {{alds|stable}}
* ERJ190 - {{alds|stable}}
* ERJ195 - {{alds|stable}}
* Legacy - {{alds|not started}}

= Fokker Aero-structures =
== Fokker F27 ==
* Fokker F27 - {{alds|not started}}

== Fokker 50 ==
* [[Fokker 50]] - {{alds|abandoned}}

== Fokker 60 ==
* Fokker 60 - {{alds|not started}}

== Fokker 70 ==
* [[Fokker 70]] - {{alds|abandoned}}

== Fokker 100 ==
* [[Fokker 100]] - {{alds|abandoned}}

= Lockheed Corporation =
== Lockheed 1049H ==
* L1049H - {{alds|stable}}

== Lockheed L1011 ==
* L1011-1 - {{alds|not started}}
* L1011-100 - {{alds|not started}}
* L1011-200 - {{alds|not started}}
* L1011-500 - {{alds|abandoned}}

= McDonnell Douglas =

== MD-10 ==
* MD-10-10 - {{alds|stable}}, {{alds|active}} by [[user:it0uchpods]] http://www.github.com/it0uchpods/MD-10-10
* MD-10-30 - {{alds|abandoned}}
== MD-11 ==
* [[MD-11]] - {{alds|stable}}, {{alds|active}} by [[user:it0uchpods]] http://www.github.com/FGMEMBERS/MD-11

== MD-80 ==
* MD-81 - {{alds|abandoned}}
* MD-82 - {{alds|abandoned}}
* MD-83 - {{alds|abandoned}}
* MD-87 - {{alds|not started}}
* MD-88 - {{alds|stable}}, {{alds|active}} by [[user:it0uchpods]] http://www.github.com/it0uchpods/MD-88

== MD-90 ==
* MD-90 - {{alds|active}} by [[user:it0uchpods]] http://www.github.com/it0uchpods/MD-90

[[Category:Aircraft enhancement]]

Airliner development status

2016-04-05T07:34:45Z

Tikibar: /* Boeing 747 */

The Airliner Development Statuses were previously managed by Skyop in the forum but due to no response there, I created this page. Here, you don't have to go asking someone to change an airliner's status, you can do this yourself.

= Airbus Industries =
== Airbus A300 ==
* Airbus A300-B2 - {{alds|stalled}}
* Airbus A300-B4 - {{alds|stalled}}
* [[Airbus A300-600]] - {{alds|active}}
* [[Airbus A300-600ST]] - {{alds|abandoned}}

== Airbus A310 ==
* Airbus A310-200 - {{alds|not started}}
* [[Airbus A310-300]] - {{alds|active}}

== Airbus A320 ==
* [[A320-family]]
** Airbus A318-100 - {{alds|stable}}
** Airbus A318-200 - {{alds|stable}}
** Airbus A319-100 - {{alds|stable}}
** Airbus A319-200 - {{alds|stable}}
** Airbus A320-100 - {{alds|stable}}
** Airbus A320-200 - {{alds|stable}}
** Airbus A321-100 - {{alds|stable}}
** Airbus A321-200 - {{alds|stable}}

* [[Airbus A320neo|A320neo]]
** Airbus A319neo - {{alds|active}}
** Airbus A320neo - {{alds|active}}
** Airbus A321neo - {{alds|active}}

== Airbus A330 ==
* [[Airbus A330-200]] - {{alds|stable}}, continued by Artix and the Project 300 Dev Team
* Airbus A330-200F - {{alds|not started}}
* [[Airbus A330-300]] - {{alds|stable}}

== Airbus A340 ==
* Airbus A340 - {{alds|not started}}
* [[Airbus A340|Airbus A340-300]] - {{alds|stalled}}
* [[Airbus A340|Airbus A340-500]] - {{alds|active}}
* [[Airbus A340-600]] - {{alds|active}}

== Airbus A350 ==
* Airbus A350-800 -{{alds|not started}}
* Airbus A350-900 - {{alds|stable}}
* Airbus A350-1000 -{{alds|not started}}

== Airbus A380 ==
* [[Airbus A380|Airbus A380-800]] - {{alds|active}}
* Airbus A380-900 - {{alds|not started}}

= Avions Transportation Regional =
== ATR-42 ==
* ATR-42-200 - {{alds|not started}}
* ATR-42-300 - {{alds|not started}}
* ATR-42-500 - {{alds|stalled}}
* ATR-42-600 - {{alds|stalled}}

== ATR-72 ==
* [[ATR 72-500|ATR-72-500]] - {{alds|stalled}}
* ATR-72-600 - {{alds|stalled}}

= Boeing Commercial Airplanes =
== Boeing 707 ==
* [[Boeing 707]]
** Boeing 707-100 - {{alds|not started}}
** Boeing 707-200 - {{alds|not started}}
** Boeing 707-300 - {{alds|abandoned}}
* Boeing 720 - {{alds|not started}}

== Boeing 717 ==
* [[Boeing 717|Boeing 717-200]] - {{alds|stalled}}

== Boeing 727 ==
* Boeing 727-100 - {{alds|not started}}
* Boeing 727-200 - {{alds|stable}}, {{alds|active}} by [[user:it0uchpods]] http://www.github.com/FGMEMBERS/727-230

== Boeing 737 ==
* Boeing 737-100 - {{alds|abandoned}}
* Boeing 737-200 - {{alds|abandoned}}
* [[Boeing 737-300]] - {{alds|stalled}}
* [[Boeing 737-400]] - {{alds|stalled}}
* [[Boeing 737-500]] - {{alds|stalled}}
* Boeing 737NG models - {{alds|active}} by [[user:zakalawe]]
* [[Boeing 737-7 MAX]] - {{alds|not started}}
* [[Boeing 737-8 MAX]] - {{alds|not started}}
* [[Boeing 737-9 MAX]] - {{alds|not started}}

== Boeing 747 ==
* [[Boeing 747-100]] - {{alds|abandoned}}
* [[Boeing 747-200]] - {{alds|abandoned}}
* Boeing 747-300 - {{alds|not started}}
* [[Boeing 747-400]] - {{alds|stable}}
* [[Boeing 747-8i]] - {{alds|active}}
* Boeing 747SP - {{alds|active}} by [[user:it0uchpods]] http://www.github.com/it0uchpods/747SP

== Boeing 757 ==
* [[Boeing 757-200]] - {{alds|stable}}
* Boeing 757-300 - {{alds|stable}}

== Boeing 767 ==
* Boeing 767-200 - {{alds|not started}}
* [[Boeing 767-300]] - {{alds|active}}
* [[Boeing 767-300F]] - {{alds|active}}
* Boeing 767-400 - {{alds|not started}}

== Boeing 777 ==
* [[Boeing 777-200]] - {{alds|stable}}
* [[Boeing 777-300]] - {{alds|stable}}
* Boeing 777-8X - {{alds|not started}}
* Boeing 777-9X - {{alds|not started}}

== Boeing 787 ==
* [[Boeing 787-8]] - {{alds|stable}}
* Boeing 787-9 - {{alds|stable}}

= Bombardier Aerospace =
== Dash 7 ==
* Dash 7-100 - {{alds|abandoned}}

== Dash 8 ==
* Dash 8-300 - {{alds|abandoned}}
* Dash 8-Q400 - {{alds|active}}

== Canadair Regional Jets ==
* [[CRJ-200|CRJ200]] - {{alds|active}}
* CRJ700 - {{alds|stable}}
* [[CRJ-900|CRJ900]] - {{alds|stable}}
* CRJ1000 - {{alds|stable}}

== CSeries ==
* CS100 - {{alds|stalled}}
* CS300 - {{alds|stalled}}

= Douglas Aircraft Company =
== DC-1 ==
* DC-1 - {{alds|not started}}

== DC-2 ==
* DC-2 - {{alds|abandoned}}

== DC-3 ==
* DC-3 - {{alds|stable}}

== DC-4 ==
* DC-4 - {{alds|not started}}

== DC-5 ==
* DC-5 - {{alds|not started}}

== DC-6 ==
* DC-6 - {{alds|stable}}

== DC-7 ==
* DC-1 - {{alds|not started}}

== DC-8 ==
* DC-8-10 - {{alds|not started}}
* DC-8-20 - {{alds|not started}}
* DC-8-30 - {{alds|not started}}
* DC-8-40 - {{alds|not started}}
* DC-8-50 - {{alds|not started}}
* DC-8-60 - {{alds|stable}}
* DC-8-70 - {{alds|stable}}

== DC-9 ==
* DC-9-10 - {{alds|not started}}
* DC-9-20 - {{alds|not started}}
* DC-9-30 - {{alds|stalled}} by [[user:it0uchpods]] http://www.github.com/FGMEMBERS-NONGPL/DC-9-32
* DC-9-40 - {{alds|not started}}

== DC-10 ==
* DC-10-10 - {{alds|not started}}
* DC-10-20 - {{alds|not started}}
* DC-10-30 - {{alds|stable}}
* DC-10-40 - {{alds|not started}}

= Embraer Manufacturers =
== Embraer 120 Series ==
* EMB120 - {{alds|not started}}
* EMB125 - {{alds|not started}}
* EMB140 - {{alds|not started}}
* EMB145 - {{alds|abandoned}}

== Embraer E-jet Series ==
* ERJ170 - {{alds|stable}}
* ERJ175 - {{alds|stable}}
* ERJ190 - {{alds|stable}}
* ERJ195 - {{alds|stable}}
* Legacy - {{alds|not started}}

= Fokker Aero-structures =
== Fokker F27 ==
* Fokker F27 - {{alds|not started}}

== Fokker 50 ==
* [[Fokker 50]] - {{alds|abandoned}}

== Fokker 60 ==
* Fokker 60 - {{alds|not started}}

== Fokker 70 ==
* [[Fokker 70]] - {{alds|abandoned}}

== Fokker 100 ==
* [[Fokker 100]] - {{alds|abandoned}}

= Lockheed Corporation =
== Lockheed 1049H ==
* L1049H - {{alds|stable}}

== Lockheed L1011 ==
* L1011-1 - {{alds|not started}}
* L1011-100 - {{alds|not started}}
* L1011-200 - {{alds|not started}}
* L1011-500 - {{alds|abandoned}}

= McDonnell Douglas =

== MD-10 ==
* MD-10-10 - {{alds|stable}}, {{alds|active}} by [[user:it0uchpods]] http://www.github.com/it0uchpods/MD-10-10
* MD-10-30 - {{alds|abandoned}}
== MD-11 ==
* [[MD-11]] - {{alds|stable}}, {{alds|active}} by [[user:it0uchpods]] http://www.github.com/FGMEMBERS/MD-11

== MD-80 ==
* MD-81 - {{alds|abandoned}}
* MD-82 - {{alds|abandoned}}
* MD-83 - {{alds|abandoned}}
* MD-87 - {{alds|not started}}
* MD-88 - {{alds|stable}}, {{alds|active}} by [[user:it0uchpods]] http://www.github.com/it0uchpods/MD-88

== MD-90 ==
* MD-90 - {{alds|active}} by [[user:it0uchpods]] http://www.github.com/it0uchpods/MD-90

[[Category:Aircraft enhancement]]

User:Tikibar

2016-04-05T05:58:24Z

Tikibar: Created page with "Tikibar's real name is John. He works on the following aircraft: * Boeing 747-8, both Intercontinental and Freighter ([https://github.com/dogsaysmoo/747-8i/archive/master.zip..."

Canvas ND framework

2015-12-22T16:48:57Z

Tikibar: /* Aircraft Support */

[[File:Canvasready.png|right]]
{{infobox subsystem
|image = Navigation display MAP mode.png
|alt = MAP mode with a [[Standard Instrument Departure|SID]] from Eindhoven Airport
|name = NavDisplay
|started = 11/2013
|description = [[Canvas]]/[[Nasal]] driven NDs
|status = Under active development as of 12/2013
|maintainers = Gijs (B747), Hyde (B777), Soitanen (B737NG), (Hooray, Philosopher & D-LEON via [[MapStructure]])
|developers = [[User:Gijs]] (since 11/2013)
}}
{{Canvas Avionics}}

The '''navigation display''' ('''ND''') is a display in a glass cockpit, providing information about an aircraft's lateral situation. As of late 2013, a new fully-scripted ND ([[Navigation display]] being the old) is in development for [[FlightGear]] using the new [[MapStructure]] back-end for charting purposes, and SVG symbols animated via Nasal functions for any non-mapping aspects (typically using listeners and timers).

Thanks to [[Canvas]], much more complex and sophisticated graphics are possible now, without having to know any C++, and without having to rebuild FlightGear from source. Anybody able to run FlightGear and a text editor, can now easily use and extend the ND framework, or add support for new types (styles) of NDs.

Extending the framework should normally require very little in terms of coding - typically, people can simply take an existing feature/symbol, copy & paste the code section and customize it according to their needs (e.g. different SVG element id, different animations, different properties) - symbols can be easily changed by providing a separate SVG file, or by creating a new one via Inkscape.

The main source is located at {{fgdata file|Nasal/canvas/map/navdisplay.mfd}}. Aircraft-specifics can be found in {{fgdata file|Nasal/canvas/map/navdisplay.styles}}.

[[File:777-200-ND-Controls.png|thumb|Screen shot showing the control panel of the 777-200ER for controlling the Canvas-based [[NavDisplay]]]]

== Adding the navigation display to your aircraft ==
The new ND is available in FlightGear 3.0 as of February 2014.

Note that the latest ND code is currently only available in Git and not in the latest stable release.
# Add a surface object to your 3D model and apply a place holder texture to it. You can refer to the 747-400 and 777 for examples.
# Copy the ND.nas file of the Boeing 777 into your own aircraft directory ([{{fgaddon url|777|Models/Instruments/ND/ND.nas}} $FG_ROOT/Aircraft/777/Models/Instruments/ND/ND.nas]).
# Add the file to the <nasal> block in your aircraft's [[Aircraft-set.xml|-set.xml]] file.
# In order to customize the ND for your specific aircraft, change a few options in your ND.nas file:
## the node behind <code>addPlacement</code> is the name of the object in your 3D model. For multiple independent NDs, each ND should have its own object (and thus placement node). The 777 for example has a "ndScreenL" and a "ndScreenR".
## Rename the properties in the "myCockpit_switches" hash at the top of the ND.nas file to match your own properties (range selector, mode selector etc.), see [{{fgaddon url|747-400|Models/Cockpit/Instruments/ND/ND.nas}} $FG_ROOT/Aircraft/747-400/Models/Cockpit/Instruments/ND/ND.nas]. You're advised to use the defaults (and change other systems of your aircraft accordingly). For an overview of switches, see [[#Cockpit switches]].
# Add knobs/buttons to the 3D model of your cockpit to control the various options of the ND. See [{{fgaddon url|777|Models/Instruments/EFIS/efis-ctl1.xml}} $FG_ROOT/Aircraft/777/Models/Instruments/EFIS/efis-ctl1.xml] for an example.
# Add a binding to your screen(s) to open the ND in a popup dialog. See [{{fgaddon url|777|Models/Instruments/ND/ND_L.xml}} $FG_ROOT/Aircraft/777/Models/Instruments/ND/ND_L.xml] for an example.

That's the only thing you need to do right now. future changes will be in navdisplay.mfd and will be automatically available to you once they're committed/merged, no changes needed in your ND.nas at all, except for additional switches/buttons that may be created, and which would obviously need to be mapped to your cockpit hot spots.

If you are facing problems with the steps outlined above, please get in touch via the article's talk page or the forum, so that the instructions can be improved accordingly. Thank you!

A more detailed step-by-step guide can be [[#Step by Step|found below]].

=== Cockpit switches ===
{{Note|The default property is '''relative''' to the root location of your ND, it is NOT an absolute path. Boolean values (true/false) can also be just 1/0. The list of switches below is correct for FG 3.0 - future versions may support additional switches. In the future, we're also going to make the ND style-able this way, so that colors, fonts, size (LOD) and symbols can be customized easily via ND.nas. FlightGear 3.1 introduces an optional hash argument called '''options''' which is a hash that supports layer-specific options (more details to follow) }}

{| class="wikitable"
! Switch !! Description !! Default property !! Accepted values !! new in 3.1+
|-
| toggle_airports || Display airports on the map || /inputs/arpt || true, false
|-
| toggle_centered || Center ND modes || /inputs/nd-centered || true, false
|-
| toggle_data || Display way point data on the map || /inputs/data || true, false
|-
| toggle_display_mode || Change display mode || /mfd/display-mode || APP, MAP, PLAN, VOR
|-
| toggle_display_type || Change display type || /mfd/display-type || CRT, LCD
|-
| toggle_lh_vor_adf || Left navigation (-1 = ADF, 0 = OFF, 1 = VOR) || /inputs/lh-vor-adf || -1, 0, 1
|-
| toggle_position || Display position data on the map (currently unused) || /inputs/pos || true, false
|-
| toggle_range || Range of the maps in nautical miles || /inputs/range-nm || Any positive number
|-
| toggle_rangearc || Display range arcs || /mfd/rangearc || true,false
|-
| toggle_rh_vor_adf || Right navigation (-1 = ADF, 0 = OFF, 1 = VOR) || /inputs/rh-vor-adf || -1, 0, 1
|-
| toggle_stations || Show/hide stations (VOR/DME/NDB) || /inputs/sta || true/false || options:{ radios:[0,1] } (WIP)
|-
| toggle_terrain || Terrain radar (currently unused) || /inputs/terr || true, false
|-
| toggle_track_heading || toggle track/heading mode (new in 3.1+)|| /trk-selected || true, false ||
|-
| toggle_traffic || Display [[Traffic alert and collision avoidance system|TCAS]] data || /inputs/tfc || true, false
|-
| toggle_true_north || Toggle true or magnetic north || /mfd/true-north || true, false
|-
| toggle_waypoints || Display way points (fixes) on the map || /inputs/wpt || true, false
|-
| toggle_weather || Weather radar || /inputs/wxr || true, false
|}

== Aircraft Support ==
For the framework to become sufficiently generalized and aircraft-agnostic, we need many different aircraft to adopt it and aircraft developers to provide feedback regarding missing features.
We are looking for people interested in integrating the new system, so that it can be better developed with different requirements in mind.

The 747 and 777 are the primary reference examples for now.
The following people/aircraft are currently in the process of adopting the new NavDisplay (please add any related efforts here):

* 01/2014: Gijs (747-400) {{Progressbar|100}}
* 01/2014: Hyde (777-200) {{Progressbar|100}}
* 02/2014: mueko (A320) {{Progressbar|90}} [http://forum.flightgear.org/viewtopic.php?f=71&t=22045&p=200427#p200422]
* 08/2014: artix (A330-200) {{Progressbar|70}} [http://forum.flightgear.org/viewtopic.php?f=14&t=23736] (including a [http://forum.flightgear.org/viewtopic.php?f=71&t=24201 custom Airbus ND style])

* 02/2014: Soitanen (737-300) {{Progressbar|80}} [http://forum.flightgear.org/viewtopic.php?f=71&t=21509&start=15#p200304]
* 02/2014: Sascha (A310) {{Progressbar|10}}
* 02/2014: drdavid (DC10) {{Progressbar|30}}
* 02/2014: 5H1N0B1 (m2000-5) {{Progressbar|100}}
* 09/2014: cain071546 (707) [http://forum.flightgear.org/viewtopic.php?f=14&t=24095&p=219086#p219086] {{Progressbar|10}}
* 05/2015: tikibar (747-8) {{Progressbar|100}}
* 05/2015: tikibar (757-200) {{Progressbar|100}}
* 05/2015: jormapaapa1235 and tikibar (MD-11) {{Progressbar|100}}
* 12/2015: tikibar (767-300) {{Progressbar|100}}

If you are finding yourself having problems integrating the framework, please refer to already integrated aircraft as reference/example, or get in touch with their maintainers - ideally, via the forum, so that everybody can contribute and benefit.

== Design ==
{{FGCquote
|Originally, it was a single monolithic update() method that would basically be called at frame rate using a settimer/maketimer callback.<br/>
When things were restructured, the conditional parts of this huge method were moved into predicates that reside in a huge hash: [https://gitorious.org/fg/fgdata/source/Nasal/canvas/map/navdisplay.styles#L14 https://gitorious.org/fg/fgdata/source/ ... styles#L14]<br/>
Meanwhile, the update() method has been inflated again due to some logic that wasn't added to the hash, e.g. see: [https://gitorious.org/fg/fgdata/source/Nasal/canvas/map/navdisplay.mfd#L476 https://gitorious.org/fg/fgdata/source/ ... y.mfd#L476]<br/>
<br/>
The meat of it still is in update(), and those "layers" are fairly boring meanwhile because they're separately managed by Philosopher's MapStructure framework.<br/>
<br/>
But individual ND elements (canvas groups) are basically SVG-driven, i.e. SVG elements that are looked up and then updated/animated via timers and listeners: [https://gitorious.org/fg/fgdata/source/f3df87622ca60eb45f359c05bd913524eeb44667:Nasal/canvas/map/navdisplay.styles#L183 https://gitorious.org/fg/fgdata/source/ ... tyles#L183]<br/>
<br/>
The actual code evaluating each SVG predicate is still called via the update() method, but it's just a foreach loop with a few lines:<br/>
[https://gitorious.org/fg/fgdata/source/Nasal/canvas/map/navdisplay.mfd#L760-769 https://gitorious.org/fg/fgdata/source/ ... d#L760-769]<br/>
<br/>
None of this is set in stone, and we're actually looking forward to generalizing this some more.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=212488#p212488
|title=<nowiki>Re: Event Management module for post 3.2</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Fri Jun 13</nowiki>
}}
}}
== Custom ND Styles ==

{{Note|As of early 2015 the following section is slightly outdated: Artix has recently created an Airbus specific ND style and we're hoping to see additional ND styles/types to be supported over time, to help increasingly unify the framework accordingly.}}

Note that setup instructions above will initially just give you a Boeing-centric ND, because it is currently being developed by the 747/777 maintainers primarily - please use the issue tracker to file feature requests for missing features.

Over time, the framework will grow and become more flexible,so that also specifics of non-Boeing aircraft can be properly emulated. But obviously this will take a while. We invite aircraft developers to help extend and refine the framework accordingly.

Design-wise, the ND code still isn't quite there yet, so unless someone is already very familiar with Nasal/Canvas, I would still postpone any custom implementations - it is better to coordinate things with Gijs and Hyde to keep on improving the existing ND, rather than re-implementing an airbus-specific one at the moment. Simply because things are very much in flux still - there's quite a bit of refactoring pending, and it seems that neither of us is going to tackle this anytime soon.

We can obviously not stop anybody from working with that code, but we would very much prefer to scratch off a handful of items from our todo list first - otherwise, this is going to be a maintenance problem in the mid-term.

Working on anything listed there should help prepare the design such that the framework becomes more aircraft agnostic, i.e. to support manufacturer-specific ND types.

Currently, we are simply not there yet - and some of the recent additions aren't exactly making this much easier unfortunately.

''The thing is, even if someone were to come up with a 100% correct/working A320 implementation now, the framework itself would not yet be sufficiently generalized - some of the recent additions are making things more complicated here, such as the inflated update() method, the Boeing-specific constructor and hard-coded assumptions in the newMFD() method.''

None of this is really difficult to fix, but these things need to be tackled first - otherwise, we'll have too many "construction sites" eventually.

Also, working on different Boeing-centric implementations will help us generalize things a bit more over time, which will surely come in handy once supporting other airliners.

We appreciate any help in maintaining and updating these frameworks, but currently these are not yet as flexible (aircraft-agnostic) as they need to be.

'''Speaking in non-coding terms: When we refactored the ND code, we explicitly wanted to support different makes/models for different aircraft using a single back-end and code base. And that's something that is already prepared in the design in several places, and it may seem straightforward to people not familiar with the code.

Here, you could say that the ND itself is the 3D model, while the "style" is analogous to a "livery" (texture pack).

The way things are implemented, we prepared support for "livery packs", and for easily creating new styles without having to touch the code.

However, currently there's still some work that needs to be done, and Gijs, Hyde and Soitanen have added features that need to be integrated properly first - you could say that they're working on the "3D model" still, so it's not such a good idea to create lots of "liveries" (styles) currently. Or those would need to updated/ported later on.'''

So it would be better to wait a little here and provide plenty of feedback in the meantime - if you really want to, you can get involved in the ND/MapStructure efforts themselves, but I would not yet suggest to come up with a totally new ND implementation - unless you're also prepared/willing to do the necessary groundwork, i.e. Nasal-space refactoring - the latter will mostly affect the new/newMFD/update functions - so not too difficult to understand if you are interested.

Otherwise, I would just suggest to watch the whole effort - The Boeing-ND stuff still needs quite a bit of work, and once more things are completed, we can better finalize the underlying frameworks.

== Gallery ==
<gallery mode="packed" widths="230px" heights="230px">
Navigation display MAP mode.png|MAP mode
Navigation display centered MAP mode.png|Centered MAP mode
Navigation display PLAN mode.png|PLAN mode
NavDisplay-GUIFrontend.png|NavDisplay/MapStructure testbed
</gallery>

== Adding new MapStructure Layers ==
To add a new mapping layer to display custom symbols (radar, scenery objects etc), you only need to open $FG_ROOT/Nasal/canvas/map/navdisplay.styles, navigate to the vector named '''layers''' and add your new layer there, e.g. named "AA":
<syntaxhighlight lang="nasal">
{ name:'AA', isMapStructure:1, update_on:['toggle_range','toggle_display_mode'],
predicate: func(nd, layer) {
# toggle visibility here
var visible=nd.in_mode('toggle_display_mode', ['MAP']);
layer.group.setVisible( visible );
if (visible) {
#print("Updating MapStructure ND layer: AA");
layer.update();
}
}, # end of layer update predicate
'z-index': 1,
}, # end of AA layer
</syntaxhighlight>

You may want to add new switches to directly toggle the layer on/off

== Adding new features ==
{{Note|Please get in touch with [[User:Gijs]] before touching navdisplay.styles, and don't touch navdisplay.mfd without coordinating your work via the forum first.
If you are primarily interested in porting/adding new '''mapping''' layers (such as e.g. waypoints, route, weather etc), please see the [[MapStructure]] article for details.
Otherwise, this section is focused on dealing with non-mapping aspects, i.e. ND-specific SVG symbols and animating them via properties and calculations. Typically, a new symbol will require 10-20 lines of code added to navdisplay.styles - it will typically take 5-10 minutes to add a new animated symbol to the ND.}}
If you want to add new features to the navdisplay.styles code, you need to open that file and map an existing SVG element to a Nasal callback routine - that's how everything is working currently. A straightforward examples can be found in the implementation of the '''planArcs''' symbol animation:

<syntaxhighlight lang="nasal">
{
id:'planArcs',
impl: {
init: func(nd,symbol) {},
predicate: func(nd) { nd.in_mode('toggle_display_mode', ['PLAN']) },
is_true: func(nd) { nd.symbols.planArcs.show() },
is_false: func(nd) { nd.symbols.planArcs.hide() },
},
},
</syntaxhighlight>

This is hash entry, linked to the SVG element whose id is '''planArcs'''. The embedded hash named '''impl''' contains 4 fields:
* '''init()''': a Nasal function that will be invoked to initialize the symbol
* '''predicate()''': a Nasal function that will be invoked to check some condition when updating (predicate)
* '''is_true()''': the Nasal function that will be executed if the condition is true
* '''is_false()''': the Nasal function that will be executed if the condition is false

Except for the init() callback, all others get passed a single argument called '''nd''' which is the instance of the current nd, i.e. the equivalent of '''me''', Nasal's '''this''' pointer. In the future, we're hoping to generalize this a little better and also use the init signature, which should make for shorter/more readable code.

In this case, the predicate will merely determine in which mode a certain switch is and hide/show the symbol (SVG element) accordingly. Here, it's checking that the '''display-mode''' switch is set to '''PLAN''' mode, and otherwise hide the symbol.

Switches are configured at the top of the navdisplay.mfd file, but will usually be overridden by each aircraft-specific ND.nas, i.e. by the aircraft developer. For now, modes are hard-coded and people should refer to the code to see what's supported there.

{{Note|The whole layout/approach of the navdisplay.style file isn't set in stone at all - it just ended up being a simple workaround to accomplish some goals, while also allowing newcomers to easily maintain/extend the system by just having to go through a handful of lines of code. At some point this may further evolve. It would now even be straightforward to move the whole thing to XML space using a simple script that turns our hash into XML. But ultimately we hope to wait a little with that until a generic '''MFD''' framework has evolved that can also be used for other displays like a PFD, CDU or EFB.}}

There's a "configuration hash" called "NDStyles" at the top of the file. Each aircraft can have its own entry in NDStyles, such as NDStyles["Boeing"] or NavDisplay["Airbus"]. Then, all the required canvas callbacks are listed there, i.e. the font mapper etc.

There's also an entry for a custom SVG filename. However, we encourage people to get in touch with Gijs and Hyde to help coordinate all ND development a little - so that a common (and shared) SVG file can be used for most use-cases, this is already the case for the B744 and B777 - we're hoping to get other aircraft developers involved, to help generalize the SVG file, instead of having dozens of different files and symbols. Most features should be identical or at least very similar. Which is why it's a good idea to get in touch with other people working on the ND code.

Lines 52-131 set up existing layers, which are now shared with the GUI code - so that is where new layers are added.
Aircraft specific SVG elements are added at the end, after line 132

For now, we suggest to directly use the 747-400 ND - but the framework is now prepared to easily style & customize it for different aircraft, we will probably add a tutorial to the wiki to explain how things are hanging together there. The constructor and init methods may still need some work to generalize things there, because they are basically still the original code.

So to replace the 747 ND and customize it, these are the steps:

* add a new entry to the NDStyles hash, for example "777-200"
* you can simply copy the configuration stuff from the 747 to get started
* start customizing things there
* open the SVG file in inkscape and change it as required, save it
* change the SVG filename in your NDStyles["777-200"] hash entry to match your own file name
* provide animation callbacks for any 777 specific elements
* open your own copy of ND.nas
* change the constructor call .new() to specify the name of your new NDStyles entry
* by default, this is 747-400 for the time being, for example:
<syntaxhighlight lang="nasal">
var NDCpt = ND.new("instrumentation/efis", myCockpit_switches, "777-200" );
</syntaxhighlight>

the "777-200" part needs to match the identifier used in the NDStyles hash.

To get started, just copy the whole 747-400 section in NDStyles and rename it to match your needs. Once that is working (getting a 747-400 ND via the 777-200 identifier), you can simply replace the SVG file name and add your own update handlers to incrementally come up with your own ND.

== Step by Step ==

{{Note|The following section is currently work-in-progress, it is being written by 5H1N0B1 and drdavid, please get in touch to help reviewing/improving things.}}
More detailed instruction. See if it could help.

# Have an updated version of FlightGear (V. 3.0+).
# Set up the 3D model in this way:

To create a 3D MFD ->
* Select a 3D Border (border of the screen, with screws, etc.)
* Need to have a 3D Button/switch, molette, or turnable knob
* A 3D Screen object, with:
** correct dimensions
** Single texture, -> with correct dimensions
** Correct dimension of the UVmap

# Copy and paste the ND.nas file to the appropriate folder (In the Mirage 2000 this was the "Center-mfd" folder).
# Add the ND.nas pathway to your base .xml file in the Nasal block.
# Edit ND.nas :
* Rename the screen to match the object in 1)c) if needed.
* If installing a single MFD, you do not need another object, so suppress the line (when it's calling the object itself)
* Keep the property's name -> it's ok. You just need to input it with the .xml button in 1)b)

Now, let's add the xml itself.

Really simple, it's just playing with properties. For example, see this for the airport property:

<syntaxhighlight lang="xml">

<animation>
<type>pick</type>
<object-name>bt-h1</object-name>
<visible>true</visible>
<action>
<button>0</button>
<binding>
<command>property-toggle</command>
<property>/instrumentation/efis/inputs/arpt</property>
</binding>
</action>
</animation>
</syntaxhighlight>

Or here again for the range selection:
<syntaxhighlight lang="xml">
<animation>
<type>pick</type>
<object-name>trim1</object-name>
<action>
<button>4</button>

<repeatable>false</repeatable>
<binding>
<command>property-cycle</command>
<property>/instrumentation/efis/inputs/range-nm</property>
<value>10</value>
<value>20</value>
<value>40</value>
<value>80</value>
<value>160</value>
<value>320</value>
</binding>
</action>
</animation>

<animation>
<type>pick</type>
<object-name>trim1</object-name>
<action>
<button>3</button>

<repeatable>false</repeatable>
<binding>
<command>property-cycle</command>
<property>/instrumentation/efis/inputs/range-nm</property>
<value>320</value>
<value>160</value>
<value>80</value>
<value>40</value>
<value>20</value>
<value>10</value>
</binding>
</action>
</animation>
</syntaxhighlight>

Next, you can optionally add this:

<syntaxhighlight lang="xml">
<animation>
<type>pick</type>
<object-name>blackbkd</object-name>
<action>
<button>0</button>
<repeatable>false</repeatable>
<binding>
<command>nasal</command>
<script>mirage2000.showNd();</script>
</binding>
</action>
</animation>
</syntaxhighlight>

Where 'blackbkd' is the screen.

This last option allows you to open a dialog box with what the actual canvas should display in your 1)c) screen. This is very useful to check all the different steps when something isn't working well. However, you'll need to change '''mirage2000''' to match the name of your own aircraft/namespace.

Normally following these steps, you should have a working MFD.

== Development ==

== Team Boeing ==
{{Note| Please get in touch with the following contributors if you're planning on making changes related to the Boeing ND:
* Gijs
* Hyde
}}

== Team Airbus ==
{{Note| Please get in touch with the following contributors if you're planning on making changes related to the Airbus ND:
* artix
* omega95
}}

=== Backward Compatibility ===
Once we support a handful of different '''styles''', it would probably make sense to refactor the styles file so that we end up with dedicated files for each style, e.g. by having:

* $FG_ROOT/Nasal/canvas/map/ND/nd.airbus
* $FG_ROOT/Nasal/canvas/map/ND/nd.boeing

However, it makes sense to wait a little with this so that multiple styles can evolve in parallel, to ensure that overlapping functionality can be generalized and refactored/reused. Equally, that would allow us to provide versioning support, so that aircraft developers can request a certain version of the "ND API", e.g.:

* $FG_ROOT/Nasal/canvas/map/ND/nd.airbus-3_4
* $FG_ROOT/Nasal/canvas/map/ND/nd.airbus-4_0

{{FGCquote
|Overall, we may sooner or later support backward compatibility by using something like io.include() with a nested version number and/or API call, it is not exactly difficult. For now, it would require just a few lines of code. The real challenge is that the code is very much evolving still, so it would be premature to implement something like that currently, especially because there's still many features missing so that establishing feature parity would be difficult at best - once things stabilize, and once multiple styles/aircraft are supported, we could/should revisit that. But unless someone else steps up to implement a working scheme, I am not currently interested in establishing such an API, at a time when things are being constantly refactored - we are seeing a handful of related efforts currently. And even Gijs mentioned a few times that he's still hoping to add new features - so adding API-level versioning/backward compatibility would probably become pretty awkward soon, and it would also involve other parts that don't actively support backward compatibility - Tom is using a getprop("/sim/version") check in api.nas - so it is possible, but only makes sense once the dust settles.
At least for the time being, I'd estimate that it might take another 2-3 release cycles until this should be re-considered, unless we'll see more ND contributions rolling in shortly.
If you do want to work out some kind of BC scheme, you are obviously invited to post your thoughts, I won't object any suggestions and will surely help review them to get them committed - but I'd probably not target 3.0, but instead 3.2 so that you have some kind of baseline to work with.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=221158#p221158
|title=<nowiki>Re: What's going on with the Navdisplay</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sat Oct 18</nowiki>
}}
}}

=== Getting rid of Aircraft Dependencies ===
* the constructor/newMFD() methods still contain a few hard-coded assumptions due to the origins of the code, but those can be also moved into some kind of construct() field in the hash, or you can simply use the method I suggested, i.e. hiding unneeded symbols. But you're right, that the most proper solution would be identifying non-generic code that contains hard-coded assumptions and moving that into some kind of construct() field that is simply invoked by the new/newMFD() methods. Doing that would not be difficult, it would be just copy & paste - i.e. copy from the navdisplay.mfd file into the style file, by adding a corresponding hash field entry there - and calling it instead. Takes under 3 minutes[http://forum.flightgear.org/viewtopic.php?f=71&t=21509&p=214897#p214835]

=== Encapsulating Properties ===
{{FGCquote
| think this and similar problems will be coming up for more or less every aircraft as the properties differ between FDM:s and sometimes even between aircraft.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213016#p213016
|title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
|author=<nowiki>Johan G</nowiki>
|date=<nowiki>Fri Jun 20</nowiki>
}}
}}
{{FGCquote
|aircraft, which will use NavDisplay must have airspeed-indicator, created as built-in instrument, so I prefer to select airspeed indicator as source (which is close to reality).
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213018#p213018
|title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
|author=<nowiki>Soitanen</nowiki>
|date=<nowiki>Fri Jun 20</nowiki>
}}
}}

{{FGCquote
|We could implement a way for individual aircraft to feed the ND with their own properties. However, standardizing the properties would make more sense, also for other use cases (bindings for input devices, dialogs etc.). That is even more important for the PFD, since there are dozens of different autopilot properties being used in FlightGear.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213025#p213025
|title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
|author=<nowiki>Gijs</nowiki>
|date=<nowiki>Fri Jun 20</nowiki>
}}
}}

{{FGCquote
|This kind of thing is already done in both, MapStructure and the NavDisplay, it just isn't widely used yet - but we did establish the infrastructure for this. You must be aware of it, because you kept maintaining and fixing the NDSourceDriver logic that encapsulates properties for AI traffic. The same method can be found in aircraftpos.controller to hide aircraft specifics in a "delegate" hash that provides an "abstract interface" without the back-end code having to be aware of the underlying properties.<br/>
<br/>
As long as aircraft developers agree to use, and help maintain, a corresponding hash, we can help enforce this as a "best practice" - but this should obviously be part of navdisplay.mfd itself (or even a separately-included file), so that it can be easily reused by PFD code eventually, without being specific to the MapStructure/ND code.<br/>
<br/>
We reall only need to extend the ND.new() constructor to support such "overrides" and pass them on to the underlying callbacks, which is kinda touching the whole MVC approach already used by the MapStructure framework.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214377#p214377
|title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Tue Jul 08</nowiki>
}}
}}

=== Post 3.2 ===
Gijs has already begun to clean up the update() method, and navdisplay.mfd is now back down to under 800 lines of code. Hooray will need to revisit adding support for '''switches''' (i.e. a helper class) and corresponding display modes.

At that point, we can probably simplify most things easily and move them out of the mfd file. There are some opportunities to clean up navdisplay.styles by looking at identical/similar code, such as the altArc vs. altArcCtr handling, which is basically boilerplate code. We can probably reduce navdisplay.mfd down to ~500 lines, which is mainly a matter of fixing up the update() method and making the newMFD() helper more generic.

Once that is the case, navdisplay.mfd should be generic enough to be also useful to help with porting the existing PFD code, because it's ultimately no longer ND specific, but simply a framework for animation SVG elements on a Canvas. Performance-wise, we can easily optimize the existing code by getting rid of the foreach() loop in update() and using exclusively listeners to selectively invoke only required predicates.

That would even allow us to get rid of the maketimer() hack. A few computations could/should probably be shared by being moved to '''common''' entry and writing their results to a hash, so that other elements can reuse previous results, e.g. altRangePx, rotation angles etc - there's no need, to recompute those in each callback. On the ctor side, we may want to allow individual elements to be easily disabled or overridden, analogous to how MapStructure layers can be customized/styled and disabled. We could probably reuse the same code we're using for options/style handling here. Otherwise, there are still a few "hard-coded" getprop() references that should better use the NDSourceDriver logic, or its MapStructure equivalent, i.e. aircraftpos.controller.

There are also still a few properties that should become configurable, like we once said WRT to having multiple instances of an instrument/radio etc

{{FGCquote
|just so that I don't forget about it: [https://gitorious.org/fg/fgdata/commit/7da1406cfbed8af69c5cefe215b4f327d791423d https://gitorious.org/fg/fgdata/commit/ ... 27d791423d]<br/>
<br/>
<ul>
<li> append(m.listeners ........ seems a common idiom: provide either a helper method or extend the underlying base class accordingly</li>
<li> WPT/RTE options should probably be exposed via the ctor, so that the ND code can override those defaults ?</li>
<li> unify WPT/RTE handling for wpt num ?</li>
<li> maybe provide a base class for both that encapsulates identical requirements ?</li>
<li> FIX.symbol still contains hard-coded colors, should be using styling there, TFC.symbol is using hard-coded colors & font size</li>
<li> navdisplay: swithcing between CTR & PLAN mode should be better supported by encapsulating setTranslation() etc</li>
<li> get rid of _draw_rwy_nd() calls</li>
<li> port runway-nd.draw , and support styling there</li>
</ul>

|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214252#p214252
|title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Mon Jul 07</nowiki>
}}
}}

=== Misc ===
{{Todo:NavDisplay}}

== Bugs ==

== Feature Requests ==
* feature layers: also pass the symbol instance to each predicate/callback to simplify those methods
* generalize & unify with MapStructure layer handling (update, show, hide)

[[Category:Aircraft instruments]]
[[Category:Canvas]]

Canvas ND framework

2015-05-17T17:24:56Z

Tikibar: /* Aircraft Support */

{{Template:Non-stable|version=3.2|progress=60}}

[[File:Canvasready.png|right]]
{{infobox subsystem
|image = Navigation display MAP mode.png
|alt = MAP mode with a [[Standard Instrument Departure|SID]] from Eindhoven Airport
|name = NavDisplay
|started = 11/2013
|description = [[Canvas]]/[[Nasal]] driven NDs
|status = Under active development as of 12/2013
|maintainers = Gijs (B747), Hyde(B777), Soitanen(B737NG), (Hooray, Philosopher & D-LEON via [[MapStructure]])
|developers = [[User:Gijs]] (since 11/2013)
}}
{{Canvas Avionics}}

The '''navigation display''' ('''ND''') is a display in a glass cockpit, providing information about an aircraft's lateral situation. As of late 2013, a new fully-scripted ND ([[Navigation display]] being the old) is in development for [[FlightGear]] using the new [[MapStructure]] back-end for charting purposes, and SVG symbols animated via Nasal functions for any non-mapping aspects (typically using listeners and timers).

Thanks to [[Canvas]], much more complex and sophisticated graphics are possible now, without having to know any C++, and without having to rebuild FlightGear from source. Anybody able to run FlightGear and a text editor, can now easily use and extend the ND framework, or add support for new types (styles) of NDs.

Extending the framework should normally require very little in terms of coding - typically, people can simply take an existing feature/symbol, copy & paste the code section and customize it according to their needs (e.g. different SVG element id, different animations, different properties) - symbols can be easily changed by providing a separate SVG file, or by creating a new one via Inkscape.

It can be found on [[Git]] in fgdata/master (2.99). The main source is located in <tt>{{Git link|gitorious|fg/fgdata|master|Nasal/canvas/map/navdisplay.mfd|pre=$FG_ROOT/}}</tt> aircraft-specifics can be found in {{Git link|gitorious|fg/fgdata|master|Nasal/canvas/map/navdisplay.styles|pre=$FG_ROOT/}}.

[[File:777-200-ND-Controls.png|thumb|Screen shot showing the control panel of the 777-200ER for controlling the Canvas-based [[NavDisplay]]]]

== Adding the navigation display to your aircraft ==
The new ND is available in FlightGear 3.0 as of February 2014.

Note that the latest ND code is currently only available in Git and not in the latest stable release.
# Add a surface object to your 3D model and apply a place holder texture to it. You can refer to the 747-400 and 777 for examples.
# Copy the ND.nas file of the Boeing 777 into your own aircraft directory (<tt>{{Git link|gitorious|fg/fgdata|master|Aircraft/777/Models/Instruments/ND/ND.nas|pre=[[$FG_ROOT]]/}}</tt>).
# Add the file to the <nasal> block in your aircraft's [[Aircraft-set.xml|-set.xml]] file.
# In order to customize the ND for your specific aircraft, change a few options in your ND.nas file:
## the node behind <code>addPlacement</code> is the name of the object in your 3D model. For multiple independent NDs, each ND should have its own object (and thus placement node). The 777 for example has a "ndScreenL" and a "ndScreenR".
## Rename the properties in the "myCockpit_switches" hash at the top of the ND.nas file to match your own properties (range selector, mode selector etc.), see {{Git link|gitorious|fg/fgdata|master|Aircraft/747-400/Models/Cockpit/Instruments/ND/ND.nas|3|22|pre=[[$FG_ROOT]]/}} You're advised to use the defaults (and change other systems of your aircraft accordingly). For an overview of switches, see [[#Cockpit switches]].
# Add knobs/buttons to the 3D model of your cockpit to control the various options of the ND. See <tt>{{Git link|gitorious|fg/fgdata|master|Aircraft/777/Models/Instruments/EFIS/efis-ctl1.xml|pre=[[$FG_ROOT]]/}}</tt> for an example.
# Add a binding to your screen(s) to open the ND in a popup dialog. See <tt>{{Git link|gitorious|fg/fgdata|master|Aircraft/777/Models/Instruments/ND/ND_L.xml|pre=[[$FG_ROOT]]/}}</tt> for an example.

That's the only thing you need to do right now. future changes will be in navdisplay.mfd and will be automatically available to you once they're committed/merged, no changes needed in your ND.nas at all, except for additional switches/buttons that may be created, and which would obviously need to be mapped to your cockpit hot spots.

If you are facing problems with the steps outlined above, please get in touch via the article's talk page or the forum, so that the instructions can be improved accordingly. Thank you!

A more detailed step-by-step guide can be [[#Step by Step|found below]].

=== Cockpit switches ===
{{Note|The default property is '''relative''' to the root location of your ND, it is NOT an absolute path. Boolean values (true/false) can also be just 1/0. The list of switches below is correct for FG 3.0 - future versions may support additional switches. In the future, we're also going to make the ND style-able this way, so that colors, fonts, size (LOD) and symbols can be customized easily via ND.nas. FlightGear 3.1 introduces an optional hash argument called '''options''' which is a hash that supports layer-specific options (more details to follow) }}

{| class="wikitable"
! Switch !! Description !! Default property !! Accepted values !! new in 3.1+
|-
| toggle_airports || Display airports on the map || /inputs/arpt || true, false
|-
| toggle_centered || Center ND modes || /inputs/nd-centered || true, false
|-
| toggle_data || Display way point data on the map || /inputs/data || true, false
|-
| toggle_display_mode || Change display mode || /mfd/display-mode || APP, MAP, PLAN, VOR
|-
| toggle_display_type || Change display type || /mfd/display-type || CRT, LCD
|-
| toggle_lh_vor_adf || Left navigation (-1 = ADF, 0 = OFF, 1 = VOR) || /inputs/lh-vor-adf || -1, 0, 1
|-
| toggle_position || Display position data on the map (currently unused) || /inputs/pos || true, false
|-
| toggle_range || Range of the maps in nautical miles || /inputs/range-nm || Any positive number
|-
| toggle_rangearc || Display range arcs || /mfd/rangearc || true,false
|-
| toggle_rh_vor_adf || Right navigation (-1 = ADF, 0 = OFF, 1 = VOR) || /inputs/rh-vor-adf || -1, 0, 1
|-
| toggle_stations || Show/hide stations (VOR/DME/NDB) || /inputs/sta || true/false || options:{ radios:[0,1] } (WIP)
|-
| toggle_terrain || Terrain radar (currently unused) || /inputs/terr || true, false
|-
| toggle_track_heading || toggle track/heading mode (new in 3.1+)|| /trk-selected || true, false ||
|-
| toggle_traffic || Display [[Traffic alert and collision avoidance system|TCAS]] data || /inputs/tfc || true, false
|-
| toggle_true_north || Toggle true or magnetic north || /mfd/true-north || true, false
|-
| toggle_waypoints || Display way points (fixes) on the map || /inputs/wpt || true, false
|-
| toggle_weather || Weather radar || /inputs/wxr || true, false
|}

== Aircraft Support ==
For the framework to become sufficiently generalized and aircraft-agnostic, we need many different aircraft to adopt it and aircraft developers to provide feedback regarding missing features.
We are looking for people interested in integrating the new system, so that it can be better developed with different requirements in mind.

The 747 and 777 are the primary reference examples for now.
The following people/aircraft are currently in the process of adopting the new NavDisplay (please add any related efforts here):

* 01/2014: Gijs (747-400) {{Progressbar|100}}
* 01/2014: Hyde (777-200) {{Progressbar|100}}
* 02/2014: mueko (A320) {{Progressbar|90}} [http://forum.flightgear.org/viewtopic.php?f=71&t=22045&p=200427#p200422]
* 08/2014: artix (A330-200) {{Progressbar|70}} [http://forum.flightgear.org/viewtopic.php?f=14&t=23736] (including a [http://forum.flightgear.org/viewtopic.php?f=71&t=24201 custom Airbus ND style])

* 02/2014: Soitanen (737-300) {{Progressbar|80}} [http://forum.flightgear.org/viewtopic.php?f=71&t=21509&start=15#p200304]
* 02/2014: Sascha (A310) {{Progressbar|10}}
* 02/2014: drdavid (DC10) {{Progressbar|30}}
* 02/2014: 5H1N0B1 (m2000-5) {{Progressbar|100}}
* 09/2014: cain071546 (707) [http://forum.flightgear.org/viewtopic.php?f=14&t=24095&p=219086#p219086] {{Progressbar|10}}
* 05/2015: tikibar (747-8) {{Progressbar|100}}
* 05/2015: tikibar (757-200) {{Progressbar|100}}
* 05/2015: jormapaapa1235 and tikibar (MD-11) {{Progressbar|100}}

If you are finding yourself having problems integrating the framework, please refer to already integrated aircraft as reference/example, or get in touch with their maintainers - ideally, via the forum, so that everybody can contribute and benefit.

== Design ==
{{FGCquote
|Originally, it was a single monolithic update() method that would basically be called at frame rate using a settimer/maketimer callback.<br/>
When things were restructured, the conditional parts of this huge method were moved into predicates that reside in a huge hash: [https://gitorious.org/fg/fgdata/source/Nasal/canvas/map/navdisplay.styles#L14 https://gitorious.org/fg/fgdata/source/ ... styles#L14]<br/>
Meanwhile, the update() method has been inflated again due to some logic that wasn't added to the hash, e.g. see: [https://gitorious.org/fg/fgdata/source/Nasal/canvas/map/navdisplay.mfd#L476 https://gitorious.org/fg/fgdata/source/ ... y.mfd#L476]<br/>
<br/>
The meat of it still is in update(), and those "layers" are fairly boring meanwhile because they're separately managed by Philosopher's MapStructure framework.<br/>
<br/>
But individual ND elements (canvas groups) are basically SVG-driven, i.e. SVG elements that are looked up and then updated/animated via timers and listeners: [https://gitorious.org/fg/fgdata/source/f3df87622ca60eb45f359c05bd913524eeb44667:Nasal/canvas/map/navdisplay.styles#L183 https://gitorious.org/fg/fgdata/source/ ... tyles#L183]<br/>
<br/>
The actual code evaluating each SVG predicate is still called via the update() method, but it's just a foreach loop with a few lines:<br/>
[https://gitorious.org/fg/fgdata/source/Nasal/canvas/map/navdisplay.mfd#L760-769 https://gitorious.org/fg/fgdata/source/ ... d#L760-769]<br/>
<br/>
None of this is set in stone, and we're actually looking forward to generalizing this some more.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=212488#p212488
|title=<nowiki>Re: Event Management module for post 3.2</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Fri Jun 13</nowiki>
}}
}}
== Custom ND Styles ==

{{Note|As of early 2015 the following section is slightly outdated: Artix has recently created an Airbus specific ND style and we're hoping to see additional ND styles/types to be supported over time, to help increasingly unify the framework accordingly.}}

Note that setup instructions above will initially just give you a Boeing-centric ND, because it is currently being developed by the 747/777 maintainers primarily - please use the issue tracker to file feature requests for missing features.

Over time, the framework will grow and become more flexible,so that also specifics of non-Boeing aircraft can be properly emulated. But obviously this will take a while. We invite aircraft developers to help extend and refine the framework accordingly.

Design-wise, the ND code still isn't quite there yet, so unless someone is already very familiar with Nasal/Canvas, I would still postpone any custom implementations - it is better to coordinate things with Gijs and Hyde to keep on improving the existing ND, rather than re-implementing an airbus-specific one at the moment. Simply because things are very much in flux still - there's quite a bit of refactoring pending, and it seems that neither of us is going to tackle this anytime soon.

We can obviously not stop anybody from working with that code, but we would very much prefer to scratch off a handful of items from our todo list first - otherwise, this is going to be a maintenance problem in the mid-term.

Working on anything listed there should help prepare the design such that the framework becomes more aircraft agnostic, i.e. to support manufacturer-specific ND types.

Currently, we are simply not there yet - and some of the recent additions aren't exactly making this much easier unfortunately.

''The thing is, even if someone were to come up with a 100% correct/working A320 implementation now, the framework itself would not yet be sufficiently generalized - some of the recent additions are making things more complicated here, such as the inflated update() method, the Boeing-specific constructor and hard-coded assumptions in the newMFD() method.''

None of this is really difficult to fix, but these things need to be tackled first - otherwise, we'll have too many "construction sites" eventually.

Also, working on different Boeing-centric implementations will help us generalize things a bit more over time, which will surely come in handy once supporting other airliners.

We appreciate any help in maintaining and updating these frameworks, but currently these are not yet as flexible (aircraft-agnostic) as they need to be.

'''Speaking in non-coding terms: When we refactored the ND code, we explicitly wanted to support different makes/models for different aircraft using a single back-end and code base. And that's something that is already prepared in the design in several places, and it may seem straightforward to people not familiar with the code.

Here, you could say that the ND itself is the 3D model, while the "style" is analogous to a "livery" (texture pack).

The way things are implemented, we prepared support for "livery packs", and for easily creating new styles without having to touch the code.

However, currently there's still some work that needs to be done, and Gijs, Hyde and Soitanen have added features that need to be integrated properly first - you could say that they're working on the "3D model" still, so it's not such a good idea to create lots of "liveries" (styles) currently. Or those would need to updated/ported later on.'''

So it would be better to wait a little here and provide plenty of feedback in the meantime - if you really want to, you can get involved in the ND/MapStructure efforts themselves, but I would not yet suggest to come up with a totally new ND implementation - unless you're also prepared/willing to do the necessary groundwork, i.e. Nasal-space refactoring - the latter will mostly affect the new/newMFD/update functions - so not too difficult to understand if you are interested.

Otherwise, I would just suggest to watch the whole effort - The Boeing-ND stuff still needs quite a bit of work, and once more things are completed, we can better finalize the underlying frameworks.

== Gallery ==
<gallery mode=packed widths=230px heights=230px>
Navigation display MAP mode.png|MAP mode
Navigation display centered MAP mode.png|Centered MAP mode
Navigation display PLAN mode.png|PLAN mode
NavDisplay-GUIFrontend.png|NavDisplay/MapStructure testbed
</gallery>

== Adding new MapStructure Layers ==
To add a new mapping layer to display custom symbols (radar, scenery objects etc), you only need to open $FG_ROOT/Nasal/canvas/map/navdisplay.styles, navigate to the vector named '''layers''' and add your new layer there, e.g. named "AA":
<syntaxhighlight lang="nasal">
{ name:'AA', isMapStructure:1, update_on:['toggle_range','toggle_display_mode'],
predicate: func(nd, layer) {
# toggle visibility here
var visible=nd.in_mode('toggle_display_mode', ['MAP']);
layer.group.setVisible( visible );
if (visible) {
#print("Updating MapStructure ND layer: AA");
layer.update();
}
}, # end of layer update predicate
'z-index': 1,
}, # end of AA layer
</syntaxhighlight>

You may want to add new switches to directly toggle the layer on/off

== Adding new features ==
{{Note|Please get in touch with [[User:Gijs]] before touching navdisplay.styles, and don't touch navdisplay.mfd without coordinating your work via the forum first.
If you are primarily interested in porting/adding new '''mapping''' layers (such as e.g. waypoints, route, weather etc), please see the [[MapStructure]] article for details.
Otherwise, this section is focused on dealing with non-mapping aspects, i.e. ND-specific SVG symbols and animating them via properties and calculations. Typically, a new symbol will require 10-20 lines of code added to navdisplay.styles - it will typically take 5-10 minutes to add a new animated symbol to the ND.}}
If you want to add new features to the navdisplay.styles code, you need to open that file and map an existing SVG element to a Nasal callback routine - that's how everything is working currently. A straightforward examples can be found in the implementation of the '''planArcs''' symbol animation:

<syntaxhighlight lang="nasal">
{
id:'planArcs',
impl: {
init: func(nd,symbol) {},
predicate: func(nd) { nd.in_mode('toggle_display_mode', ['PLAN']) },
is_true: func(nd) { nd.symbols.planArcs.show() },
is_false: func(nd) { nd.symbols.planArcs.hide() },
},
},
</syntaxhighlight>

This is hash entry, linked to the SVG element whose id is '''planArcs'''. The embedded hash named '''impl''' contains 4 fields:
* '''init()''': a Nasal function that will be invoked to initialize the symbol
* '''predicate()''': a Nasal function that will be invoked to check some condition when updating (predicate)
* '''is_true()''': the Nasal function that will be executed if the condition is true
* '''is_false()''': the Nasal function that will be executed if the condition is false

Except for the init() callback, all others get passed a single argument called '''nd''' which is the instance of the current nd, i.e. the equivalent of '''me''', Nasal's '''this''' pointer. In the future, we're hoping to generalize this a little better and also use the init signature, which should make for shorter/more readable code.

In this case, the predicate will merely determine in which mode a certain switch is and hide/show the symbol (SVG element) accordingly. Here, it's checking that the '''display-mode''' switch is set to '''PLAN''' mode, and otherwise hide the symbol.

Switches are configured at the top of the navdisplay.mfd file, but will usually be overridden by each aircraft-specific ND.nas, i.e. by the aircraft developer. For now, modes are hard-coded and people should refer to the code to see what's supported there.

{{Note|The whole layout/approach of the navdisplay.style file isn't set in stone at all - it just ended up being a simple workaround to accomplish some goals, while also allowing newcomers to easily maintain/extend the system by just having to go through a handful of lines of code. At some point this may further evolve. It would now even be straightforward to move the whole thing to XML space using a simple script that turns our hash into XML. But ultimately we hope to wait a little with that until a generic '''MFD''' framework has evolved that can also be used for other displays like a PFD, CDU or EFB.}}

There's a "configuration hash" called "NDStyles" at the top of the file. Each aircraft can have its own entry in NDStyles, such as NDStyles["Boeing"] or NavDisplay["Airbus"]. Then, all the required canvas callbacks are listed there, i.e. the font mapper etc.

There's also an entry for a custom SVG filename. However, we encourage people to get in touch with Gijs and Hyde to help coordinate all ND development a little - so that a common (and shared) SVG file can be used for most use-cases, this is already the case for the B744 and B777 - we're hoping to get other aircraft developers involved, to help generalize the SVG file, instead of having dozens of different files and symbols. Most features should be identical or at least very similar. Which is why it's a good idea to get in touch with other people working on the ND code.

Lines 52-131 set up existing layers, which are now shared with the GUI code - so that is where new layers are added.
Aircraft specific SVG elements are added at the end, after line 132

For now, we suggest to directly use the 747-400 ND - but the framework is now prepared to easily style & customize it for different aircraft, we will probably add a tutorial to the wiki to explain how things are hanging together there. The constructor and init methods may still need some work to generalize things there, because they are basically still the original code.

So to replace the 747 ND and customize it, these are the steps:

* add a new entry to the NDStyles hash, for example "777-200"
* you can simply copy the configuration stuff from the 747 to get started
* start customizing things there
* open the SVG file in inkscape and change it as required, save it
* change the SVG filename in your NDStyles["777-200"] hash entry to match your own file name
* provide animation callbacks for any 777 specific elements
* open your own copy of ND.nas
* change the constructor call .new() to specify the name of your new NDStyles entry
* by default, this is 747-400 for the time being, for example:
<syntaxhighlight lang="nasal">
var NDCpt = ND.new("instrumentation/efis", myCockpit_switches, "777-200" );
</syntaxhighlight>

the "777-200" part needs to match the identifier used in the NDStyles hash.

To get started, just copy the whole 747-400 section in NDStyles and rename it to match your needs. Once that is working (getting a 747-400 ND via the 777-200 identifier), you can simply replace the SVG file name and add your own update handlers to incrementally come up with your own ND.

== Step by Step ==

{{Note|The following section is currently work-in-progress, it is being written by 5H1N0B1 and drdavid, please get in touch to help reviewing/improving things.}}
More detailed instruction. See if it could help.

# Have an updated version of FlightGear (V. 3.0+).
# Set up the 3D model in this way:

To create a 3D MFD ->
* Select a 3D Border (border of the screen, with screws, etc.)
* Need to have a 3D Button/switch, molette, or turnable knob
* A 3D Screen object, with:
** correct dimensions
** Single texture, -> with correct dimensions
** Correct dimension of the UVmap

# Copy and paste the ND.nas file to the appropriate folder (In the Mirage 2000 this was the "Center-mfd" folder).
# Add the ND.nas pathway to your base .xml file in the Nasal block.
# Edit ND.nas :
* Rename the screen to match the object in 1)c) if needed.
* If installing a single MFD, you do not need another object, so suppress the line (when it's calling the object itself)
* Keep the property's name -> it's ok. You just need to input it with the .xml button in 1)b)

Now, let's add the xml itself.

Really simple, it's just playing with properties. For example, see this for the airport property:

<syntaxhighlight lang="xml">

<animation>
<type>pick</type>
<object-name>bt-h1</object-name>
<visible>true</visible>
<action>
<button>0</button>
<binding>
<command>property-toggle</command>
<property>/instrumentation/efis/inputs/arpt</property>
</binding>
</action>
</animation>
</syntaxhighlight>

Or here again for the range selection:
<syntaxhighlight lang="xml">
<animation>
<type>pick</type>
<object-name>trim1</object-name>
<action>
<button>4</button>

<repeatable>false</repeatable>
<binding>
<command>property-cycle</command>
<property>/instrumentation/efis/inputs/range-nm</property>
<value>10</value>
<value>20</value>
<value>40</value>
<value>80</value>
<value>160</value>
<value>320</value>
</binding>
</action>
</animation>

<animation>
<type>pick</type>
<object-name>trim1</object-name>
<action>
<button>3</button>

<repeatable>false</repeatable>

<binding>
<command>property-cycle</command>
<property>/instrumentation/efis/inputs/range-nm</property>
<value>320</value>
<value>160</value>
<value>80</value>
<value>40</value>
<value>20</value>
<value>10</value>
</binding>
</action>
</animation>
</syntaxhighlight>

Next, you can optionally add this:

<syntaxhighlight lang="xml">
<animation>
<type>pick</type>
<object-name>blackbkd</object-name>
<action>
<button>0</button>
<repeatable>false</repeatable>
<binding>
<command>nasal</command>
<script>mirage2000.showNd();</script>
</binding>
</action>
</animation>
</syntaxhighlight>

Where 'blackbkd' is the screen.

This last option allows you to open a dialog box with what the actual canvas should display in your 1)c) screen. This is very useful to check all the different steps when something isn't working well. However, you'll need to change '''mirage2000''' to match the name of your own aircraft/namespace.

Normally following these steps, you should have a working MFD.

== Development ==

== Team Boeing ==
{{Note| Please get in touch with the following contributors if you're planning on making changes related to the Boeing ND:
* Gijs
* Hyde
}}

== Team Airbus ==
{{Note| Please get in touch with the following contributors if you're planning on making changes related to the Airbus ND:
* artix
* omega95
}}

=== Backward Compatibility ===
Once we support a handful of different '''styles''', it would probably make sense to refactor the styles file so that we end up with dedicated files for each style, e.g. by having:

* $FG_ROOT/Nasal/canvas/map/ND/nd.airbus
* $FG_ROOT/Nasal/canvas/map/ND/nd.boeing

However, it makes sense to wait a little with this so that multiple styles can evolve in parallel, to ensure that overlapping functionality can be generalized and refactored/reused. Equally, that would allow us to provide versioning support, so that aircraft developers can request a certain version of the "ND API", e.g.:

* $FG_ROOT/Nasal/canvas/map/ND/nd.airbus-3_4
* $FG_ROOT/Nasal/canvas/map/ND/nd.airbus-4_0

{{FGCquote
|Overall, we may sooner or later support backward compatibility by using something like io.include() with a nested version number and/or API call, it is not exactly difficult. For now, it would require just a few lines of code. The real challenge is that the code is very much evolving still, so it would be premature to implement something like that currently, especially because there's still many features missing so that establishing feature parity would be difficult at best - once things stabilize, and once multiple styles/aircraft are supported, we could/should revisit that. But unless someone else steps up to implement a working scheme, I am not currently interested in establishing such an API, at a time when things are being constantly refactored - we are seeing a handful of related efforts currently. And even Gijs mentioned a few times that he's still hoping to add new features - so adding API-level versioning/backward compatibility would probably become pretty awkward soon, and it would also involve other parts that don't actively support backward compatibility - Tom is using a getprop("/sim/version") check in api.nas - so it is possible, but only makes sense once the dust settles.
At least for the time being, I'd estimate that it might take another 2-3 release cycles until this should be re-considered, unless we'll see more ND contributions rolling in shortly.
If you do want to work out some kind of BC scheme, you are obviously invited to post your thoughts, I won't object any suggestions and will surely help review them to get them committed - but I'd probably not target 3.0, but instead 3.2 so that you have some kind of baseline to work with.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=221158#p221158
|title=<nowiki>Re: What's going on with the Navdisplay</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sat Oct 18</nowiki>
}}
}}

=== Getting rid of Aircraft Dependencies ===
* the constructor/newMFD() methods still contain a few hard-coded assumptions due to the origins of the code, but those can be also moved into some kind of construct() field in the hash, or you can simply use the method I suggested, i.e. hiding unneeded symbols. But you're right, that the most proper solution would be identifying non-generic code that contains hard-coded assumptions and moving that into some kind of construct() field that is simply invoked by the new/newMFD() methods. Doing that would not be difficult, it would be just copy & paste - i.e. copy from the navdisplay.mfd file into the style file, by adding a corresponding hash field entry there - and calling it instead. Takes under 3 minutes[http://forum.flightgear.org/viewtopic.php?f=71&t=21509&p=214897#p214835]
=== Encapsulating Properties ===
{{FGCquote
| think this and similar problems will be coming up for more or less every aircraft as the properties differ between FDM:s and sometimes even between aircraft.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213016#p213016
|title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
|author=<nowiki>Johan G</nowiki>
|date=<nowiki>Fri Jun 20</nowiki>
}}
}}
{{FGCquote
|aircraft, which will use NavDisplay must have airspeed-indicator, created as built-in instrument, so I prefer to select airspeed indicator as source (which is close to reality).
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213018#p213018
|title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
|author=<nowiki>Soitanen</nowiki>
|date=<nowiki>Fri Jun 20</nowiki>
}}
}}

{{FGCquote
|We could implement a way for individual aircraft to feed the ND with their own properties. However, standardizing the properties would make more sense, also for other use cases (bindings for input devices, dialogs etc.). That is even more important for the PFD, since there are dozens of different autopilot properties being used in FlightGear.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213025#p213025
|title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
|author=<nowiki>Gijs</nowiki>
|date=<nowiki>Fri Jun 20</nowiki>
}}
}}

{{FGCquote
|This kind of thing is already done in both, MapStructure and the NavDisplay, it just isn't widely used yet - but we did establish the infrastructure for this. You must be aware of it, because you kept maintaining and fixing the NDSourceDriver logic that encapsulates properties for AI traffic. The same method can be found in aircraftpos.controller to hide aircraft specifics in a "delegate" hash that provides an "abstract interface" without the back-end code having to be aware of the underlying properties.<br/>
<br/>
As long as aircraft developers agree to use, and help maintain, a corresponding hash, we can help enforce this as a "best practice" - but this should obviously be part of navdisplay.mfd itself (or even a separately-included file), so that it can be easily reused by PFD code eventually, without being specific to the MapStructure/ND code.<br/>
<br/>
We reall only need to extend the ND.new() constructor to support such "overrides" and pass them on to the underlying callbacks, which is kinda touching the whole MVC approach already used by the MapStructure framework.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214377#p214377
|title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Tue Jul 08</nowiki>
}}
}}
=== Post 3.2 ===
Gijs has already begun to clean up the update() method, and navdisplay.mfd is now back down to under 800 lines of code. Hooray will need to revisit adding support for '''switches''' (i.e. a helper class) and corresponding display modes.

At that point, we can probably simplify most things easily and move them out of the mfd file. There are some opportunities to clean up navdisplay.styles by looking at identical/similar code, such as the altArc vs. altArcCtr handling, which is basically boilerplate code. We can probably reduce navdisplay.mfd down to ~500 lines, which is mainly a matter of fixing up the update() method and making the newMFD() helper more generic.

Once that is the case, navdisplay.mfd should be generic enough to be also useful to help with porting the existing PFD code, because it's ultimately no longer ND specific, but simply a framework for animation SVG elements on a Canvas. Performance-wise, we can easily optimize the existing code by getting rid of the foreach() loop in update() and using exclusively listeners to selectively invoke only required predicates.

That would even allow us to get rid of the maketimer() hack. A few computations could/should probably be shared by being moved to '''common''' entry and writing their results to a hash, so that other elements can reuse previous results, e.g. altRangePx, rotation angles etc - there's no need, to recompute those in each callback. On the ctor side, we may want to allow individual elements to be easily disabled or overridden, analogous to how MapStructure layers can be customized/styled and disabled. We could probably reuse the same code we're using for options/style handling here. Otherwise, there are still a few "hard-coded" getprop() references that should better use the NDSourceDriver logic, or its MapStructure equivalent, i.e. aircraftpos.controller.

There are also still a few properties that should become configurable, like we once said WRT to having multiple instances of an instrument/radio etc

{{FGCquote
|just so that I don't forget about it: [https://gitorious.org/fg/fgdata/commit/7da1406cfbed8af69c5cefe215b4f327d791423d https://gitorious.org/fg/fgdata/commit/ ... 27d791423d]<br/>
<br/>
<ul>
<li> append(m.listeners ........ seems a common idiom: provide either a helper method or extend the underlying base class accordingly</li>
<li> WPT/RTE options should probably be exposed via the ctor, so that the ND code can override those defaults ?</li>
<li> unify WPT/RTE handling for wpt num ?</li>
<li> maybe provide a base class for both that encapsulates identical requirements ?</li>
<li> FIX.symbol still contains hard-coded colors, should be using styling there, TFC.symbol is using hard-coded colors & font size</li>
<li> navdisplay: swithcing between CTR & PLAN mode should be better supported by encapsulating setTranslation() etc</li>
<li> get rid of _draw_rwy_nd() calls</li>
<li> port runway-nd.draw , and support styling there</li>
</ul>

|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214252#p214252
|title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Mon Jul 07</nowiki>
}}
}}

=== Misc ===
{{Todo:NavDisplay}}

== Bugs ==

== Feature Requests ==
* feature layers: also pass the symbol instance to each predicate/callback to simplify those methods
* generalize & unify with MapStructure layer handling (update, show, hide)

[[Category:Aircraft instruments]]
[[Category:Canvas]]

Changelog 3.2

2014-07-08T09:51:46Z

Tikibar:

{{draft|changelog|This changelog is currently being written for the FlightGear 3.2 release. To see what is being worked on, check out [[Changelog 3.2]].
Feel free to help! If you are aware of any FlightGear related changes, please add them to the changelog.<br/>It's a good idea to check [[:Category:Changes_after_3.00|the newsletters since the last release]], and the git commit history.
To view the changelog for the most recent release, please see [[Changelog 3.0]].
We also encourage people to help by translating the changelog and appreciate all contributions, however please keep in mind that this changelog is not yet final!

}}

==Upcoming FlightGear Changelog==



=== Breaking Changes ===

=== Major enhancements in this release ===

'''Surface Light Effects & OpenSceneGraph 3.2'''

Stuart committed a change that brings surface lights, including VASI/PAPI/taxi/runway etc. into the xml-defined Effects framework. Kudos to Tim Moore for his original Effects work - it made it very straightforward to enhance with support for point sprites and a custom texture generator required.

The relevant effect is data/Effects/surface-lights.eff. It should allow development of ALS and Rembrandt variants.

Stuart also replaced some OSG color/normal binding calls that were removed in OSG3.2.0, apparently because they were slow. So, if your
build fails, please check you've got a recent OSG build installed.

'''Core'''
* [[Reset & re-init]] is merged and now enabled
* A segfault related to scripted Nasal fgcommands (like used in joystick and other bindings) has been fixed {{Issue|1397}}
* yasim versioning support for maintenance fixes (TorstenD)
* FLITE TTS support
* Windows dependencies have been updated
* improved projection handling for the integrated [[Map]] dialog, implemented by Gijs[https://gitorious.org/fg/flightgear/commit/3f433e2c35ef533a847138e6ae10a5cb398323d7#comment_107170]

'''Aircraft Modeling'''
* galvedro's work: [[A Failure Management Framework for FlightGear]]
* extra 500
* Tu-154B2 version 3.1
* additional aircraft have started adopting Gijs' [[NavDisplay]]

'''JSBSim'''
* ground effects (see newsletter 02/2014)

'''Atmospheric Light Scattering'''

Atmospheric Light Scattering (ALS) is one of FGs three rendering frameworks, with the aim of providing an integrated simulation of the interaction between weather, light and the environment.

Additions to ALS in version 3.2 include:

* an experimental framework to render cloud shadows on the ground (requires Advanced Weather)
* a substantial extension of cloud layer visibility using impostor techniques to 150 km
* a new agriculture effect allowing to render fields without tiling artifacts
* a new forest effect to simulate managed forest, varying tree size by patch
* sparkle and fog effect on runway lights
* much improved visual appearance of rock faces

'''Environment Rendering'''

* EarthView, a simple orbital rendering engine based on projecting a textured sphere into the scene. By default, EarthView uses low resolution textures, however using hires textures e.g. from the NASA [http://visibleearth.nasa.gov/ Visible Earth] project very realistic results from altitudes above 100 km can be achieved.

* new deciduous and needle tree textures with much improved visuals

* new regional texture definitions for Ireland, Alaska/Northwest territories and US Southwest

'''Performance'''
* F-JJTH and Stuart have started working on using osg::Simplifier [https://gitorious.org/fg/simgear/commit/3429e0072103a8c90d8e456f1f6b711099851225]: http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/CAP3ntysifK34TxANKUj1s4Of_dJRg7dvJ74Gbko4zXVFHdV-YQ%40mail.gmail.com/#msg32016452

'''Misc/Uncategorized'''
* AIModels use PagedLOD
* Optimise NavCache airport query
* osg::Switch for masking scenery rendering
* Torsten's metar work, newradio, mongoose httpd
* HTTP: improve handling of connection errors
* [[FGCamera]] (external addon, not yet reviewed/committed as of 03/2014)
* Windows installer has been reworked
* Windows installer creates 3 news directories pre-configured in FGRun:
** {user}\Documents\FlightGear\Aircraft
** {user}\Documents\FlightGear\TerraSync
** {user}\Documents\FlightGear\Custom Scenery

''' Usability '''
* Windows users are now able to use scrollwheel in dialog

''' Internationalization '''

''' Scenery '''

'''Canvas System'''

FlightGear's fully scriptable 2D rendering system now includes improved APIs for creating maps and navigation displays amongst many other improvements. People no longer need to have programming experience to add a working ND to their aircraft, it can now be all done by copying and pasting 30 lines of text and customizing a few properties. The so called MapStructure back-end handles efficient updating of all ND layers transparently. Also, maps can now be mostly customized, including custom styling (colors, fonts, symbols etc).

* Tom has pushed an update to git (simgear) which removes a lot of unneeded OpenGL state changes for Canvas paths. Depending on the GPU/driver this can lead to quite a noticeable performance improvement. For example, he was able to get from ~120ms down to ~45ms [http://forum.flightgear.org/viewtopic.php?f=71&t=16984&p=204730#p204730].

* Gijs is currently working on additional projections as part of {{Issue|550}}
* The [[MapStructure]] back-end used by the [[NavDisplay]] now supports symbol instancing, so that performance is improved
* MapStructure-based layers can now be customized and styled
* Tom added support for button/modifiers (mouse handling) [http://wiki.flightgear.org/index.php?title=Canvas_Event_Handling&curid=10777&diff=68569&oldid=68422]
* CanvasImage now supports the ''http://'' protocol for dynamically retrieving raster images. See the renamed [[Canvas_Image#src|src attribute]] (''file'' is now deprecated).
* As part of the ongoing effort on [[Unifying the 2D rendering backend via canvas]], we have started re-implementing the integrated [[Map]] dialog using Nasal & Canvas instead of C++ {{Progressbar|80}}
* Custom event handlers can now be registered.
* Canvas Layout Engine
* Canvas-based dialog for downloading aircraft [[Aircraft Center]]
[[File:Aircraft-center-prototype.png|400px|thumb|Canvas dialog showing the prototype for an [[Aircraft Center]] for directly installing/managing aircraft from within FlightGear, an upcoming feature scheduled for FlightGear 3.2, currently being developed by TheTom and Zakalawe]]

'''Nasal Scripting'''

* getprop()/setprop() arguments (those that form a path) can now be numeric to specify a index, so:
<syntaxhighlight lang="nasal">
getprop("canvas/by-index", "texture", 1, "name");
</syntaxhighlight>
: is now the same as:
<syntaxhighlight lang="nasal">
getprop("canvas/by-index/texture[1]/name");
</syntaxhighlight>
: (see [https://gitorious.org/fg/flightgear/commit/5eee5e42ae4f5cf56283b3bf5a3be46efc2b51c4 merge request 54] and [https://gitorious.org/fg/flightgear/commit/34ed79e5f88ffdfc5e651a1fe3e639cb8f4d3353 actual commit])
* A new fully-interactive Nasal GUI console based on [[Canvas]] has been added: [[Interactive Nasal Console]]
* the hard-coded '''flight path history''' subsystem which samples aircraft position, which was previously only accessible to C++ code, has now been exposed to scripting space by Tom so that people can easily access the system and reuse the data for their own purpoes (e.g. for creating an instructor console). The first use-case will involve the new [[Canvas]] based [[Map]] dialog which will be 100% scripted by then.
: Usage:
<syntaxhighlight lang="nasal">
var hist = aircraft.history(); debug.dump(hist.pathForHistory(50));
</syntaxhighlight>
* cppbind: Nasal ghosts can now support arbitrary setters/getters for when members are not mapped to a C++ member/method.
* Language enhancements
** Bitwise operators (|, &, ^, ~, |=, &=, ^=)
** Support for octal, decimal and hexadecimal numbers in literals as well as in strings

'''Documentation'''

'''Highlighted new and improved aircraft'''

* Tuned autopilot and improved instrument stack for the Cessna337G Skymaster.
* All new systems and two engine options for the Boeing 757-200.

'''Other'''

'''Bug fixes'''

* See [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D3.2 our bugtracker] for an extensive, yet incomplete, list of the bugs fixed in this release.

[[Category:FlightGear changelogs]]

Virtual airlines

2013-05-13T22:12:06Z

Tikibar:

A '''virtual airline''' (VA) is a dedicated hobby organization that uses flight simulation to model the operations of an airline. Virtual airlines generally have a presence on the internet, similar to a real airline. There are over 100 virtual airlines of significance currently active in the internet (supporting a number of flightsims), with thousands of participants involved at any one time each using different simulator platforms.

== Purpose ==
Virtual airlines were started to give a sense of purpose to activities conducted within a flight simulator. This basic premise has evolved over time, along with available technology, to provide increasing levels of immersion but always with the same core purpose. When combined with increasingly powerful personal computers, advancing flight simulation software, and communications networks, virtual airlines are often able to provide compelling, realistic, experiences similar to operations inside a real airline. Virtual airlines also provide an avenue for members to gain access to additional content, such as aircraft and scenery, for use with their simulator. The appeal varies; for younger members, virtual airlines provide a sandbox environment where they can experience the corporate environment of commercial business in the airline industry, without the risk of financial loss. These organizations also provide an outlet for those who are interested in aviation but unable to fly themselves in real life due to financial, health, or other reasons.
Most of all, its one step closer to enthusiasts feeling more involved in an airline environment and share their interests with others.
Virtual Airlines also benefit the flight simulator community by providing valuable services such as ATC, events, and general help and knowledge.

== Common elements ==
There are several elements that are common across many virtual airlines:
* A website as the focal point of the community
* Internet forum where discussion and social interaction can occur
* Customized livery that users can download together with aircraft and install in their flight simulator
* Route schedules for members to fly in their simulators
* Multiplayer events, often on a game network such as VATSIM or IVAO
* Less common elements include:
** An Online database for recording and reporting flights and membership statistics
** Dedicated game server hosting to provide private areas for members to complete flights
** Award, rank and recognition systems
** Voice over Internet Protocol servers for members to communicate freely by voice

== Current FlightGear Virtual Airlines ==

{{Virtual airline summary
|name = Air Lanaudière - NorskAir
|established =
|logo = Alqlogo.png
|status = Active
|niche =
|has-atc =
|callsign =
* ALQxxxx
* ALExxxx
* ALXxxxx
* NKAxxxx
* NKHxxxx
|history =
|fleet =
* Cessna Caravan
* ATR72-500
* Embraer E-170LR
* Embraer E-190LR
* Airbus A318
* Airbus A319
* Boeing 777-200LR
* Boeing 787-8
|main-hub = CYUL
|hubs =
* CYUL (ALQ, ALE)
* CSK3 (ALE)
* CSM5 (ALE)
* CYMX (ALX)
* ENGM (ALX, NKA)
* ENBR (NKH)
|map =
|website = http://www.airlanaudiere.com
|forum =
}}

{{Virtual airline summary
|name = BRT Virtual Airlines
|established = Nov 2010
|logo = LOGO_BRT_VIRTUAL_AIRLINE_big.png
|status = Active
|has-atc = Yes, FGCom / FlightGear
|callsign = BRT<pilot>
|history = Founded in Nov 2010, BRT has strived to achieve excellence in flying in FlightGear, and to create a quality community in flightsims.
|fleet =
* 737-300 (8)
* 747-800i (4)
* 777-200ER (17)
* 787-800 (8; all grounded)
* E190-200 (22)
* DHC6-300 (5)
|main-hub = UKBB
|hubs =
* VHHH
* KSFO
* NZAA
|map =
|website = http://brtvirtualairlines.com
|forum =
}}

{{Virtual airline summary
|name = Century Airlines
|established = March 2012
|logo = Calogo.png
|status = Active
|has-atc = FGCom, RaidCall, Mumble
|callsign = CAxxxxx
|history = Century Airlines was born on March 25, 2012 from an idea to change the system used by the virtual airlines in FlightGear and allow virtual pilots to have more freedom when flying. The airline began with a diffusion through FG community forums (not official), then it began a gradual expansion of a new system for pilots and their way of flying in a virtual airline. On January 25, 2013 Century Airlines got more than 500 reported flights from its virtual pilots.
|fleet =
* Airbus A330-243 (2)
* Airbus A340-600 (2)
* Airbus A321-231 (2)
* Airbus A320-214 (5)
* Airbus A319-111 (4)
* Airbus A318-111 (4)
* CRJ-700 (9)
* 787-8 (3)
* 747-8i (3)
* 777F (5)
* 777-200ER (5)
* 777-200LR (4)
* CRJ-200 (1)
* Citation X (1)
* DHC8-Q300 (3)
|main-hub = SKBO
|hubs =
* LEMD
* SAEZ
* SBGL
|map =
|website = http://centuryairlines.jimdo.com/
|forum = http://centuryairlines.forumbuild.com/
|registration = http://centuryairlines.jimdo.com/become-century-pilot/
}}

{{Virtual airline summary
|name = Global Virtual Airlines
|established = April 2010 (as Atlas Virtual Airlines)
|logo = Globalair 20.jpg
|status = Active
|niche =
|has-atc = YES, FGCom
|callsign = GVAxxxx
|history =
|fleet =
* 737-300
* 737-900
* 747-8i
* 777-200ER
* 787-8
* B1900D
* CRJ700LR
* DHC6-300
* DHC8-400Q
* Il-96-400
* MD-81
|main-hub = EDDF
|hubs =
* KDEN
* KJFK
* TNCM
|map =
|website = http://globalvirtualair.com/
|forum = http://www.globalvirtualair.com/forum/
}}

{{Virtual airline summary
|name = Merlion Virtual Airlines
|established = November 2010
|logo = Merlionvalogo.png
|status = Active
|has-atc =
|callsign = MIAxxxx
|history = Will soon be added to the Information area of the website.
|fleet =
* Airbus A320NEO (CFM LeapX) (69)
* Airbus A330-243 (16)
* Airbus A330-343 (10)
* Airbus A380-842 (4)
* ATR72-500C (17)
* Boeing 757-200PF (17)
* Boeing 777-200ER (19)
* Boeing 777F (5)
* Boeing 787-8 (6)
* Bombardier CRJ200LR (18)
* Bombardier CRJ700LR (28)
* Cessna C172P Skyhawk
* de Havilland Canada DHC6-300
* Embraer ERJ170-100LR (47)
* Embraer ERJ190-100LR (11)
|main-hub = WSSS
|hubs =
* KLAX
* EGKK
* ELLX
* KMEM
|map =
|website = http://www.flymerlion.org/
|forum = Soon to be included in the website.
}}

{{Virtual airline summary
|name = Virtual Air Canada
|established = May 2013
|logo = ACA Logo.png
|status = Just Opened, looking for pilots
|callsign =
* ACAxxx
* ACTxxx
|history = Founded in May 2013 on the 11th. We hope to bring realism to the airline and community. We hope that this'll turn into a good airline in the future.
|fleet =
* B1900D
* Embraer E175
* A320NEO (Will be leased out soon for 737NG)
* ATR72-500
* 777-200LR
* A330-300
|main-hub = CYYZ
|hubs =
* CYVR
|website = http://virtualaircanada.x10.mx/
|forum = Soon be added onto the website
}}

[[Category:Virtual airlines| ]]

== Defunct Flightgear Virtual Airlines ==

{{Virtual airline summary
|name = Cresder Nixrof
|established = November 2010
|logo = CNA_logo_with_hawk.png
|status = Defunct
|niche =
|has-atc = No
|callsign = CNAxxxx
|history = Dissolved January 2012
|fleet =
|main-hub =
|hubs =
* OLBA
* WMKK
* EGKK
* YSSY
* KSTL
* SBGR
|map =
|website =
|forum =
}}