FlightGear wiki - User contributions [en]

Leipzig/Halle Airport

2015-01-13T17:09:19Z

August: /* Download via GIT */ new download link

{{infobox Airport
|name = Leipzig/Halle Airport
|image =2014_new-layout-EDDP_07.jpg
|image2 =2014_new-layout-EDDP_02.jpg
|alt =New layout (development 2014)
|alt2 =DHL area (development 2014)
|iata =LEJ
|icao =EDDP
|type =Public
|city =Between Leipzig and Halle
|owner =Mitteldeutsche Airport Holding
|website =http://www.leipzig-halle-airport.de/
|scenerytile =e012n51
|download = http://wiki.flightgear.org/Leipzig/Halle_Airport#Download_via_GIT
|terrasync = published
|runway= 08L/26R
|length= 11,811 ft
|material= Concrete
|runway2= 08R/26L
|length2= 11,811 ft
|material2= Concrete
}}

'''Leipzig/Halle Airport''' is located in Schkeuditz, Saxony and serves both Leipzig, Saxony and Halle, Saxony-Anhalt, [[Germany]]. In Flightgear this airport was published on [[TerraSync|TerraSync]] in 2010 und updated due to new developments 2012. In 2014 according to the new world scenery a complete overhaul started.
EDDP is also the centre of Leipzig/Halle airspace, which provides air traffic control also for the regional airfield [[Leipzig-Altenburg Airport]].

{{Note|Users are asked to test the '''beta Version of the new 850-Layout''' (see [[#Download_via_GIT]])}}

== Flying at Leipzig/Halle airspace ==

=== Charts ===
All [http://www.vacc-sag.org/airport/EDDP diagrams and charts] are available for download.

=== Runways and ILS ===

==== Runway 08L/26R ====
[[File:2014 new-layout-EDDP 06.jpg|thumb|620px|Overview 2014 (reshaped layout under development)]]The northern [[runway]] is 3600m long with a width of 45m. In real life its usually used by passenger airliners. In Flightgear this runway is equipped with Outer Marker and Middle Marker and offers best conditions for '''low visibility operations'''.
* ILS-CAT-III '''08L''' (083°): 108.55
* ILS-CAT-III '''26R''' (263°): 108.35
==== Runway 08R/26L ====
The southern [[runway]] is 3600m long with a width of 60m. In real life its mostly used by freighters due to its proximity to freight areas (Apron 2 and 4). It has no Outer Marker an no Middle Marker.
* ILS-CAT-III '''08R''' (083°): 111.90 (111.75 in FG older than Version 2.0.0)
* ILS-CAT-III '''26L''' (263°): 110.30

=== ATC ===
* Leipzig Ground - frequency 121.800
* Leipzig Tower - frequency 121.100

Leipzig/Halle Airport is regularly served by Air Traffic Control ([[ATC]]).

== Infrastructure ==
Connected by terminal C and three taxiway bridges (W1, E7, E8) the airport layout combines the northern part with runway 08L/26L and Apron 3 (new cargo area since 2012) and the southern part with Apron 1 (terminal B), runway 08R/26L, Apron 2, Apron 4 (DHL), Apron 5. Between both parts an airport railway station and the autobahn A14 is connecting to the check-in area of terminal C. Railway and motorway are not modelled in Flightgear.

=== Access and connection ===
[[File:TerminalC-morning.jpg|thumb|270px|Terminal C at dawn (2012)]]
==== Terminal C ====
In August 2012 the completely new modelled terminal C was published on TerraSync. It is built as a connection between the check-in building with car-park and train station in the north and the departure area at terminal B in the south. Due to this efforts it stands on piers like a long bridge from apron 1 to apron 3, crossing different car-parks, a rail-track and the autobahn.
On the one hand the FlighGear model tries to give the airport a well designed model with highly detailed structures, but on the other hand it was programmed as simple as possible to save visitors simulation performance.

==== Taxiway bridges ====
[[File:EDDP-Taxibridges-e7e8-night.jpg|thumb|270px|Rampbridges E7, E8 with new lightning (2012)]]A highway and railway lines go straight between the two runways. Three bridges connect the terminal with the northern runway. The western bridge (taxiway W1) is used in both directions. The eastern bridges (taxiways E7 and E8) are used as one way taxiways. Due to safety improvements all bridges are equipped with special taxi lights.
Due to changes in the TerraData the bridges had to be repositioned in 2012.

=== Apron 1 ===

The main apron at Leipzig/Halle Airport is located in the middle of the airport. It houses the commercial aviation area at terminal B in the west and the general aviation area in the eastern part. It is connected by taxiways L, N and W1.

==== Terminal B ====
[[File:EDDP VDGS-134 thumbnail.jpg|thumb|270px|VDGS on each gateway at terminal B]]'''Real world''':
This building is the main terminal for most commercial flights at EDDP. It is connected to terminal C in the north and provides the passenger transfer to Apron 1 via 6 gateways. It also has a connection to the luggage terminal.

'''Scenery in TerraSync''':
In Flightgear the main terminal is modelled very slim and efficiently. 6 unmovable gateways link to park positions 126, 128, 130, 132, 134 and 136. In 2012 it will be improved. Since September 2012 it has been equipped with a non-animated [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System VDGS].

==== Luggage terminal ====
This building was first published in 2004 and remodelled by Thomas Großberger in 2012. The terminal is connected via the old tower next to it to terminal A by a tube, which is used to transport luggage between the checkin- and arrival-area and Apron 1. Both. the connection and the old tower building will be modelled in 2013. The new luggage terminal in FlightGear is offering:
* realistic roof design
* simplified but detailed interior
* 6 clock controlled automatic gates
* complex light design (Rembrandt-Design outstanding)

==== GAT ====

=== Apron 2 ===

=== Apron 3 ===
This Apron in real life went into service with a new cargo hangar in 2012. In Flightgear it is still closed. The corresponding facilities are still under development.

=== Apron 4/5 (DHL-area) ===
[[File:2014 new-layout-EDDP 01.jpg|thumb|620px|Apron 4 and runway 26L at night (2014)]]'''Real world:''' Leipzig/Halle is just a small international airport. But in 2008 it became the [http://www.dp-dhl.com/en/logistics_around_us/from_our_divisions/leipzig_hub.html European DHL hub] with up to 60 planes per night. The DHL Hub Leipzig GmbH, place of business in Schkeuditz, is running under contract to the logistic group DHL at Leipzig/Halle Airport one of six international aviation hubs. In order to provide maintenance to the new fleet the [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig GmbH] was founded. European Air Transport operates services to Europe, Middle East and Africa. 56 countries are covered in total. A second aviation company, called [http://en.wikipedia.org/wiki/Aerologic AeroLogic], was founded in EDDP. AeroLogic GmbH, a joint-venture between DHL Express and Lufthansa Cargo, is a German cargo airline headquartered in Schkeuditz, Saxony. It operates cargo flights out of Leipzig/Halle Airport and Frankfurt, most of which are on behalf of its parent companies.

{| class="wikitable" cellpadding="3" style="margin-left:auto; margin-right:auto"
|+ '''Fleet of [http://en.wikipedia.org/wiki/Aerologic AeroLogic] and [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig] and others''' (2012)
|-
!Aircraft
!Total
!Orders
!Oparator
|-
|[[Airbus A300|Airbus A300B4-203F]]
|<center>10</center>
|
|Air Contractors
|-
|[[Airbus A300|Airbus A300-600RF]]
|<center>8</center>
|<center>10</center>
|European Air Transport Leipzig
|-
|Boeing 737-300F
|<center>9</center>
|
|European Air Transport Leipzig
|-
|Boeing 737-400F
|<center>1</center>
|
|Europe Airpost
|-
|[[Boeing 757|Boeing 757-236SF]]
|<center>10</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 757|Boeing 757-23APF]]
|<center>1</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 777F]]
|<center>8</center>
|
|AeroLogic
|-
!Total
!47
!10
!colspan=2|
|}

[[File:EDDP-DHL-tank.jpeg|thumb|270px|DHL-Tank at fuel storage area on apron 4]]'''Scenery in TerraSync:''' The hub (warehouse, hangar and aprons) is modelled in the scenery. In 2012 its redesign for TerraSync started. First all lampposts at apron 4 had been replaced with those which fit into the correct layout of every single parking position. Afterwards lots of goods and ground vehicles where placed. As soon as some missing storage buildings are modelled, the new content of apron 4 will be published on TerraSync. Last modifications will take place when the new [[Airport data (apt.dat) update|850-standard layout]] of EDDP will be created in the future.

'''DHL-hub at EDDP in Flightgear:''' Leipzig/Halle Airport offers ground space for more than 70 Boeing [[757-200|757-PF]] or up to 50 [[777F]] as well as space for 10 [[Antonov An-124|An-124]] at Apron 2, 4 and 5. Airmail flights can be flown from and to EDDP. One of the middle sized and highly connected hubs of DHL, the [[Orio al Serio Airport]] (Italy) is also modelled in FlightGear and can be used for realistic flights out of Leipzig/Halle Airport.
In FlighGear apron 4 is equipped with all stands. Additionally to the main apron lightning each stand has one centred lamppost, which will be replaced by a VDGS-signs in the future. Ground markings will come with the new 850-layout. The major storage buildings from DHL are modelled as well as three DHL-tanks south from apron 4.

=== De-icing areas ===
Leipzig/Halle Airport has four special areas, two in the north at taxiway C and two in the south at taxiway N. In FlightGear only the two areas at taxiway C are build into the layout. In 2012 both areas had been equipped with shared models like lampposts, buildings and ground lights.

==== De-icing area 2 - multiplayer ready ====

Based on the Zurich type model "Elephant" - originally modelled by Oliver Thurau - an improved version with full multiplayer support is under development. This version isn't only adapted to the special efforts at EDDP, but its also designed to be controlled by ATC. It will be published via TerraSync in November 2014.

== Surroundings and "Other" ==

=== Kursdorf - the village within the airport ===
There is a village right in middle of the airport. So it's no surprise the number of inhabitants is shrinking each year. Once a thriving village with 537 inhabitants in 1950, they were down to 119 in 2006 [http://de.wikipedia.org/wiki/Kursdorf_%28Schkeuditz%29 (Wikipedia)]. It might be a little loud with the two runways, highway and express railways, but the transport links, hey ... The village is modelled in the scenery.

== Scenery ==
{|
| Authors: ||
* Models: David G., D-STHO
* Airport layout: Christian Schmitt
* Additional models: Don Lavelle, Alex Park, Robert Shearman
* Redesigning & Development 2012: [[User:August|August]], D-STHO
|-
|}

=== Download via GIT ===
With FlightGear 3.0 a new world scenery was published, including a new but incorrect 850-layout for EDDP. Developers started a huge overhaul of the EDDP scenery in April 2014. First a new taxiway layout was programmed. Additionally all buildings and objects are replaced. Some models will be remodelled, others will be added. Due to the fact that airport layouts can't be simply updated via TerraSync in a short way, pilots are asked to use the new EDDP CUSTOM SCENERY as long as things aren't updated at TerraSync.

* always get the newest development version automatically:
<code>
git clone git@gitorious.org:eddp-custom-scenery/eddp-custom-scenery.git
</code>
** or [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/archive/e937c6bfee58314c397bd5d93045c8de7013147b.tar.gz download a ZIP] (102 MB)

=== Download via TerraSync ===
[[TerraSync]] has it all! There is no custom scenery existing (only the GIT-repository for testing the new 850-layout before publishing it). The authors believe on the advantages of TerraSync which makes it easy for every user to have the latest scenery installed automatically. Updates are published regularly via TerraSync.
* Next update in '''<daysuntil in="days">12-August-2014</daysuntil>''' {{Progressbar|height=45|percentage={{#expr: trunc ({{#time: z}} - {{#time: z | May 19 2014 }}) round -1 }}}}

* '''Latest update on TerraSync:'''
** '''2014-04-29''' ''Objects adapted to new (but incorrect) 850-layout''

* Last five updates:
** '''2013-04-21''' ''Rembrandt lights at apron 1''
** 2013-02-13 ''new Messeturm at final approach area of runway 26R''
** 2012-12-21 ''new luggage terminal at apron 1''
** 2012-10-22 ''three new DHL-tanks placed at DHL-area''
** 2012-09-20 ''new VisualGuidingDockingSystem at terminal B''

=== Development ===
Since the Scenery had been modelled by [[User:D-79|D-79]] in 2010, D-STHO and [[User:August|August]] started enhancements and redesigning in 2012. In 2014 development of a new 850-layout started. Improvements are made on the following objects:

'''Layout''' 
* Taxiway bridges: new Position, improved lightning ''(published 07/2012)'' {{tick}}
* New 850-standard: new Layout with all parking positions and improved taxiways {{progressbar|90}} (see [[#Download_via_GIT]])

'''Scenery (Shared Models)''' 
* Airport lightning: more than 80 lampposts ([[EDDM]]-model) on Apron 1 and 4 and both northern de-icing areas ''(published 07/2012)'' {{tick}}
* DHL-tanks at apron 4 ''(published 10/2012)'' {{tick}}
* Ground traffic: lots of goods and vehicles (shared) make apron 1 and 4 much more realistic ''(published 08/2012)'' {{tick}}
* Flora and boundaries: Trees and fences on Apron 1, 2 and 4 are added ''(published 08/2012)'' {{tick}}
* New shared ground vehicles
** Container dolly ''(under development)'' {{hourglass}}
** Luggage dolly ''(under development)'' {{hourglass}}
** Pallet dolly ''(planned)''
* New shared Unit Load Devices (ULD)
** Airfreight container - Type AKH ''(pre-development)'' {{hourglass}}
** Airfreight pallet ''(planed)''
* Village and industrial surroundings: Kursdorf within the airport and industrial areas around are created with shared models ''(published 04/2010)'' {{tick}}

'''Buildings and infrastructure (Static models)''' 
* Cargo-hangar apron 3 ''(planned)''
* Cargo-center apron 2 ''(published 2010)'' {{tick}}
* DHL-hangar ''(published 2010)'' {{tick}}
* DHL-terminal ''(published 2010)'' {{tick}}
* Interactive DE-ICING areas (Multiplayer supported) {{hourglass}}
* Interactive luggage dolly traffic between terminal B and lugage terminal ''(planned)''
* Luggage terminal ''(published 12/2012)'' {{tick}}
* Storage buildings at DHL-area ''(pre-development)'' {{hourglass}}
* Terminal B ''(published 04/2010)'' {{tick}}
* Terminal C ''(published 08/2012)'' {{tick}}
* Tower ''(published 2010)'' {{tick}}
* Turbo engine hall ''(pre-development)'' {{hourglass}}
* Old Tower next to terminal B ''(pre-development)'' {{hourglass}}
* Visual Docking Guiding System at Apron 4 ''(planned)''
* Visual Docking Guiding System at Terminal B ''(published 09/2012)'' {{tick}}
* Visual Docking Guiding System: replacement with animated interactive version ''(planned)''
'''Rembrandt lightning improvements'''
* Converting Lightning to [[Project Rembrandt|Rembrandt]]
** Rembrandt lights at apron 1 ''(published 04/2013)'' {{tick}}
** Rembrandt lights at apron 2 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 3 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 4 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 5 {{progressbar|90}} (see [[#Download_via_GIT]])
* Converting Buildings to [[Project Rembrandt|Rembrandt]] Lightning
** Luggage terminal ''(pre-development)'' {{hourglass}}
** Terminal B ''(planned)''
** Terminal C ''(planned)''
** Tower ''(planned)''
** DHL-hangar ''(planned)''
* Lampposts in EDDP-style ''(planned)''

'''Buildings at the city of Leipzig (Static models)''' 
* City-Hochhaus {{progressbar|90}}
* Wintergartenhochhaus ''(published 02/2013)'' {{tick}}
* Völkerschlachtdenkmal (Battle of Nations Monument) {{hourglass}}
* Red-Bull Arena {{hourglass}}
* Gondwanaland (tropical zoo) ''(published 02/2013)'' {{tick}}
* DVB-T-Tower ''(published 02/2013)'' {{tick}}
* Messeturm Leipzig ''(published 02/2013)'' {{tick}}
* Hauptbahnhof (Central Station) ''(planned)''

=== Scenery since 2014 ===
<gallery mode=packed widths=180px heights=180px>
2014 new-layout-EDDP 04.jpg|Redesigned Layout: Taxiway T - new ground textures
2014 new-layout-EDDP 01.jpg|Redesigned Layout: Runway 26L with DHL-area
2014 new-layout-EDDP 02.jpg|Redesigned Layout: Apron 4
</gallery>

=== Scenery since 2012 ===
[[File:EDDP TerminalC.jpeg|Terminal C]] [[File:EDDP VDGS-136 thumbnail.jpg|VDGS at position 136]] [[File:EDDP-DHL-tank.jpeg|DHL-Tank at fuel storage area on apron 4]] [[File:EDDP_luggageterminal_thumb.jpg|Luggage Terminal at Apron 1]]

=== Scenery since 2010 ===
Here is a selection of the models. [http://www.youtube.com/watch?v=3kNDGiSNUdE YouTube video 2010].

[[File:EDDP10.jpg]] [[File:EDDP11.jpg]] [[File:EDDP12.jpg]] [[File:EDDP13.jpg]] [[File:EDDPbridge1.png]]

== Related content ==
* [[Germany]]
* [[Leipzig/Halle Airspace]]

== External links ==
* [http://www.vacc-sag.org/airport/EDDP Airport Diagrams]
* [http://de.wikipedia.org/wiki/EDDP Leipzig/Halle Airport at Wikipedia] (German)

[[Category:Airports in Germany]]

FlightGear Newsletter July 2014

2014-07-11T15:21:26Z

August: /* Paro Int. Airport - VQPR */ point of view

{{Newsletter being written}}

== 5 years of newsletters ==
[[File:Fgmagfiveyears.png]]

The newsletter started in July 2009. (more to write here, just so we don't forget about it)

{{FGCquote
|Would it be an idea to provide some sort of weekly or monthly newsletter? I often find out that there are new things I didn't new about or other users that don't follow all topics won't know if there's an awsome plane released. That's why I think we need a newsletter. 
 
'''Possible things to write about could be:''' 
- New planes that are released. 
- New scenery projects (like a new/redrawed airport, things like the corse scenery etc.). 
- New FG releases (this is not very often, but it should be in the letter if so). 
- New forum features/subforums and other news from the forum. 
- News from the wiki (only detailed and large tutorials, or new portals etc. so not every new article ofcourse) 
- Events that will be held within a short periode or (links to) screenshots of the latest event(s). 
- The first 3 or 5 pictures of a screenshot contest. 
 
If you got other idea's, post in this topic so we could extend the list. 
I don't really know what's best way to provide the letter. But we have some options: 
- a topic that's closed, only open for people that are making the letter (at the moment this sounds best to me). 
- emails send to all forum-users (I don't really like this myself). 
- a .pdf file with a link on the main page of [http://www.flightgear.org http://www.flightgear.org] 
- or even something else 
 
I would like to write the letter, but if there are other people to we might split stuff (someone for scenery news, someone else for aircrafts etc.). Please respond and vote in the poll. Tips/ideas are very much appreciated.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=11211#p11211
|title=<nowiki>Newsletter</nowiki>
|author=<nowiki>Gijs</nowiki>
|date=<nowiki>Mon May 26</nowiki>
}}
}}

{{FGCquote
|The devel-list is great, I'm subscribed to, but not simple to read. It's more like the forum. Usually I don't want to or have time to read through all emails. So I delete most of it without reading anything more than the subject. We don't want to read a lot of topics if we only want to know what function is new and what it does. The the users (so not the developers) want something more ease to read/check. With some screenies of what they will get with a new function etc. So my idea was to make it especially for users. 
 
Events aren't listed on the pages you gave nor some other stuff we could place in the newsletter. In the letter all important news to know will be listed together. If we get this of the ground it could be a great way to reach users to (for events etc.). So I think the newsletter still will be a addition to the lists.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=11216#p11216
|title=<nowiki>Re: Newsletter</nowiki>
|author=<nowiki>Gijs</nowiki>
|date=<nowiki>Mon May 26</nowiki>
}}
}}

{{FGCquote
|At one time a few years ago we attempted to launch a newsletter. We had two volunteers, but we never got even the first issue out. It's a lot of work so we need a pretty dedicated volunteer. I've heard of other folks using scribus, but even open-office writer would probably be just fine. Let's not get too caught up in the details of a print/publishing quality layout if we have to sacrifice time for content and just getting the newsletter out on a regular time frame. There are a bazillion ideas for articles. I could dust off my unpublished "yasim howto" for instance. That ended up being about 10 pages (so not newsletter material really) but I could trim it down to a teaser article and we could post the full version on the wiki or something? 
 
But if you are willing to get a newsletter rolling, that would be awsome.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=11277#p11277
|title=<nowiki>Re: Newsletter</nowiki>
|author=<nowiki>curt</nowiki>
|date=<nowiki>Tue May 27</nowiki>
}}
}}

{{FGCquote
|Gijs is right when it comes to being a Developer or a User of FG is Vastly different. I know when i first started here i had no clue about lots of developmental things, now i talk of writing .xml files, modelling nasal scripting. That is due to people describing things is basic easy to understand" Laymans" terms and not the kind of language that the DEvs use (understandably of course) 

|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=11368#p11368
|title=<nowiki>Re: Newsletter</nowiki>
|author=<nowiki>MaverickAlex</nowiki>
|date=<nowiki>Thu May 29</nowiki>
}}
}}

{{FGCquote
|Since 16 to 3 voted for Yes I will release the first Newsletter as soon as possible.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=15619#p15619
|title=<nowiki>Re: Newsletter</nowiki>
|author=<nowiki>Gijs</nowiki>
|date=<nowiki>Thu Aug 21</nowiki>
}}
}}

{{FGCquote
|Why not simply start a new page on the wiki where anybody can provide contents, so that whenever it's time to send out a newsletter, the draft from the wiki could be taken? 
That way, it wouldn't be too much work for a single person - more like a "community-driven" newsletter, while this may appear to sort of defeat the purpose, not all newsletter recipients are necessarily also wiki users.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=18015#p18015
|title=<nowiki>Re: Newsletter</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Fri Oct 03</nowiki>
}}
}}

== Adding backdrop styling to Canvas (by Gijs) ==
Gijs was looking for an outline that follows the shape of the text, which is what backdrop provides.

For his solution, see the two diffs below. He didn't add the full range of backdrop options, just outline for now [http://forum.flightgear.org/viewtopic.php?f=71&t=23500&p=214278#p214275].
{{FGCquote
|And this is how it looks in FlightGear now :-) Notice how the overlapping waypoints are easier to read (this image is a little exaggerated with all those fixes). 
 
(see the [http://i.imgur.com/dqMzBS4.png linked image])
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214268#p214268
|title=<nowiki>Re: osgText backdrop</nowiki>
|author=<nowiki>Gijs</nowiki>
|date=<nowiki>Mon Jul 07</nowiki>
}}
}}

<syntaxhighlight lang="diff">
commit 5cc0adc778bda1773189b0119d24fbaf5ecd4500
Author: Gijs de Rooy
Date: Mon Jul 7 18:26:16 2014 +0200

Canvas: add backdrop option to text

diff --git a/simgear/canvas/elements/CanvasText.cxx b/simgear/canvas/elements/CanvasText.cxx
index d99760a..3a986e1 100644
--- a/simgear/canvas/elements/CanvasText.cxx
+++ b/simgear/canvas/elements/CanvasText.cxx
@@ -39,6 +39,7 @@ namespace canvas
void setLineHeight(float factor);
void setFill(const std::string& fill);
void setBackgroundColor(const std::string& fill);
+ void setOutlineColor(const std::string& backdrop);

SGVec2i sizeForWidth(int w) const;
osg::Vec2 handleHit(const osg::Vec2f& pos);
@@ -97,6 +98,15 @@ namespace canvas
}

//----------------------------------------------------------------------------
+ void Text::TextOSG::setOutlineColor(const std::string& backdrop)
+ {
+ osg::Vec4 color;
+ setBackdropType(osgText::Text::OUTLINE);
+ if( parseColor(backdrop, color) )
+ setBackdropColor( color );
+ }
+
+ //----------------------------------------------------------------------------
// simplified version of osgText::Text::computeGlyphRepresentation() to
// just calculate the size for a given weight. Glpyh calculations/creating
// is not necessary for this...
@@ -546,6 +556,7 @@ namespace canvas

addStyle("fill", "color", &TextOSG::setFill, text);
addStyle("background", "color", &TextOSG::setBackgroundColor, text);
+ addStyle("backdrop", "color", &TextOSG::setOutlineColor, text);
addStyle("character-size",
"numeric",
static_cast<
</syntaxhighlight>

<syntaxhighlight lang="diff">commit 838cabd2a551834cbcac2b3edd21500409ff2e98
Author: Gijs de Rooy
Date: Mon Jul 7 18:27:50 2014 +0200

Canvas: add backdrop option to text

diff --git a/Nasal/canvas/api.nas b/Nasal/canvas/api.nas
index 8bc12d8..3047dbf 100644
--- a/Nasal/canvas/api.nas
+++ b/Nasal/canvas/api.nas
@@ -634,6 +634,8 @@ var Text = {

setColorFill: func me.set('background', _getColor(arg)),
getColorFill: func me.get('background'),
+
+ setBackdropColor: func me.set('backdrop', _getColor(arg)),
};

# Path
</syntaxhighlight>

== FGCanvas Updates ==
[[File:Dedicated-aircraft-subsystem-group-for-fgcanvas.png|600px|thumb|checking how difficult it would be to put all aircraft related subsystems (fdm, replay, history, controls etc) into a single SGSubsystemGroup named "main-aircraft" to easily make the whole shebang optional using a single --prop for "FGCanvas" use, but also to check if it's feasible to prepare things for later reuse by the AI traffic system (for AI traffic that uses actual FDMs, APs and RMs - but also so that things are affected by the environment) , and it's actually working - even though reset/re-init is obviously hard-coded currently, which I am breaking by shuffling around subsystems, but as long as each SGSubsystemGroup implements the full SGSubsystem interface (postinit, reinit, shutdown etc), this could help clean up fg_init.cxx quite considerably [http://forum.flightgear.org/viewtopic.php?f=71&t=23499]]]
{{FGCquote
|Since the early Canvas days, we started toying with the idea of providing an FGPanel-equivalent integrated right into FlightGear using the Canvas system: 
 
{{cquote|Creating a 'fgcanvas' client analogous to 'fgpanel' should be doable too, since the canvas simply renders to a single osg-Camera. Unlike fgpanel this will require OSG instead of raw GL of course, but that's the price we pay for unifying the rendering backend. 
 
If we're rendering each display as an OSG sub-camera, extracting that logic and wrapping it in a stand-alone OSG viewer should be simplicity itself - 
and so long as it's driven by properties, those can be sent over a socket. That's an approach which seems a lot more bearable to me than 
sending per-frame pixel surfaces over shared memory or sockets / pipes.}}
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214206#p214206
|title=<nowiki>FGCanvas Experiments & Updates</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sun Jul 06</nowiki>
}}
}}

The whole discussion dates back to the early FGPanel days:

{{FGCquote
|I am going to be overhauls the 2D panels / displays code in the near future, and was planning to create exactly the same idea - a standalone app that can run a single panel - good to know the idea works! (I'm also planning to internally port the 2D panel code to the new system, but that should be invisible to most people). It will be part of the main FG codebase, not a fork. As you say, the hope is to make fggc and some related things obsolete, since the same XML+Nasal can be used in the main sim or stand-alone. Anyway, all off-topic!
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=101044#p101044
|title=<nowiki>Re: FSWeekend 2010</nowiki>
|author=<nowiki>zakalawe</nowiki>
|date=<nowiki>Tue Nov 02</nowiki>
}}
}}

{{FGCquote
|Since then, we made some first FGCanvas experiments, and things proved to be fairly tricky, because many C++ subsystems were not exactly easy to make entirely optional, and because of all the implicit assumptions in Nasal code that is unconditionally-loaded from $FG_ROOT/Nasal, and which assumes to have a full session up and running: 
 
{{cquote|Yeah, the stand alone mode won't be to easy. Maybe for now we should use a powerful enough computer which can also run the unneeded parts Separating the parts will be very important, not only for FGCanvas...}}
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214206#p214206
|title=<nowiki>FGCanvas Experiments & Updates</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sun Jul 06</nowiki>
}}
}}

{{FGCquote
|Fast forward a year later, many of those show stoppers have already been resolved, mainly thanks to the work done by Zakalawe and TheTom, who've both been working on reset&re-init, but also overall better run-time re-initialization support, as can be seen in the screen-shot below: 
 
[[FGCanvas]] 
[[File:Patching-fg-3.2-to-make-more-subsystems-optional.png|250px]] 
Most subsystems still running in the screen shot shown here can be considered to be essential now, the only remaining subsystems that still need to be decoupled are: 
<ul>
<li> flight (FDM)</li>
<li> scenery (tile manager, ephemeris)</li>
<li>view manager</li>
<li>lighting</li>
<li>terrasync</li>
</ul>
Otherwise, it's mostly Nasal code in $FG_ROOT/Nasal where dependencies need to be better established and formalized to get rid of implicit assumptions regarding availability of certain subsystems (e.g. view.nas)
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214206#p214206
|title=<nowiki>FGCanvas Experiments & Updates</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sun Jul 06</nowiki>
}}
}}

{{FGCquote
|This means that there's basically just a handful of subsystems that now need to be made optional, and that '''FGCanvas''' will actually become reality. I am going to help rework MapStructure and the ND code in order to ensure that there's no implicit assumptions on running instruments locally, so that we can eventually also drive displays remotely via properties. Roughly a year ago, I already posted some screen shots showing a FG instance that replicates a canvas property tree via telnet's "subscribe" command - it was a hack, but it worked well enough. Even though using UDP-based PUB/SUB, or maybe HLA, should probably scale better. Given the recent progress in this department, I am guessing that it may take us another ~2-3 release cycles until this materializes "automagically". 
 
In the mid-term, I would hope that we could agree to provide some dedicated API for implementing and initializing subsystems, to ensure that most future subsystems can be easily made optional/run-time configurable, which will entail establishing dependencies among subsystems in some "run-levels"-like setup, which will also touch Nasal bootstrapping, i.e. the stuff we're currently doing in FGNasalSys::init(), but which we're hoping to move into scripting space.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214206#p214206
|title=<nowiki>FGCanvas Experiments & Updates</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sun Jul 06</nowiki>
}}
}}

{{FGCquote
|I'll revisit bootstrapping soon, because it's the only sane way to resolve dependencies (intra-module or even subsystem support). FGCnvas definitely sounds like an excellent idea.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214207#p214207
|title=<nowiki>Re: FGCanvas Experiments & Updates</nowiki>
|author=<nowiki>Philosopher</nowiki>
|date=<nowiki>Sun Jul 06</nowiki>
}}
}}

== FGCamera ==
Development of FGCamera continues. The script is being redesigned to be compatible with default view system.
Upcoming version (FGCamera v1) will have new camera mode: "world-view".

{{#ev:youtube|hebx8WdXHa0}}

== Scenery corner ==
=== Paro Int. Airport - VQPR ===
[[File:VQPR PARO AIRPORT.jpg|320px|right]]
{{#ev:youtube|itNY9YUmY3M||right|domestic flight from Bumthang to Paro}}
Works have been added to [[Paro Airport|Paro International Airport]] (VQPR) with terminal, tower, hangars and other buildings. Now users you can enjoy the apron lights, the reference points like Mr. Smiths House or other POIs like the Sangchen Choekhor Monastery. [[TerraSync]] has it all! It is not necessary to download any custom scenery. More information can be found on the wiki page: [[Paro Airport]]. This is the first airport of the Bhutanese Series. Three new domestic airports like Gelephu Airport (VQGP) are currently being developed. Work also continues on navaids for the Kingdom of Bhutan - of course only in the FlightGear-World. Everybody is invited to follow the stage of development at the designers wiki user page ([[User:Fgjosh|Fgjosh]]).

FlightGear wiki:Village pump

2014-07-10T22:21:51Z

August: /* Having separate image categories or not? */

{{Archives|[[/Archive 2012|2012]], [[/Archive 2013|2013]]}}
Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

: Please [{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics] to the '''bottom''' of this page.

: Old discussion should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.

----

== MediaWiki updated to 1.22.0 ==
I've updated MediaWiki to the latest stable, 1.22.0 today. Please report bugs if you find any. For a list of changes, see https://www.mediawiki.org/wiki/Release_notes/1.22

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:00, 26 December 2013 (UTC)

=== Found bugs ===
* Clicking the category link at the bottom of some articles will give a fatal error. For clicking the [[:Category:FlightGear]] at [[FlightGear]] will give the error message: ''Fatal error: Class 'Services_JSON' not found in /home/wiki/wiki/extensions/CategoryTree/CategoryTreeFunctions.php on line 224''.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 03:44, 28 December 2013 (UTC)
:: The CategoryTree extension relies on a function that was removed as of 1.22.0, so the extensions needs some fixing. I've disabled it for now.
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:01, 28 December 2013 (UTC)
::: Yay, CategoryTree is back. Thanks Gijs!
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:50, 6 May 2014 (UTC)

* Also, the mobile theme results in an error: ''Fatal error: Call to undefined method MobileFormatter::setHtmlMode() in /home/wiki/wiki/extensions/MobileFrontend/includes/MobileFormatter.php on line 62'' (works fine after selecting desktop mode).
: Thanks,
: [[User:Philosopher|—Philosopher]] ([[User talk:Philosopher|talk]]) 03:59, 28 December 2013 (UTC)
:: I forgot to update the mobile extension. Works again ;-)
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:01, 28 December 2013 (UTC)

* In the CategoryTree the FlightGear category [[:Category:Documentation|appears empty]]. The solution is reported at [[mw:Extension:CategoryTree#Member counts are wrong, gray arrows ► are shown instead of ►]]. It's a minor problem but the solution looks easy, for what I can tell.
: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 00:27, 11 May 2014 (UTC)

:: Unfortunately that doesn't seem to help...
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:11, 11 May 2014 (UTC)

== Got any ideas for a better name for this page? ==
As this is for this page in particular, see the [[FlightGear wiki talk:Village pump#Any ideas for a better name|talk page]].

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:44, 5 March 2014 (UTC)

== Template for announcement of changes and new features ==

From a forum PM from Hooray (posted here with his permission):

<div style="background: #fafaf0; padding: 1em;">
hi, whenever we announce a new feature, we typically need to do this in three places:

* newsletter
* changelog
* the docs (corresponding wiki articles)

so far, we have always copied & pasted things, I would prefer to have a single template for this instead, something like
{{tlx|Announce|version|description}}

This could add announcements to each release cycle (i.e. 3.2 currently), and we could maybe automatically add things to the newsletter and the release changelog.

Like I said, I would like to avoid redundant efforts, i.e. less copy & paste

Do you have any ideas on how to implement this using existing wiki means ?

Ideally, we would create a new announcement, like for example "canvas mouse button support", and could then use this announcement in all 3 places by calling the corresponding template.

Thanks
</div>
My take is that to use a separate template for each new feature is not a good idea, but if I understand him correctly his intention is to gather up each months new features in one template.

Any thoughts on this?

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:14, 5 March 2014 (UTC)

{{WIP}}

<pre style="white-space: pre-wrap; margin-left: 1.5em;">I am thinking of restructuring the way we're writing our newsletter by focusing on our "ugly stepchild", namely the "changelog" - as others like Torsten have pointed out, we should ideally be writing the changelog as early as possible - but the truth is, it's mostly forum people contributing to it, and it's not seen too many edits. The newsletter is working a bit better for us. So I was thinking of how to unify both worlds - especially keeping in mind that our changelog encompasses basically 6 months, i.e. 6 newsletter editions.

So I am considering to split up our newsletter into a handful of building blocks and use a few templates, so that additions are added through a few custom templates, that would automatically add things to the changelog.

The changelog would then be written by contributing to the newsletter and using the proper templates, such as e.g.:

{{changelog|version=3.2|category:aircraft|type=updated|announcement=The 747-400 and 777-200 have received extensive updates, and are now both using the new MapStructure-based NavDisplay framework|screenshots=|videos=}}

The changelog would then be procedurally assembled by processing all templates for the corresponding release cycle.

I would even consider locking the changelog itself, and making it just a template that references the stuff included via templates.

We may however benefit from a few additional mediawiki extensions. But otherwise, I am hoping that the changelog is going to be more comprehensive, while the wiki would become more "formal" - we could obviously still support additions without using changelog-templates, i.e. those would be excluded.

thoughts / ideas ?

(CC'ing Philosopher, because he's been doing some template stuff, too)</pre>

:Need to come up with a template that handles announcements, primarily for the changelog and the newsletter. There's a mutual relationship here, but the newsletter is much more popular, i.e. sees more contributions and more activity overall. Changelog writing is still a chore. But basically 6 months worth of newsletters are equivalent to a single changelog, we only need to establish some framework around this - and then the whole changelog could be mostly based on newsletter contributions. It would greatly help to request people to make announcements ALWAYS using 3rd person speech, so that things can be directly copied from the forum/devel list to the newsletter/changelog. That's kinda the idea here. It would reduce our workload quite significantly

:* Changelog
:* Newsletter
:* Devel List
:* Forum
:* Website

:{{unsigned|21:25, 24 April 2014‎|Hooray}}

::I will probably have to take a look at this now and again to think about if and how this could be done. I assume Hooray is aiming at having each newsletter and change log built up mostly from "instances" of a template like in the above comments.

::There are pros and cons with this approach, as with any. I think that one of the cons is that even the slightest overhead and/or complication might scare away a few contributors. But at the other hand I fully understand that reading through six months of newsletters + forum posts + devel list posts are not that fun either (though I would guess that is not how things are done ;-).

::''Slightly off topic'' is that I would like to see a section in the change log mentioning changes that will break backwards compatibility. I first saw such a section, "Breaking changes", in the [https://www.mediawiki.org/w/index.php?title=Release_notes/1.22&oldid=848518#MediaWiki_1.22.0 change log of MedeiaWiki 1.22] when the software of this wiki was updated, and figured it would be a good idea. This could be useful for things like for example figuring out whether FlightGear x.x can use World Scenery y.y.

::''Even more off topic'' I think that the wiki/newsletter/devel list/etc are rather blunt tools for keeping an up to date change log. My gut feeling is that there are tools for that around, and even if we do not use them we might borrow some ideas from them, hopefully without bringing a lot of red tape(!).

::—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 20:14, 27 April 2014 (UTC)

::: Interesting subject! I think going through just 6 newsletters by hand is more rewarding than coming up with complex templates that will increase the entry barrier of the newsletter and still require summarising/rewordings afterwards to fit the concise format of a changelog. Introducing a template on the wiki won't take away the forum/devel list scanning that's required as not everyone contributes to the wiki.
::: I do support the "breaking changes" idea though ;-)
::: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 19:18, 1 May 2014 (UTC)

== Very dispersed Boeing 777 articles! ==

Hi, I got interested in Flightgear and was taking a look at the Boeing 777 articles and noticed that it was incredibly spread out.

Each aircraft has it's own page with information to varying degrees of completeness. Having a look at the A330 articles, they are much more 'aligned' and it's a lot easier to find stuff. Maybe this could be something that could be done with the Boeing. Since both seem to be very similar, I'm thinking that there could be a common page on help and tutorials respectively, with the individual type pages catering to unique information. I started on some stuff but pretty quickly figured out it was a better idea to check here first :)

--[[User:Manfred|Manfred]] ([[User talk:Manfred|talk]]) 11:55, 25 March 2014 (UTC)

: Doing a simple search for pages containing "777" (see [http://wiki.flightgear.org/index.php?search=777&title=Special%3ASearch&fulltext=1 this link]) I quickly see what you mean.

: I assume that the different versions may have different authors and thus probably are slightly different from each other when it comes to handling and completeness. It might be a good idea to start by going through each of the help pages and tutorials (preferably while playing with the different aircraft at the same time), as well as having a look at help dialogues and any readmes in the aircraft packages.

: Making a common page, while highlighting differences between the different versions, could probably help other users a lot and may perhaps be a help for aircraft developers to use features from more complete versions to improve the other ones as well as help motivate harmonizing handling like for example key bindings.

: If I understand your intention I can not see why anyone would do anything but trying to give you helpful hints, after all this is a wiki. :-)

: One hint for starters is to begin working on a page as a subpage to your user page, like for example [[User:Manfred/Boeing 777 Autopilot]] (I just moved it) and then moving it to the article namespace when you feel it has reached the level where you are comfortable with it (though this is not by any means necessary, it's just that I like doing so myself).

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:40, 28 March 2014 (UTC)

: I am interested to help, this page could be a model of what we could offer : [http://wiki.flightgear.org/Boeing_787-8_Dreamliner 777-8 Dreamliner]
: -- [[User:F-JYL|F-JYL]] 21 April 2014 09:32

== Bash and DOS syntax highlighting ==

[[User:Daemonburrito|Daemonburrito]] found that we can use syntax highlighting for Bash. I guess that means that we could use syntax highlighting for most Linux (and possibly also Mac) command lines. Looking at [[mediawikiwiki:Extension:SyntaxHighlight_GeSHi]] I find that we also also probably can use that for DOS prompts.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:24, 5 May 2014 (UTC)

: We've had that extension installed for a while now. Everything that's listed at [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi#Supported_languages Supported languages] is supported, plus Nasal.
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:23, 5 May 2014 (UTC)

:: I'm aware of the list, but was not aware that syntax highlighting could be used for shell programming (and hence shell promts) and guessed I was not alone.
:: Basically added the topic to highlight (pun intended) the possibility to do so. I should probably also mention it in [[Help:Formatting#Syntax highlighting]].
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:53, 5 May 2014 (UTC)

== A plan for a reorganization of the wiki ==

There is an ongoing discussion on [[User:Bigstones/Essay:A plan for a reorganization of the wiki]]. Please comment on its talk page, to avoid scattering the discussion. This "section" is only intended to inform about it.
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 12:53, 7 May 2014 (UTC)

== The new progress bar icons ==

I just changed icons that {{tl|progressbar}} is using and would like some constructive feedback.

Some things I have noted myself is that while I used a blend of the colours used in the old icons and in some of [[Special:ListFiles/Johan_G|my other icons]], these icons have a much larger coloured area and thus might have a little high contrast.

In any way I am going to let this rest for a week or two and follow it up then.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 01:05, 10 May 2014 (UTC)

: After having made them a tiny pixel smaller (from 16 px to 15 px) and having done no other changes I seem to be liking them more and more, so I leave them in their current state.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:13, 24 May 2014 (UTC)

== Category:Support ==
As it seems that support organization is a priority, I created [[:Category:Support]]. I hope the name is generic enough to avoid misunderstandings... but I thought better to have a bad one, than nothing. I'll try to put there everything on support I find so that it can be better organized (merged/split and then cleaned up).
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:06, 11 May 2014 (UTC)

:Hi,
:
:I didn't read through all of your ideas yet, but isn't "Support" a rather obscure term? Everything could fit under that branch, so we'll end up with yet another giant category; which you tried to prevent, right? Or maybe I'm just missing the bigger picture...

:[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:23, 11 May 2014 (UTC)

:: Hi, I figured out (''edit: led to figure out'') that support organization is a major problem. There's a lot of "support" related articles, 2-3 articles only on OpenGL. I hoped that this name could indeed be wide enough, and that in case it could just be renamed. Troubleshooting seemed to narrow to me on the other side, but if you think that would be better I can change it now (waiting for response before proceeding).--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:29, 11 May 2014 (UTC)

::: Take [[Settings for slower graphics cards]] for example. It's categorised under [[:Category:Performance tuning]]. I would expect that to be a sub of [[:Category:Support]]. Anyone looking for articles on how to improve performance can check that category then. I don't expect anyone to go through a very broad category with 100s of articles to find info on a rather specific subject.
::: Or maybe I should reword my comment into a question: What would be the use case of [[:Category:Support]]?
::: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:39, 11 May 2014 (UTC)
::: PS: I know we have a lot of bloated categories on this wiki, so I'm glad you've brought all this back on the agenda ;-)

:::: With the example: I confess I was probably deceived by the presence of some development related stuff in [[:Category:Performance tuning]]. I thought it would be better to separate development and usage. Framerate is either a user issue, or a developer's aim. I think the two can be separated. The problem is I moved out the most of it! I should consider the contrary. I'll undo. (I currently have like 20 open browser tabs so it might take me some time).
:::: The use case however is: gather support articles so that a maintainer can split/merge them to make them more organized. Once that's done, there won't probably be more than 10 articles, and if there are, still one can subcategorize. In the above case, I just took the longest path, but given the lack of tools I confess I just wanted to get started.
:::: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 14:00, 11 May 2014 (UTC)
:::: ... I must confess also that after undoing, I feel the urge to redo that again. The two non-support related articles, [[GIT Performance Tests]] and [[Howto:Use the system monitor]] (where btw, the "profiling" section might be directed to ''core'' developers?) would have no place if I move this category into support. That's also why I moved it into Development. Let me know what you think, also regarding the Support category name.
:::: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 14:24, 11 May 2014 (UTC)

== FlightGear screenshot categories ==

I have been thinking about this for quite a while. When I was categorising the images, I gave the categories with the FlightGear screenshots quite cumbersome and long names.

I guess the discussions with Bigstones, in particular [http://wiki.flightgear.org/index.php?title=User_talk:Bigstones/Essay:A_plan_for_a_reorganization_of_the_wiki&diff=70678&oldid=70675 my reply here] (see second paragraph under 2.) might have stirred up some old dust for me. :-)

The cumbersome and long names has a couple negative effects. Firstly they are way longer to type than should be necessary, secondly, and more important I think, the probability that they show up in the upload wizard probably is rather low as they all begin with "FlightGear..." (what was I thinking, like if someone would upload a bunch of X-Plane screenshots here). I ''guess'' that by beginning most if not all screenshot category names with "Screenshots of..." the chances they would be used will increase.

In addition to that some of those categories are way too large and need to be diffused (broken down into smaller categories).

I have noted that a lot of aircraft images have been added to the aircraft article categories. I would prefer if the screenshot categories associated with different kinds of aircraft (e.g. fighters or airliners) would be subcategories to the screenshot categories ''and'' that those screenshot categories would be a subcategory to the category for those kinds of aircraft. I have at some point started to try mimic the structure of [[:Category:Aircraft by type]] in [[:Category:FlightGear screenshots of aircraft by type]], but got distracted or forgot about it for a while. Someting similar might be needed for the cockpit screenshots.

The note about intended contents should also mention that these categories are intended only for in-sim screenshots from FlightGear.

In conclusion I suggest, and would like feedback on, the following:

{| class="wikitable"
! Current category !! Suggested new category !! Alternative new category !! Comment
|-
| [[:Category:FlightGear cockpit screenshots‎]] || [[:Category:Screenshots of cockpits]] || Cockpit screenshots ||
|-
| [[:Category:FlightGear cockpit close-up screenshots‎]] || [[:Category:Screenshots of cockpit details]] || Cockpit close-up screenshots ||
|-
| [[:Category:FlightGear dialogue screenshots‎]]
| <s>Category:Screenshots of ‎dialogues</s>

[[:Category:Screenshots of dialogs in FlightGear‎]]
| <s>Dialogue</s> dialog box screenshots ||
|-
| [[:Category:FlightGear exterior screenshots]]‎ || [[:Category:Screenshots of aircraft]] || Exterior screenshots ||
|-
| [[:Category:FlightGear interior screenshots]] || [[:Category:Screenshots of cabins]] || Cabin screenshots ||
|-
| [[:Category:FlightGear scenery screenshots]]‎ || [[:Category:Screenshots of scenery]] || Scenery screenshots ||
|-
| Category:FlightGear screenshots of aircraft by type || [[:Category:Screenshots of aircraft by type]] || — || Should only contain categories
|-
| [[:Category:FlightGear screenshots of vehicles]] || [[:Category:Screenshots of vehicles]] || Vehicle screenshots ||
|-
| [[:Category:FlightGear weather screenshots]]‎ || [[:Category:Screenshots of weather]] || Weather screenshots ||
|}

In essence it is a huge bot job, except for the diffusion of the largest screenshot categories.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:57, 12 May 2014 (UTC)

: As I might have said already, I'm ok with it and in particular I agree that images would be easier to find if in their own branch. The only thing, I think it's not going to last if the upload wizard doesn't enforce the use of a subcat of "Files", or at least, suggests that area in some handy way (i.e. not a written notice). Maybe the CategoryTree could be included (like with templates) to help finding the right category? It's hard to figure out a good one by typing characters one by one.
: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 21:49, 12 May 2014 (UTC)

:: Created the category pages as above, except for Category:Screenshots of ‎dialogues, which I found a bit ambiguous. I named that one Category:Screenshots of dialogues in FlightGear‎ instead.
:: I have also added a request at the [[User talk:BotFlightGear#FlightGear screenshot categories|bot talk page]] ([http://wiki.flightgear.org/index.php?title=User_talk:BotFlightGear&oldid=71130#FlightGear_screenshot_categories permalink])
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:59, 13 May 2014 (UTC)

::: Did the move to [[:Category:Screenshots of aircraft by type]] by hand. Was only a few files.
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:46, 13 May 2014 (UTC)

::: I hope I'm not late, I noticed only now, but ''dialogue'' tends to be used more as in "discussion between two", while the GUI elements are usually spelled ''dialogs''. I guess that more than real confusion this distinction would cause just minor hilarity, but... you never know, you might find in there screenshots of radio chat with ATC. (being not a native english speaker, [http://english.stackexchange.com/questions/59640/what-is-the-difference-between-dialogue-and-dialog here's my ref.]) --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 19:20, 13 May 2014 (UTC)

:::: Well spotted, good reference as well and most important not too late. Thank you! I was wondering a bit but guessed that dialog was more or less colloquial as dialogue seemed correct with both my browsers English and American English dictionaries. Swedish schools teaching (very!) British English probably have something to do with my spelling as well.
:::: Changed the request on the [[User talk:BotFlightGear#FlightGear screenshot categories|bot page]] from Category:Screenshots of dialogues in FlightGear‎ to [[:Category:Screenshots of dialogs in FlightGear‎]].
:::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:06, 14 May 2014 (UTC)

=== Having separate image categories or not? ===
One thing that keeps nagging me is that all Wikipedias I have been able to read and some I can hardly read (English, Swedish + German and French) have separate categories for files/images. There is probably a reason for that (I am guessing at mainly ease of finding images for articles and possibly also for bandwidth reasons).

The upload wizard is borrowed from Wikimedia Commons (but is it properly attributed?) where pretty much all categories are for files/images. While I am not aware of its technical details I see few if any efficient ways it could be modified to only or primarily suggest image categories. As I see it it would require a ''fresh and updated'' list of categories that in one way or another would require some manual intervention.

Two things I have done so far is to re-categorize images and that I have begun trying to link the nodes to the nodes in the branch with the article categories by putting the image categories in the article categories (this is done on a very small scale though).

Questions is though: What is in the best interest of the users? Should I keep on having them separate or should I just let it grow wild(er)? It could be an interesting experiment though it would require a lot of work if it turns out less favourable.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 22:02, 10 July 2014 (UTC)

:I saw you implementing this at some of my airport screen-shots and immediately adopted it on other images. I think your idea of separating those categories would help us puting a link at the end of each article which says: "Media about :XY". Thats why I think all the other wikis provide separated categories. That's the only way to get linkable categories which only contain media.

:--[[User:August|August]] ([[User talk:August|talk]]) 22:18, 10 July 2014 (UTC)

== Conventions on discussion conclusions ==
Sometimes proposals don't get the attention the proposer might have hoped for. Of course, everyone's involved in their projects, and following discussions in "recent changes" isn't easy, so nothing personal, my question is ''very practical''.

Sometimes these proposals need help from others (like my [[User_talk:Bigstones/Essay:A plan for a reorganization of the wiki#Bot proposal .28request.3F.29|"remove redundant categories"]]) so it's pretty clear that one will have to wait and retry/insist for that. Some other times though (like my above "Category:Support" topic - with which btw I did some mess moving messages around) one could easily continue on his/her own. In such cases, I feel that lack/loss of attention means "Ok, I don't mind if you do that, in case, we'll discuss the results" (like for the FAQ update - btw, thanks to the reviewers of [http://wiki.flightgear.org/index.php?title=Frequently_asked_questions&oldid=71015 my cuts]). If this is correct, I'd like to add it to the [[Help:Maintenance]] page, because it could help getting more things done and avoid misunderstandings. Oh, and by what I said, if I don't get answers, I'll take it for granted :D

--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 12:43, 13 May 2014 (UTC)

: I have found the lack of feedback to be discouraging at times, but at other times I have just went ahead and done things the way I would like to have them done, like for example my reorganisation and extension of the help pages, as well as adding the "[[FlightGear wiki:Village pump|Discuss!]]" link to the left side menu.

: I would guess that you draw the right conclusion with the statement that "Ok, I don't mind if you do that, in case, we'll discuss the results". The very most of the times that is the way to go. The good thing with a wiki is that it is so easy to revert a change (i.e "View history" tab → Go to topmost edit → Click the "undo" link). If if things go really wrong most things can be salvaged from the page history (though it can be a lot of work at times). ;-)

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:03, 13 May 2014 (UTC)

== Editing JavaScript files ? ==

: ''Moved here from [[Talk:Portal:Wiki#Editing JavaScript files ?]] ([http://wiki.flightgear.org/index.php?title=Talk:Portal:Wiki&oldid=72290 permalink]) since this might affect all users.''

I think, at some point, I saw someone editing JavaScript files here (Johan_G or Gijs probably) - what is involved to do that ? Any links/pointers ? Okay, found something at [[MediaWiki:Common.js]] Is it also possible to create custom JS/plain text files without any wiki markup ? Are my privileges even sufficient ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 21:11, 2 June 2014 (UTC)

: Nope, was not me. Javascript files is as far as I know currently limited to [[MediaWiki:Common.js]]. It is apparently possible to change some settings so that one can add "user javascript pages" (as well as "user Cascading Style Sheets"), see the WikiMedia Wiki pages [http://www.mediawiki.org/wiki/Manual:$wgAllowUserJs Manual:$wgAllowUserJs] (and [http://www.mediawiki.org/wiki/Manual:$wgAllowUserCss Manual:$wgAllowUserCss]).

: Both can be useful for testing stuff before including them in the "common" (i.e. site wide) files, as well as for personalizing the look, feel and functionality. I do not know what issues they could cause or if we have the permissions to change it. Maybe Simon and Gijs are the ones who can do it.

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 04:40, 3 June 2014 (UTC)

== MediaWiki updated to 1.23.0 ==

I've updated MediaWiki to the latest stable release (1.23.0) today. I'm now updating all extensions, so some things may be broken temporarily. Please report bugs if you find any. For a list of changes, see https://www.mediawiki.org/wiki/Release_notes/1.23

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:04, 8 June 2014 (UTC)

FlightGear wiki:Village pump

2014-07-10T22:20:50Z

August: /* Having separate image categories or not? */

{{Archives|[[/Archive 2012|2012]], [[/Archive 2013|2013]]}}
Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

: Please [{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics] to the '''bottom''' of this page.

: Old discussion should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.

----

== MediaWiki updated to 1.22.0 ==
I've updated MediaWiki to the latest stable, 1.22.0 today. Please report bugs if you find any. For a list of changes, see https://www.mediawiki.org/wiki/Release_notes/1.22

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:00, 26 December 2013 (UTC)

=== Found bugs ===
* Clicking the category link at the bottom of some articles will give a fatal error. For clicking the [[:Category:FlightGear]] at [[FlightGear]] will give the error message: ''Fatal error: Class 'Services_JSON' not found in /home/wiki/wiki/extensions/CategoryTree/CategoryTreeFunctions.php on line 224''.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 03:44, 28 December 2013 (UTC)
:: The CategoryTree extension relies on a function that was removed as of 1.22.0, so the extensions needs some fixing. I've disabled it for now.
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:01, 28 December 2013 (UTC)
::: Yay, CategoryTree is back. Thanks Gijs!
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:50, 6 May 2014 (UTC)

* Also, the mobile theme results in an error: ''Fatal error: Call to undefined method MobileFormatter::setHtmlMode() in /home/wiki/wiki/extensions/MobileFrontend/includes/MobileFormatter.php on line 62'' (works fine after selecting desktop mode).
: Thanks,
: [[User:Philosopher|—Philosopher]] ([[User talk:Philosopher|talk]]) 03:59, 28 December 2013 (UTC)
:: I forgot to update the mobile extension. Works again ;-)
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:01, 28 December 2013 (UTC)

* In the CategoryTree the FlightGear category [[:Category:Documentation|appears empty]]. The solution is reported at [[mw:Extension:CategoryTree#Member counts are wrong, gray arrows ► are shown instead of ►]]. It's a minor problem but the solution looks easy, for what I can tell.
: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 00:27, 11 May 2014 (UTC)

:: Unfortunately that doesn't seem to help...
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:11, 11 May 2014 (UTC)

== Got any ideas for a better name for this page? ==
As this is for this page in particular, see the [[FlightGear wiki talk:Village pump#Any ideas for a better name|talk page]].

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:44, 5 March 2014 (UTC)

== Template for announcement of changes and new features ==

From a forum PM from Hooray (posted here with his permission):

<div style="background: #fafaf0; padding: 1em;">
hi, whenever we announce a new feature, we typically need to do this in three places:

* newsletter
* changelog
* the docs (corresponding wiki articles)

so far, we have always copied & pasted things, I would prefer to have a single template for this instead, something like
{{tlx|Announce|version|description}}

This could add announcements to each release cycle (i.e. 3.2 currently), and we could maybe automatically add things to the newsletter and the release changelog.

Like I said, I would like to avoid redundant efforts, i.e. less copy & paste

Do you have any ideas on how to implement this using existing wiki means ?

Ideally, we would create a new announcement, like for example "canvas mouse button support", and could then use this announcement in all 3 places by calling the corresponding template.

Thanks
</div>
My take is that to use a separate template for each new feature is not a good idea, but if I understand him correctly his intention is to gather up each months new features in one template.

Any thoughts on this?

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:14, 5 March 2014 (UTC)

{{WIP}}

<pre style="white-space: pre-wrap; margin-left: 1.5em;">I am thinking of restructuring the way we're writing our newsletter by focusing on our "ugly stepchild", namely the "changelog" - as others like Torsten have pointed out, we should ideally be writing the changelog as early as possible - but the truth is, it's mostly forum people contributing to it, and it's not seen too many edits. The newsletter is working a bit better for us. So I was thinking of how to unify both worlds - especially keeping in mind that our changelog encompasses basically 6 months, i.e. 6 newsletter editions.

So I am considering to split up our newsletter into a handful of building blocks and use a few templates, so that additions are added through a few custom templates, that would automatically add things to the changelog.

The changelog would then be written by contributing to the newsletter and using the proper templates, such as e.g.:

{{changelog|version=3.2|category:aircraft|type=updated|announcement=The 747-400 and 777-200 have received extensive updates, and are now both using the new MapStructure-based NavDisplay framework|screenshots=|videos=}}

The changelog would then be procedurally assembled by processing all templates for the corresponding release cycle.

I would even consider locking the changelog itself, and making it just a template that references the stuff included via templates.

We may however benefit from a few additional mediawiki extensions. But otherwise, I am hoping that the changelog is going to be more comprehensive, while the wiki would become more "formal" - we could obviously still support additions without using changelog-templates, i.e. those would be excluded.

thoughts / ideas ?

(CC'ing Philosopher, because he's been doing some template stuff, too)</pre>

:Need to come up with a template that handles announcements, primarily for the changelog and the newsletter. There's a mutual relationship here, but the newsletter is much more popular, i.e. sees more contributions and more activity overall. Changelog writing is still a chore. But basically 6 months worth of newsletters are equivalent to a single changelog, we only need to establish some framework around this - and then the whole changelog could be mostly based on newsletter contributions. It would greatly help to request people to make announcements ALWAYS using 3rd person speech, so that things can be directly copied from the forum/devel list to the newsletter/changelog. That's kinda the idea here. It would reduce our workload quite significantly

:* Changelog
:* Newsletter
:* Devel List
:* Forum
:* Website

:{{unsigned|21:25, 24 April 2014‎|Hooray}}

::I will probably have to take a look at this now and again to think about if and how this could be done. I assume Hooray is aiming at having each newsletter and change log built up mostly from "instances" of a template like in the above comments.

::There are pros and cons with this approach, as with any. I think that one of the cons is that even the slightest overhead and/or complication might scare away a few contributors. But at the other hand I fully understand that reading through six months of newsletters + forum posts + devel list posts are not that fun either (though I would guess that is not how things are done ;-).

::''Slightly off topic'' is that I would like to see a section in the change log mentioning changes that will break backwards compatibility. I first saw such a section, "Breaking changes", in the [https://www.mediawiki.org/w/index.php?title=Release_notes/1.22&oldid=848518#MediaWiki_1.22.0 change log of MedeiaWiki 1.22] when the software of this wiki was updated, and figured it would be a good idea. This could be useful for things like for example figuring out whether FlightGear x.x can use World Scenery y.y.

::''Even more off topic'' I think that the wiki/newsletter/devel list/etc are rather blunt tools for keeping an up to date change log. My gut feeling is that there are tools for that around, and even if we do not use them we might borrow some ideas from them, hopefully without bringing a lot of red tape(!).

::—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 20:14, 27 April 2014 (UTC)

::: Interesting subject! I think going through just 6 newsletters by hand is more rewarding than coming up with complex templates that will increase the entry barrier of the newsletter and still require summarising/rewordings afterwards to fit the concise format of a changelog. Introducing a template on the wiki won't take away the forum/devel list scanning that's required as not everyone contributes to the wiki.
::: I do support the "breaking changes" idea though ;-)
::: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 19:18, 1 May 2014 (UTC)

== Very dispersed Boeing 777 articles! ==

Hi, I got interested in Flightgear and was taking a look at the Boeing 777 articles and noticed that it was incredibly spread out.

Each aircraft has it's own page with information to varying degrees of completeness. Having a look at the A330 articles, they are much more 'aligned' and it's a lot easier to find stuff. Maybe this could be something that could be done with the Boeing. Since both seem to be very similar, I'm thinking that there could be a common page on help and tutorials respectively, with the individual type pages catering to unique information. I started on some stuff but pretty quickly figured out it was a better idea to check here first :)

--[[User:Manfred|Manfred]] ([[User talk:Manfred|talk]]) 11:55, 25 March 2014 (UTC)

: Doing a simple search for pages containing "777" (see [http://wiki.flightgear.org/index.php?search=777&title=Special%3ASearch&fulltext=1 this link]) I quickly see what you mean.

: I assume that the different versions may have different authors and thus probably are slightly different from each other when it comes to handling and completeness. It might be a good idea to start by going through each of the help pages and tutorials (preferably while playing with the different aircraft at the same time), as well as having a look at help dialogues and any readmes in the aircraft packages.

: Making a common page, while highlighting differences between the different versions, could probably help other users a lot and may perhaps be a help for aircraft developers to use features from more complete versions to improve the other ones as well as help motivate harmonizing handling like for example key bindings.

: If I understand your intention I can not see why anyone would do anything but trying to give you helpful hints, after all this is a wiki. :-)

: One hint for starters is to begin working on a page as a subpage to your user page, like for example [[User:Manfred/Boeing 777 Autopilot]] (I just moved it) and then moving it to the article namespace when you feel it has reached the level where you are comfortable with it (though this is not by any means necessary, it's just that I like doing so myself).

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:40, 28 March 2014 (UTC)

: I am interested to help, this page could be a model of what we could offer : [http://wiki.flightgear.org/Boeing_787-8_Dreamliner 777-8 Dreamliner]
: -- [[User:F-JYL|F-JYL]] 21 April 2014 09:32

== Bash and DOS syntax highlighting ==

[[User:Daemonburrito|Daemonburrito]] found that we can use syntax highlighting for Bash. I guess that means that we could use syntax highlighting for most Linux (and possibly also Mac) command lines. Looking at [[mediawikiwiki:Extension:SyntaxHighlight_GeSHi]] I find that we also also probably can use that for DOS prompts.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:24, 5 May 2014 (UTC)

: We've had that extension installed for a while now. Everything that's listed at [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi#Supported_languages Supported languages] is supported, plus Nasal.
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:23, 5 May 2014 (UTC)

:: I'm aware of the list, but was not aware that syntax highlighting could be used for shell programming (and hence shell promts) and guessed I was not alone.
:: Basically added the topic to highlight (pun intended) the possibility to do so. I should probably also mention it in [[Help:Formatting#Syntax highlighting]].
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:53, 5 May 2014 (UTC)

== A plan for a reorganization of the wiki ==

There is an ongoing discussion on [[User:Bigstones/Essay:A plan for a reorganization of the wiki]]. Please comment on its talk page, to avoid scattering the discussion. This "section" is only intended to inform about it.
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 12:53, 7 May 2014 (UTC)

== The new progress bar icons ==

I just changed icons that {{tl|progressbar}} is using and would like some constructive feedback.

Some things I have noted myself is that while I used a blend of the colours used in the old icons and in some of [[Special:ListFiles/Johan_G|my other icons]], these icons have a much larger coloured area and thus might have a little high contrast.

In any way I am going to let this rest for a week or two and follow it up then.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 01:05, 10 May 2014 (UTC)

: After having made them a tiny pixel smaller (from 16 px to 15 px) and having done no other changes I seem to be liking them more and more, so I leave them in their current state.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:13, 24 May 2014 (UTC)

== Category:Support ==
As it seems that support organization is a priority, I created [[:Category:Support]]. I hope the name is generic enough to avoid misunderstandings... but I thought better to have a bad one, than nothing. I'll try to put there everything on support I find so that it can be better organized (merged/split and then cleaned up).
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:06, 11 May 2014 (UTC)

:Hi,
:
:I didn't read through all of your ideas yet, but isn't "Support" a rather obscure term? Everything could fit under that branch, so we'll end up with yet another giant category; which you tried to prevent, right? Or maybe I'm just missing the bigger picture...

:[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:23, 11 May 2014 (UTC)

:: Hi, I figured out (''edit: led to figure out'') that support organization is a major problem. There's a lot of "support" related articles, 2-3 articles only on OpenGL. I hoped that this name could indeed be wide enough, and that in case it could just be renamed. Troubleshooting seemed to narrow to me on the other side, but if you think that would be better I can change it now (waiting for response before proceeding).--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:29, 11 May 2014 (UTC)

::: Take [[Settings for slower graphics cards]] for example. It's categorised under [[:Category:Performance tuning]]. I would expect that to be a sub of [[:Category:Support]]. Anyone looking for articles on how to improve performance can check that category then. I don't expect anyone to go through a very broad category with 100s of articles to find info on a rather specific subject.
::: Or maybe I should reword my comment into a question: What would be the use case of [[:Category:Support]]?
::: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:39, 11 May 2014 (UTC)
::: PS: I know we have a lot of bloated categories on this wiki, so I'm glad you've brought all this back on the agenda ;-)

:::: With the example: I confess I was probably deceived by the presence of some development related stuff in [[:Category:Performance tuning]]. I thought it would be better to separate development and usage. Framerate is either a user issue, or a developer's aim. I think the two can be separated. The problem is I moved out the most of it! I should consider the contrary. I'll undo. (I currently have like 20 open browser tabs so it might take me some time).
:::: The use case however is: gather support articles so that a maintainer can split/merge them to make them more organized. Once that's done, there won't probably be more than 10 articles, and if there are, still one can subcategorize. In the above case, I just took the longest path, but given the lack of tools I confess I just wanted to get started.
:::: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 14:00, 11 May 2014 (UTC)
:::: ... I must confess also that after undoing, I feel the urge to redo that again. The two non-support related articles, [[GIT Performance Tests]] and [[Howto:Use the system monitor]] (where btw, the "profiling" section might be directed to ''core'' developers?) would have no place if I move this category into support. That's also why I moved it into Development. Let me know what you think, also regarding the Support category name.
:::: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 14:24, 11 May 2014 (UTC)

== FlightGear screenshot categories ==

I have been thinking about this for quite a while. When I was categorising the images, I gave the categories with the FlightGear screenshots quite cumbersome and long names.

I guess the discussions with Bigstones, in particular [http://wiki.flightgear.org/index.php?title=User_talk:Bigstones/Essay:A_plan_for_a_reorganization_of_the_wiki&diff=70678&oldid=70675 my reply here] (see second paragraph under 2.) might have stirred up some old dust for me. :-)

The cumbersome and long names has a couple negative effects. Firstly they are way longer to type than should be necessary, secondly, and more important I think, the probability that they show up in the upload wizard probably is rather low as they all begin with "FlightGear..." (what was I thinking, like if someone would upload a bunch of X-Plane screenshots here). I ''guess'' that by beginning most if not all screenshot category names with "Screenshots of..." the chances they would be used will increase.

In addition to that some of those categories are way too large and need to be diffused (broken down into smaller categories).

I have noted that a lot of aircraft images have been added to the aircraft article categories. I would prefer if the screenshot categories associated with different kinds of aircraft (e.g. fighters or airliners) would be subcategories to the screenshot categories ''and'' that those screenshot categories would be a subcategory to the category for those kinds of aircraft. I have at some point started to try mimic the structure of [[:Category:Aircraft by type]] in [[:Category:FlightGear screenshots of aircraft by type]], but got distracted or forgot about it for a while. Someting similar might be needed for the cockpit screenshots.

The note about intended contents should also mention that these categories are intended only for in-sim screenshots from FlightGear.

In conclusion I suggest, and would like feedback on, the following:

{| class="wikitable"
! Current category !! Suggested new category !! Alternative new category !! Comment
|-
| [[:Category:FlightGear cockpit screenshots‎]] || [[:Category:Screenshots of cockpits]] || Cockpit screenshots ||
|-
| [[:Category:FlightGear cockpit close-up screenshots‎]] || [[:Category:Screenshots of cockpit details]] || Cockpit close-up screenshots ||
|-
| [[:Category:FlightGear dialogue screenshots‎]]
| <s>Category:Screenshots of ‎dialogues</s>

[[:Category:Screenshots of dialogs in FlightGear‎]]
| <s>Dialogue</s> dialog box screenshots ||
|-
| [[:Category:FlightGear exterior screenshots]]‎ || [[:Category:Screenshots of aircraft]] || Exterior screenshots ||
|-
| [[:Category:FlightGear interior screenshots]] || [[:Category:Screenshots of cabins]] || Cabin screenshots ||
|-
| [[:Category:FlightGear scenery screenshots]]‎ || [[:Category:Screenshots of scenery]] || Scenery screenshots ||
|-
| Category:FlightGear screenshots of aircraft by type || [[:Category:Screenshots of aircraft by type]] || — || Should only contain categories
|-
| [[:Category:FlightGear screenshots of vehicles]] || [[:Category:Screenshots of vehicles]] || Vehicle screenshots ||
|-
| [[:Category:FlightGear weather screenshots]]‎ || [[:Category:Screenshots of weather]] || Weather screenshots ||
|}

In essence it is a huge bot job, except for the diffusion of the largest screenshot categories.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:57, 12 May 2014 (UTC)

: As I might have said already, I'm ok with it and in particular I agree that images would be easier to find if in their own branch. The only thing, I think it's not going to last if the upload wizard doesn't enforce the use of a subcat of "Files", or at least, suggests that area in some handy way (i.e. not a written notice). Maybe the CategoryTree could be included (like with templates) to help finding the right category? It's hard to figure out a good one by typing characters one by one.
: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 21:49, 12 May 2014 (UTC)

:: Created the category pages as above, except for Category:Screenshots of ‎dialogues, which I found a bit ambiguous. I named that one Category:Screenshots of dialogues in FlightGear‎ instead.
:: I have also added a request at the [[User talk:BotFlightGear#FlightGear screenshot categories|bot talk page]] ([http://wiki.flightgear.org/index.php?title=User_talk:BotFlightGear&oldid=71130#FlightGear_screenshot_categories permalink])
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:59, 13 May 2014 (UTC)

::: Did the move to [[:Category:Screenshots of aircraft by type]] by hand. Was only a few files.
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:46, 13 May 2014 (UTC)

::: I hope I'm not late, I noticed only now, but ''dialogue'' tends to be used more as in "discussion between two", while the GUI elements are usually spelled ''dialogs''. I guess that more than real confusion this distinction would cause just minor hilarity, but... you never know, you might find in there screenshots of radio chat with ATC. (being not a native english speaker, [http://english.stackexchange.com/questions/59640/what-is-the-difference-between-dialogue-and-dialog here's my ref.]) --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 19:20, 13 May 2014 (UTC)

:::: Well spotted, good reference as well and most important not too late. Thank you! I was wondering a bit but guessed that dialog was more or less colloquial as dialogue seemed correct with both my browsers English and American English dictionaries. Swedish schools teaching (very!) British English probably have something to do with my spelling as well.
:::: Changed the request on the [[User talk:BotFlightGear#FlightGear screenshot categories|bot page]] from Category:Screenshots of dialogues in FlightGear‎ to [[:Category:Screenshots of dialogs in FlightGear‎]].
:::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:06, 14 May 2014 (UTC)

=== Having separate image categories or not? ===
One thing that keeps nagging me is that all Wikipedias I have been able to read and some I can hardly read (English, Swedish + German and French) have separate categories for files/images. There is probably a reason for that (I am guessing at mainly ease of finding images for articles and possibly also for bandwidth reasons).

The upload wizard is borrowed from Wikimedia Commons (but is it properly attributed?) where pretty much all categories are for files/images. While I am not aware of its technical details I see few if any efficient ways it could be modified to only or primarily suggest image categories. As I see it it would require a ''fresh and updated'' list of categories that in one way or another would require some manual intervention.

Two things I have done so far is to re-categorize images and that I have begun trying to link the nodes to the nodes in the branch with the article categories by putting the image categories in the article categories (this is done on a very small scale though).

Questions is though: What is in the best interest of the users? Should I keep on having them separate or should I just let it grow wild(er)? It could be an interesting experiment though it would require a lot of work if it turns out less favourable.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 22:02, 10 July 2014 (UTC)

:I saw you implementing this at some of my airport screen-shots and immediately adopted it on other images. I think your idea of separating those categories would help us puting a link at the end of each article which says: "Media about :XY". Thats why I think all the other wikis provide separated categories. That's the only way to get linkable categories which only contains media.

:--[[User:August|August]] ([[User talk:August|talk]]) 22:18, 10 July 2014 (UTC)

== Conventions on discussion conclusions ==
Sometimes proposals don't get the attention the proposer might have hoped for. Of course, everyone's involved in their projects, and following discussions in "recent changes" isn't easy, so nothing personal, my question is ''very practical''.

Sometimes these proposals need help from others (like my [[User_talk:Bigstones/Essay:A plan for a reorganization of the wiki#Bot proposal .28request.3F.29|"remove redundant categories"]]) so it's pretty clear that one will have to wait and retry/insist for that. Some other times though (like my above "Category:Support" topic - with which btw I did some mess moving messages around) one could easily continue on his/her own. In such cases, I feel that lack/loss of attention means "Ok, I don't mind if you do that, in case, we'll discuss the results" (like for the FAQ update - btw, thanks to the reviewers of [http://wiki.flightgear.org/index.php?title=Frequently_asked_questions&oldid=71015 my cuts]). If this is correct, I'd like to add it to the [[Help:Maintenance]] page, because it could help getting more things done and avoid misunderstandings. Oh, and by what I said, if I don't get answers, I'll take it for granted :D

--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 12:43, 13 May 2014 (UTC)

: I have found the lack of feedback to be discouraging at times, but at other times I have just went ahead and done things the way I would like to have them done, like for example my reorganisation and extension of the help pages, as well as adding the "[[FlightGear wiki:Village pump|Discuss!]]" link to the left side menu.

: I would guess that you draw the right conclusion with the statement that "Ok, I don't mind if you do that, in case, we'll discuss the results". The very most of the times that is the way to go. The good thing with a wiki is that it is so easy to revert a change (i.e "View history" tab → Go to topmost edit → Click the "undo" link). If if things go really wrong most things can be salvaged from the page history (though it can be a lot of work at times). ;-)

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:03, 13 May 2014 (UTC)

== Editing JavaScript files ? ==

: ''Moved here from [[Talk:Portal:Wiki#Editing JavaScript files ?]] ([http://wiki.flightgear.org/index.php?title=Talk:Portal:Wiki&oldid=72290 permalink]) since this might affect all users.''

I think, at some point, I saw someone editing JavaScript files here (Johan_G or Gijs probably) - what is involved to do that ? Any links/pointers ? Okay, found something at [[MediaWiki:Common.js]] Is it also possible to create custom JS/plain text files without any wiki markup ? Are my privileges even sufficient ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 21:11, 2 June 2014 (UTC)

: Nope, was not me. Javascript files is as far as I know currently limited to [[MediaWiki:Common.js]]. It is apparently possible to change some settings so that one can add "user javascript pages" (as well as "user Cascading Style Sheets"), see the WikiMedia Wiki pages [http://www.mediawiki.org/wiki/Manual:$wgAllowUserJs Manual:$wgAllowUserJs] (and [http://www.mediawiki.org/wiki/Manual:$wgAllowUserCss Manual:$wgAllowUserCss]).

: Both can be useful for testing stuff before including them in the "common" (i.e. site wide) files, as well as for personalizing the look, feel and functionality. I do not know what issues they could cause or if we have the permissions to change it. Maybe Simon and Gijs are the ones who can do it.

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 04:40, 3 June 2014 (UTC)

== MediaWiki updated to 1.23.0 ==

I've updated MediaWiki to the latest stable release (1.23.0) today. I'm now updating all extensions, so some things may be broken temporarily. Please report bugs if you find any. For a list of changes, see https://www.mediawiki.org/wiki/Release_notes/1.23

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:04, 8 June 2014 (UTC)

FlightGear wiki:Village pump

2014-07-10T22:18:18Z

August: /* Having separate image categories or not? */

{{Archives|[[/Archive 2012|2012]], [[/Archive 2013|2013]]}}
Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

: Please [{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics] to the '''bottom''' of this page.

: Old discussion should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.

----

== MediaWiki updated to 1.22.0 ==
I've updated MediaWiki to the latest stable, 1.22.0 today. Please report bugs if you find any. For a list of changes, see https://www.mediawiki.org/wiki/Release_notes/1.22

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:00, 26 December 2013 (UTC)

=== Found bugs ===
* Clicking the category link at the bottom of some articles will give a fatal error. For clicking the [[:Category:FlightGear]] at [[FlightGear]] will give the error message: ''Fatal error: Class 'Services_JSON' not found in /home/wiki/wiki/extensions/CategoryTree/CategoryTreeFunctions.php on line 224''.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 03:44, 28 December 2013 (UTC)
:: The CategoryTree extension relies on a function that was removed as of 1.22.0, so the extensions needs some fixing. I've disabled it for now.
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:01, 28 December 2013 (UTC)
::: Yay, CategoryTree is back. Thanks Gijs!
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:50, 6 May 2014 (UTC)

* Also, the mobile theme results in an error: ''Fatal error: Call to undefined method MobileFormatter::setHtmlMode() in /home/wiki/wiki/extensions/MobileFrontend/includes/MobileFormatter.php on line 62'' (works fine after selecting desktop mode).
: Thanks,
: [[User:Philosopher|—Philosopher]] ([[User talk:Philosopher|talk]]) 03:59, 28 December 2013 (UTC)
:: I forgot to update the mobile extension. Works again ;-)
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:01, 28 December 2013 (UTC)

* In the CategoryTree the FlightGear category [[:Category:Documentation|appears empty]]. The solution is reported at [[mw:Extension:CategoryTree#Member counts are wrong, gray arrows ► are shown instead of ►]]. It's a minor problem but the solution looks easy, for what I can tell.
: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 00:27, 11 May 2014 (UTC)

:: Unfortunately that doesn't seem to help...
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:11, 11 May 2014 (UTC)

== Got any ideas for a better name for this page? ==
As this is for this page in particular, see the [[FlightGear wiki talk:Village pump#Any ideas for a better name|talk page]].

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:44, 5 March 2014 (UTC)

== Template for announcement of changes and new features ==

From a forum PM from Hooray (posted here with his permission):

<div style="background: #fafaf0; padding: 1em;">
hi, whenever we announce a new feature, we typically need to do this in three places:

* newsletter
* changelog
* the docs (corresponding wiki articles)

so far, we have always copied & pasted things, I would prefer to have a single template for this instead, something like
{{tlx|Announce|version|description}}

This could add announcements to each release cycle (i.e. 3.2 currently), and we could maybe automatically add things to the newsletter and the release changelog.

Like I said, I would like to avoid redundant efforts, i.e. less copy & paste

Do you have any ideas on how to implement this using existing wiki means ?

Ideally, we would create a new announcement, like for example "canvas mouse button support", and could then use this announcement in all 3 places by calling the corresponding template.

Thanks
</div>
My take is that to use a separate template for each new feature is not a good idea, but if I understand him correctly his intention is to gather up each months new features in one template.

Any thoughts on this?

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:14, 5 March 2014 (UTC)

{{WIP}}

<pre style="white-space: pre-wrap; margin-left: 1.5em;">I am thinking of restructuring the way we're writing our newsletter by focusing on our "ugly stepchild", namely the "changelog" - as others like Torsten have pointed out, we should ideally be writing the changelog as early as possible - but the truth is, it's mostly forum people contributing to it, and it's not seen too many edits. The newsletter is working a bit better for us. So I was thinking of how to unify both worlds - especially keeping in mind that our changelog encompasses basically 6 months, i.e. 6 newsletter editions.

So I am considering to split up our newsletter into a handful of building blocks and use a few templates, so that additions are added through a few custom templates, that would automatically add things to the changelog.

The changelog would then be written by contributing to the newsletter and using the proper templates, such as e.g.:

{{changelog|version=3.2|category:aircraft|type=updated|announcement=The 747-400 and 777-200 have received extensive updates, and are now both using the new MapStructure-based NavDisplay framework|screenshots=|videos=}}

The changelog would then be procedurally assembled by processing all templates for the corresponding release cycle.

I would even consider locking the changelog itself, and making it just a template that references the stuff included via templates.

We may however benefit from a few additional mediawiki extensions. But otherwise, I am hoping that the changelog is going to be more comprehensive, while the wiki would become more "formal" - we could obviously still support additions without using changelog-templates, i.e. those would be excluded.

thoughts / ideas ?

(CC'ing Philosopher, because he's been doing some template stuff, too)</pre>

:Need to come up with a template that handles announcements, primarily for the changelog and the newsletter. There's a mutual relationship here, but the newsletter is much more popular, i.e. sees more contributions and more activity overall. Changelog writing is still a chore. But basically 6 months worth of newsletters are equivalent to a single changelog, we only need to establish some framework around this - and then the whole changelog could be mostly based on newsletter contributions. It would greatly help to request people to make announcements ALWAYS using 3rd person speech, so that things can be directly copied from the forum/devel list to the newsletter/changelog. That's kinda the idea here. It would reduce our workload quite significantly

:* Changelog
:* Newsletter
:* Devel List
:* Forum
:* Website

:{{unsigned|21:25, 24 April 2014‎|Hooray}}

::I will probably have to take a look at this now and again to think about if and how this could be done. I assume Hooray is aiming at having each newsletter and change log built up mostly from "instances" of a template like in the above comments.

::There are pros and cons with this approach, as with any. I think that one of the cons is that even the slightest overhead and/or complication might scare away a few contributors. But at the other hand I fully understand that reading through six months of newsletters + forum posts + devel list posts are not that fun either (though I would guess that is not how things are done ;-).

::''Slightly off topic'' is that I would like to see a section in the change log mentioning changes that will break backwards compatibility. I first saw such a section, "Breaking changes", in the [https://www.mediawiki.org/w/index.php?title=Release_notes/1.22&oldid=848518#MediaWiki_1.22.0 change log of MedeiaWiki 1.22] when the software of this wiki was updated, and figured it would be a good idea. This could be useful for things like for example figuring out whether FlightGear x.x can use World Scenery y.y.

::''Even more off topic'' I think that the wiki/newsletter/devel list/etc are rather blunt tools for keeping an up to date change log. My gut feeling is that there are tools for that around, and even if we do not use them we might borrow some ideas from them, hopefully without bringing a lot of red tape(!).

::—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 20:14, 27 April 2014 (UTC)

::: Interesting subject! I think going through just 6 newsletters by hand is more rewarding than coming up with complex templates that will increase the entry barrier of the newsletter and still require summarising/rewordings afterwards to fit the concise format of a changelog. Introducing a template on the wiki won't take away the forum/devel list scanning that's required as not everyone contributes to the wiki.
::: I do support the "breaking changes" idea though ;-)
::: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 19:18, 1 May 2014 (UTC)

== Very dispersed Boeing 777 articles! ==

Hi, I got interested in Flightgear and was taking a look at the Boeing 777 articles and noticed that it was incredibly spread out.

Each aircraft has it's own page with information to varying degrees of completeness. Having a look at the A330 articles, they are much more 'aligned' and it's a lot easier to find stuff. Maybe this could be something that could be done with the Boeing. Since both seem to be very similar, I'm thinking that there could be a common page on help and tutorials respectively, with the individual type pages catering to unique information. I started on some stuff but pretty quickly figured out it was a better idea to check here first :)

--[[User:Manfred|Manfred]] ([[User talk:Manfred|talk]]) 11:55, 25 March 2014 (UTC)

: Doing a simple search for pages containing "777" (see [http://wiki.flightgear.org/index.php?search=777&title=Special%3ASearch&fulltext=1 this link]) I quickly see what you mean.

: I assume that the different versions may have different authors and thus probably are slightly different from each other when it comes to handling and completeness. It might be a good idea to start by going through each of the help pages and tutorials (preferably while playing with the different aircraft at the same time), as well as having a look at help dialogues and any readmes in the aircraft packages.

: Making a common page, while highlighting differences between the different versions, could probably help other users a lot and may perhaps be a help for aircraft developers to use features from more complete versions to improve the other ones as well as help motivate harmonizing handling like for example key bindings.

: If I understand your intention I can not see why anyone would do anything but trying to give you helpful hints, after all this is a wiki. :-)

: One hint for starters is to begin working on a page as a subpage to your user page, like for example [[User:Manfred/Boeing 777 Autopilot]] (I just moved it) and then moving it to the article namespace when you feel it has reached the level where you are comfortable with it (though this is not by any means necessary, it's just that I like doing so myself).

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:40, 28 March 2014 (UTC)

: I am interested to help, this page could be a model of what we could offer : [http://wiki.flightgear.org/Boeing_787-8_Dreamliner 777-8 Dreamliner]
: -- [[User:F-JYL|F-JYL]] 21 April 2014 09:32

== Bash and DOS syntax highlighting ==

[[User:Daemonburrito|Daemonburrito]] found that we can use syntax highlighting for Bash. I guess that means that we could use syntax highlighting for most Linux (and possibly also Mac) command lines. Looking at [[mediawikiwiki:Extension:SyntaxHighlight_GeSHi]] I find that we also also probably can use that for DOS prompts.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:24, 5 May 2014 (UTC)

: We've had that extension installed for a while now. Everything that's listed at [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi#Supported_languages Supported languages] is supported, plus Nasal.
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:23, 5 May 2014 (UTC)

:: I'm aware of the list, but was not aware that syntax highlighting could be used for shell programming (and hence shell promts) and guessed I was not alone.
:: Basically added the topic to highlight (pun intended) the possibility to do so. I should probably also mention it in [[Help:Formatting#Syntax highlighting]].
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:53, 5 May 2014 (UTC)

== A plan for a reorganization of the wiki ==

There is an ongoing discussion on [[User:Bigstones/Essay:A plan for a reorganization of the wiki]]. Please comment on its talk page, to avoid scattering the discussion. This "section" is only intended to inform about it.
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 12:53, 7 May 2014 (UTC)

== The new progress bar icons ==

I just changed icons that {{tl|progressbar}} is using and would like some constructive feedback.

Some things I have noted myself is that while I used a blend of the colours used in the old icons and in some of [[Special:ListFiles/Johan_G|my other icons]], these icons have a much larger coloured area and thus might have a little high contrast.

In any way I am going to let this rest for a week or two and follow it up then.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 01:05, 10 May 2014 (UTC)

: After having made them a tiny pixel smaller (from 16 px to 15 px) and having done no other changes I seem to be liking them more and more, so I leave them in their current state.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:13, 24 May 2014 (UTC)

== Category:Support ==
As it seems that support organization is a priority, I created [[:Category:Support]]. I hope the name is generic enough to avoid misunderstandings... but I thought better to have a bad one, than nothing. I'll try to put there everything on support I find so that it can be better organized (merged/split and then cleaned up).
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:06, 11 May 2014 (UTC)

:Hi,
:
:I didn't read through all of your ideas yet, but isn't "Support" a rather obscure term? Everything could fit under that branch, so we'll end up with yet another giant category; which you tried to prevent, right? Or maybe I'm just missing the bigger picture...

:[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:23, 11 May 2014 (UTC)

:: Hi, I figured out (''edit: led to figure out'') that support organization is a major problem. There's a lot of "support" related articles, 2-3 articles only on OpenGL. I hoped that this name could indeed be wide enough, and that in case it could just be renamed. Troubleshooting seemed to narrow to me on the other side, but if you think that would be better I can change it now (waiting for response before proceeding).--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:29, 11 May 2014 (UTC)

::: Take [[Settings for slower graphics cards]] for example. It's categorised under [[:Category:Performance tuning]]. I would expect that to be a sub of [[:Category:Support]]. Anyone looking for articles on how to improve performance can check that category then. I don't expect anyone to go through a very broad category with 100s of articles to find info on a rather specific subject.
::: Or maybe I should reword my comment into a question: What would be the use case of [[:Category:Support]]?
::: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:39, 11 May 2014 (UTC)
::: PS: I know we have a lot of bloated categories on this wiki, so I'm glad you've brought all this back on the agenda ;-)

:::: With the example: I confess I was probably deceived by the presence of some development related stuff in [[:Category:Performance tuning]]. I thought it would be better to separate development and usage. Framerate is either a user issue, or a developer's aim. I think the two can be separated. The problem is I moved out the most of it! I should consider the contrary. I'll undo. (I currently have like 20 open browser tabs so it might take me some time).
:::: The use case however is: gather support articles so that a maintainer can split/merge them to make them more organized. Once that's done, there won't probably be more than 10 articles, and if there are, still one can subcategorize. In the above case, I just took the longest path, but given the lack of tools I confess I just wanted to get started.
:::: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 14:00, 11 May 2014 (UTC)
:::: ... I must confess also that after undoing, I feel the urge to redo that again. The two non-support related articles, [[GIT Performance Tests]] and [[Howto:Use the system monitor]] (where btw, the "profiling" section might be directed to ''core'' developers?) would have no place if I move this category into support. That's also why I moved it into Development. Let me know what you think, also regarding the Support category name.
:::: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 14:24, 11 May 2014 (UTC)

== FlightGear screenshot categories ==

I have been thinking about this for quite a while. When I was categorising the images, I gave the categories with the FlightGear screenshots quite cumbersome and long names.

I guess the discussions with Bigstones, in particular [http://wiki.flightgear.org/index.php?title=User_talk:Bigstones/Essay:A_plan_for_a_reorganization_of_the_wiki&diff=70678&oldid=70675 my reply here] (see second paragraph under 2.) might have stirred up some old dust for me. :-)

The cumbersome and long names has a couple negative effects. Firstly they are way longer to type than should be necessary, secondly, and more important I think, the probability that they show up in the upload wizard probably is rather low as they all begin with "FlightGear..." (what was I thinking, like if someone would upload a bunch of X-Plane screenshots here). I ''guess'' that by beginning most if not all screenshot category names with "Screenshots of..." the chances they would be used will increase.

In addition to that some of those categories are way too large and need to be diffused (broken down into smaller categories).

I have noted that a lot of aircraft images have been added to the aircraft article categories. I would prefer if the screenshot categories associated with different kinds of aircraft (e.g. fighters or airliners) would be subcategories to the screenshot categories ''and'' that those screenshot categories would be a subcategory to the category for those kinds of aircraft. I have at some point started to try mimic the structure of [[:Category:Aircraft by type]] in [[:Category:FlightGear screenshots of aircraft by type]], but got distracted or forgot about it for a while. Someting similar might be needed for the cockpit screenshots.

The note about intended contents should also mention that these categories are intended only for in-sim screenshots from FlightGear.

In conclusion I suggest, and would like feedback on, the following:

{| class="wikitable"
! Current category !! Suggested new category !! Alternative new category !! Comment
|-
| [[:Category:FlightGear cockpit screenshots‎]] || [[:Category:Screenshots of cockpits]] || Cockpit screenshots ||
|-
| [[:Category:FlightGear cockpit close-up screenshots‎]] || [[:Category:Screenshots of cockpit details]] || Cockpit close-up screenshots ||
|-
| [[:Category:FlightGear dialogue screenshots‎]]
| <s>Category:Screenshots of ‎dialogues</s>

[[:Category:Screenshots of dialogs in FlightGear‎]]
| <s>Dialogue</s> dialog box screenshots ||
|-
| [[:Category:FlightGear exterior screenshots]]‎ || [[:Category:Screenshots of aircraft]] || Exterior screenshots ||
|-
| [[:Category:FlightGear interior screenshots]] || [[:Category:Screenshots of cabins]] || Cabin screenshots ||
|-
| [[:Category:FlightGear scenery screenshots]]‎ || [[:Category:Screenshots of scenery]] || Scenery screenshots ||
|-
| Category:FlightGear screenshots of aircraft by type || [[:Category:Screenshots of aircraft by type]] || — || Should only contain categories
|-
| [[:Category:FlightGear screenshots of vehicles]] || [[:Category:Screenshots of vehicles]] || Vehicle screenshots ||
|-
| [[:Category:FlightGear weather screenshots]]‎ || [[:Category:Screenshots of weather]] || Weather screenshots ||
|}

In essence it is a huge bot job, except for the diffusion of the largest screenshot categories.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:57, 12 May 2014 (UTC)

: As I might have said already, I'm ok with it and in particular I agree that images would be easier to find if in their own branch. The only thing, I think it's not going to last if the upload wizard doesn't enforce the use of a subcat of "Files", or at least, suggests that area in some handy way (i.e. not a written notice). Maybe the CategoryTree could be included (like with templates) to help finding the right category? It's hard to figure out a good one by typing characters one by one.
: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 21:49, 12 May 2014 (UTC)

:: Created the category pages as above, except for Category:Screenshots of ‎dialogues, which I found a bit ambiguous. I named that one Category:Screenshots of dialogues in FlightGear‎ instead.
:: I have also added a request at the [[User talk:BotFlightGear#FlightGear screenshot categories|bot talk page]] ([http://wiki.flightgear.org/index.php?title=User_talk:BotFlightGear&oldid=71130#FlightGear_screenshot_categories permalink])
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:59, 13 May 2014 (UTC)

::: Did the move to [[:Category:Screenshots of aircraft by type]] by hand. Was only a few files.
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:46, 13 May 2014 (UTC)

::: I hope I'm not late, I noticed only now, but ''dialogue'' tends to be used more as in "discussion between two", while the GUI elements are usually spelled ''dialogs''. I guess that more than real confusion this distinction would cause just minor hilarity, but... you never know, you might find in there screenshots of radio chat with ATC. (being not a native english speaker, [http://english.stackexchange.com/questions/59640/what-is-the-difference-between-dialogue-and-dialog here's my ref.]) --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 19:20, 13 May 2014 (UTC)

:::: Well spotted, good reference as well and most important not too late. Thank you! I was wondering a bit but guessed that dialog was more or less colloquial as dialogue seemed correct with both my browsers English and American English dictionaries. Swedish schools teaching (very!) British English probably have something to do with my spelling as well.
:::: Changed the request on the [[User talk:BotFlightGear#FlightGear screenshot categories|bot page]] from Category:Screenshots of dialogues in FlightGear‎ to [[:Category:Screenshots of dialogs in FlightGear‎]].
:::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:06, 14 May 2014 (UTC)

=== Having separate image categories or not? ===
One thing that keeps nagging me is that all Wikipedias I have been able to read and some I can hardly read (English, Swedish + German and French) have separate categories for files/images. There is probably a reason for that (I am guessing at mainly ease of finding images for articles and possibly also for bandwidth reasons).

The upload wizard is borrowed from Wikimedia Commons (but is it properly attributed?) where pretty much all categories are for files/images. While I am not aware of its technical details I see few if any efficient ways it could be modified to only or primarily suggest image categories. As I see it it would require a ''fresh and updated'' list of categories that in one way or another would require some manual intervention.

Two things I have done so far is to re-categorize images and that I have begun trying to link the nodes to the nodes in the branch with the article categories by putting the image categories in the article categories (this is done on a very small scale though).

Questions is though: What is in the best interest of the users? Should I keep on having them separate or should I just let it grow wild(er)? It could be an interesting experiment though it would require a lot of work if it turns out less favourable.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 22:02, 10 July 2014 (UTC)

I saw you implementing this at some of my airport screen-shots and immediately adopted it on other images. I think your idea of separating those categories would help us puting a link at the end of each article which says: "Media about XY". Thats why I think all the other wikis provide separated categories. That's the only way to get linkable categories which only contains media.

--[[User:August|August]] ([[User talk:August|talk]]) 22:18, 10 July 2014 (UTC)

== Conventions on discussion conclusions ==
Sometimes proposals don't get the attention the proposer might have hoped for. Of course, everyone's involved in their projects, and following discussions in "recent changes" isn't easy, so nothing personal, my question is ''very practical''.

Sometimes these proposals need help from others (like my [[User_talk:Bigstones/Essay:A plan for a reorganization of the wiki#Bot proposal .28request.3F.29|"remove redundant categories"]]) so it's pretty clear that one will have to wait and retry/insist for that. Some other times though (like my above "Category:Support" topic - with which btw I did some mess moving messages around) one could easily continue on his/her own. In such cases, I feel that lack/loss of attention means "Ok, I don't mind if you do that, in case, we'll discuss the results" (like for the FAQ update - btw, thanks to the reviewers of [http://wiki.flightgear.org/index.php?title=Frequently_asked_questions&oldid=71015 my cuts]). If this is correct, I'd like to add it to the [[Help:Maintenance]] page, because it could help getting more things done and avoid misunderstandings. Oh, and by what I said, if I don't get answers, I'll take it for granted :D

--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 12:43, 13 May 2014 (UTC)

: I have found the lack of feedback to be discouraging at times, but at other times I have just went ahead and done things the way I would like to have them done, like for example my reorganisation and extension of the help pages, as well as adding the "[[FlightGear wiki:Village pump|Discuss!]]" link to the left side menu.

: I would guess that you draw the right conclusion with the statement that "Ok, I don't mind if you do that, in case, we'll discuss the results". The very most of the times that is the way to go. The good thing with a wiki is that it is so easy to revert a change (i.e "View history" tab → Go to topmost edit → Click the "undo" link). If if things go really wrong most things can be salvaged from the page history (though it can be a lot of work at times). ;-)

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:03, 13 May 2014 (UTC)

== Editing JavaScript files ? ==

: ''Moved here from [[Talk:Portal:Wiki#Editing JavaScript files ?]] ([http://wiki.flightgear.org/index.php?title=Talk:Portal:Wiki&oldid=72290 permalink]) since this might affect all users.''

I think, at some point, I saw someone editing JavaScript files here (Johan_G or Gijs probably) - what is involved to do that ? Any links/pointers ? Okay, found something at [[MediaWiki:Common.js]] Is it also possible to create custom JS/plain text files without any wiki markup ? Are my privileges even sufficient ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 21:11, 2 June 2014 (UTC)

: Nope, was not me. Javascript files is as far as I know currently limited to [[MediaWiki:Common.js]]. It is apparently possible to change some settings so that one can add "user javascript pages" (as well as "user Cascading Style Sheets"), see the WikiMedia Wiki pages [http://www.mediawiki.org/wiki/Manual:$wgAllowUserJs Manual:$wgAllowUserJs] (and [http://www.mediawiki.org/wiki/Manual:$wgAllowUserCss Manual:$wgAllowUserCss]).

: Both can be useful for testing stuff before including them in the "common" (i.e. site wide) files, as well as for personalizing the look, feel and functionality. I do not know what issues they could cause or if we have the permissions to change it. Maybe Simon and Gijs are the ones who can do it.

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 04:40, 3 June 2014 (UTC)

== MediaWiki updated to 1.23.0 ==

I've updated MediaWiki to the latest stable release (1.23.0) today. I'm now updating all extensions, so some things may be broken temporarily. Please report bugs if you find any. For a list of changes, see https://www.mediawiki.org/wiki/Release_notes/1.23

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:04, 8 June 2014 (UTC)

File:EDXW-terminal1.jpeg

2014-07-10T00:15:11Z

August:

=={{int:filedesc}}==
{{Information
|description={{en|1=Terminal at Flughafen Sylt - modelled by Thomas Polzer}}
|date=2012-09-21
|source={{own}}
|author=[[User:August|August]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-zero}}

[[Category:Screenshots of airports in Germany]]

File:EDDC APRON1.jpg

2014-07-10T00:14:02Z

August:

=={{int:filedesc}}==
{{Information
|description={{en|1=EDDC APRON 1}}
|date=2012-12-06
|source={{own}}
|author=[[User:Fgjosh|Fgjosh]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

[[Category:Screenshots of airports in Germany]]

File:EDDC2012.jpg

2014-07-10T00:12:59Z

August:

=={{int:filedesc}}==
{{Information
|description={{en|1=Dresden International Airport}}
|date=2012-12-06
|source={{own}}
|author=[[User:Fgjosh|Fgjosh]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

[[Category:Screenshots of airports in Germany]]

File:EDAC1.jpg

2014-07-10T00:12:03Z

August:

=={{int:filedesc}}==
{{Information
|description={{de|1=Leipzig-Altenburg Airport in TerraSync September 2012}}{{en|1=Leipzig-Altenburg Airport in TerraSync September 2012}}
|date=2012-09-19
|source={{own}}
|author=[[User:August|August]]
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{self|cc-zero}}

[[Category:Screenshots of airports in Germany]]

File:2014 new-layout-EDDP 01.jpg

2014-07-10T00:10:58Z

August:

=={{int:filedesc}}==
{{Information
|description={{en|1=Leipzig/Halle Airport, redesigned model 2014: Runway 26L with DHL-area}}
|date=2014-06-29 12:25:23
|source={{own}}
|author=[[User:August|August]]
|permission=
|other_versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

[[Category:Screenshots of airports in Germany]]

File:2014 new-layout-EDDP 02.jpg

2014-07-10T00:10:52Z

August:

=={{int:filedesc}}==
{{Information
|description={{en|1=Leipzig/Halle Airport, redesigned model 2014: Apron 4}}
|date=2014-06-29 12:25:33
|source={{own}}
|author=[[User:August|August]]
|permission=
|other_versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

[[Category:Screenshots of airports in Germany]]

File:2014 new-layout-EDDP 03.jpg

2014-07-10T00:10:21Z

August:

=={{int:filedesc}}==
{{Information
|description={{en|1=Leipzig/Halle Airport, redesigned model 2014 at night}}
|date=2014-06-29 12:25:45
|source={{own}}
|author=[[User:August|August]]
|permission=
|other_versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

[[Category:Screenshots of airports in Germany]]

File:2014 new-layout-EDDP 04.jpg

2014-07-10T00:09:45Z

August:

=={{int:filedesc}}==
{{Information
|description={{en|1=Leipzig/Halle Airport, redesigned model 2014: Taxiway T with DHL-area}}
|date=2014-06-29 12:25:57
|source={{own}}
|author=[[User:August|August]]
|permission=
|other_versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

[[Category:Screenshots of airports in Germany]]

File:2014 new-layout-EDDP 06.jpg

2014-07-10T00:09:05Z

August:

=={{int:filedesc}}==
{{Information
|description={{en|1=new layout of EDDP in 2014}}
|date=2014-07-07 18:10:13
|source={{own}}
|author=[[User:August|August]]
|permission=
|other_versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

[[Category:Screenshots of airports in Germany]]

File:2014 new-layout-EDDP 05.jpg

2014-07-10T00:08:33Z

August:

=={{int:filedesc}}==
{{Information
|description={{en|1=Leipzig/Halle Airport, redesigned model 2014: departing Extra500 from Runway 26L}}
|date=2014-06-29 12:26:04
|source={{own}}
|author=[[User:August|August]]
|permission=
|other_versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

[[Category:Screenshots of airports in Germany]]

Leipzig/Halle Airport

2014-07-07T16:35:34Z

August:

{{infobox Airport
|name = Leipzig/Halle Airport
|image =2014_new-layout-EDDP_07.jpg
|image2 =2014_new-layout-EDDP_02.jpg
|alt =New layout (development 2014)
|alt2 =DHL area (development 2014)
|iata =LEJ
|icao =EDDP
|type =Public
|city =Between Leipzig and Halle
|owner =Mitteldeutsche Airport Holding
|website =http://www.leipzig-halle-airport.de/
|scenerytile =e012n51
|download = http://wiki.flightgear.org/Leipzig/Halle_Airport#Download_via_GIT
|terrasync = published
|runway= 08L/26R
|length= 11,811 ft
|material= Concrete
|runway2= 08R/26L
|length2= 11,811 ft
|material2= Concrete
}}

'''Leipzig/Halle Airport''' is located in Schkeuditz, Saxony and serves both Leipzig, Saxony and Halle, Saxony-Anhalt, [[Germany]]. In Flightgear this airport was published on [[TerraSync|TerraSync]] in 2010 und updated due to new developments 2012. In 2014 according to the new world scenery a complete overhaul started.
EDDP is also the centre of Leipzig/Halle airspace, which provides air traffic control also for the regional airfield [[Leipzig-Altenburg Airport]].

{{Note|Users are asked to test the '''beta Version of the new 850-Layout''' (see [[#Download_via_GIT]])}}

== Flying at Leipzig/Halle airspace ==

=== Charts ===
All [http://www.vacc-sag.org/airport/EDDP diagrams and charts] are available for download.

=== Runways and ILS ===

==== Runway 08L/26R ====
[[File:2014 new-layout-EDDP 06.jpg|thumb|620px|Overview 2014 (reshaped layout under development)]]The northern [[runway]] is 3600m long with a width of 45m. In real life its usually used by passenger airliners. In Flightgear this runway is equipped with Outer Marker and Middle Marker and offers best conditions for '''low visibility operations'''.
* ILS-CAT-III '''08L''' (083°): 108.55
* ILS-CAT-III '''26R''' (263°): 108.35
==== Runway 08R/26L ====
The southern [[runway]] is 3600m long with a width of 60m. In real life its mostly used by freighters due to its proximity to freight areas (Apron 2 and 4). It has no Outer Marker an no Middle Marker.
* ILS-CAT-III '''08R''' (083°): 111.90 (111.75 in FG older than Version 2.0.0)
* ILS-CAT-III '''26L''' (263°): 110.30

=== ATC ===
* Leipzig Ground - frequency 121.800
* Leipzig Tower - frequency 121.100

Leipzig/Halle Airport is regularly served by Air Traffic Control ([[ATC]]).

== Infrastructure ==
Connected by terminal C and three taxiway bridges (W1, E7, E8) the airport layout combines the northern part with runway 08L/26L and Apron 3 (new cargo area since 2012) and the southern part with Apron 1 (terminal B), runway 08R/26L, Apron 2, Apron 4 (DHL), Apron 5. Between both parts an airport railway station and the autobahn A14 is connecting to the check-in area of terminal C. Railway and motorway are not modelled in Flightgear.

=== Access and connection ===
[[File:TerminalC-morning.jpg|thumb|270px|Terminal C at dawn (2012)]]
==== Terminal C ====
In August 2012 the completely new modelled terminal C was published on TerraSync. It is built as a connection between the check-in building with car-park and train station in the north and the departure area at terminal B in the south. Due to this efforts it stands on piers like a long bridge from apron 1 to apron 3, crossing different car-parks, a rail-track and the autobahn.
On the one hand the FlighGear model tries to give the airport a well designed model with highly detailed structures, but on the other hand it was programmed as simple as possible to save visitors simulation performance.

==== Taxiway bridges ====
[[File:EDDP-Taxibridges-e7e8-night.jpg|thumb|270px|Rampbridges E7, E8 with new lightning (2012)]]A highway and railway lines go straight between the two runways. Three bridges connect the terminal with the northern runway. The western bridge (taxiway W1) is used in both directions. The eastern bridges (taxiways E7 and E8) are used as one way taxiways. Due to safety improvements all bridges are equipped with special taxi lights.
Due to changes in the TerraData the bridges had to be repositioned in 2012.

=== Apron 1 ===

The main apron at Leipzig/Halle Airport is located in the middle of the airport. It houses the commercial aviation area at terminal B in the west and the general aviation area in the eastern part. It is connected by taxiways L, N and W1.

==== Terminal B ====
[[File:EDDP VDGS-134 thumbnail.jpg|thumb|270px|VDGS on each gateway at terminal B]]'''Real world''':
This building is the main terminal for most commercial flights at EDDP. It is connected to terminal C in the north and provides the passenger transfer to Apron 1 via 6 gateways. It also has a connection to the luggage terminal.

'''Scenery in TerraSync''':
In Flightgear the main terminal is modelled very slim and efficiently. 6 unmovable gateways link to park positions 126, 128, 130, 132, 134 and 136. In 2012 it will be improved. Since September 2012 it has been equipped with a non-animated [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System VDGS].

==== Luggage terminal ====
This building was first published in 2004 and remodelled by Thomas Großberger in 2012. The terminal is connected via the old tower next to it to terminal A by a tube, which is used to transport luggage between the checkin- and arrival-area and Apron 1. Both. the connection and the old tower building will be modelled in 2013. The new luggage terminal in FlightGear is offering:
* realistic roof design
* simplified but detailed interior
* 6 clock controlled automatic gates
* complex light design (Rembrandt-Design outstanding)

==== GAT ====

=== Apron 2 ===

=== Apron 3 ===
This Apron in real life went into service with a new cargo hangar in 2012. In Flightgear it is still closed. The corresponding facilities are still under development.

=== Apron 4/5 (DHL-area) ===
[[File:2014 new-layout-EDDP 01.jpg|thumb|620px|Apron 4 and runway 26L at night (2014)]]'''Real world:''' Leipzig/Halle is just a small international airport. But in 2008 it became the [http://www.dp-dhl.com/en/logistics_around_us/from_our_divisions/leipzig_hub.html European DHL hub] with up to 60 planes per night. The DHL Hub Leipzig GmbH, place of business in Schkeuditz, is running under contract to the logistic group DHL at Leipzig/Halle Airport one of six international aviation hubs. In order to provide maintenance to the new fleet the [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig GmbH] was founded. European Air Transport operates services to Europe, Middle East and Africa. 56 countries are covered in total. A second aviation company, called [http://en.wikipedia.org/wiki/Aerologic AeroLogic], was founded in EDDP. AeroLogic GmbH, a joint-venture between DHL Express and Lufthansa Cargo, is a German cargo airline headquartered in Schkeuditz, Saxony. It operates cargo flights out of Leipzig/Halle Airport and Frankfurt, most of which are on behalf of its parent companies.

{| class="wikitable" cellpadding="3" style="margin-left:auto; margin-right:auto"
|+ '''Fleet of [http://en.wikipedia.org/wiki/Aerologic AeroLogic] and [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig] and others''' (2012)
|-
!Aircraft
!Total
!Orders
!Oparator
|-
|[[Airbus A300|Airbus A300B4-203F]]
|<center>10</center>
|
|Air Contractors
|-
|[[Airbus A300|Airbus A300-600RF]]
|<center>8</center>
|<center>10</center>
|European Air Transport Leipzig
|-
|Boeing 737-300F
|<center>9</center>
|
|European Air Transport Leipzig
|-
|Boeing 737-400F
|<center>1</center>
|
|Europe Airpost
|-
|[[Boeing 757|Boeing 757-236SF]]
|<center>10</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 757|Boeing 757-23APF]]
|<center>1</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 777F]]
|<center>8</center>
|
|AeroLogic
|-
!Total
!47
!10
!colspan=2|
|}

[[File:EDDP-DHL-tank.jpeg|thumb|270px|DHL-Tank at fuel storage area on apron 4]]'''Scenery in TerraSync:''' The hub (warehouse, hangar and aprons) is modelled in the scenery. In 2012 its redesign for TerraSync started. First all lampposts at apron 4 had been replaced with those which fit into the correct layout of every single parking position. Afterwards lots of goods and ground vehicles where placed. As soon as some missing storage buildings are modelled, the new content of apron 4 will be published on TerraSync. Last modifications will take place when the new [[Airport data (apt.dat) update|850-standard layout]] of EDDP will be created in the future.

'''DHL-hub at EDDP in Flightgear:''' Leipzig/Halle Airport offers ground space for more than 70 Boeing [[757-200|757-PF]] or up to 50 [[777F]] as well as space for 10 [[Antonov An-124|An-124]] at Apron 2, 4 and 5. Airmail flights can be flown from and to EDDP. One of the middle sized and highly connected hubs of DHL, the [[Orio al Serio Airport]] (Italy) is also modelled in FlightGear and can be used for realistic flights out of Leipzig/Halle Airport.
In FlighGear apron 4 is equipped with all stands. Additionally to the main apron lightning each stand has one centred lamppost, which will be replaced by a VDGS-signs in the future. Ground markings will come with the new 850-layout. The major storage buildings from DHL are modelled as well as three DHL-tanks south from apron 4.

=== De-icing areas ===
Leipzig/Halle Airport has four special areas, two in the north at taxiway C and two in the south at taxiway N. In FlightGear only the two areas at taxiway C are build into the layout. In 2012 both areas had been equipped with shared models like lampposts, buildings and ground lights.

==== De-icing area 2 - multiplayer ready ====

Based on the Zurich type model "Elephant" - originally modelled by Oliver Thurau - an improved version with full multiplayer support is under development. This version isn't only adapted to the special efforts at EDDP, but its also designed to be controlled by ATC. It will be published via TerraSync in November 2014.

== Surroundings and "Other" ==

=== Kursdorf - the village within the airport ===
There is a village right in middle of the airport. So it's no surprise the number of inhabitants is shrinking each year. Once a thriving village with 537 inhabitants in 1950, they were down to 119 in 2006 [http://de.wikipedia.org/wiki/Kursdorf_%28Schkeuditz%29 (Wikipedia)]. It might be a little loud with the two runways, highway and express railways, but the transport links, hey ... The village is modelled in the scenery.

== Scenery ==
{|
| Authors: ||
* Models: David G., D-STHO
* Airport layout: Christian Schmitt
* Additional models: Don Lavelle, Alex Park, Robert Shearman
* Redesigning & Development 2012: [[User:August|August]], D-STHO
|-
|}

=== Download via GIT ===
With FlightGear 3.0 a new world scenery was published, including a new but incorrect 850-layout for EDDP. Developers started a huge overhaul of the EDDP scenery in April 2014. First a new taxiway layout was programmed. Additionally all buildings and objects are replaced. Some models will be remodelled, others will be added. Due to the fact that airport layouts can't be simply updated via TerraSync in a short way, pilots are asked to use the new EDDP CUSTOM SCENERY as long as things aren't updated at TerraSync.

* Download-Development-Scenery
* updated regularly
** '''git clone''' [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/ https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/]
** or [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/archive/5a25c94d403f09e5b5bf4d72117e297191acb3ce.tar.gz download a ZIP] (101 MB)

=== Download via TerraSync ===
[[TerraSync]] has it all! There is no custom scenery existing (only the GIT-repository for testing the new 850-layout before publishing it). The authors believe on the advantages of TerraSync which makes it easy for every user to have the latest scenery installed automatically. Updates are published regularly via TerraSync.
* Next update in '''<daysuntil in="days">12-August-2014</daysuntil>''' {{Progressbar|height=45|percentage={{#expr: trunc ({{#time: z}} - {{#time: z | May 19 2014 }}) round -1 }}}}

* '''Latest update on TerraSync:'''
** '''2014-04-29''' ''Objects adapted to new (but incorrect) 850-layout''

* Last five updates:
** '''2013-04-21''' ''Rembrandt lights at apron 1''
** 2013-02-13 ''new Messeturm at final approach area of runway 26R''
** 2012-12-21 ''new luggage terminal at apron 1''
** 2012-10-22 ''three new DHL-tanks placed at DHL-area''
** 2012-09-20 ''new VisualGuidingDockingSystem at terminal B''

=== Development ===
Since the Scenery had been modelled by [[User:D-79|D-79]] in 2010, D-STHO and [[User:August|August]] started enhancements and redesigning in 2012. In 2014 development of a new 850-layout started. Improvements are made on the following objects:

'''Layout''' 
* Taxiway bridges: new Position, improved lightning ''(published 07/2012)'' {{tick}}
* New 850-standard: new Layout with all parking positions and improved taxiways {{progressbar|90}} (see [[#Download_via_GIT]])

'''Scenery (Shared Models)''' 
* Airport lightning: more than 80 lampposts ([[EDDM]]-model) on Apron 1 and 4 and both northern de-icing areas ''(published 07/2012)'' {{tick}}
* DHL-tanks at apron 4 ''(published 10/2012)'' {{tick}}
* Ground traffic: lots of goods and vehicles (shared) make apron 1 and 4 much more realistic ''(published 08/2012)'' {{tick}}
* Flora and boundaries: Trees and fences on Apron 1, 2 and 4 are added ''(published 08/2012)'' {{tick}}
* New shared ground vehicles
** Container dolly ''(under development)'' {{hourglass}}
** Luggage dolly ''(under development)'' {{hourglass}}
** Pallet dolly ''(planned)''
* New shared Unit Load Devices (ULD)
** Airfreight container - Type AKH ''(pre-development)'' {{hourglass}}
** Airfreight pallet ''(planed)''
* Village and industrial surroundings: Kursdorf within the airport and industrial areas around are created with shared models ''(published 04/2010)'' {{tick}}

'''Buildings and infrastructure (Static models)''' 
* Cargo-hangar apron 3 ''(planned)''
* Cargo-center apron 2 ''(published 2010)'' {{tick}}
* DHL-hangar ''(published 2010)'' {{tick}}
* DHL-terminal ''(published 2010)'' {{tick}}
* Interactive DE-ICING areas (Multiplayer supported) {{hourglass}}
* Interactive luggage dolly traffic between terminal B and lugage terminal ''(planned)''
* Luggage terminal ''(published 12/2012)'' {{tick}}
* Storage buildings at DHL-area ''(pre-development)'' {{hourglass}}
* Terminal B ''(published 04/2010)'' {{tick}}
* Terminal C ''(published 08/2012)'' {{tick}}
* Tower ''(published 2010)'' {{tick}}
* Turbo engine hall ''(pre-development)'' {{hourglass}}
* Old Tower next to terminal B ''(pre-development)'' {{hourglass}}
* Visual Docking Guiding System at Apron 4 ''(planned)''
* Visual Docking Guiding System at Terminal B ''(published 09/2012)'' {{tick}}
* Visual Docking Guiding System: replacement with animated interactive version ''(planned)''
'''Rembrandt lightning improvements'''
* Converting Lightning to [[Project Rembrandt|Rembrandt]]
** Rembrandt lights at apron 1 ''(published 04/2013)'' {{tick}}
** Rembrandt lights at apron 2 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 3 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 4 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 5 {{progressbar|90}} (see [[#Download_via_GIT]])
* Converting Buildings to [[Project Rembrandt|Rembrandt]] Lightning
** Luggage terminal ''(pre-development)'' {{hourglass}}
** Terminal B ''(planned)''
** Terminal C ''(planned)''
** Tower ''(planned)''
** DHL-hangar ''(planned)''
* Lampposts in EDDP-style ''(planned)''

'''Buildings at the city of Leipzig (Static models)''' 
* City-Hochhaus {{progressbar|90}}
* Wintergartenhochhaus ''(published 02/2013)'' {{tick}}
* Völkerschlachtdenkmal (Battle of Nations Monument) {{hourglass}}
* Red-Bull Arena {{hourglass}}
* Gondwanaland (tropical zoo) ''(published 02/2013)'' {{tick}}
* DVB-T-Tower ''(published 02/2013)'' {{tick}}
* Messeturm Leipzig ''(published 02/2013)'' {{tick}}
* Hauptbahnhof (Central Station) ''(planned)''

=== Scenery since 2014 ===
<gallery mode=packed widths=180px heights=180px>
2014 new-layout-EDDP 04.jpg|Redesigned Layout: Taxiway T - new ground textures
2014 new-layout-EDDP 01.jpg|Redesigned Layout: Runway 26L with DHL-area
2014 new-layout-EDDP 02.jpg|Redesigned Layout: Apron 4
</gallery>

=== Scenery since 2012 ===
[[File:EDDP TerminalC.jpeg|Terminal C]] [[File:EDDP VDGS-136 thumbnail.jpg|VDGS at position 136]] [[File:EDDP-DHL-tank.jpeg|DHL-Tank at fuel storage area on apron 4]] [[File:EDDP_luggageterminal_thumb.jpg|Luggage Terminal at Apron 1]]

=== Scenery since 2010 ===
Here is a selection of the models. [http://www.youtube.com/watch?v=3kNDGiSNUdE YouTube video 2010].

[[File:EDDP10.jpg]] [[File:EDDP11.jpg]] [[File:EDDP12.jpg]] [[File:EDDP13.jpg]] [[File:EDDPbridge1.png]]

== Related content ==
* [[Germany]]
* [[Leipzig/Halle Airspace]]

== External links ==
* [http://www.vacc-sag.org/airport/EDDP Airport Diagrams]
* [http://de.wikipedia.org/wiki/EDDP Leipzig/Halle Airport at Wikipedia] (German)

[[Category:Airports in Germany]]

Leipzig/Halle Airport

2014-07-07T16:33:53Z

August: Infobox and pictures update

{{infobox Airport
|name = Leipzig/Halle Airport
|image =2014_new-layout-EDDP_07.jpg
|image2 =2014_new-layout-EDDP_02.jpg
|alt =New layout (development 2014)
|alt2 =DHL area (development 2014)
|iata =LEJ
|icao =EDDP
|type =Public
|city =Between Leipzig and Halle
|owner =Mitteldeutsche Airport Holding
|website =http://www.leipzig-halle-airport.de/
|scenerytile =e012n51
|download = http://wiki.flightgear.org/index.php?title=Leipzig/Halle_Airport&action=submit#Download_via_GIT
|terrasync = published
|runway= 08L/26R
|length= 11,811 ft
|material= Concrete
|runway2= 08R/26L
|length2= 11,811 ft
|material2= Concrete
}}

'''Leipzig/Halle Airport''' is located in Schkeuditz, Saxony and serves both Leipzig, Saxony and Halle, Saxony-Anhalt, [[Germany]]. In Flightgear this airport was published on [[TerraSync|TerraSync]] in 2010 und updated due to new developments 2012. In 2014 according to the new world scenery a complete overhaul started.
EDDP is also the centre of Leipzig/Halle airspace, which provides air traffic control also for the regional airfield [[Leipzig-Altenburg Airport]].

{{Note|Users are asked to test the '''beta Version of the new 850-Layout''' (see [[#Download_via_GIT]])}}

== Flying at Leipzig/Halle airspace ==

=== Charts ===
All [http://www.vacc-sag.org/airport/EDDP diagrams and charts] are available for download.

=== Runways and ILS ===

==== Runway 08L/26R ====
[[File:2014 new-layout-EDDP 06.jpg|thumb|620px|Overview 2014 (reshaped layout under development)]]The northern [[runway]] is 3600m long with a width of 45m. In real life its usually used by passenger airliners. In Flightgear this runway is equipped with Outer Marker and Middle Marker and offers best conditions for '''low visibility operations'''.
* ILS-CAT-III '''08L''' (083°): 108.55
* ILS-CAT-III '''26R''' (263°): 108.35
==== Runway 08R/26L ====
The southern [[runway]] is 3600m long with a width of 60m. In real life its mostly used by freighters due to its proximity to freight areas (Apron 2 and 4). It has no Outer Marker an no Middle Marker.
* ILS-CAT-III '''08R''' (083°): 111.90 (111.75 in FG older than Version 2.0.0)
* ILS-CAT-III '''26L''' (263°): 110.30

=== ATC ===
* Leipzig Ground - frequency 121.800
* Leipzig Tower - frequency 121.100

Leipzig/Halle Airport is regularly served by Air Traffic Control ([[ATC]]).

== Infrastructure ==
Connected by terminal C and three taxiway bridges (W1, E7, E8) the airport layout combines the northern part with runway 08L/26L and Apron 3 (new cargo area since 2012) and the southern part with Apron 1 (terminal B), runway 08R/26L, Apron 2, Apron 4 (DHL), Apron 5. Between both parts an airport railway station and the autobahn A14 is connecting to the check-in area of terminal C. Railway and motorway are not modelled in Flightgear.

=== Access and connection ===
[[File:TerminalC-morning.jpg|thumb|270px|Terminal C at dawn (2012)]]
==== Terminal C ====
In August 2012 the completely new modelled terminal C was published on TerraSync. It is built as a connection between the check-in building with car-park and train station in the north and the departure area at terminal B in the south. Due to this efforts it stands on piers like a long bridge from apron 1 to apron 3, crossing different car-parks, a rail-track and the autobahn.
On the one hand the FlighGear model tries to give the airport a well designed model with highly detailed structures, but on the other hand it was programmed as simple as possible to save visitors simulation performance.

==== Taxiway bridges ====
[[File:EDDP-Taxibridges-e7e8-night.jpg|thumb|270px|Rampbridges E7, E8 with new lightning (2012)]]A highway and railway lines go straight between the two runways. Three bridges connect the terminal with the northern runway. The western bridge (taxiway W1) is used in both directions. The eastern bridges (taxiways E7 and E8) are used as one way taxiways. Due to safety improvements all bridges are equipped with special taxi lights.
Due to changes in the TerraData the bridges had to be repositioned in 2012.

=== Apron 1 ===

The main apron at Leipzig/Halle Airport is located in the middle of the airport. It houses the commercial aviation area at terminal B in the west and the general aviation area in the eastern part. It is connected by taxiways L, N and W1.

==== Terminal B ====
[[File:EDDP VDGS-134 thumbnail.jpg|thumb|270px|VDGS on each gateway at terminal B]]'''Real world''':
This building is the main terminal for most commercial flights at EDDP. It is connected to terminal C in the north and provides the passenger transfer to Apron 1 via 6 gateways. It also has a connection to the luggage terminal.

'''Scenery in TerraSync''':
In Flightgear the main terminal is modelled very slim and efficiently. 6 unmovable gateways link to park positions 126, 128, 130, 132, 134 and 136. In 2012 it will be improved. Since September 2012 it has been equipped with a non-animated [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System VDGS].

==== Luggage terminal ====
This building was first published in 2004 and remodelled by Thomas Großberger in 2012. The terminal is connected via the old tower next to it to terminal A by a tube, which is used to transport luggage between the checkin- and arrival-area and Apron 1. Both. the connection and the old tower building will be modelled in 2013. The new luggage terminal in FlightGear is offering:
* realistic roof design
* simplified but detailed interior
* 6 clock controlled automatic gates
* complex light design (Rembrandt-Design outstanding)

==== GAT ====

=== Apron 2 ===

=== Apron 3 ===
This Apron in real life went into service with a new cargo hangar in 2012. In Flightgear it is still closed. The corresponding facilities are still under development.

=== Apron 4/5 (DHL-area) ===
[[File:2014 new-layout-EDDP 01.jpg|thumb|620px|Apron 4 and runway 26L at night (2014)]]'''Real world:''' Leipzig/Halle is just a small international airport. But in 2008 it became the [http://www.dp-dhl.com/en/logistics_around_us/from_our_divisions/leipzig_hub.html European DHL hub] with up to 60 planes per night. The DHL Hub Leipzig GmbH, place of business in Schkeuditz, is running under contract to the logistic group DHL at Leipzig/Halle Airport one of six international aviation hubs. In order to provide maintenance to the new fleet the [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig GmbH] was founded. European Air Transport operates services to Europe, Middle East and Africa. 56 countries are covered in total. A second aviation company, called [http://en.wikipedia.org/wiki/Aerologic AeroLogic], was founded in EDDP. AeroLogic GmbH, a joint-venture between DHL Express and Lufthansa Cargo, is a German cargo airline headquartered in Schkeuditz, Saxony. It operates cargo flights out of Leipzig/Halle Airport and Frankfurt, most of which are on behalf of its parent companies.

{| class="wikitable" cellpadding="3" style="margin-left:auto; margin-right:auto"
|+ '''Fleet of [http://en.wikipedia.org/wiki/Aerologic AeroLogic] and [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig] and others''' (2012)
|-
!Aircraft
!Total
!Orders
!Oparator
|-
|[[Airbus A300|Airbus A300B4-203F]]
|<center>10</center>
|
|Air Contractors
|-
|[[Airbus A300|Airbus A300-600RF]]
|<center>8</center>
|<center>10</center>
|European Air Transport Leipzig
|-
|Boeing 737-300F
|<center>9</center>
|
|European Air Transport Leipzig
|-
|Boeing 737-400F
|<center>1</center>
|
|Europe Airpost
|-
|[[Boeing 757|Boeing 757-236SF]]
|<center>10</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 757|Boeing 757-23APF]]
|<center>1</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 777F]]
|<center>8</center>
|
|AeroLogic
|-
!Total
!47
!10
!colspan=2|
|}

[[File:EDDP-DHL-tank.jpeg|thumb|270px|DHL-Tank at fuel storage area on apron 4]]'''Scenery in TerraSync:''' The hub (warehouse, hangar and aprons) is modelled in the scenery. In 2012 its redesign for TerraSync started. First all lampposts at apron 4 had been replaced with those which fit into the correct layout of every single parking position. Afterwards lots of goods and ground vehicles where placed. As soon as some missing storage buildings are modelled, the new content of apron 4 will be published on TerraSync. Last modifications will take place when the new [[Airport data (apt.dat) update|850-standard layout]] of EDDP will be created in the future.

'''DHL-hub at EDDP in Flightgear:''' Leipzig/Halle Airport offers ground space for more than 70 Boeing [[757-200|757-PF]] or up to 50 [[777F]] as well as space for 10 [[Antonov An-124|An-124]] at Apron 2, 4 and 5. Airmail flights can be flown from and to EDDP. One of the middle sized and highly connected hubs of DHL, the [[Orio al Serio Airport]] (Italy) is also modelled in FlightGear and can be used for realistic flights out of Leipzig/Halle Airport.
In FlighGear apron 4 is equipped with all stands. Additionally to the main apron lightning each stand has one centred lamppost, which will be replaced by a VDGS-signs in the future. Ground markings will come with the new 850-layout. The major storage buildings from DHL are modelled as well as three DHL-tanks south from apron 4.

=== De-icing areas ===
Leipzig/Halle Airport has four special areas, two in the north at taxiway C and two in the south at taxiway N. In FlightGear only the two areas at taxiway C are build into the layout. In 2012 both areas had been equipped with shared models like lampposts, buildings and ground lights.

==== De-icing area 2 - multiplayer ready ====

Based on the Zurich type model "Elephant" - originally modelled by Oliver Thurau - an improved version with full multiplayer support is under development. This version isn't only adapted to the special efforts at EDDP, but its also designed to be controlled by ATC. It will be published via TerraSync in November 2014.

== Surroundings and "Other" ==

=== Kursdorf - the village within the airport ===
There is a village right in middle of the airport. So it's no surprise the number of inhabitants is shrinking each year. Once a thriving village with 537 inhabitants in 1950, they were down to 119 in 2006 [http://de.wikipedia.org/wiki/Kursdorf_%28Schkeuditz%29 (Wikipedia)]. It might be a little loud with the two runways, highway and express railways, but the transport links, hey ... The village is modelled in the scenery.

== Scenery ==
{|
| Authors: ||
* Models: David G., D-STHO
* Airport layout: Christian Schmitt
* Additional models: Don Lavelle, Alex Park, Robert Shearman
* Redesigning & Development 2012: [[User:August|August]], D-STHO
|-
|}

=== Download via GIT ===
With FlightGear 3.0 a new world scenery was published, including a new but incorrect 850-layout for EDDP. Developers started a huge overhaul of the EDDP scenery in April 2014. First a new taxiway layout was programmed. Additionally all buildings and objects are replaced. Some models will be remodelled, others will be added. Due to the fact that airport layouts can't be simply updated via TerraSync in a short way, pilots are asked to use the new EDDP CUSTOM SCENERY as long as things aren't updated at TerraSync.

* Download-Development-Scenery
* updated regularly
** '''git clone''' [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/ https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/]
** or [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/archive/5a25c94d403f09e5b5bf4d72117e297191acb3ce.tar.gz download a ZIP] (101 MB)

=== Download via TerraSync ===
[[TerraSync]] has it all! There is no custom scenery existing (only the GIT-repository for testing the new 850-layout before publishing it). The authors believe on the advantages of TerraSync which makes it easy for every user to have the latest scenery installed automatically. Updates are published regularly via TerraSync.
* Next update in '''<daysuntil in="days">12-August-2014</daysuntil>''' {{Progressbar|height=45|percentage={{#expr: trunc ({{#time: z}} - {{#time: z | May 19 2014 }}) round -1 }}}}

* '''Latest update on TerraSync:'''
** '''2014-04-29''' ''Objects adapted to new (but incorrect) 850-layout''

* Last five updates:
** '''2013-04-21''' ''Rembrandt lights at apron 1''
** 2013-02-13 ''new Messeturm at final approach area of runway 26R''
** 2012-12-21 ''new luggage terminal at apron 1''
** 2012-10-22 ''three new DHL-tanks placed at DHL-area''
** 2012-09-20 ''new VisualGuidingDockingSystem at terminal B''

=== Development ===
Since the Scenery had been modelled by [[User:D-79|D-79]] in 2010, D-STHO and [[User:August|August]] started enhancements and redesigning in 2012. In 2014 development of a new 850-layout started. Improvements are made on the following objects:

'''Layout''' 
* Taxiway bridges: new Position, improved lightning ''(published 07/2012)'' {{tick}}
* New 850-standard: new Layout with all parking positions and improved taxiways {{progressbar|90}} (see [[#Download_via_GIT]])

'''Scenery (Shared Models)''' 
* Airport lightning: more than 80 lampposts ([[EDDM]]-model) on Apron 1 and 4 and both northern de-icing areas ''(published 07/2012)'' {{tick}}
* DHL-tanks at apron 4 ''(published 10/2012)'' {{tick}}
* Ground traffic: lots of goods and vehicles (shared) make apron 1 and 4 much more realistic ''(published 08/2012)'' {{tick}}
* Flora and boundaries: Trees and fences on Apron 1, 2 and 4 are added ''(published 08/2012)'' {{tick}}
* New shared ground vehicles
** Container dolly ''(under development)'' {{hourglass}}
** Luggage dolly ''(under development)'' {{hourglass}}
** Pallet dolly ''(planned)''
* New shared Unit Load Devices (ULD)
** Airfreight container - Type AKH ''(pre-development)'' {{hourglass}}
** Airfreight pallet ''(planed)''
* Village and industrial surroundings: Kursdorf within the airport and industrial areas around are created with shared models ''(published 04/2010)'' {{tick}}

'''Buildings and infrastructure (Static models)''' 
* Cargo-hangar apron 3 ''(planned)''
* Cargo-center apron 2 ''(published 2010)'' {{tick}}
* DHL-hangar ''(published 2010)'' {{tick}}
* DHL-terminal ''(published 2010)'' {{tick}}
* Interactive DE-ICING areas (Multiplayer supported) {{hourglass}}
* Interactive luggage dolly traffic between terminal B and lugage terminal ''(planned)''
* Luggage terminal ''(published 12/2012)'' {{tick}}
* Storage buildings at DHL-area ''(pre-development)'' {{hourglass}}
* Terminal B ''(published 04/2010)'' {{tick}}
* Terminal C ''(published 08/2012)'' {{tick}}
* Tower ''(published 2010)'' {{tick}}
* Turbo engine hall ''(pre-development)'' {{hourglass}}
* Old Tower next to terminal B ''(pre-development)'' {{hourglass}}
* Visual Docking Guiding System at Apron 4 ''(planned)''
* Visual Docking Guiding System at Terminal B ''(published 09/2012)'' {{tick}}
* Visual Docking Guiding System: replacement with animated interactive version ''(planned)''
'''Rembrandt lightning improvements'''
* Converting Lightning to [[Project Rembrandt|Rembrandt]]
** Rembrandt lights at apron 1 ''(published 04/2013)'' {{tick}}
** Rembrandt lights at apron 2 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 3 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 4 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 5 {{progressbar|90}} (see [[#Download_via_GIT]])
* Converting Buildings to [[Project Rembrandt|Rembrandt]] Lightning
** Luggage terminal ''(pre-development)'' {{hourglass}}
** Terminal B ''(planned)''
** Terminal C ''(planned)''
** Tower ''(planned)''
** DHL-hangar ''(planned)''
* Lampposts in EDDP-style ''(planned)''

'''Buildings at the city of Leipzig (Static models)''' 
* City-Hochhaus {{progressbar|90}}
* Wintergartenhochhaus ''(published 02/2013)'' {{tick}}
* Völkerschlachtdenkmal (Battle of Nations Monument) {{hourglass}}
* Red-Bull Arena {{hourglass}}
* Gondwanaland (tropical zoo) ''(published 02/2013)'' {{tick}}
* DVB-T-Tower ''(published 02/2013)'' {{tick}}
* Messeturm Leipzig ''(published 02/2013)'' {{tick}}
* Hauptbahnhof (Central Station) ''(planned)''

=== Scenery since 2014 ===
<gallery mode=packed widths=180px heights=180px>
2014 new-layout-EDDP 04.jpg|Redesigned Layout: Taxiway T - new ground textures
2014 new-layout-EDDP 01.jpg|Redesigned Layout: Runway 26L with DHL-area
2014 new-layout-EDDP 02.jpg|Redesigned Layout: Apron 4
</gallery>

=== Scenery since 2012 ===
[[File:EDDP TerminalC.jpeg|Terminal C]] [[File:EDDP VDGS-136 thumbnail.jpg|VDGS at position 136]] [[File:EDDP-DHL-tank.jpeg|DHL-Tank at fuel storage area on apron 4]] [[File:EDDP_luggageterminal_thumb.jpg|Luggage Terminal at Apron 1]]

=== Scenery since 2010 ===
Here is a selection of the models. [http://www.youtube.com/watch?v=3kNDGiSNUdE YouTube video 2010].

[[File:EDDP10.jpg]] [[File:EDDP11.jpg]] [[File:EDDP12.jpg]] [[File:EDDP13.jpg]] [[File:EDDPbridge1.png]]

== Related content ==
* [[Germany]]
* [[Leipzig/Halle Airspace]]

== External links ==
* [http://www.vacc-sag.org/airport/EDDP Airport Diagrams]
* [http://de.wikipedia.org/wiki/EDDP Leipzig/Halle Airport at Wikipedia] (German)

[[Category:Airports in Germany]]

File:2014 new-layout-EDDP 07.jpg

2014-07-07T16:12:11Z

August: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=new layout of EDDP in 2014}}
|date=2014-07-07 18:10:17
|source={{own}}
|author=[[User:August|August]]
|permission=
|other_versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

[[Category:Airports in Germany]]

File:2014 new-layout-EDDP 06.jpg

2014-07-07T16:12:00Z

August: User created page with UploadWizard

ATC best practices

2014-07-02T20:57:25Z

August: /* Additional best practices */ Linking to relevant airport wiki pages

In case you decide to fly into an area controlled by [[Air Traffic Control]], please read these guidelines. Even though the FlightGear multiplayer experience is not by any means a formal environment, you should still follow them to make the experience enjoyable by everyone.

== How do I know if the area is controlled by ATC? ==
*Check for announced ATC sessions on [http://flightgear-atc.alwaysdata.net/ Lenny's website].
*Check the Pilot List in FlightGear or the [[MPMap|Multiplayer map]]. Usually, controllers:
** have a callsign ''XXXX_DE'', ''XXXX_GN'', ''XXXX_TW'' or ''XXXX_AP'' (where ''XXXX'' is the ICAO code of the airport they are manning);
** use the ''[[OpenRadar]]'', ''ATC-TOWER'', ''[[ATC-aircraft|ATC]]'' (or similarly named) aircraft.

In case multiple controllers are at the same airport, make sure to contact the appropriate one:
* if you are flying to an airport, contact Approach (or Tower if Approach is not available);
* if you are flying from an airport, contact Delivery; if that position is not present, contact Ground (if available) or, failing that, Tower.

== Minimum list of best practices ==
At a minimum, you should do the following:
# '''Know your aircraft well!''' You should be able to take off, land (instrumentally and also visually), maintain an assigned altitude and heading without difficulty.
# '''Know basic ATC phraseology.''' The [[ATC phraseology]] and [[ATC Tutorial]] pages should be enough to get started; if you want to learn more, the [http://vateud.net/manuals/phraseology Phraseology page on the VATEUD site] is a great resource.
# '''Follow the instructions given by ATC timely and read them back.''' This will let the ATC know that you have received the clearance and that you understood it completely and correctly.
# '''Mention your callsign every time you contact ATC.'''
# '''Avoid colliding with other players.'''
# '''Do not start on runways''' - start FlightGear without connecting to the multiplayer server, taxi to an unoccupied parking position if necessary, then connect. It's not nice for other players to land and have another aircraft appear on the runway just before touchdown.
# '''Do not take off/land/cross runways/change altitude or heading unless you have ATC authorization.'''
# '''Do not simulate emergencies/squawk 7700 just to land earlier at a busy field.'''
# '''If other players are abusive, simply ignore them''' (open the Pilot List and click on the Ignore button next to their callsign).

== Additional best practices ==
This is not essential, but would be really nice on your part:
# '''[[Getting aeronautical charts|Get updated charts]] for the areas you are going to fly to and read them.''' If a controller is following real life procedures, it's better to get an idea of what you should expect.
# '''Use [[TerraSync]] or [[TerraMaster]]''' to get the latest scenery for the area you are flying from/to.
# '''Contact the controller''' when you're about 60 NM out from his/her airport (if in flight) or before starting the engines (on ground).
# '''If both you and the controller are able to use [[FGCom]], use it.''' This will make communication easier for both of you (and adds realism). Some controllers also use TeamSpeak or Mumble as an alternative to FGCom (that is usually announced when the controller contacts you for the first time).
# '''If you are using text chat, prefix messages directed to the controller with his/her callsign;''' the controller will do the same for you. It's a lifesaver in busy areas.
# '''Use a multiplayer server that's not overloaded to avoid communication delays''' - use the Multiplayer server status page ([http://mpserver16.flightgear.org/], [http://mpmap01.flightgear.org/mpstatus/] or [http://flightgear.mxchange.org/mpstatus/]) to select a server that's near you and with a low number of active clients.
# '''Respect speed restrictions.''' Don't taxi at more than 20/30 kts and be aware that in most parts of the world you are required not to exceed 250 kts below FL100.
# '''Disable [[Interactive traffic|AI traffic]]''' (but leave AI models on).
# If you have planned your flight, '''consider using [http://flightgear-atc.alwaysdata.net/ Lenny's website] to file your flightplan'''.
# If you are using a recent version of FlightGear (3.2 or later), '''use the transponder''' if the controller requests it.
# If you're flying into an uncontrolled area, use the multiplayer chat to advise nearby traffic of your intentions.
# Check the wiki to get more information about the scenery existing at your destination
## The list of [[Developed Airports]] gives a good overview of well modelled airports published on TerraSync.
## Regularly controlled Airports like [[Amsterdam Airport Schiphol|Amsterdam]], [[LIME|Bergamo]], [[Frankfurt am Main Airport|Frankfurt]], [[Leipzig/Halle Airport|Leipzig/Halle]] or [[LKPR - Vaclav Havel Airport Prague|Praque]] are well documented here.

== Best practices for controllers ==
# '''Offer voice communication if able'''; use text chat for initial contact and as a backup.
# '''Make sure you know phraseology very well'''.
# '''Plan your sessions''' on [http://flightgear-atc.alwaysdata.net/ Lenny's website].
# '''Be patient and polite''' - not all pilots know real life procedures. On initial contact, ask them if they do; if not, just give them vectors.
# '''Get charts''' for the airspace you're controlling and familiarize with the standard procedures.
# Before asking a pilot if he's "inbound" (flying to your airport), check the heading he's flying to and his current altitude and read his flightstrip to see his destination. Contact him only if:
## his flightstrip mentions he's inbound;
## if no destination is indicated, he must be flying towards the space you're controlling and must be definitely not just overflying.
# '''Use the flightplan exchange feature''' as a courtesy to other controllers. At a minimum, fill in the pilot's destination and cruise altitude; if the pilot did not file a flightplan, ask him those data.
# '''Make sure you know how to handoff aircraft''' to other ATCs.

[[Category:Aviation]][[Category:Air Traffic Control]][[Category:Multiplayer]]

ATC best practices

2014-07-02T20:43:54Z

August: lenny's website for pilots

In case you decide to fly into an area controlled by [[Air Traffic Control]], please read these guidelines. Even though the FlightGear multiplayer experience is not by any means a formal environment, you should still follow them to make the experience enjoyable by everyone.

== How do I know if the area is controlled by ATC? ==
*Check for announced ATC sessions on [http://flightgear-atc.alwaysdata.net/ Lenny's website].
*Check the Pilot List in FlightGear or the [[MPMap|Multiplayer map]]. Usually, controllers:
** have a callsign ''XXXX_DE'', ''XXXX_GN'', ''XXXX_TW'' or ''XXXX_AP'' (where ''XXXX'' is the ICAO code of the airport they are manning);
** use the ''[[OpenRadar]]'', ''ATC-TOWER'', ''[[ATC-aircraft|ATC]]'' (or similarly named) aircraft.

In case multiple controllers are at the same airport, make sure to contact the appropriate one:
* if you are flying to an airport, contact Approach (or Tower if Approach is not available);
* if you are flying from an airport, contact Delivery; if that position is not present, contact Ground (if available) or, failing that, Tower.

== Minimum list of best practices ==
At a minimum, you should do the following:
# '''Know your aircraft well!''' You should be able to take off, land (instrumentally and also visually), maintain an assigned altitude and heading without difficulty.
# '''Know basic ATC phraseology.''' The [[ATC phraseology]] and [[ATC Tutorial]] pages should be enough to get started; if you want to learn more, the [http://vateud.net/manuals/phraseology Phraseology page on the VATEUD site] is a great resource.
# '''Follow the instructions given by ATC timely and read them back.''' This will let the ATC know that you have received the clearance and that you understood it completely and correctly.
# '''Mention your callsign every time you contact ATC.'''
# '''Avoid colliding with other players.'''
# '''Do not start on runways''' - start FlightGear without connecting to the multiplayer server, taxi to an unoccupied parking position if necessary, then connect. It's not nice for other players to land and have another aircraft appear on the runway just before touchdown.
# '''Do not take off/land/cross runways/change altitude or heading unless you have ATC authorization.'''
# '''Do not simulate emergencies/squawk 7700 just to land earlier at a busy field.'''
# '''If other players are abusive, simply ignore them''' (open the Pilot List and click on the Ignore button next to their callsign).

== Additional best practices ==
This is not essential, but would be really nice on your part:
# '''[[Getting aeronautical charts|Get updated charts]] for the areas you are going to fly to and read them.''' If a controller is following real life procedures, it's better to get an idea of what you should expect.
# '''Use [[TerraSync]] or [[TerraMaster]]''' to get the latest scenery for the area you are flying from/to.
# '''Contact the controller''' when you're about 60 NM out from his/her airport (if in flight) or before starting the engines (on ground).
# '''If both you and the controller are able to use [[FGCom]], use it.''' This will make communication easier for both of you (and adds realism). Some controllers also use TeamSpeak or Mumble as an alternative to FGCom (that is usually announced when the controller contacts you for the first time).
# '''If you are using text chat, prefix messages directed to the controller with his/her callsign;''' the controller will do the same for you. It's a lifesaver in busy areas.
# '''Use a multiplayer server that's not overloaded to avoid communication delays''' - use the Multiplayer server status page ([http://mpserver16.flightgear.org/], [http://mpmap01.flightgear.org/mpstatus/] or [http://flightgear.mxchange.org/mpstatus/]) to select a server that's near you and with a low number of active clients.
# '''Respect speed restrictions.''' Don't taxi at more than 20/30 kts and be aware that in most parts of the world you are required not to exceed 250 kts below FL100.
# '''Disable [[Interactive traffic|AI traffic]]''' (but leave AI models on).
# If you have planned your flight, '''consider using [http://flightgear-atc.alwaysdata.net/ Lenny's website] to file your flightplan'''.
# If you are using a recent version of FlightGear (2.12 or later), '''use the transponder''' if the controller requests it.
# If you're flying into an uncontrolled area, use the multiplayer chat to advise nearby traffic of your intentions.

== Best practices for controllers ==
# '''Offer voice communication if able'''; use text chat for initial contact and as a backup.
# '''Make sure you know phraseology very well'''.
# '''Plan your sessions''' on [http://flightgear-atc.alwaysdata.net/ Lenny's website].
# '''Be patient and polite''' - not all pilots know real life procedures. On initial contact, ask them if they do; if not, just give them vectors.
# '''Get charts''' for the airspace you're controlling and familiarize with the standard procedures.
# Before asking a pilot if he's "inbound" (flying to your airport), check the heading he's flying to and his current altitude and read his flightstrip to see his destination. Contact him only if:
## his flightstrip mentions he's inbound;
## if no destination is indicated, he must be flying towards the space you're controlling and must be definitely not just overflying.
# '''Use the flightplan exchange feature''' as a courtesy to other controllers. At a minimum, fill in the pilot's destination and cruise altitude; if the pilot did not file a flightplan, ask him those data.
# '''Make sure you know how to handoff aircraft''' to other ATCs.

[[Category:Aviation]][[Category:Air Traffic Control]][[Category:Multiplayer]]

Airports under construction

2014-07-02T08:25:52Z

August: /* Submit your work plans and schedule your activities */ update EDDP

== Preface ==

=== Found a beacon in the middle of the runway in [http://mpmap02.flightgear.org/?ll=48.34849178268444,-107.88724422454834&z=16&t=s&fg_server=mpserver02:5000,mpserver02.flightgear.org,5001&update_interval=5&pilot_label=always&icon_mode=normal LMML] or some other faults? ===
First you have to know that 90 % of the airports have "bad layouts" at the moment and at some places even maps are not updated (have a [http://mpmap02.flightgear.org/?ll=48.34849178268444,-107.88724422454834&z=16&t=s&fg_server=mpserver02:5000,mpserver02.flightgear.org,5001&update_interval=5&pilot_label=always&icon_mode=normal look here] i.e.). Most of the airports need updates. This is a lot of work when you think about the 20’000 airports in the database. When you read the tutorials how to build airports you can do it yourself and submit your work. Or someone of the contributors here will once start to work on your "wish" - but please be patient and do not send any messages/mails to contributors. You can go to the forum ([http://forum.flightgear.org/viewforum.php?f=5 Scenery Enhancement]) to discuss some issues.

== Airports under construction ==
In this article you find a list of all airports which currently are under construction. You can also see if an airport is "finished" and if the data is already submited to the current database of the mapserver (apt.dat).

=== Availability of new/changed airports needs some time ===
In FlightGear there is a common workflow to edit airports. First, experienced contributors have to change the airport data with [[Wed]]. Then they submit the new data to the X-Plane community (main scenery data files/airport data file apt.dat). Meantime, other contributors can also submit some scenery to the custom scenery database (for downloading via TerraSync). But for runways, taxiways, beacons, frequencies, the apt.dat file needs an update anyway and maybe also the base scenery around the airport needs an update. Please be patient with updates. It needs more time than you expected.

== Submit your work plans and schedule your activities ==
Please feel free to edit this page and submit your "pending airport" directly.

=== Current Activities ===

{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"
|-
! style="background:#efefef" | ICAO !! style="background:#efefef" | Who !! class="unsortable" style="background:#efefef" | Airport layout !! class="unsortable" style="background:#efefef" | Airport objects !! class="unsortable" style="background:#efefef" | AI Network !! class="unsortable" style="background:#efefef" | Start date !! class="unsortable" style="background:#efefef" | .dat submitted !! class="unsortable" style="background:#efefef" | Comments
|-
|[[EDDP]]||August, D-STHO||x||x||||2012-07-01|||| improved 850-layout (available via GIT, will be published via TerraSync 10/2014), more static buildings
|-
|EDLM||laserman|| ||x|||||2013||||
|-
|EDWG||gral||x||||||2010-02-03||||
|-
|EDWJ||gral||x||||||2010-02-01||2010-02-03||taxiway, runways, positions
|-
|[[EDWL]]||gral||x||||||2010-02-03||||
|-
|[[EDWP]]||TeXnicer||||||||2013-12-05||||First attempts with WED & Co., small airfield
|-
|EDWY||gral||x||||||2010-02-03||||
|-
|EEKE||henrikp||x||||||2010-10||||
|-
|EERU||henrikp||x||||||2010-10||||
|-
|EEKA||henrikp||x||||||2010-10||||
|-
|EGGD||karla||||x||x||2009-07-12||2010-12-02||customized buildings, stock buildings, stock models and vehicles, high detail
|-
|[[London Gatwick Airport|EGKK]]||karla||||x||x||2010-02-13||2010-02-07||fully complete; over 60 customized buildings and other features with highly detailed day and night textures; full taxiway signs; AI traffic, parking and taxiways; available as direct download (see forum) or on Git/Git
|-
! style="background:#efefef" | ICAO !! style="background:#efefef" | Who !! class="unsortable" style="background:#efefef" | Airport layout !! class="unsortable" style="background:#efefef" | Airport objects !! class="unsortable" style="background:#efefef" | AI Network !! class="unsortable" style="background:#efefef" | Start date !! class="unsortable" style="background:#efefef" | .dat submitted !! class="unsortable" style="background:#efefef" | Comments
|-
|EHGG||Gijs||x||x||x||x||x|| || ||
|-
|[[EHAM]]||Gijs||x||x||x||x||x|| || ||
|-
|[[EHLE]]||Gijs||x||x||x||x||x|| || ||
|-
|[[EHVK]]||Gijs||x||x||x||x||x|| || ||
|-
|EHEH||Gijs||x||x||x||x||x|| || ||
|-
|EHKD||Gijs||x||x||x||x||x|| || ||
|-
|EHTX||Gijs||x||x||x||x||x|| || ||
|-
|EHAL||Gijs||x||x||x||x||x|| || ||
|-
|EHRD||Gijs||x||x||x||x||x|| || ||
|-
|EHLW||Gijs||x||x||x||x||x|| || ||
|-
|KCHO||Catchatyou||x|| || ||2010-12-05|| ||The basic structure of the airport is almost complete, and once the airport is correctly modeled, I will be adding the parking lot, hangars...||
|-
|KDMA||gral||x|||| ||2010-02-10||2010-02-10||runways, taxiways
|-
|KDTW||Fgoldbatch||||x||||2011-03-30||||Replacement of McNamara Terminal and addition of North Terminal
|-
|KHND||Armchair Ace|| ||x|| || || ||Hangars and static aircraft added. Terminal still needed.
|-
|KSFO||karla|| ||x|| ||2010-08-06 ||2010-08-27 ||Terminal 2 fully remodelled; new day and night textures; new light masts; jetways included; actual T2 under reconstruction 2010; available as direct download (see forum) or on Git/Git
|-
! style="background:#efefef" | ICAO !! style="background:#efefef" | Who !! class="unsortable" style="background:#efefef" | Airport layout !! class="unsortable" style="background:#efefef" | Airport objects !! class="unsortable" style="background:#efefef" | AI Network !! class="unsortable" style="background:#efefef" | Start date !! class="unsortable" style="background:#efefef" | .dat submitted !! class="unsortable" style="background:#efefef" | Comments
|-
|LHPP||sztamas6||x||||||2011-11-02|| || Changin generic taxiways to realistic ones. Adding paved and unpaved aprons. Moving tower position to actual location
|-
|LIDF||[[User:Bigstones|bigstones]]||x||||||2014-05-18||2014-05-18||Layout from OSM.
|-
|LIPX||elgaton||x||||||2013-12-16||||Redone from scratch using OSM data: runway, taxiways, airport boundary, PAPI, windsocks, radio frequencies. To be done: signs, markings, objects. [http://forum.flightgear.org/viewtopic.php?f=5&t=21576 Beta release available on the forum].
|-
|LIPR||[[User:Bigstones|bigstones]]||x||||||2014-04-25||2014-05-18||Layout from OSM.
|-
|[[LIPY]]||[[User:Bigstones|bigstones]]||x||x||||2014-04-06||2014-05-18||Layout from OSM, models converted from an FS scenery, with author consent ([http://forum.flightgear.org/viewtopic.php?f=5&t=22623 read more])
|-
|LSMA||gral||x||||||2010-04-12||2010-04-12||runways, taxiways, tower position, atc freqs
|-
|OMDB||D-SKY1||||||x||2010-06-25||||added AI traffic (UAE)
|-
|RPLL||D-SKY1||||x||x||2009-12-03||2010-02-11||T1, T2, T3, Tower, AI ground network, AI traffic, ATC freqs. Todo: taxi- and runways redesign
|-
|SBBG||Prestes||x||x|| ||2009-12-26 || ||
|-
|SBPA||Prestes||x||x|| ||2009-12-28 || ||Airport objects by George Luiz
|-
|SBPK||Prestes||x||x|| ||2010-01-31 || ||
|-
|SBRG||Prestes||x||x|| ||2010-01-31 || ||
|-
|SUMU||Prestes||x||x|| ||2010-01-31 || ||
|-
|UEST||gral||x|||| ||2010-01-10||2010-01-12||fixed taxiways and some minor issues
|-
|VTBD||D-SKY1||||x||x||2010-11-27 || ||[http://forum.flightgear.org/viewtopic.php?f=5&t=10075 Work in progress]
|-
|YSSY||scotth1||x||x||x|| ||2011-01-11||adjusted aprons, taxiways, moved windsocks, AI ground network submitted. very basic International terminal yet to be submitted, TODO: domestic terminal, cargo terminal
|}

== Submit your wishes ==
If you wish to add an airport or think this or another airport needs a change '''[http://forum.flightgear.org/viewtopic.php?f=5&t=6749 you have to post in the forum (scenery enhancement)]'''. But first search the forum with the ICAO code of the airport and be sure that you have read all the posts about this airport. And please submit also some links to images and information you have about/from this airport.

== Links ==
* [http://mapserver.flightgear.org/Apt.Dat.txt List of updated airports in apt.dat mapserver] 1)
* [http://mapserver.flightgear.org/apt.dat.gz Updated apt.dat.gz mapserver] 1)
* [http://cvs.flightgear.org/viewvc/data/Airports/apt.dat.gz?view=log Log of apt.dat.gz in FlightGear Git]
* [[Taxidraw|TaxiDraw Tutorial]]
* [http://taxidraw.sourceforge.net/taxidraw/tutorial.html Another (outdated) Tutorial for TaxiDraw]
* [http://taxidraw.sourceforge.net/#download TaxiDraw download - includes also working binaries (i.e. for OSX)]

1) "mapserver.flightgear.org" is NOT "mpmap02.flightgear.org". The mpmap02 is hosted on another server and could reflect an older apt.dat.gz than the current one of the mapserver or of the Git server.

=== Other airport work related pages in the FlightGear wiki ===
* List of [[Developed Airports]] with buildings and [[Signs]] already included in the [[FlightGear Scenery Database]]
* [[Germany|Current work in Germany]]
* [[Current Scenery Projects]]
* [[FlightGear User Created Helipad List]]

[[Category:Airports]]

File:2014 new-layout-EDDP 05.jpg

2014-07-01T09:48:11Z

August:

User:August

2014-06-29T16:17:52Z

August:

I have been using FlightGear since 2011 and started modelling airports in June 2012.
Regularly I provide Air Traffic Control at EDDP.
[[File:2014 new-layout-EDDP 04.jpg|new ground layout under development at EDDP|450px|thumbnail|right]]
My main contributions to TerraSync and FlightGear are:
* Under development: Improvement of [[EDDP|Leipzig-Halle Airport (EDDP)]] (originally designed by [[User:D-79|D-79]])

File:EDAC1.jpg

2014-06-29T15:32:37Z

August: August uploaded a new version of "File:EDAC1.jpg"

Leipzig-Altenburg Airport

2014-06-29T15:25:20Z

August: Scenery update

{{airport-stub}}

{{infobox Airport
|name = Leipzig-Altenburg Airport
|image =EDAC1.jpg
|alt =
|iata =AOC
|icao =EDAC
|type =Public
|city =in Nobitz near Altenburg (26mi from Leipzig)
|owner =Flugplatz Altenburg-Nobitz GmbH
|website =http://www.leipzig-altenburg-airport.de/
|terrasync = only generic layout
|runway= 04/22
|length= 7,989 ft
|material= Concrete (in FG still Asphalt)
}}
'''Leipzig-Altenburg Airport''', until 2008 known as Altenburg-Nobitz Airport, is a German regional airport near Altenburg and 42 km (26 mi) south of Leipzig in the state of Thuringia. Its close to the well developed Flightgear-airport [[Leipzig/Halle Airport|Leipzig/Halle]]. The former military Airfield was transformed into a public airport in 1992. In Flightgear this airport was never developed over the status of simple [[Taxidraw]].

== Flying at Leipzig/Halle airspace ==
In Flightgear Leipzig-Altenburg Airport is usually operated by the Air traffic controller at [[Leipzig/Halle Airport]], because Departure and Approach is leading pilots normally through Leipzig/Halle Airspace.

=== Charts ===
All [http://www.vacc-sag.org/airport/EDAC diagrams and charts] are available for download.

=== Runways 04/22 ===

The runway is 2.435m long with a width of 45m.
* NDB/DME '''04''' (038°)
* ILS-CAT-I '''22''' (218°): 108.70

=== ATC ===
* Altenburg Tower - frequency 123.570
Due to lac of real centre controls in Flightgear, frequency of Leipzig Tower is usually used in the airspace around Leipzig-Alternburg Airport
* Leipzig Tower - frequency 121.100
* Munich Radar - frequency 126.170
* Munich Radar - frequency 132.300

== Infrastructure ==

=== Access and connection ===
The Airport is only connected by bus to Altenburg. There is no direct public connection to Leipzig any-more.

=== Apron 1 ===
==== Terminal ====

=== Apron 2 ===

== Scenery ==

In TerraSync only a simple ground layout exists. Currently this airport is under development.
First scenery had been modelled and published via [[TerraSync]] in 2013. There is no custom scenery existing. The authors believe on the advantages of TerraSync which makes it easy for every user always to have the latest scenery installed automatically. In 2014 the layout will be updated to 850-standard.

=== Development ===

The Scenery is developed by Thomas G. and [[User:August|August]] by using shared models and newly designed static objects:

== External links ==
* [http://www.vacc-sag.org/airport/EDAC Airport Diagrams]

[[Category:Airports in Germany]]

Leipzig/Halle Airport

2014-06-29T12:23:51Z

August:

{{infobox Airport
|name = Leipzig/Halle Airport
|image =EDDP TerminalC.jpeg
|alt =New terminal C (published 2012)
|iata =LEJ
|icao =EDDP
|type =Public
|city =Between Leipzig and Halle
|owner =Mitteldeutsche Airport Holding
|website =http://www.leipzig-halle-airport.de/
|scenerytile =e012n51
|download =
|terrasync = [[#Download_via_GIT]] for latest scenery
|runway= 08L/26R
|length= 11,811 ft
|material= Concrete (in FG still Asphalt)
|runway2= 08R/26L
|length2= 11,811 ft
|material2= Concrete (in FG still Asphalt)
}}

'''Leipzig/Halle Airport''' is located in Schkeuditz, Saxony and serves both Leipzig, Saxony and Halle, Saxony-Anhalt, [[Germany]]. In Flightgear this airport was published on [[TerraSync|TerraSync]] in 2010 und updated due to new developments 2012. In 2014 according to the new world scenery a complete overhaul started.
EDDP is also the centre of Leipzig/Halle airspace, which provides air traffic control also for the regional airfield [[Leipzig-Altenburg Airport]].

{{Note|Users are asked to test the '''beta Version of the new 850-Layout''' (see [[#Download_via_GIT]])}}

== Flying at Leipzig/Halle airspace ==

=== Charts ===
All [http://www.vacc-sag.org/airport/EDDP diagrams and charts] are available for download.

=== Runways and ILS ===

==== Runway 08L/26R ====
[[File:2012-09 Apron4 Luftbild-at-night.png|thumb|270px|Apron 4 and runway 26L at night]]The northern [[runway]] is 3600m long with a width of 45m. In real life its usually used by passenger airliners. In Flightgear this runway is equipped with Outer Marker and Middle Marker and offers best conditions for '''low visibility operations'''.
* ILS-CAT-III '''08L''' (083°): 108.55
* ILS-CAT-III '''26R''' (263°): 108.35
==== Runway 08R/26L ====
The southern [[runway]] is 3600m long with a width of 60m. In real life its mostly used by freighters due to its proximity to freight areas (Apron 2 and 4). It has no Outer Marker an no Middle Marker.
* ILS-CAT-III '''08R''' (083°): 111.90 (111.75 in FG older than Version 2.0.0)
* ILS-CAT-III '''26L''' (263°): 110.30

=== ATC ===
* Leipzig Ground - frequency 121.800
* Leipzig Tower - frequency 121.100

Leipzig/Halle Airport is regularly served by Air Traffic Control ([[ATC]]).

== Infrastructure ==
[[File:EDDP-overview-daytime.jpg|thumb|270px|Overview 2012]]Connected by terminal C and three taxiway bridges (W1, E7, E8) the airport layout combines the northern part with runway 08L/26L and Apron 3 (new cargo area since 2012) and the southern part with Apron 1 (terminal B), runway 08R/26L, Apron 2, Apron 4 (DHL), Apron 5. Between both parts an airport railway station and the autobahn A14 is connecting to the check-in area of terminal C. Railway and motorway are not modelled in Flightgear.

=== Access and connection ===
[[File:TerminalC-morning.jpg|thumb|270px|Terminal C at dawn]]
==== Terminal C ====
In August 2012 the completely new modelled terminal C was published on TerraSync. It is built as a connection between the check-in building with car-park and train station in the north and the departure area at terminal B in the south. Due to this efforts it stands on piers like a long bridge from apron 1 to apron 3, crossing different car-parks, a rail-track and the autobahn.
On the one hand the FlighGear model tries to give the airport a well designed model with highly detailed structures, but on the other hand it was programmed as simple as possible to save visitors simulation performance.

==== Taxiway bridges ====
[[File:EDDP-Taxibridges-e7e8-night.jpg|thumb|270px|Rampbridges E7, E8 with new lightning in 2012]]A highway and railway lines go straight between the two runways. Three bridges connect the terminal with the northern runway. The western bridge (taxiway W1) is used in both directions. The eastern bridges (taxiways E7 and E8) are used as one way taxiways. Due to safety improvements all bridges are equipped with special taxi lights.
Due to changes in the TerraData the bridges had to be repositioned in 2012.

=== Apron 1 ===

The main apron at Leipzig/Halle Airport is located in the middle of the airport. It houses the commercial aviation area at terminal B in the west and the general aviation area in the eastern part. It is connected by taxiways L, N and W1.

==== Terminal B ====
[[File:EDDP VDGS-134 thumbnail.jpg|thumb|270px|VDGS on each gateway at terminal B]]'''Real world''':
This building is the main terminal for most commercial flights at EDDP. It is connected to terminal C in the north and provides the passenger transfer to Apron 1 via 6 gateways. It also has a connection to the luggage terminal.

'''Scenery in TerraSync''':
In Flightgear the main terminal is modelled very slim and efficiently. 6 unmovable gateways link to park positions 126, 128, 130, 132, 134 and 136. In 2012 it will be improved. Since September 2012 it has been equipped with a non-animated [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System VDGS].

==== Luggage terminal ====
This building was first published in 2004 and remodelled by Thomas Großberger in 2012. The terminal is connected via the old tower next to it to terminal A by a tube, which is used to transport luggage between the checkin- and arrival-area and Apron 1. Both. the connection and the old tower building will be modelled in 2013. The new luggage terminal in FlightGear is offering:
* realistic roof design
* simplified but detailed interior
* 6 clock controlled automatic gates
* complex light design (Rembrandt-Design outstanding)

==== GAT ====

=== Apron 2 ===

=== Apron 3 ===
This Apron in real life went into service with a new cargo hangar in 2012. In Flightgear it is still closed. The corresponding facilities are still under development.

=== Apron 4/5 (DHL-area) ===
[[File:2012-08 Apron4 Pos432 BOX1522-D-STHO-and-DC10.png|thumb|270px|DHL-area at apron 4]]'''Real world:''' Leipzig/Halle is just a small international airport. But in 2008 it became the [http://www.dp-dhl.com/en/logistics_around_us/from_our_divisions/leipzig_hub.html European DHL hub] with up to 60 planes per night. The DHL Hub Leipzig GmbH, place of business in Schkeuditz, is running under contract to the logistic group DHL at Leipzig/Halle Airport one of six international aviation hubs. In order to provide maintenance to the new fleet the [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig GmbH] was founded. European Air Transport operates services to Europe, Middle East and Africa. 56 countries are covered in total. A second aviation company, called [http://en.wikipedia.org/wiki/Aerologic AeroLogic], was founded in EDDP. AeroLogic GmbH, a joint-venture between DHL Express and Lufthansa Cargo, is a German cargo airline headquartered in Schkeuditz, Saxony. It operates cargo flights out of Leipzig/Halle Airport and Frankfurt, most of which are on behalf of its parent companies.

{| class="wikitable" cellpadding="3" style="margin-left:auto; margin-right:auto"
|+ '''Fleet of [http://en.wikipedia.org/wiki/Aerologic AeroLogic] and [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig] and others''' (2012)
|-
!Aircraft
!Total
!Orders
!Oparator
|-
|[[Airbus A300|Airbus A300B4-203F]]
|<center>10</center>
|
|Air Contractors
|-
|[[Airbus A300|Airbus A300-600RF]]
|<center>8</center>
|<center>10</center>
|European Air Transport Leipzig
|-
|Boeing 737-300F
|<center>9</center>
|
|European Air Transport Leipzig
|-
|Boeing 737-400F
|<center>1</center>
|
|Europe Airpost
|-
|[[Boeing 757|Boeing 757-236SF]]
|<center>10</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 757|Boeing 757-23APF]]
|<center>1</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 777F]]
|<center>8</center>
|
|AeroLogic
|-
!Total
!47
!10
!colspan=2|
|}

[[File:EDDP-DHL-tank.jpeg|thumb|270px|DHL-Tank at fuel storage area on apron 4]]'''Scenery in TerraSync:''' The hub (warehouse, hangar and aprons) is modelled in the scenery. In 2012 its redesign for TerraSync started. First all lampposts at apron 4 had been replaced with those which fit into the correct layout of every single parking position. Afterwards lots of goods and ground vehicles where placed. As soon as some missing storage buildings are modelled, the new content of apron 4 will be published on TerraSync. Last modifications will take place when the new [[Airport data (apt.dat) update|850-standard layout]] of EDDP will be created in the future.

'''DHL-hub at EDDP in Flightgear:''' Leipzig/Halle Airport offers ground space for more than 70 Boeing [[757-200|757-PF]] or up to 50 [[777F]] as well as space for 10 [[Antonov An-124|An-124]] at Apron 2, 4 and 5. Airmail flights can be flown from and to EDDP. One of the middle sized and highly connected hubs of DHL, the [[Orio al Serio Airport]] (Italy) is also modelled in FlightGear and can be used for realistic flights out of Leipzig/Halle Airport.
In FlighGear apron 4 is equipped with all stands. Additionally to the main apron lightning each stand has one centred lamppost, which will be replaced by a VDGS-signs in the future. Ground markings will come with the new 850-layout. The major storage buildings from DHL are modelled as well as three DHL-tanks south from apron 4.

=== De-icing areas ===
Leipzig/Halle Airport has four special areas, two in the north at taxiway C and two in the south at taxiway N. In FlightGear only the two areas at taxiway C are build into the layout. In 2012 both areas had been equipped with shared models like lampposts, buildings and ground lights.

==== De-icing area 2 - multiplayer ready ====

Based on the Zurich type model "Elephant" - originally modelled by Oliver Thurau - an improved version with full multiplayer support is under development. This version isn't only adapted to the special efforts at EDDP, but its also designed to be controlled by ATC. It will be published via TerraSync in November 2014.

== Surroundings and "Other" ==

=== Kursdorf - the village within the airport ===
There is a village right in middle of the airport. So it's no surprise the number of inhabitants is shrinking each year. Once a thriving village with 537 inhabitants in 1950, they were down to 119 in 2006 [http://de.wikipedia.org/wiki/Kursdorf_%28Schkeuditz%29 (Wikipedia)]. It might be a little loud with the two runways, highway and express railways, but the transport links, hey ... The village is modelled in the scenery.

== Scenery ==
{|
| Authors: ||
* Models: David G., D-STHO
* Airport layout: Christian Schmitt
* Additional models: Don Lavelle, Alex Park, Robert Shearman
* Redesigning & Development 2012: [[User:August|August]], D-STHO
|-
|}

=== Download via GIT ===
With FlightGear 3.0 a new world scenery was published, including a new but incorrect 850-layout for EDDP. Developers started a huge overhaul of the EDDP scenery in April 2014. First a new taxiway layout was programmed. Additionally all buildings and objects are replaced. Some models will be remodelled, others will be added. Due to the fact that airport layouts can't be simply updated via TerraSync in a short way, pilots are asked to use the new EDDP CUSTOM SCENERY as long as things aren't updated at TerraSync.

* Download-Development-Scenery
* updated regularly
** '''git clone''' [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/ https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/]
** or [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/archive/5a25c94d403f09e5b5bf4d72117e297191acb3ce.tar.gz download a ZIP] (101 MB)

=== Download via TerraSync ===
[[TerraSync]] has it all! There is no custom scenery existing (only the GIT-repository for testing the new 850-layout before publishing it). The authors believe on the advantages of TerraSync which makes it easy for every user to have the latest scenery installed automatically. Updates are published regularly via TerraSync.
* Next update in '''<daysuntil in="days">12-August-2014</daysuntil>''' {{Progressbar|height=45|percentage={{#expr: trunc ({{#time: z}} - {{#time: z | May 19 2014 }}) round -1 }}}}

* '''Latest update on TerraSync:'''
** '''2014-04-29''' ''Objects adapted to new (but incorrect) 850-layout''

* Last five updates:
** '''2013-04-21''' ''Rembrandt lights at apron 1''
** 2013-02-13 ''new Messeturm at final approach area of runway 26R''
** 2012-12-21 ''new luggage terminal at apron 1''
** 2012-10-22 ''three new DHL-tanks placed at DHL-area''
** 2012-09-20 ''new VisualGuidingDockingSystem at terminal B''

=== Development ===
Since the Scenery had been modelled by [[User:D-79|D-79]] in 2010, D-STHO and [[User:August|August]] started enhancements and redesigning in 2012. In 2014 development of a new 850-layout started. Improvements are made on the following objects:

'''Layout''' 
* Taxiway bridges: new Position, improved lightning ''(published 07/2012)'' {{tick}}
* New 850-standard: new Layout with all parking positions and improved taxiways {{progressbar|90}} (see [[#Download_via_GIT]])

'''Scenery (Shared Models)''' 
* Airport lightning: more than 80 lampposts ([[EDDM]]-model) on Apron 1 and 4 and both northern de-icing areas ''(published 07/2012)'' {{tick}}
* DHL-tanks at apron 4 ''(published 10/2012)'' {{tick}}
* Ground traffic: lots of goods and vehicles (shared) make apron 1 and 4 much more realistic ''(published 08/2012)'' {{tick}}
* Flora and boundaries: Trees and fences on Apron 1, 2 and 4 are added ''(published 08/2012)'' {{tick}}
* New shared ground vehicles
** Container dolly ''(under development)'' {{hourglass}}
** Luggage dolly ''(under development)'' {{hourglass}}
** Pallet dolly ''(planned)''
* New shared Unit Load Devices (ULD)
** Airfreight container - Type AKH ''(pre-development)'' {{hourglass}}
** Airfreight pallet ''(planed)''
* Village and industrial surroundings: Kursdorf within the airport and industrial areas around are created with shared models ''(published 04/2010)'' {{tick}}

'''Buildings and infrastructure (Static models)''' 
* Cargo-hangar apron 3 ''(planned)''
* Cargo-center apron 2 ''(published 2010)'' {{tick}}
* DHL-hangar ''(published 2010)'' {{tick}}
* DHL-terminal ''(published 2010)'' {{tick}}
* Interactive DE-ICING areas (Multiplayer supported) {{hourglass}}
* Interactive luggage dolly traffic between terminal B and lugage terminal ''(planned)''
* Luggage terminal ''(published 12/2012)'' {{tick}}
* Storage buildings at DHL-area ''(pre-development)'' {{hourglass}}
* Terminal B ''(published 04/2010)'' {{tick}}
* Terminal C ''(published 08/2012)'' {{tick}}
* Tower ''(published 2010)'' {{tick}}
* Turbo engine hall ''(pre-development)'' {{hourglass}}
* Old Tower next to terminal B ''(pre-development)'' {{hourglass}}
* Visual Docking Guiding System at Apron 4 ''(planned)''
* Visual Docking Guiding System at Terminal B ''(published 09/2012)'' {{tick}}
* Visual Docking Guiding System: replacement with animated interactive version ''(planned)''
'''Rembrandt lightning improvements'''
* Converting Lightning to [[Project Rembrandt|Rembrandt]]
** Rembrandt lights at apron 1 ''(published 04/2013)'' {{tick}}
** Rembrandt lights at apron 2 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 3 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 4 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 5 {{progressbar|90}} (see [[#Download_via_GIT]])
* Converting Buildings to [[Project Rembrandt|Rembrandt]] Lightning
** Luggage terminal ''(pre-development)'' {{hourglass}}
** Terminal B ''(planned)''
** Terminal C ''(planned)''
** Tower ''(planned)''
** DHL-hangar ''(planned)''
* Lampposts in EDDP-style ''(planned)''

'''Buildings at the city of Leipzig (Static models)''' 
* City-Hochhaus {{progressbar|90}}
* Wintergartenhochhaus ''(published 02/2013)'' {{tick}}
* Völkerschlachtdenkmal (Battle of Nations Monument) {{hourglass}}
* Red-Bull Arena {{hourglass}}
* Gondwanaland (tropical zoo) ''(published 02/2013)'' {{tick}}
* DVB-T-Tower ''(published 02/2013)'' {{tick}}
* Messeturm Leipzig ''(published 02/2013)'' {{tick}}
* Hauptbahnhof (Central Station) ''(planned)''

=== Scenery since 2014 ===
<gallery mode=packed widths=180px heights=180px>
2014 new-layout-EDDP 04.jpg|Redesigned Layout: Taxiway T - new ground textures
2014 new-layout-EDDP 01.jpg|Redesigned Layout: Runway 26L with DHL-area
2014 new-layout-EDDP 02.jpg|Redesigned Layout: Apron 4
</gallery>

=== Scenery since 2012 ===
[[File:EDDP TerminalC.jpeg|Terminal C]] [[File:EDDP VDGS-136 thumbnail.jpg|VDGS at position 136]] [[File:EDDP-DHL-tank.jpeg|DHL-Tank at fuel storage area on apron 4]] [[File:EDDP_luggageterminal_thumb.jpg|Luggage Terminal at Apron 1]]

=== Scenery since 2010 ===
Here is a selection of the models. [http://www.youtube.com/watch?v=3kNDGiSNUdE YouTube video 2010].

[[File:EDDP10.jpg]] [[File:EDDP11.jpg]] [[File:EDDP12.jpg]] [[File:EDDP13.jpg]] [[File:EDDPbridge1.png]]

== Related content ==
* [[Germany]]
* [[Leipzig/Halle Airspace]]

== External links ==
* [http://www.vacc-sag.org/airport/EDDP Airport Diagrams]
* [http://de.wikipedia.org/wiki/EDDP Leipzig/Halle Airport at Wikipedia] (German)

[[Category:Airports in Germany]]

Leipzig/Halle Airport

2014-06-29T12:22:43Z

August:

{{infobox Airport
|name = Leipzig/Halle Airport
|image =EDDP TerminalC.jpeg
|alt =New terminal C (published 2012)
|iata =LEJ
|icao =EDDP
|type =Public
|city =Between Leipzig and Halle
|owner =Mitteldeutsche Airport Holding
|website =http://www.leipzig-halle-airport.de/
|scenerytile =e012n51
|download =
|terrasync = [[#Download_via_GIT]] for latest scenery
|runway= 08L/26R
|length= 11,811 ft
|material= Concrete (in FG still Asphalt)
|runway2= 08R/26L
|length2= 11,811 ft
|material2= Concrete (in FG still Asphalt)
}}

'''Leipzig/Halle Airport''' is located in Schkeuditz, Saxony and serves both Leipzig, Saxony and Halle, Saxony-Anhalt, [[Germany]]. In Flightgear this airport was published on [[TerraSync|TerraSync]] in 2010 und updated due to new developments 2012. In 2014 according to the new world scenery a complete overhaul started.
EDDP is also the centre of Leipzig/Halle airspace, which provides air traffic control also for the regional airfield [[Leipzig-Altenburg Airport]].

{{Note|Currently users are asked to test the '''beta Version of the new 850-Layout''' (see [[#Download_via_GIT]])}}

== Flying at Leipzig/Halle airspace ==

=== Charts ===
All [http://www.vacc-sag.org/airport/EDDP diagrams and charts] are available for download.

=== Runways and ILS ===

==== Runway 08L/26R ====
[[File:2012-09 Apron4 Luftbild-at-night.png|thumb|270px|Apron 4 and runway 26L at night]]The northern [[runway]] is 3600m long with a width of 45m. In real life its usually used by passenger airliners. In Flightgear this runway is equipped with Outer Marker and Middle Marker and offers best conditions for '''low visibility operations'''.
* ILS-CAT-III '''08L''' (083°): 108.55
* ILS-CAT-III '''26R''' (263°): 108.35
==== Runway 08R/26L ====
The southern [[runway]] is 3600m long with a width of 60m. In real life its mostly used by freighters due to its proximity to freight areas (Apron 2 and 4). It has no Outer Marker an no Middle Marker.
* ILS-CAT-III '''08R''' (083°): 111.90 (111.75 in FG older than Version 2.0.0)
* ILS-CAT-III '''26L''' (263°): 110.30

=== ATC ===
* Leipzig Ground - frequency 121.800
* Leipzig Tower - frequency 121.100

Leipzig/Halle Airport is regularly served by Air Traffic Control ([[ATC]]).

== Infrastructure ==
[[File:EDDP-overview-daytime.jpg|thumb|270px|Overview 2012]]Connected by terminal C and three taxiway bridges (W1, E7, E8) the airport layout combines the northern part with runway 08L/26L and Apron 3 (new cargo area since 2012) and the southern part with Apron 1 (terminal B), runway 08R/26L, Apron 2, Apron 4 (DHL), Apron 5. Between both parts an airport railway station and the autobahn A14 is connecting to the check-in area of terminal C. Railway and motorway are not modelled in Flightgear.

=== Access and connection ===
[[File:TerminalC-morning.jpg|thumb|270px|Terminal C at dawn]]
==== Terminal C ====
In August 2012 the completely new modelled terminal C was published on TerraSync. It is built as a connection between the check-in building with car-park and train station in the north and the departure area at terminal B in the south. Due to this efforts it stands on piers like a long bridge from apron 1 to apron 3, crossing different car-parks, a rail-track and the autobahn.
On the one hand the FlighGear model tries to give the airport a well designed model with highly detailed structures, but on the other hand it was programmed as simple as possible to save visitors simulation performance.

==== Taxiway bridges ====
[[File:EDDP-Taxibridges-e7e8-night.jpg|thumb|270px|Rampbridges E7, E8 with new lightning in 2012]]A highway and railway lines go straight between the two runways. Three bridges connect the terminal with the northern runway. The western bridge (taxiway W1) is used in both directions. The eastern bridges (taxiways E7 and E8) are used as one way taxiways. Due to safety improvements all bridges are equipped with special taxi lights.
Due to changes in the TerraData the bridges had to be repositioned in 2012.

=== Apron 1 ===

The main apron at Leipzig/Halle Airport is located in the middle of the airport. It houses the commercial aviation area at terminal B in the west and the general aviation area in the eastern part. It is connected by taxiways L, N and W1.

==== Terminal B ====
[[File:EDDP VDGS-134 thumbnail.jpg|thumb|270px|VDGS on each gateway at terminal B]]'''Real world''':
This building is the main terminal for most commercial flights at EDDP. It is connected to terminal C in the north and provides the passenger transfer to Apron 1 via 6 gateways. It also has a connection to the luggage terminal.

'''Scenery in TerraSync''':
In Flightgear the main terminal is modelled very slim and efficiently. 6 unmovable gateways link to park positions 126, 128, 130, 132, 134 and 136. In 2012 it will be improved. Since September 2012 it has been equipped with a non-animated [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System VDGS].

==== Luggage terminal ====
This building was first published in 2004 and remodelled by Thomas Großberger in 2012. The terminal is connected via the old tower next to it to terminal A by a tube, which is used to transport luggage between the checkin- and arrival-area and Apron 1. Both. the connection and the old tower building will be modelled in 2013. The new luggage terminal in FlightGear is offering:
* realistic roof design
* simplified but detailed interior
* 6 clock controlled automatic gates
* complex light design (Rembrandt-Design outstanding)

==== GAT ====

=== Apron 2 ===

=== Apron 3 ===
This Apron in real life went into service with a new cargo hangar in 2012. In Flightgear it is still closed. The corresponding facilities are still under development.

=== Apron 4/5 (DHL-area) ===
[[File:2012-08 Apron4 Pos432 BOX1522-D-STHO-and-DC10.png|thumb|270px|DHL-area at apron 4]]'''Real world:''' Leipzig/Halle is just a small international airport. But in 2008 it became the [http://www.dp-dhl.com/en/logistics_around_us/from_our_divisions/leipzig_hub.html European DHL hub] with up to 60 planes per night. The DHL Hub Leipzig GmbH, place of business in Schkeuditz, is running under contract to the logistic group DHL at Leipzig/Halle Airport one of six international aviation hubs. In order to provide maintenance to the new fleet the [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig GmbH] was founded. European Air Transport operates services to Europe, Middle East and Africa. 56 countries are covered in total. A second aviation company, called [http://en.wikipedia.org/wiki/Aerologic AeroLogic], was founded in EDDP. AeroLogic GmbH, a joint-venture between DHL Express and Lufthansa Cargo, is a German cargo airline headquartered in Schkeuditz, Saxony. It operates cargo flights out of Leipzig/Halle Airport and Frankfurt, most of which are on behalf of its parent companies.

{| class="wikitable" cellpadding="3" style="margin-left:auto; margin-right:auto"
|+ '''Fleet of [http://en.wikipedia.org/wiki/Aerologic AeroLogic] and [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig] and others''' (2012)
|-
!Aircraft
!Total
!Orders
!Oparator
|-
|[[Airbus A300|Airbus A300B4-203F]]
|<center>10</center>
|
|Air Contractors
|-
|[[Airbus A300|Airbus A300-600RF]]
|<center>8</center>
|<center>10</center>
|European Air Transport Leipzig
|-
|Boeing 737-300F
|<center>9</center>
|
|European Air Transport Leipzig
|-
|Boeing 737-400F
|<center>1</center>
|
|Europe Airpost
|-
|[[Boeing 757|Boeing 757-236SF]]
|<center>10</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 757|Boeing 757-23APF]]
|<center>1</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 777F]]
|<center>8</center>
|
|AeroLogic
|-
!Total
!47
!10
!colspan=2|
|}

[[File:EDDP-DHL-tank.jpeg|thumb|270px|DHL-Tank at fuel storage area on apron 4]]'''Scenery in TerraSync:''' The hub (warehouse, hangar and aprons) is modelled in the scenery. In 2012 its redesign for TerraSync started. First all lampposts at apron 4 had been replaced with those which fit into the correct layout of every single parking position. Afterwards lots of goods and ground vehicles where placed. As soon as some missing storage buildings are modelled, the new content of apron 4 will be published on TerraSync. Last modifications will take place when the new [[Airport data (apt.dat) update|850-standard layout]] of EDDP will be created in the future.

'''DHL-hub at EDDP in Flightgear:''' Leipzig/Halle Airport offers ground space for more than 70 Boeing [[757-200|757-PF]] or up to 50 [[777F]] as well as space for 10 [[Antonov An-124|An-124]] at Apron 2, 4 and 5. Airmail flights can be flown from and to EDDP. One of the middle sized and highly connected hubs of DHL, the [[Orio al Serio Airport]] (Italy) is also modelled in FlightGear and can be used for realistic flights out of Leipzig/Halle Airport.
In FlighGear apron 4 is equipped with all stands. Additionally to the main apron lightning each stand has one centred lamppost, which will be replaced by a VDGS-signs in the future. Ground markings will come with the new 850-layout. The major storage buildings from DHL are modelled as well as three DHL-tanks south from apron 4.

=== De-icing areas ===
Leipzig/Halle Airport has four special areas, two in the north at taxiway C and two in the south at taxiway N. In FlightGear only the two areas at taxiway C are build into the layout. In 2012 both areas had been equipped with shared models like lampposts, buildings and ground lights.

==== De-icing area 2 - multiplayer ready ====

Based on the Zurich type model "Elephant" - originally modelled by Oliver Thurau - an improved version with full multiplayer support is under development. This version isn't only adapted to the special efforts at EDDP, but its also designed to be controlled by ATC. It will be published via TerraSync in November 2014.

== Surroundings and "Other" ==

=== Kursdorf - the village within the airport ===
There is a village right in middle of the airport. So it's no surprise the number of inhabitants is shrinking each year. Once a thriving village with 537 inhabitants in 1950, they were down to 119 in 2006 [http://de.wikipedia.org/wiki/Kursdorf_%28Schkeuditz%29 (Wikipedia)]. It might be a little loud with the two runways, highway and express railways, but the transport links, hey ... The village is modelled in the scenery.

== Scenery ==
{|
| Authors: ||
* Models: David G., D-STHO
* Airport layout: Christian Schmitt
* Additional models: Don Lavelle, Alex Park, Robert Shearman
* Redesigning & Development 2012: [[User:August|August]], D-STHO
|-
|}

=== Download via GIT ===
With FlightGear 3.0 a new world scenery was published, including a new but incorrect 850-layout for EDDP. Developers started a huge overhaul of the EDDP scenery in April 2014. First a new taxiway layout was programmed. Additionally all buildings and objects are replaced. Some models will be remodelled, others will be added. Due to the fact that airport layouts can't be simply updated via TerraSync in a short way, pilots are asked to use the new EDDP CUSTOM SCENERY as long as things aren't updated at TerraSync.

* Download-Development-Scenery
* updated regularly
** '''git clone''' [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/ https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/]
** or [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/archive/5a25c94d403f09e5b5bf4d72117e297191acb3ce.tar.gz download a ZIP] (101 MB)

=== Download via TerraSync ===
[[TerraSync]] has it all! There is no custom scenery existing (only the GIT-repository for testing the new 850-layout before publishing it). The authors believe on the advantages of TerraSync which makes it easy for every user to have the latest scenery installed automatically. Updates are published regularly via TerraSync.
* Next update in '''<daysuntil in="days">12-August-2014</daysuntil>''' {{Progressbar|height=45|percentage={{#expr: trunc ({{#time: z}} - {{#time: z | May 19 2014 }}) round -1 }}}}

* '''Latest update on TerraSync:'''
** '''2014-04-29''' ''Objects adapted to new (but incorrect) 850-layout''

* Last five updates:
** '''2013-04-21''' ''Rembrandt lights at apron 1''
** 2013-02-13 ''new Messeturm at final approach area of runway 26R''
** 2012-12-21 ''new luggage terminal at apron 1''
** 2012-10-22 ''three new DHL-tanks placed at DHL-area''
** 2012-09-20 ''new VisualGuidingDockingSystem at terminal B''

=== Development ===
Since the Scenery had been modelled by [[User:D-79|D-79]] in 2010, D-STHO and [[User:August|August]] started enhancements and redesigning in 2012. In 2014 development of a new 850-layout started. Improvements are made on the following objects:

'''Layout''' 
* Taxiway bridges: new Position, improved lightning ''(published 07/2012)'' {{tick}}
* New 850-standard: new Layout with all parking positions and improved taxiways {{progressbar|90}} (see [[#Download_via_GIT]])

'''Scenery (Shared Models)''' 
* Airport lightning: more than 80 lampposts ([[EDDM]]-model) on Apron 1 and 4 and both northern de-icing areas ''(published 07/2012)'' {{tick}}
* DHL-tanks at apron 4 ''(published 10/2012)'' {{tick}}
* Ground traffic: lots of goods and vehicles (shared) make apron 1 and 4 much more realistic ''(published 08/2012)'' {{tick}}
* Flora and boundaries: Trees and fences on Apron 1, 2 and 4 are added ''(published 08/2012)'' {{tick}}
* New shared ground vehicles
** Container dolly ''(under development)'' {{hourglass}}
** Luggage dolly ''(under development)'' {{hourglass}}
** Pallet dolly ''(planned)''
* New shared Unit Load Devices (ULD)
** Airfreight container - Type AKH ''(pre-development)'' {{hourglass}}
** Airfreight pallet ''(planed)''
* Village and industrial surroundings: Kursdorf within the airport and industrial areas around are created with shared models ''(published 04/2010)'' {{tick}}

'''Buildings and infrastructure (Static models)''' 
* Cargo-hangar apron 3 ''(planned)''
* Cargo-center apron 2 ''(published 2010)'' {{tick}}
* DHL-hangar ''(published 2010)'' {{tick}}
* DHL-terminal ''(published 2010)'' {{tick}}
* Interactive DE-ICING areas (Multiplayer supported) {{hourglass}}
* Interactive luggage dolly traffic between terminal B and lugage terminal ''(planned)''
* Luggage terminal ''(published 12/2012)'' {{tick}}
* Storage buildings at DHL-area ''(pre-development)'' {{hourglass}}
* Terminal B ''(published 04/2010)'' {{tick}}
* Terminal C ''(published 08/2012)'' {{tick}}
* Tower ''(published 2010)'' {{tick}}
* Turbo engine hall ''(pre-development)'' {{hourglass}}
* Old Tower next to terminal B ''(pre-development)'' {{hourglass}}
* Visual Docking Guiding System at Apron 4 ''(planned)''
* Visual Docking Guiding System at Terminal B ''(published 09/2012)'' {{tick}}
* Visual Docking Guiding System: replacement with animated interactive version ''(planned)''
'''Rembrandt lightning improvements'''
* Converting Lightning to [[Project Rembrandt|Rembrandt]]
** Rembrandt lights at apron 1 ''(published 04/2013)'' {{tick}}
** Rembrandt lights at apron 2 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 3 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 4 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 5 {{progressbar|90}} (see [[#Download_via_GIT]])
* Converting Buildings to [[Project Rembrandt|Rembrandt]] Lightning
** Luggage terminal ''(pre-development)'' {{hourglass}}
** Terminal B ''(planned)''
** Terminal C ''(planned)''
** Tower ''(planned)''
** DHL-hangar ''(planned)''
* Lampposts in EDDP-style ''(planned)''

'''Buildings at the city of Leipzig (Static models)''' 
* City-Hochhaus {{progressbar|90}}
* Wintergartenhochhaus ''(published 02/2013)'' {{tick}}
* Völkerschlachtdenkmal (Battle of Nations Monument) {{hourglass}}
* Red-Bull Arena {{hourglass}}
* Gondwanaland (tropical zoo) ''(published 02/2013)'' {{tick}}
* DVB-T-Tower ''(published 02/2013)'' {{tick}}
* Messeturm Leipzig ''(published 02/2013)'' {{tick}}
* Hauptbahnhof (Central Station) ''(planned)''

=== Scenery since 2014 ===
<gallery mode=packed widths=180px heights=180px>
2014 new-layout-EDDP 04.jpg|Redesigned Layout: Taxiway T - new ground textures
2014 new-layout-EDDP 01.jpg|Redesigned Layout: Runway 26L with DHL-area
2014 new-layout-EDDP 02.jpg|Redesigned Layout: Apron 4
</gallery>

=== Scenery since 2012 ===
[[File:EDDP TerminalC.jpeg|Terminal C]] [[File:EDDP VDGS-136 thumbnail.jpg|VDGS at position 136]] [[File:EDDP-DHL-tank.jpeg|DHL-Tank at fuel storage area on apron 4]] [[File:EDDP_luggageterminal_thumb.jpg|Luggage Terminal at Apron 1]]

=== Scenery since 2010 ===
Here is a selection of the models. [http://www.youtube.com/watch?v=3kNDGiSNUdE YouTube video 2010].

[[File:EDDP10.jpg]] [[File:EDDP11.jpg]] [[File:EDDP12.jpg]] [[File:EDDP13.jpg]] [[File:EDDPbridge1.png]]

== Related content ==
* [[Germany]]
* [[Leipzig/Halle Airspace]]

== External links ==
* [http://www.vacc-sag.org/airport/EDDP Airport Diagrams]
* [http://de.wikipedia.org/wiki/EDDP Leipzig/Halle Airport at Wikipedia] (German)

[[Category:Airports in Germany]]

Leipzig/Halle Airport

2014-06-29T12:19:53Z

August: /* Scenery */ new layout 2014

{{infobox Airport
|name = Leipzig/Halle Airport
|image =EDDP TerminalC.jpeg
|alt =New terminal C (published 2012)
|iata =LEJ
|icao =EDDP
|type =Public
|city =Between Leipzig and Halle
|owner =Mitteldeutsche Airport Holding
|website =http://www.leipzig-halle-airport.de/
|scenerytile =e012n51
|download =
|terrasync = [[#Download_via_GIT]] for latest scenery
|runway= 08L/26R
|length= 11,811 ft
|material= Concrete (in FG still Asphalt)
|runway2= 08R/26L
|length2= 11,811 ft
|material2= Concrete (in FG still Asphalt)
}}

'''Leipzig/Halle Airport''' is located in Schkeuditz, Saxony and serves both Leipzig, Saxony and Halle, Saxony-Anhalt, [[Germany]]. In Flightgear this airport was published on [[TerraSync|TerraSync]] in 2010 und updated due to new developments 2012. In 2014 according to the new world scenery a complete overhaul started.
EDDP is also the centre of Leipzig/Halle airspace, which provides air traffic control also for the regional airfield [[Leipzig-Altenburg Airport]].

{{Note|Currently users are asked to test the '''beta Version of the new 850-Layout''' (see [[#Download_via_GIT]])}}

However, if you want something to be configurable, one important thing is having an element ID that we can refer to, in order to look up the key and modify the symbol via Nasal. Without having an element id (e.g. for labels) we cannot easily modify such SVG images procedurally.}}
== Flying at Leipzig/Halle airspace ==

=== Charts ===
All [http://www.vacc-sag.org/airport/EDDP diagrams and charts] are available for download.

=== Runways and ILS ===

==== Runway 08L/26R ====
[[File:2012-09 Apron4 Luftbild-at-night.png|thumb|270px|Apron 4 and runway 26L at night]]The northern [[runway]] is 3600m long with a width of 45m. In real life its usually used by passenger airliners. In Flightgear this runway is equipped with Outer Marker and Middle Marker and offers best conditions for '''low visibility operations'''.
* ILS-CAT-III '''08L''' (083°): 108.55
* ILS-CAT-III '''26R''' (263°): 108.35
==== Runway 08R/26L ====
The southern [[runway]] is 3600m long with a width of 60m. In real life its mostly used by freighters due to its proximity to freight areas (Apron 2 and 4). It has no Outer Marker an no Middle Marker.
* ILS-CAT-III '''08R''' (083°): 111.90 (111.75 in FG older than Version 2.0.0)
* ILS-CAT-III '''26L''' (263°): 110.30

=== ATC ===
* Leipzig Ground - frequency 121.800
* Leipzig Tower - frequency 121.100

Leipzig/Halle Airport is regularly served by Air Traffic Control ([[ATC]]).

== Infrastructure ==
[[File:EDDP-overview-daytime.jpg|thumb|270px|Overview 2012]]Connected by terminal C and three taxiway bridges (W1, E7, E8) the airport layout combines the northern part with runway 08L/26L and Apron 3 (new cargo area since 2012) and the southern part with Apron 1 (terminal B), runway 08R/26L, Apron 2, Apron 4 (DHL), Apron 5. Between both parts an airport railway station and the autobahn A14 is connecting to the check-in area of terminal C. Railway and motorway are not modelled in Flightgear.

=== Access and connection ===
[[File:TerminalC-morning.jpg|thumb|270px|Terminal C at dawn]]
==== Terminal C ====
In August 2012 the completely new modelled terminal C was published on TerraSync. It is built as a connection between the check-in building with car-park and train station in the north and the departure area at terminal B in the south. Due to this efforts it stands on piers like a long bridge from apron 1 to apron 3, crossing different car-parks, a rail-track and the autobahn.
On the one hand the FlighGear model tries to give the airport a well designed model with highly detailed structures, but on the other hand it was programmed as simple as possible to save visitors simulation performance.

==== Taxiway bridges ====
[[File:EDDP-Taxibridges-e7e8-night.jpg|thumb|270px|Rampbridges E7, E8 with new lightning in 2012]]A highway and railway lines go straight between the two runways. Three bridges connect the terminal with the northern runway. The western bridge (taxiway W1) is used in both directions. The eastern bridges (taxiways E7 and E8) are used as one way taxiways. Due to safety improvements all bridges are equipped with special taxi lights.
Due to changes in the TerraData the bridges had to be repositioned in 2012.

=== Apron 1 ===

The main apron at Leipzig/Halle Airport is located in the middle of the airport. It houses the commercial aviation area at terminal B in the west and the general aviation area in the eastern part. It is connected by taxiways L, N and W1.

==== Terminal B ====
[[File:EDDP VDGS-134 thumbnail.jpg|thumb|270px|VDGS on each gateway at terminal B]]'''Real world''':
This building is the main terminal for most commercial flights at EDDP. It is connected to terminal C in the north and provides the passenger transfer to Apron 1 via 6 gateways. It also has a connection to the luggage terminal.

'''Scenery in TerraSync''':
In Flightgear the main terminal is modelled very slim and efficiently. 6 unmovable gateways link to park positions 126, 128, 130, 132, 134 and 136. In 2012 it will be improved. Since September 2012 it has been equipped with a non-animated [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System VDGS].

==== Luggage terminal ====
This building was first published in 2004 and remodelled by Thomas Großberger in 2012. The terminal is connected via the old tower next to it to terminal A by a tube, which is used to transport luggage between the checkin- and arrival-area and Apron 1. Both. the connection and the old tower building will be modelled in 2013. The new luggage terminal in FlightGear is offering:
* realistic roof design
* simplified but detailed interior
* 6 clock controlled automatic gates
* complex light design (Rembrandt-Design outstanding)

==== GAT ====

=== Apron 2 ===

=== Apron 3 ===
This Apron in real life went into service with a new cargo hangar in 2012. In Flightgear it is still closed. The corresponding facilities are still under development.

=== Apron 4/5 (DHL-area) ===
[[File:2012-08 Apron4 Pos432 BOX1522-D-STHO-and-DC10.png|thumb|270px|DHL-area at apron 4]]'''Real world:''' Leipzig/Halle is just a small international airport. But in 2008 it became the [http://www.dp-dhl.com/en/logistics_around_us/from_our_divisions/leipzig_hub.html European DHL hub] with up to 60 planes per night. The DHL Hub Leipzig GmbH, place of business in Schkeuditz, is running under contract to the logistic group DHL at Leipzig/Halle Airport one of six international aviation hubs. In order to provide maintenance to the new fleet the [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig GmbH] was founded. European Air Transport operates services to Europe, Middle East and Africa. 56 countries are covered in total. A second aviation company, called [http://en.wikipedia.org/wiki/Aerologic AeroLogic], was founded in EDDP. AeroLogic GmbH, a joint-venture between DHL Express and Lufthansa Cargo, is a German cargo airline headquartered in Schkeuditz, Saxony. It operates cargo flights out of Leipzig/Halle Airport and Frankfurt, most of which are on behalf of its parent companies.

{| class="wikitable" cellpadding="3" style="margin-left:auto; margin-right:auto"
|+ '''Fleet of [http://en.wikipedia.org/wiki/Aerologic AeroLogic] and [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig] and others''' (2012)
|-
!Aircraft
!Total
!Orders
!Oparator
|-
|[[Airbus A300|Airbus A300B4-203F]]
|<center>10</center>
|
|Air Contractors
|-
|[[Airbus A300|Airbus A300-600RF]]
|<center>8</center>
|<center>10</center>
|European Air Transport Leipzig
|-
|Boeing 737-300F
|<center>9</center>
|
|European Air Transport Leipzig
|-
|Boeing 737-400F
|<center>1</center>
|
|Europe Airpost
|-
|[[Boeing 757|Boeing 757-236SF]]
|<center>10</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 757|Boeing 757-23APF]]
|<center>1</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 777F]]
|<center>8</center>
|
|AeroLogic
|-
!Total
!47
!10
!colspan=2|
|}

[[File:EDDP-DHL-tank.jpeg|thumb|270px|DHL-Tank at fuel storage area on apron 4]]'''Scenery in TerraSync:''' The hub (warehouse, hangar and aprons) is modelled in the scenery. In 2012 its redesign for TerraSync started. First all lampposts at apron 4 had been replaced with those which fit into the correct layout of every single parking position. Afterwards lots of goods and ground vehicles where placed. As soon as some missing storage buildings are modelled, the new content of apron 4 will be published on TerraSync. Last modifications will take place when the new [[Airport data (apt.dat) update|850-standard layout]] of EDDP will be created in the future.

'''DHL-hub at EDDP in Flightgear:''' Leipzig/Halle Airport offers ground space for more than 70 Boeing [[757-200|757-PF]] or up to 50 [[777F]] as well as space for 10 [[Antonov An-124|An-124]] at Apron 2, 4 and 5. Airmail flights can be flown from and to EDDP. One of the middle sized and highly connected hubs of DHL, the [[Orio al Serio Airport]] (Italy) is also modelled in FlightGear and can be used for realistic flights out of Leipzig/Halle Airport.
In FlighGear apron 4 is equipped with all stands. Additionally to the main apron lightning each stand has one centred lamppost, which will be replaced by a VDGS-signs in the future. Ground markings will come with the new 850-layout. The major storage buildings from DHL are modelled as well as three DHL-tanks south from apron 4.

=== De-icing areas ===
Leipzig/Halle Airport has four special areas, two in the north at taxiway C and two in the south at taxiway N. In FlightGear only the two areas at taxiway C are build into the layout. In 2012 both areas had been equipped with shared models like lampposts, buildings and ground lights.

==== De-icing area 2 - multiplayer ready ====

Based on the Zurich type model "Elephant" - originally modelled by Oliver Thurau - an improved version with full multiplayer support is under development. This version isn't only adapted to the special efforts at EDDP, but its also designed to be controlled by ATC. It will be published via TerraSync in November 2014.

== Surroundings and "Other" ==

=== Kursdorf - the village within the airport ===
There is a village right in middle of the airport. So it's no surprise the number of inhabitants is shrinking each year. Once a thriving village with 537 inhabitants in 1950, they were down to 119 in 2006 [http://de.wikipedia.org/wiki/Kursdorf_%28Schkeuditz%29 (Wikipedia)]. It might be a little loud with the two runways, highway and express railways, but the transport links, hey ... The village is modelled in the scenery.

== Scenery ==
{|
| Authors: ||
* Models: David G., D-STHO
* Airport layout: Christian Schmitt
* Additional models: Don Lavelle, Alex Park, Robert Shearman
* Redesigning & Development 2012: [[User:August|August]], D-STHO
|-
|}

=== Download via GIT ===
With FlightGear 3.0 a new world scenery was published, including a new but incorrect 850-layout for EDDP. Developers started a huge overhaul of the EDDP scenery in April 2014. First a new taxiway layout was programmed. Additionally all buildings and objects are replaced. Some models will be remodelled, others will be added. Due to the fact that airport layouts can't be simply updated via TerraSync in a short way, pilots are asked to use the new EDDP CUSTOM SCENERY as long as things aren't updated at TerraSync.

* Download-Development-Scenery
* updated regularly
** '''git clone''' [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/ https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/]
** or [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/archive/5a25c94d403f09e5b5bf4d72117e297191acb3ce.tar.gz download a ZIP] (101 MB)

=== Download via TerraSync ===
[[TerraSync]] has it all! There is no custom scenery existing (only the GIT-repository for testing the new 850-layout before publishing it). The authors believe on the advantages of TerraSync which makes it easy for every user to have the latest scenery installed automatically. Updates are published regularly via TerraSync.
* Next update in '''<daysuntil in="days">12-August-2014</daysuntil>''' {{Progressbar|height=45|percentage={{#expr: trunc ({{#time: z}} - {{#time: z | May 19 2014 }}) round -1 }}}}

* '''Latest update on TerraSync:'''
** '''2014-04-29''' ''Objects adapted to new (but incorrect) 850-layout''

* Last five updates:
** '''2013-04-21''' ''Rembrandt lights at apron 1''
** 2013-02-13 ''new Messeturm at final approach area of runway 26R''
** 2012-12-21 ''new luggage terminal at apron 1''
** 2012-10-22 ''three new DHL-tanks placed at DHL-area''
** 2012-09-20 ''new VisualGuidingDockingSystem at terminal B''

=== Development ===
Since the Scenery had been modelled by [[User:D-79|D-79]] in 2010, D-STHO and [[User:August|August]] started enhancements and redesigning in 2012. In 2014 development of a new 850-layout started. Improvements are made on the following objects:

'''Layout''' 
* Taxiway bridges: new Position, improved lightning ''(published 07/2012)'' {{tick}}
* New 850-standard: new Layout with all parking positions and improved taxiways {{progressbar|90}} (see [[#Download_via_GIT]])

'''Scenery (Shared Models)''' 
* Airport lightning: more than 80 lampposts ([[EDDM]]-model) on Apron 1 and 4 and both northern de-icing areas ''(published 07/2012)'' {{tick}}
* DHL-tanks at apron 4 ''(published 10/2012)'' {{tick}}
* Ground traffic: lots of goods and vehicles (shared) make apron 1 and 4 much more realistic ''(published 08/2012)'' {{tick}}
* Flora and boundaries: Trees and fences on Apron 1, 2 and 4 are added ''(published 08/2012)'' {{tick}}
* New shared ground vehicles
** Container dolly ''(under development)'' {{hourglass}}
** Luggage dolly ''(under development)'' {{hourglass}}
** Pallet dolly ''(planned)''
* New shared Unit Load Devices (ULD)
** Airfreight container - Type AKH ''(pre-development)'' {{hourglass}}
** Airfreight pallet ''(planed)''
* Village and industrial surroundings: Kursdorf within the airport and industrial areas around are created with shared models ''(published 04/2010)'' {{tick}}

'''Buildings and infrastructure (Static models)''' 
* Cargo-hangar apron 3 ''(planned)''
* Cargo-center apron 2 ''(published 2010)'' {{tick}}
* DHL-hangar ''(published 2010)'' {{tick}}
* DHL-terminal ''(published 2010)'' {{tick}}
* Interactive DE-ICING areas (Multiplayer supported) {{hourglass}}
* Interactive luggage dolly traffic between terminal B and lugage terminal ''(planned)''
* Luggage terminal ''(published 12/2012)'' {{tick}}
* Storage buildings at DHL-area ''(pre-development)'' {{hourglass}}
* Terminal B ''(published 04/2010)'' {{tick}}
* Terminal C ''(published 08/2012)'' {{tick}}
* Tower ''(published 2010)'' {{tick}}
* Turbo engine hall ''(pre-development)'' {{hourglass}}
* Old Tower next to terminal B ''(pre-development)'' {{hourglass}}
* Visual Docking Guiding System at Apron 4 ''(planned)''
* Visual Docking Guiding System at Terminal B ''(published 09/2012)'' {{tick}}
* Visual Docking Guiding System: replacement with animated interactive version ''(planned)''
'''Rembrandt lightning improvements'''
* Converting Lightning to [[Project Rembrandt|Rembrandt]]
** Rembrandt lights at apron 1 ''(published 04/2013)'' {{tick}}
** Rembrandt lights at apron 2 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 3 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 4 {{progressbar|90}} (see [[#Download_via_GIT]])
** Rembrandt lights at apron 5 {{progressbar|90}} (see [[#Download_via_GIT]])
* Converting Buildings to [[Project Rembrandt|Rembrandt]] Lightning
** Luggage terminal ''(pre-development)'' {{hourglass}}
** Terminal B ''(planned)''
** Terminal C ''(planned)''
** Tower ''(planned)''
** DHL-hangar ''(planned)''
* Lampposts in EDDP-style ''(planned)''

'''Buildings at the city of Leipzig (Static models)''' 
* City-Hochhaus {{progressbar|90}}
* Wintergartenhochhaus ''(published 02/2013)'' {{tick}}
* Völkerschlachtdenkmal (Battle of Nations Monument) {{hourglass}}
* Red-Bull Arena {{hourglass}}
* Gondwanaland (tropical zoo) ''(published 02/2013)'' {{tick}}
* DVB-T-Tower ''(published 02/2013)'' {{tick}}
* Messeturm Leipzig ''(published 02/2013)'' {{tick}}
* Hauptbahnhof (Central Station) ''(planned)''

=== Scenery since 2014 ===
<gallery mode=packed widths=180px heights=180px>
2014 new-layout-EDDP 04.jpg|Redesigned Layout: Taxiway T - new ground textures
2014 new-layout-EDDP 01.jpg|Redesigned Layout: Runway 26L with DHL-area
2014 new-layout-EDDP 02.jpg|Redesigned Layout: Apron 4
</gallery>

=== Scenery since 2012 ===
[[File:EDDP TerminalC.jpeg|Terminal C]] [[File:EDDP VDGS-136 thumbnail.jpg|VDGS at position 136]] [[File:EDDP-DHL-tank.jpeg|DHL-Tank at fuel storage area on apron 4]] [[File:EDDP_luggageterminal_thumb.jpg|Luggage Terminal at Apron 1]]

=== Scenery since 2010 ===
Here is a selection of the models. [http://www.youtube.com/watch?v=3kNDGiSNUdE YouTube video 2010].

[[File:EDDP10.jpg]] [[File:EDDP11.jpg]] [[File:EDDP12.jpg]] [[File:EDDP13.jpg]] [[File:EDDPbridge1.png]]

== Related content ==
* [[Germany]]
* [[Leipzig/Halle Airspace]]

== External links ==
* [http://www.vacc-sag.org/airport/EDDP Airport Diagrams]
* [http://de.wikipedia.org/wiki/EDDP Leipzig/Halle Airport at Wikipedia] (German)

[[Category:Airports in Germany]]

FlightGear Newsletter June 2014

2014-06-29T12:06:42Z

August: /* Airports */ adding new article about EDDP

{{newsletter}}
{{TOC_right|limit=2}}
{{Newsletter being written}}

== Development news ==
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].

=== FlightGear 3.2 - Feature Freeze ===

{{FGCquote
|Hi all, 
 
this is just a short reminder that yesterday, we entered our scheduled 
feature freeze state for the next release. 
 
Please use the next four weeks to improve the existing features, harden 
and cleanup the code, edit the ChangeLog 
(http://wiki.flightgear.org/Next_Changelog), improve the Manual, 
document the undocumented etc. etc. 
 
I'll create the release branches on July 17th to have the release ready 
by Aug. 17th. 
 
Torsten 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32475295/
|title=<nowiki>[Flightgear-devel] Feature Freeze for 3.2</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2014-06-18</nowiki>
}}
}}
=== Canvas GUI: MessageBox Support ===
Thanks to Tom's and James' recent work on the upcoming [[Aircraft Center]] for downloading and switching between aircraft without having to exit FlightGear, beginning with FlightGear 3.2, FlightGear's [[Canvas]]-based GUI will contain support for so called [[Canvas MessageBox|Message Boxes]]:
{|
|- style="vertical-align:top;"
| [[File:Canvas-MessageBox-demo information.png|link=]] ||
<syntaxhighlight lang="nasal">
canvas.MessageBox.info("Success", "The operation has successfully completed.");
</syntaxhighlight>
|- style="vertical-align:top;"
| [[File:Canvas-MessageBox-demo question.png|link=]] ||
<syntaxhighlight lang="nasal">
canvas.MessageBox.question(
"Do you want it?",
"The question is: Do you want to get a real question?.",
func(sel)
{
if( sel == canvas.MessageBox.Yes )
print("I only know that the answer is 42.");
else
print("Ok, I will not give you a real question.");
}
);
</syntaxhighlight>
|- style="vertical-align:top;"
| [[File:Canvas-MessageBox-demo warning dont-show-again.png|link=]] ||
<syntaxhighlight lang="nasal">
canvas.MessageBox.warning(
"Warning...",
"Have you read this warning? If you want it will not be shown again.",
func(sel)
{
if( sel != canvas.MessageBox.Ok )
return;

print("You have been warned. Let the games begin...");
},
canvas.MessageBox.Ok
| canvas.MessageBox.Cancel
| canvas.MessageBox.DontShowAgain
);
</syntaxhighlight>
|}

=== Logo Proposal ===
This is the new logo badge concept proposal for FlightGear designed by Michat.

[[File:Fglogo1.png]]
[[File:Fglogowiki.png]]
[[File:Fglogoforum.png]]

===MapStructure stress-testing ===

[[File:Map-canvas-mapstructure-performance.png|thumb|stress-testing [[MapStructure]] using the ufo @ KSFO circling at 2000 kts in a climb, see [http://forum.flightgear.org/viewtopic.php?f=71&t=21509&p=211611#p211611] ]]

{{cquote
|<nowiki>Now that Hyde has committed Philosopher's latest changes, I'd be interested in getting some more feedback on performance.</nowiki> <nowiki>
Here, I am using the ufo @ksfo circling in a shuttle climb at >= 2000 kts GS and getting roughly 30 fps and 40-60 ms.</nowiki>
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211611#p211611
|title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Tue Jun 03</nowiki>
}}
}}

=== 777 EFB Prototype by I-NEMO ===
[[File:777-EFB-MAIN.png|thumb|777-200ER EFB [http://forum.flightgear.org/viewtopic.php?f=71&t=23196]]]
[[File:777-EFB-AIRPORT-SEARCH.png|thumb|777-200 EFB AIRPORT SEARCH, see [http://forum.flightgear.org/viewtopic.php?f=71&t=23196&p=211410#p211410]]]

I-NEMO has started porting his 777/EFB prototype to [[Canvas]]

{{cquote
|<nowiki>As I wrote several times, I finally decided to put hands on the EFB (Reason: No one ever took care of developing an EFB for the 777; a 'working' EFB, though) with two (2) main goals in mind:</nowiki> <nowiki>
</nowiki> <nowiki>
1) to do something to compensate for the lacking of an EFB inside the Seattle.</nowiki> <nowiki>
2) to actually try (I repeat it: 'try') to learn some first essentials of nasal.</nowiki> <nowiki>
</nowiki>
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211550#p211550
|title=<nowiki>Re: 777 EFB status & plans ?</nowiki>
|author=<nowiki>I-NEMO</nowiki>
|date=<nowiki>Mon Jun 02</nowiki>
}}
}}

{{cquote
|<nowiki> this Seattle EFB is just a 'rude' one: with this term, I mean (as a word's pun) 'unpolite'. I'm perfectly aware that the coding is horrible, clumsy, repetitive, silly and very, very far from what it should be. </nowiki> <nowiki>
My first aim was simply to have a somehow 'working' EFB inside the Seattle's Cockpit.</nowiki> <nowiki>
</nowiki> <nowiki>
My second aim was to use EFB.nas as a starting playground for a newbie as I am on 'nasal'. </nowiki>
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211550#p211550
|title=<nowiki>Re: 777 EFB status & plans ?</nowiki>
|author=<nowiki>I-NEMO</nowiki>
|date=<nowiki>Mon Jun 02</nowiki>
}}
}}

{{cquote
|<nowiki>I do not pretend that current 777's EFB.nas is a piece of nice software; but - to my initial purpose - it works. Not completely, not nicely, not properly...but it's a starting point. At least, it works...</nowiki>
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211550#p211550
|title=<nowiki>Re: 777 EFB status & plans ?</nowiki>
|author=<nowiki>I-NEMO</nowiki>
|date=<nowiki>Mon Jun 02</nowiki>
}}
}}

{{FGCquote
|Current development ('modernisation' phase) of the '''Boeing 777 Seattle's EFB''' is going on nicely; the code is shorter, more readable and cleaner. 
I have not finished it, yet (I'd say that it's almost 50% done).
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213104#p213104
|title=<nowiki>Re: 777 EFB: initial feedback</nowiki>
|author=<nowiki>I-NEMO</nowiki>
|date=<nowiki>Sat Jun 21</nowiki>
}}
}}

{{FGCquote
|At the moment I have a single Canvas group (i.e., ''EFB_group''), with 5 children: the text-matrix (16 left lines, 16 right lines), a Title line , an Helper line and the Display. 
The ''Display'' element is then textured with all the various pages' textures, called by the page-handler (''see'' here below). 
Currently, I'm using the .jpg textures which I had previously generated through Photoshop; in the future they might be replaced by .svg files, depending from actual interactive use of some graphical objects (a few EFB pages do need interaction with graphical parts). Besides - if i'm not wrong - I've read somewhere on the FGWiki that gradients are not handled by the SVG parser...and I do like to use some gradients effects (antialiasing and such) to achieve a sort of realism on the displays.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213104#p213104
|title=<nowiki>Re: 777 EFB: initial feedback</nowiki>
|author=<nowiki>I-NEMO</nowiki>
|date=<nowiki>Sat Jun 21</nowiki>
}}
}}

{{FGCquote
|that's the current status of the new 777 ''Seattle'''s EFB: it's still far from being perfect, but - as a newbie - I'm quite satisfied for the moment: I need to finish the first version fairly soon, because my to-do-list is long (I have to re-model all the aircraft fuselage [original model has wrong measures, ''sigh!''], produce better gears and flight-control surfaces model & animations in Blender, and then to produce a new Paint-Kit in Photoshop; then all 3D models optimizations...and so forth; of course, we also have to take care of CDU, which will interface with the EFB. So, the job is still very, very long...
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213104#p213104
|title=<nowiki>Re: 777 EFB: initial feedback</nowiki>
|author=<nowiki>I-NEMO</nowiki>
|date=<nowiki>Sat Jun 21</nowiki>
}}
}}

{{FGCquote
|The current EFB code is heavily focused on rendering raster images, which can be retained obviously, but in FG, we have additional means to render airport information that is 100% in sync with the FG side of things (navdb). 
 
For instance, we are going to "port" the airport-selection dialog to move rendering of airports/runways/taxiways/parking spots into dedicated MapStructure layers that can be properly styled and customized: [[Canvas_MapStructure#Porting_the_airports.xml_dialog]] 
 
[[File:Airport-selection-dialog.png|250px]] 
 
As you can probably tell, these kinds of layers would be very useful for any kind of EFB related application. 
 
As long as the underlying design for a "page"-based MFD framework is sufficiently generic, we can easily replace/augment raster images and procedurally created charts - we could even use the built-in support for fetching via HTTP to download images on-line. In fact, we could then even extend Canvas to directly support rendering PDFs (OSG supports this out-of-the-box), this would make many steps unnecessary, because we could directly access [http://airnav.com http://airnav.com] without having to download/convert/ship any imagery. The code required to pull this off would be very compact in comparison.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213084#p213084
|title=<nowiki>Re: 777 EFB: initial feedback</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sat Jun 21</nowiki>
}}
}}

Learn more at [[Canvas EFB Framework]] ...

=== Canvas Garmin GPSMap196 Updates ===

[[File:Gpsmap196-canvas-panel-page.png|thumb|F-JJTH has updated the SVG file implementing the panel page for the [[Garmin GPSMap 196]]]]

=== Avidyne Entegra R9 ===

[[File:Extra500canvas.png|thumb|Work has begun to analyze, refactor and generalize useful parts of the [[Avidyne Entegra R9]] to help reuse some code in similar MFD efforts, like the [[Garmin GPSMap 196]] or [[Canvas EFB Framework]]]]

=== Towards an Aircraft-agnostic MFD Framework ===

[[File:Canvas-mfd-framework-prototyping.png|thumb|This is an adapted version of the [[Garmin GPSMap 196]] that is currently being developed by F-JJTH. Here, the whole instrument is entirely set up in XML space, including buttons/event handling, but also the embedded canvas region that serves as the 'screen'. The idea is to allow arbitrary MFDs to be specified in an aircraft-agnostic fashion, including displays like a PFD, [[NavDisplay]] or EFB. For details, please see [[Canvas Glass Cockpit Efforts]].]]

[[File:Canvas-mfd-framework-prototyping-with-mapstructure.png|400px|thumb|This demonstrates how a purely XML-based MFD framework can instantiate dynamic [[MapStructure]] layers - none of this involves any [[Nasal]] coding now, it's just an XML file - to learn more, see [[Canvas Glass Cockpit Efforts]].]]

[[File:Canvas-mfd-framework-prototyping-with-mapstructure-with-kln89-skin.png|400px|thumb|This screen shot shows the texture of the hard-coded KLN89 instrument used as a skin/theme for the MFD instrument, with a MapStructure-powered map shown.]]

=== Canvas System ===
{{FGCquote
|The upcoming FlightGear version (3.2) will contain a canvas-based map dialog, including a modular "plugin" system for creating custom map layers and charts with roughly ~50 lines of code, most of it boilerplate. This is entirely XML/Nasal based (scripted) - symbols can be pretty much anything, raster or vector images (png or svg), but even animated. Styling can be customized, too. For more info, I suggest to check out: [[MapStructure#Porting_the_map_dialog|http://wiki.flightgear.org/MapStructure ... map_dialog]] [[File:MapStructureDialog.png|250px]] You can basically create arbitrary layers, even for custom objects/positions: [[File:Map-canvas-chain-home-editor.png|250px]] The same method can be used for creating a "live" radar display: [[Canvas_Radar|http://wiki.flightgear.org/Canvas_Radar]] [[File:MapStructure-TFC-Troubleshooting.png|250px]] But maps and layers can be fairly sophisticated, too - all 100% scripted: [[FlightGear_Newsletter_May_2014#A_Canvas-based_Map_dialog|http://wiki.flightgear.org/FlightGear_N ... Map_dialog]] [[File:Map-canvas-dialog-storms-overlay.png|250px]] As long as you use the MapStructure framework, all layers can be easily used in dialogs AND instruments Coding-wise, there isn't too much involved these days, all the details are covered in the MapStructure article.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=212558#p212558
|title=<nowiki>Re: Get objects to show up on Map/Radar</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sat Jun 14</nowiki>
}}
}}

[[File:Aircraft-center-prototype.png|500px|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]]

=== Missions & Adventures ===
[[File:Missionb.png|thumb]]

{{forum|79|Tutorials, Missions & Adventures}}

=== High Level Architecture ===

=== Usability Improvements ===

== Release ChangeLog ==
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.

== Interview with a contributor (NAME) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* How long have you been involved in FlightGear?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?

More questions are being collected here: [[Interview questions]].

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==
=== Damage and disintegration ===
{{#ev:youtube|OpwNaoO3xMQ|240|right|Tomaskom's V-1 used in anger over London}}
{{#ev:youtube|H4XDuLo35ks|240|right|Victor V2.0 damage script causing a catastrophic failure and fire}}
{{#ev:youtube|uLojBI7ezdM|240|right|L-159 disintegration}}
The development team at FGUK have been experimenting with modelling aircraft damage in a number of different ways. First of all, Tomaskom has used the particle system carefully to produce visually impressive fireballs and smoke columns with very little FPS impact. First seen in his V-1, we hope to adapt this to simulate realistic fireballs for ground impacts (where appropriate). For the moment, it explodes with the full force of a V-1's explosive payload. On the right is a video excerpt from the #FlightNight which Tom organised to debut the V-1, where we all had '''way''' too much fun bombing London. As you can see, the smoke is visible from quite a long way away from the impact, and despite two fires burning with huge smoke columns, and over ten multiplayer aircraft within model range, the frame rates are still more than acceptable. StuartC has already integrated the explosion and fireball into several development aircraft, and we expect eventually to combine it with the disintegration code and make the size of the explosion dependent on fuel load etc.

In a separate development, Algernon's work on the Victor V2.0(YASim) now includes modelled damage, a collection of Nasal scripts, some modified from existing FlightGear staples, which detects irregularities such as component failures, birdstrikes and combat weapon damage and adversely affects system performance and reliability accordingly. Unserviceability often follows, using the existing FlightGear failures system, and compatibility will be maintained as the failures system is improved. The damage script also calculates probabilites for chain reaction damage - for instance, an explosion or serious fire in one Victor engine will usually have an effect on the other. In extreme circumstances, an explosion will trigger further explosions and destroy the aircraft. The second video on the right shows a serious induced explosion on the Victor's number one engine at night. Some fine-tuning of the Rembrandt light has been carried out since this video was shot, so apologies for the visible cut-off.

Finally, and most spectacularly, Tomaskom has demonstrated the disintegration capabilities of his L-159, which is under development. Hopefully, he will explain all here before publication date.

=== Scenesetter ===
Scenesetter is a piece of code by Algernon, very early in development but already quite effective, which can effect changes to the time and weather from an AI scenario synchronously with other MP players. A crude proof of concept was used in the recent FGUK #FlightNight "British Weather", where pilots visited different airfields with various unpleasant flying conditions. Scenesetter pushes METAR strings to the FlightGear weather system based on the location of an associated Navaid, establishing a circular zone of a specified radius around it in which METAR will be changed. Start time can be specified too, either by providing a local start time or a local time offset (useful for Multiplayer use where players will not all start the AI scenario at precisely the same time).

== In the hangar ==

=== New aircraft ===
==== Beechcraft Bonanza ====
Flyingfisch is building the Beechcraft A35 Bonanza for Flightgear. Some pictures:
<gallery mode=packed widths=230px heights=230px>
Beech_bonanza_with_panel_lights_on.png|Panel lighting
Beech_bonanza_on_runway_(evening).png|Evening shot
</gallery>

=== Updated aircraft ===

==== Saab JA-37 Viggen ====
The Swedish fighter jet [[Saab JA-37 Viggen]] has been updated, since it was included in FlightGear 3.0. More instruments, additional liveries, aerodynamic response to payload and tooltips on instruments. Option for automatic reverse thrust at touchdown, selection of HUD brightness, disabling of structural damage. HUD can now switch to imperial units and show MP and AI aircraft and closest airport. The aircraft now also has multiplayer sounds and better cockpit view helps seeing the landing strip. Support for FG 2.8 by deleting a small section in an xml file. Also worth mentioning is countless bug-fixes and improvements, e.g. better handling at high altitudes and a bug fix in the lift force formula.

[[File:Saab JA-37 Viggen Blue Peter Livery.png|Blå Petter Livery for JA-37]]

==== Updated P-51D now in git ====
The new 3D exterior model for the [[North American P-51D Mustang|North American P-51D Mustang]] is now in git and under active development. It is currently in gray primer waiting for the UV map to be finalized. It is now fully integrated into the existing FDM. Extensive new animation work has been done including animated trim tabs and a fully functional canopy. Here are some screen shots taken in sim for your enjoyment.

<gallery mode=packed widths="250px" heights="250px">
P-51D testing it's guns before a flight..jpg|P-51D testing it's guns before a flight.
P-51D trim tab animation..jpg|P-51D trim tab animation.
</gallery>

==== Balancing the Boeing 747-400 ====
After he started developing the [[Boeing 747-400]] as a hobby project six years ago, Gijs finally managed to get the weight and balancing right. The center of gravity is now within 0.05% MAC (40 cm) of the published values.

Make sure to use the new Fuel and Payload dialog to fill your fuel tanks. There is a slider and button that will nicely distribute a specified amount of fuel, while making sure the CoG stays within the operational limits. Before takeoff, check the Takeoff Reference page on the CDU to find the required stab trim units (your current setting is displayed to the left of the throttle quadrant). When you set your trim properly, you can almost relax your yoke to the neutral position after rotate. There's still some FDM work left to fine-tune this.

The updated 747-400 is already available through Git and will be on the download page when FlightGear 3.2 is released.

[[File:Extra500 flightgear1.png|thumb|200px|Extra500 flying in clouds]]
==== Extra500 is updated to Production Status ====

The Extra500 is updated and has reached "production status"! Just a short list of changes for release 1.1.0:
* Interactive checklists
* Interior model
* Improved Moving Map etc.
A more extensive list can be found in the "version" file.

{{FGCquote
|Here it is, the latest official version of the Extra500: release 1.1.0! 
 
The Model now has reached "production" status and a small list of changes you can find below: 
* Engine+fuel: realistic flame-out, fuel flow to collector compartment, anti ice influence on TOT, improved oil press and temp model 
* Aerodynamics: flap performance, elevator-30deg-flaps authority improvement 
* User interface: interactive checklists 
* Sounds: corrected sounds for test, CWS and AP disc 
* Model: added interior, yokes 
* Avionics: IFD moving map, automatic NAV tuning, automatic NAV switching, magnetic variation fixes 
* Autopilot: added OBS and fly vectors mode, significant improvement of coupled ILS performance
 
This version does perform a bit better on my computer, but this has to do with improvements to FGFS, not of the aircraft model. So if your computer was struggling with the initial version, we recommend to use current FGFS git/nightly builds or wait until 3.2 comes out!
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213132#p213132
|title=<nowiki>Re: New Aircraft: the Extra500</nowiki>
|author=<nowiki>D-EKEW</nowiki>
|date=<nowiki>Sun Jun 22</nowiki>
}}
}}

Please checkout the [[Extra EA-500|Extra500 wiki]] for download instructions and lots of more info.

=== Liveries ===

== Scenery corner ==
There is a project to add all the USA state capital buildings into FG. It is discussed in [http://forum.flightgear.org/viewtopic.php?f=5&t=22715&sid=ea847909bde2e1f8ffe5b94bcc673f4f this scenery forum thread]. There is also a wiki page: [[State Capitol Buildings in the United States]]. So far, Idaho, Louisiana & Nebraska have been completed. Hawaii and New York are currently in progress. Please feel free to join in with any other state that has not been done yet. Just let us know through the forum and we will add it to the in progress list.

=== Airports ===
==== LIPY, a scenery conversion from MSFS ====
This month saw the [http://forum.flightgear.org/viewtopic.php?f=5&t=22623 second "preview" release] of the conversion of a scenery for MS Flight Simulator, [[Falconara Airport]] (ICAO code: LIPY), a small Italian international airport halfway down the Adriatic coast. The original author granted the permission to the conversion and even allowed for it to be included in the FlightGear official [[World Scenery]], at least the GPL compatible parts. This is not a huge limitation though, because most of the material was created from scratch, included pictures taken on purpose at the real airport, with the authorities' collaboration. Copyrighted aerial imagery only include the (unsuable) photoreal ground and some roofs.

[[File:LIPY structures landscape.jpg|650px|right]]
The conversion was made with [[ModelConverterX]], which makes the job partially easier than by [[Howto:Convert objects from X-Plane|the Blender method]], yet it's still needing fixes because of some misunderstandings with the coordinates axes. The author of the tool, though, seems not very concerned and anyway, it's so rare to have a freeware scenery author allow conversions, that the usefulness of this tool would be greatly reduced anyhow, especially if you plan to upload the models to the [[FlightGear Scenery Database]].

The conversion itself, moreover, sure is not the matter of a button press. MSFS scenery are often packed and "compiled" in *.BGL files such that independent, far objects with the same materials and same LOD level (Level Of Detail) are bound together. This is clearly against FG's way, in which each new scenery generation could change the relative heights, and however MSFS airports are flat, while in FG they're all sloped. A similar thing happens with the texture maps. This basically means that you'll have to join all these objects and split them again based on the model they belong to (e.g. tower, terminal, hangars...)

Another issue with textures is that in FG it's good practice - recommended if not mandatory - to have 2 separate texture maps for the same object, if some parts are translucent. This means that without rebuilding all the texture maps [http://forum.flightgear.org/viewtopic.php?f=5&t=22707 you'll likely get artifacts]. Then, you'd have to add the Rembrandt lights if you want, and also the lightmaps (MSFS uses night textures, but Gimp can easily convert them). This whole experience can be summed up in the following quote:

{{cquote|I really wanted to have this scenery in FG because it's my home base, and seeing it ready and so well done just made me want it. However, even if still easier than making it from scratch (even if reusing the textures), I'd have to think well if I had to do this again.|bigstones, maintainer of the conversion}}

==== Reshaping Leipzig/Halle Airport ====
[[File:2014 new-layout-EDDP 05.jpg|650px|right]]
In FlightGear Germany's second largest cargo airport [[EDDP]] is well known as a detailed model accessible for everybody via [[TerraSync]]. Until 2013 it was famous for its regular ATC-events. It has been updated several times, at least 2012 by users D-STHO and August. When FlightGear 3.0 was published the airport layout changed from the old 810-standard to the new 850-standard. But the update (based on a taxiway layout modelled for X-Plane) turned out to be very imperfect. Many aprons and taxiways did not exist, dimensions did not appear to be correct and many new facilities which had been added at the real-world airport had not been taken into account. So maintainer August decided to redesign the whole airport from the scratch using [[WorldEditor]].
Pilots and developers are now invited to test the new airport model which includes further improvements like predefined STAR-, -SID and Transition procedures and hundreds of replaced Static- and Shared Models. The project will be published on TerraSync as soon as all defects are discovered remedied.

Developer Version:
'''git clone''' [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/ https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/]

Feedback is welcome at [[User talk:August|August's wiki page]].
<gallery mode=packed widths=230px heights=230px>
2014 new-layout-EDDP 04.jpg|Taxiway T - new ground textures
2014 new-layout-EDDP 01.jpg|Runway 26L with DHL-area
2014 new-layout-EDDP 02.jpg|Apron 4
</gallery>

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==

== Suggested flights ==
== Aircraft reviews ==

== Wiki updates ==
=== An updated Weather article ===
The [[Weather]] wiki article went through a wide extension. Although Advanced Weather was released quite a while ago, its usage has never been explained in the wiki, and some thorough instructions were available only in a readme in the "docs" folder of the base package which is not commonly explored by users, while the wiki article [[Advanced weather]] is more about the project than the usage.

AW's advanced configuration is known to be not easy. So, if you always only used the weather selection menu and want to know more, or want to understand what the options actually do and how you can combine them, the [[Weather]] article has now been updated with some hints and basic notions extracted from experience and the original documentation, and quality checked by the author of the AW weather engine.

=== Translators required ===
{|
|[[File:en.gif]]
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].
|-
|[[File:de.gif]]
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
|[[File:nl.gif]]
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
|[[File:es.gif]]
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|}

== Community news ==
=== FlightGear on YouTube ===

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===

=== Call for volunteers ===
* The Terragear maintainers are looking for volunteers to help with development on the next world scenery project. If you've ever wondered how a full 3D model of earth can be generated from raw data, now is your chance. See the plan at [[World Scenery 3.0 roadmap]].

=== Did you know ===

[[Category:FlightGear Newsletter]]


[[Category:Changes after 3.00]]

User talk:August

2014-06-29T11:48:01Z

August:

I'd like to invite you to test my current developments at [[EDDP]] and state your feedback here.
Developer Version:
'''git clone''' [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/ https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/]
--[[User:August|August]] ([[User talk:August|talk]]) 11:46, 29 June 2014 (UTC)

User talk:August

2014-06-29T11:46:03Z

August: Created page with "I'd like to invite you to test my current developments at EDDP and state your feedback here. --~~~~"

I'd like to invite you to test my current developments at [[EDDP]] and state your feedback here.
--[[User:August|August]] ([[User talk:August|talk]]) 11:46, 29 June 2014 (UTC)

File:2014 new-layout-EDDP 05.jpg

2014-06-29T10:35:47Z

August: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Leipzig/Halle Airport, redesigned model 2014: departing Extrra500 from Runway 26L}}
|date=2014-06-29 12:26:04
|source={{own}}
|author=[[User:August|August]]
|permission=
|other_versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

[[Category:Airports in Germany]]

File:2014 new-layout-EDDP 04.jpg

2014-06-29T10:35:36Z

August: User created page with UploadWizard

File:2014 new-layout-EDDP 01.jpg

2014-06-29T10:35:25Z

August: User created page with UploadWizard

File:2014 new-layout-EDDP 03.jpg

2014-06-29T10:35:14Z

August: User created page with UploadWizard

File:2014 new-layout-EDDP 02.jpg

2014-06-29T10:35:02Z

August: User created page with UploadWizard

List of developed airports

2014-06-26T18:54:58Z

August: /* Airports */ adding published Paro Airport - Bhutan

This page lists developed airports which are included in FlightGear if two conditions are fulfilled. Airports are listed here if
* at least one building or [[Signs|taxi signs]] have been placed
* the respective objects are represented in the [[FlightGear Scenery Database]].
Every improvement listed here can be downloaded using [[TerraSync]] and it will also be included in the next [[World Scenery]] release.

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]].

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

'''Note:''' You can sort the table by clicking one of the [[File:Sort none.gif]] symbols in the row headers.

== Airports ==

{| class="wikitable sortable" border="0" cellspacing="0"
|-
! style="background:#efefef" | ICAO !! style="background:#efefef" | Name !! style="background:#efefef" | Country !! style="background:#efefef" | Continent !! class="unsortable" style="background:#efefef" | Comment

|-
| [http://mapserver.flightgear.org/map/?lon=13.76716&lat=51.13277&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDC] || [[Dresden Airport]] || Germany || Europe || some models: tower, terminal, animated hangars etc. ''Everything published via TerraSync''

|-
| [http://mapserver.flightgear.org/map/?lon=8.56293&lat=50.03795&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDF] || [[Frankfurt am Main Airport]] || Germany || Europe || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique scycrapers downtown

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

|-
| [http://mapserver.flightgear.org/map/?lon=13.40379&lat=52.47502&zoom=15&layers=B000000TFFFFTFFFTTFFF EDDI] ||[[Berlin Tempelhof Airport]] || Germany || Europe || Fully modeled

|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf Airport]] || Germany || Europe || Tower and terminal

|-
| [http://mapserver.flightgear.org/map/?lon=11.78609&lat=48.35378&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDM] || [[Munich Airport]] || Germany || Europe || Fully modelled

|-
| [http://mapserver.flightgear.org/map/?lon=12.23603&lat=51.42262&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDP] || [[Leipzig/Halle Airport]] || Germany || Europe || Fully modelled with [[Signs]]

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

|-
| [http://mapserver.flightgear.org/map/?lon=13.28992&lat=52.55917&zoom=15&layers=B000000TFFFFTFFFTTFFF EDDT] || [[Berlin Tegel Airport]] || Germany || Europe || Tower, terminals, [[Signs]] and unique buildings downtown

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

|-
| [http://mapserver.flightgear.org/map/?lon=10.71706&lat=53.80496&zoom=15&layers=B000000TFFFFTFFFTTFFF 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]

|-
| [http://mapserver.flightgear.org/map/?lon=7.16278&lat=50.76767&zoom=15&layers=B000000TFFFFTFFFTTFFF EDKB] || [[Bonn-Hangelar Airport]] || Germany || Europe ||

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

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

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=25.04487&lat=60.25318&zoom=15&layers=B000000TFFFFTFFFTTFFF EFHF] || Helsinki-Malmi Airport || Finland || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=24.95253&lat=60.3206&zoom=14&layers=B000000TFFFFTFFFTTFFF EFHK] || Helsinki-Vantaa Airport || Finland || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=22.26281&lat=60.51412&zoom=14&layers=B000000TFFFFTFFFTFFFF 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 ||

|-
| [http://mapserver.flightgear.org/map/?lon=-0.19224&lat=51.14869&zoom=14&layers=B000000TFFFFTFFFTTFFF 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

|-
| [http://mapserver.flightgear.org/map/?lon=-0.46095&lat=51.47139&zoom=14&layers=B000000TFFFFTFFFTTFFF EGLL] || London Heathrow Airport || United Kingdom || Europe || Basic development only

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

|-
| [http://mapserver.flightgear.org/map/?lon=1.28469&lat=52.67713&zoom=15&layers=B000000TFFFFTFFFTTFFF EGSH] || Norwich Airport || United Kingdom || Europe ||

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

|-
| [http://mapserver.flightgear.org/map/?lon=4.75487&lat=52.31296&zoom=14&layers=B000000TFFFFTFFFTTFFF EHAM] || [[Amsterdam Airport Schiphol]] || Netherlands || Europe || Fully modeled, bussiest AI airport currently

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

|-
| [http://mapserver.flightgear.org/map/?lon=5.51885&lat=52.45717&zoom=15&layers=B000000TFFFFTFFFTTFFF EHLE] || [[Lelystad Airport]] || Netherlands || Europe || Fully modeled

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=6.11017&lat=62.56037&zoom=15&layers=B000000TFFFFTFFFTTFFF ENAL] || Ålesund Airport || Norway || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=6.10949&lat=61.83027&zoom=15&layers=B000000TFFFFTFFFTTFFF ENSD] || Sandane Airport || Norway || Europe ||

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=-106.60912&lat=35.04021&zoom=14&layers=B000000TFFFFTFFFTTFFF KABQ] || Albuquerque Sunport Airport, NM || USA || America || Basic development only

|-
| [http://mapserver.flightgear.org/map/?lon=-84.42809&lat=33.63672&zoom=14&layers=B000000TFFFFTFFFTTFFF KATL] || [[Hartsfield - Jackson Atlanta International Airport]], GA || USA || America || Terminal modeled

|-
| [http://mapserver.flightgear.org/map/?lon=-81.4629595&lat=41.0421187&zoom=15&layers=B000000TFFFFTFFFTTFFF KAKR] || Akron-Fulton Intl Airport, OH || USA || America || Fully modelled

|-
| [http://mapserver.flightgear.org/map/?lon=-81.43676804&lat=40.91510112&zoom=15&layers=B000000TFFFFTFFFTTFFF KCAK] || Akron-Canton Regional Airport, OH || USA || America || Fully modelled

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=-76.66833&lat=39.17535&zoom=14&layers=B000000TFFFFTFFFTTFFF KBWI] || Baltimore-Washington International, MD || USA || America || Terminal modeled with jetways, parking garage, support buildings and [[Signs]]

|-
| [http://mapserver.flightgear.org/map/?lon=-76.92254&lat=38.98062&zoom=15&layers=B000000TFFFFTFFFTTFFF KCGS] || College Park Airport, MD || USA || America ||

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

|-
| [http://mapserver.flightgear.org/map/?lon=-104.67318&lat=39.86166&zoom=13&layers=B000000TFFFFTFFFTTFFF 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 ||

|-
| [http://mapserver.flightgear.org/map/?lon=-90.07589&lat=32.31118&zoom=14&layers=B000000TFFFFTFFFTTFFF KJAN] || Jackson-Evers Airport, MS || USA || America ||

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=-118.40809&lat=33.9425&zoom=14&layers=B000000TFFFFTFFFTTFFF KLAX] || [[Los Angeles International Airport]], CA || USA|| America || Fully modeled

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

|-
| [http://mapserver.flightgear.org/map/?lon=-109.4667&lat=47.04924&zoom=14&layers=B000000TFFFFTFFFTTFFF KLWT] || Lewistown Municipal Airport, MT || USA || America ||

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=-117.69181&lat=35.68565&zoom=14&layers=B000000TFFFFTFFFTTFFF KNID] || China Lake Naval Air Weapons Station, CA || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-122.04918&lat=37.4162&zoom=15&layers=B000000TFFFFTFFFTTFFF KNUQ] || Moffett Federal Airfield, CA || USA || America || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=-122.22062&lat=37.7214&zoom=14&layers=B000000TFFFFTFFFTTFFF KOAK] || [[Oakland International Airport]], CA || USA || America || Realistic terminal, currently undergoing maintenance

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

|-
| [http://mapserver.flightgear.org/map/?lon=-88.55704&lat=43.98436&zoom=14&layers=B000000TFFFFTFFFTTFFF KOSH] || Wittman Regional Airport, Oshkosh, WI || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-75.12398&lat=38.31045&zoom=14&layers=B000000TFFFFTFFFTTFFF KOXB] || Ocean City Municipal Airport, MD || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-122.59751&lat=45.58871&zoom=14&layers=B000000TFFFFTFFFTTFFF 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 ||

|-
| [http://mapserver.flightgear.org/map/?lon=-122.3749&lat=37.61897&zoom=14&layers=B000000TFFFFTFFFTTFFF 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 ||

|-
| 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

|-
| LFEA || Belle-Ile || France || Europe ||

|-
| LFEQ || Quiberon || France || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=-3.66479&lat=48.05247&zoom=15&layers=B000000TFFFFTFFFTTFFF LFES] || Guiscriff Scaër || France || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=2.35465&lat=49.04626&zoom=15&layers=B000000TFFFFTFFFTTFFF LFFE] || Enghien Moisselles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=4.8264&lat=45.25226&zoom=15&layers=B000000TFFFFTFFFTTFFF LFLR] || Saint Rambert d'Albon Airport || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=13.76716&lat=51.13277&zoom=15&layers=B000000TFFFFTFFFTTFFF LFMA] || Aix - Les Milles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=0.08816&lat=49.53404&zoom=14&layers=B000000TFFFFTFFFTTFFF LFOH] || Le Havre Octeville Airport || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=5.36736&lat=43.50499&zoom=14&layers=B000000TFFFFTFFFTTFFF LFPG] || Charles de Gaulle International Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=2.60632&lat=48.89629&zoom=14&layers=B000000TFFFFTFFFTTFFF LFPH] || Chelles Le Pin Airport || France || Europe || Fully modeled, high resolution textures

|-
| LFPL || Lognes Emerainville Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| LFPO || Paris-Orly Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| LFPZ || St-Cyr-l’École Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=-4.41785&lat=48.44413&zoom=12&layers=B00000000000FTFFTFFTFFFTFFFF LFRB] || Brest Bretagne Airport || France || Europe || Modeled airport with static models

|-
| [http://mapserver.flightgear.org/map/?lon=-4.15167&lat=48.53014&zoom=14&layers=B000000TFFFFTFFFTTFFF LFRL] || Lanvéoc Naval Air Base || France || Europe || Airport fitted with shared models (for helos and training)

|-
| [http://mapserver.flightgear.org/map/?lon=-4.15167&lat=48.53014&zoom=14&layers=B000000TFFFFTFFFTTFFF LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]

|-
| LFRQ || Quimper || France || Europe ||

|-
| LFRU || Morlaix || France || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=7.531611&lat=47.599621&zoom=14 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 ||

|-
| [http://mapserver.flightgear.org/map/?lon=9.70741&lat=45.66952&zoom=14&layers=B000000TFFFFTFFFTTFFF LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=9.27521&lat=45.44776&zoom=14&layers=B000000TFFFFTFFFTTFFF LIML] || [[LIML|Milano-Linate Airport]] || Italy || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=7.36789&lat=45.73857&zoom=15&layers=B000000TFFFFTFFFTTFFF LIMW] || Aosta Airport || Italy || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=14.26&lat=50.100833&zoom=15&layers=B000000TFFFFTFFFTTFFF LKPR] || [[Václav Havel Airport Prague]] (Ruzyne) || Czech Republic || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=11.34397&lat=47.26023&zoom=15&layers=B000000TFFFFTFFFTTFFF LOWI] || [[Innsbruck Airport]] || Austria || Europe ||

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

|-
| 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 ||

|-
| [http://mapserver.flightgear.org/map/?lon=136.80541&lat=34.85841&zoom=14&layers=B000000TFFFFFFFFTTFFF RJGG] || [[Chūbu Centrair International Airport]] || Japan || Asia || Detailed airport buildings, taxiway layout and customized terrain.

|-
| [http://mapserver.flightgear.org/map/?lon=139.78114&lat=35.5533&zoom=14&layers=B000000TFFFFTFFFTTFFF RJTT] || [[Tokyo Haneda International Airport]] || Japan || Asia ||

|-
| [http://mapserver.flightgear.org/map/?lon=126.45051&lat=37.46909&zoom=14&layers=B000000TFFFFTFFFTTFFF RKSI] || Seoul Incheon Airport || South Korea || Asia ||

|-
| [http://mapserver.flightgear.org/map/?lon=121.01349&lat=14.51024&zoom=14&layers=B000000TFFFFTFFFTTFFF RPLL] || Manila Aquino Airport || Philippines || Asia || Tower and three large terminals

|-
| 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 ||

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

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

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

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

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

|-
| [http://mapserver.flightgear.org/map/?zoom=14&lat=27.39994&lon=89.42272&layers=B0 VQPR] || [[Paro Airport]] || Bhutan || Asia ||

|-
| [http://mapserver.flightgear.org/map/?lon=113.9183&lat=22.308&zoom=14&layers=B000000TFFFFTFFFTTFFF VHHH] || Hong Kong International Airport || Hong Kong || Asia || Terminals, control towers, some other buildings

|-
| [http://mapserver.flightgear.org/map/?lon=-81.41707414&lat=41.15689289&zoom=15&layers=B000000TFFFFTFFFTTFFF 1G3] || Kent State University Airfield, OH || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-81.76281774&lat=41.13448335&zoom=15&layers=B000000TFFFFTFFFTTFFF 1G5] || Medina Municipal, OH || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-81.24620281&lat=41.20973295&zoom=15&layers=B000000TFFFFTFFFTTFFF 29G] || Portage Co, OH || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-90.13769&lat=43.83872&zoom=15&layers=B000000TFFFFTFFFTTFFF 82C] || Mauston-New Lisbon Union Airport, WI || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-89.02545&lat=44.50485&zoom=15&layers=B000000TFFFFTFFFTTFFF 68C] || Iola Central County Airport, WI || USA || America ||

|}

{{Suggested}}

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

Howto:Modeling Ground Signs with Blender

2014-06-22T13:20:58Z

August: exception of TerraSync

There comes a time when you want to add a few details to an airport in order to improve the realism of your flight experience. Every flight starts (and ends) on the ground, at an airfield. In simulations you generally won't spend too much time there. Generally you will immediately start at the beginning of a runway and be in the air within a few seconds.

There are however people who like learning how to move on the ground too. Learn how to maneuver their aircraft inside the airport. Well, in this case, having good ground signs/markings on the ground is mandatory, because most of the guidance is found there.

Pilots should know what ground signs to pay attention to during every phase of maneuvering, prior to reaching the runway. There are signals painted on the ground and taxi signs on the side of each runway/taxiway. You should also pay attention to tower radio communications and so on. Here you will learn how to build custom ground markings, the ones that are painted on the ground and give you useful information about what you can and cannot do during your ground maneuvering.

{{note|FlightGear has switched to a new airport format ([[apt.dat]] 850), making it possible to include proper taxiway lines and markings. However some of the ground signs are not yet supported by this format (ex: the kind shown here) and it's still advisable to add them with this technique. Be advised, though, that there's work in progress to have the format support them, and also other kinds of lines. A search for "ground signs" on the forum should give the latest news. Developers have to consider these self made ground signs are not accepted by [[TerraSync]] and can only be used for custom sceneries.}}

=== Tutorial files ===
Right click > Save link as
* [[Media:catii-iii.ac|catii-iii.ac]]
* [[Media:catii-iii.blend|catii-iii.blend]]
* [[Media:catii-iii.xml|catii-iii.xml]]
* [[Media:catii-iii.rgb|catii-iii.rgb]]

=== Holding position markings for CAT II/III operations ===

In this lesson you will learn how to create a basic ground marking. We will use the one that informs the pilot to HOLD during CAT II/III operations to ensure proper aircraft separation. There are generally a few taxiway signs as well which also help to locate these areas. CAT II/III separation is not that big of an issue in [[FlightGear]]. There is still no automatic ground traffic management and aircraft collisions are not very expensive; but this is a real ground marking. We will concentrate on the modeling phase, rather than the functional aspects of the sign.

There is no way [[FlightGear]] could position these ground markings automatically. There is no database of where they are or what they look like. Each airport customizes ground marking positions and orientations in order to get maximum efficiency and to help pilots getting correct information without filling the ground with too many of them. Rationalizing communication effectiveness is vital to an airport. Therefore you will create and position them manually.

When viewed from the air CAT II/III markings look like this:

[[File:catii-iii_markings_html_6961c87a.jpg]]

They are generally placed in the middle of the runway, following the taxiway yellow line, just before the CAT II/III operations area. Here the pilot must stop and wait for instructions from the ATC.

It is a simple red square with the text "CAT II/III" in large white letters. It is stretched out so that when viewed from an aircraft taxing over it, it looks quite proportional.

=== Modelling the marking with Blender ===

This is relatively easy. It is a simple textured rectangle. The first thing you need is the correct measurements and a nice texture to put on it. I will create this example with the same measurements used at EDDF Frankfurt airport. The rectangle is 8m wide and 7m high.

I will not explain how to paint the texture because it is covered in other tutorials. Use your preferred painting software, I used [[The Gimp]] for this one, save the file in.rgb format and make sure that its size (pixel resolution, not bytes) is a multiple of 8, otherwise [[FlightGear]] will not load it. Here you see a JPG version of the texture as an example, download catii-iii.rgb to get the RGB version you need for texturing, it has 512x512 pixel resolution. You can use smaller ones (ex. 128X128) if you think this resolution is too high.

[[File:catii-iii_markings_html_m11bd5b93.jpg]]

Modelling the rectangle with Blender is easy.

Open Blender; from the main menu choose Add -> Mesh -> Plane

This adds a 2 units width square plane.

Our ground painting is an 8m x 7m rectangle so we have to change the square's dimensions.

Enter Object mode. Object -> Transform Properties

The Transform Properties window appears. Set “Size X : 4” and “Size Y: 3.5”.

Notice here that the object name is “Plane” (OB: Plane), we will use this information later.

[[File:catii-iii_markings_html_m352e2670.jpg]]

Now you come to the texturing phase. Split the top window in two, and select UV/Image Editor for the right panel:

[[File:catii-iii_markings_html_39a834a0.jpg]]

In the 3D View window, select UV Face Select mode, the rectangle face should be still selected, if not, select it by right clicking on the rectangle. Now, while the mouse is in the 3D View window, make sure it's a top view (Numpad 7), hit the U key, and select “From window”.

Now it's time to load the texture file. Inside the right panel, choose Image -> Open ... select the file catii-iii.rgb and hit Open Image.

[[File:catii-iii_markings_html_m41735d75.jpg]]

We have to move the rectangle UV vertices in order to make the texture cover the entire rectangle geometry. We will now work in the UV/Image Editor window. Make sure “UVs -> Snap to Pixel” is set, this will make our life easier. Hit the B key, click and drag the mouse around the lower left corner in order to select it. We are not working on the 3d model, we are working on the Uvs, that's why the rectangle in the left window maintains its geometry. Once the vertex is selected, hit the G key (Grab mode) and drag the vertex to the bottom left.

[[File:catii-iii_markings_html_m3011a2ff.jpg]]

You will need to zoom in a little bit in order to position it precisely, use the CTRL-MMB (MMB = Middle Mouse Button) to zoom in and out, use the SHIFT+MMB to drag the view around. Hit G again, and move the UV vertex into the right position. While doing this, you can select the Textured Draw Mode and interactively see what's happening.

[[File:catii-iii_markings_html_3b879144.jpg]]

You can select and deselect all UV vertices by hitting the A key.

Now hit the A key to deselect the UV vertex; zoom out, hit B, by clicking and dragging select a new UV vertex, hit G and move it with the mouse to the correct position. Then do the same with the remaining two vertices. You will end up with the texture perfectly matching the geometry border:

[[File:catii-iii_markings_html_3283723d.jpg]]

Now you can go back to Object Mode, make sure the object is selected and export it as AC3D formatted file.

File -> Export -> AC3D (.ac) ... enter a filename and hit “Export AC3D”.

The 3d model is ready and you can place it into your airport [[scenery]] now. Make use of Flightgear Scenery Designer, the [[Placing 3D Objects with the UFO|UFO object placing capability]] or whatever method you prefer.

Result being:

[[File:catii-iii_markings_html_5db04368.jpg]]

[[File:catii-iii_markings_html_m1758ae9f.jpg]]

We will go further and add a few details using an XML file which will describe peculiar attributes of such an object.

=== Customizing object's attributes into Flightgear using XML ===

We have three little details here that can be annoying.

1) If you activate Shadow into Flightgear and fly very close (let's say 10meters) to those CAT II/III markings, you will notice that they cast a shadow underneath, especially if the plane has been positioned more then 20cm above the ground. This is not good at all because that should represent a painting on the ground (that could not cast any shadow, there should be no free space between the painting and ground) and a useless shadow consumes GPU power too, which is not desired.

2) If you maneuver an aircraft on the ground, right above the marking, you will notice that the aircraft hits it with the wheels, and jumps a little, just like it encountered an obstacle on the ground. That is not good again, the painting should not oppose any resistance to any ground movement.

3) If you fly high above the airport area you will not really see those little red rectangles, they are too small to be noticed from a height. Nonetheless, Flightgear will still render those little objects on the ground and consume GPU power without really giving any advantage to the simulation experience. That should be avoided, we need to make Flightgear render those markings only when the aircraft is near enough to make them visible to the pilot.

We will eliminate those three cons creating a XML file that covers the issues. Please refer to Flightgear docs in order to get more information about the usage of the XML markup language used.

You can use any text editor you prefer, fill a new empty text file with the following content and save it as catii-iii.xml in the same directory with catii-iii.ac and catii-iii.rgb.

<PropertyList>
<path>catii-iii.ac</path>

<animation>
<type>noshadow</type>
<object-name>Plane</object-name>
</animation>

<animation>
<object-name>Plane</object-name>
<enable-hot type="bool">false</enable-hot>
</animation>

<animation>
<type>range</type>
<object-name>Plane</object-name>
<min-m>0</min-m>
<max-property>/sim/rendering/static-lod/detailed</max-property>
</animation>

</PropertyList>

The <path>catii-iii.ac</path> statement means that all this refers to the 3d object file named catii-iii.ac.

Every animation transformation here applies to the the object called “Plane” inside the catii-iii.ac file (which is our marking rectangle). We could have more then one object inside the .ac file and decide which should cast a shadow and which not. Our example is very simple though, but still this statement has to be included.

1) The first “animation” transformation tells Flightgear not to apply any shadow to it.

2) The second “animation” tells Flightgear not to consider the object “Plane” as an obstacle, so any vehicle will not hit it.

3) The third “animation” tells Flightgear to render the object “Plane” only if the distance between it and the viewer is more then 0 meters and less then the value stored in Flightgear tree with the name /sim/rendering/static-lod/detailed. This value is a number that can be user customized; the default value is 1500m. When the object is more then 1500 meters distant, Flightgear will not render it; at such a distance you barely see a 8m x 7m square painting on the ground.

Now, insert the 3d object into your scenery but do not use the .ac file, make use of the .xml file instead; it will call the corresponding .ac file when needed. The following snapshot includes the yellow ILS critical area boundary stripes and the taxiway A ground marking which I made using the same technique, the only difference being those have partially transparent texture file.

[[File:Ground_marking_full_example.jpg]]

=== Adding some realism to the texture ===

Aircraft and ground vehicles do move above those markings, that makes them dirty after a short while. I like adding a touch of realism to the textures I use into my Flightgear models. Adding some dirt to the ground marking is pretty easy. I'll show you how to modify the texture with The Gimp, you can use similar techniques with every common graphic editor.

Open up Gimp and load the file catii-iii.rgb

Create a new layer by SHIFT clicking on the left button of the Layers Dialog Box:

[[File:catii-iii_addon_html_21146099.jpg]]

In the image window, go to: Filters -> Render -> Clouds -> Plasma ...

You can customize the Clouds rendering settings in order to get a nicely random cloud rendering. Now, you just use what I suggest in the picture and hit OK. It does not matter if it looks colored now, we will convert to greyscale and use the light values only to add some noise to the underlaying layer.

[[File:catii-iii_addon_html_1dad0e33.jpg]]

You will get this in your image window.

[[File:catii-iii_addon_html_m30fea806.jpg]]

Erase the saturation with: Layer -> Colors -> Desaturate

[[File:catii-iii_addon_html_7db38b6e.jpg]]

Return to the Layers dialog box, change the clouds layer mode to Multiply and the Opacity to 40.

[[File:catii-iii_addon_html_54e9cda0.jpg]]

I also tend not to use huge texture files, that's why I rescale it to smaller resolution; keep in mind that we need it to be a multiple of 8; in this case I decided a 256x128pixel resolution would look good enough. In the image window: Image -> Scale Image ...

[[File:catii-iii_addon_html_23b912fa.jpg]]

Unlock the resolution proportion constrains by clicking on the little chains at the right of the Image Size resolution boxe (the chain opens up in two pieces), then set Width:256, Height:128 and hit Scale.

[[File:catii-iii_addon_html_m19c5fb92.jpg]]

Now the image is ready to be saved with RGB format as usual, and can replace the old one. The result in Flightgear looks more realistic then the previous one, that bit of dirt smooths out the visual break caused by the perfectly clean texture used before. It integrates better with the surrounding taxiway texture.

[[File:catii-iii_addon_html_a5eaae.jpg]]

I hope you will enjoy this little lesson. Consider this as an example, because there are a lot more things to do with the XML animations provided by Simgear to Flightgear.

[[Category:Modeling]]
[[Category:Scenery enhancement]]
[[Category:Howto]]

Leipzig/Halle Airport

2014-06-20T09:05:28Z

August: /* Download via GIT */

{{infobox Airport
|name = Leipzig/Halle Airport
|image =EDDP TerminalC.jpeg
|alt =New terminal C (published 2012)
|iata =LEJ
|icao =EDDP
|type =Public
|city =Between Leipzig and Halle
|owner =Mitteldeutsche Airport Holding
|website =http://www.leipzig-halle-airport.de/
|scenerytile =e012n51
|download =
|terrasync = [[#Download_via_GIT]] for latest scenery
|runway= 08L/26R
|length= 11,811 ft
|material= Concrete (in FG still Asphalt)
|runway2= 08R/26L
|length2= 11,811 ft
|material2= Concrete (in FG still Asphalt)
}}

'''Leipzig/Halle Airport''' is located in Schkeuditz, Saxony and serves both Leipzig, Saxony and Halle, Saxony-Anhalt, [[Germany]]. In Flightgear this airport was published on [[TerraSync|TerraSync]] in 2010 und updated due to new developments 2012. In 2014 according to the new world scenery a complete overhaul started.
EDDP is also the centre of Leipzig/Halle airspace, which provides air traffic control also for the regional airfield [[Leipzig-Altenburg Airport]].

{{Note|Currently users are asked to test the '''beta Version of the new 850-Layout''' (see [[#Download_via_GIT]])}}

However, if you want something to be configurable, one important thing is having an element ID that we can refer to, in order to look up the key and modify the symbol via Nasal. Without having an element id (e.g. for labels) we cannot easily modify such SVG images procedurally.}}
== Flying at Leipzig/Halle airspace ==

=== Charts ===
All [http://www.vacc-sag.org/airport/EDDP diagrams and charts] are available for download.

=== Runways and ILS ===

==== Runway 08L/26R ====
[[File:2012-09 Apron4 Luftbild-at-night.png|thumb|270px|Apron 4 and runway 26L at night]]The northern [[runway]] is 3600m long with a width of 45m. In real life its usually used by passenger airliners. In Flightgear this runway is equipped with Outer Marker and Middle Marker and offers best conditions for '''low visibility operations'''.
* ILS-CAT-III '''08L''' (083°): 108.55
* ILS-CAT-III '''26R''' (263°): 108.35
==== Runway 08R/26L ====
The southern [[runway]] is 3600m long with a width of 60m. In real life its mostly used by freighters due to its proximity to freight areas (Apron 2 and 4). It has no Outer Marker an no Middle Marker.
* ILS-CAT-III '''08R''' (083°): 111.90 (111.75 in FG older than Version 2.0.0)
* ILS-CAT-III '''26L''' (263°): 110.30

=== ATC ===
* Leipzig Ground - frequency 121.800
* Leipzig Tower - frequency 121.100

Leipzig/Halle Airport is regularly served by Air Traffic Control ([[ATC]]).

== Infrastructure ==
[[File:EDDP-overview-daytime.jpg|thumb|270px|Overview 2012]]Connected by terminal C and three taxiway bridges (W1, E7, E8) the airport layout combines the northern part with runway 08L/26L and Apron 3 (new cargo area since 2012) and the southern part with Apron 1 (terminal B), runway 08R/26L, Apron 2, Apron 4 (DHL), Apron 5. Between both parts an airport railway station and the autobahn A14 is connecting to the check-in area of terminal C. Railway and motorway are not modelled in Flightgear.

=== Access and connection ===
[[File:TerminalC-morning.jpg|thumb|270px|Terminal C at dawn]]
==== Terminal C ====
In August 2012 the completely new modelled terminal C was published on TerraSync. It is built as a connection between the check-in building with car-park and train station in the north and the departure area at terminal B in the south. Due to this efforts it stands on piers like a long bridge from apron 1 to apron 3, crossing different car-parks, a rail-track and the autobahn.
On the one hand the FlighGear model tries to give the airport a well designed model with highly detailed structures, but on the other hand it was programmed as simple as possible to save visitors simulation performance.

==== Taxiway bridges ====
[[File:EDDP-Taxibridges-e7e8-night.jpg|thumb|270px|Rampbridges E7, E8 with new lightning in 2012]]A highway and railway lines go straight between the two runways. Three bridges connect the terminal with the northern runway. The western bridge (taxiway W1) is used in both directions. The eastern bridges (taxiways E7 and E8) are used as one way taxiways. Due to safety improvements all bridges are equipped with special taxi lights.
Due to changes in the TerraData the bridges had to be repositioned in 2012.

=== Apron 1 ===

The main apron at Leipzig/Halle Airport is located in the middle of the airport. It houses the commercial aviation area at terminal B in the west and the general aviation area in the eastern part. It is connected by taxiways L, N and W1.

==== Terminal B ====
[[File:EDDP VDGS-134 thumbnail.jpg|thumb|270px|VDGS on each gateway at terminal B]]'''Real world''':
This building is the main terminal for most commercial flights at EDDP. It is connected to terminal C in the north and provides the passenger transfer to Apron 1 via 6 gateways. It also has a connection to the luggage terminal.

'''Scenery in TerraSync''':
In Flightgear the main terminal is modelled very slim and efficiently. 6 unmovable gateways link to park positions 126, 128, 130, 132, 134 and 136. In 2012 it will be improved. Since September 2012 it has been equipped with a non-animated [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System VDGS].

==== Luggage terminal ====
This building was first published in 2004 and remodelled by Thomas Großberger in 2012. The terminal is connected via the old tower next to it to terminal A by a tube, which is used to transport luggage between the checkin- and arrival-area and Apron 1. Both. the connection and the old tower building will be modelled in 2013. The new luggage terminal in FlightGear is offering:
* realistic roof design
* simplified but detailed interior
* 6 clock controlled automatic gates
* complex light design (Rembrandt-Design outstanding)

==== GAT ====

=== Apron 2 ===

=== Apron 3 ===
This Apron in real life went into service with a new cargo hangar in 2012. In Flightgear it is still closed. The corresponding facilities are still under development.

=== Apron 4/5 (DHL-area) ===
[[File:2012-08 Apron4 Pos432 BOX1522-D-STHO-and-DC10.png|thumb|270px|DHL-area at apron 4]]'''Real world:''' Leipzig/Halle is just a small international airport. But in 2008 it became the [http://www.dp-dhl.com/en/logistics_around_us/from_our_divisions/leipzig_hub.html European DHL hub] with up to 60 planes per night. The DHL Hub Leipzig GmbH, place of business in Schkeuditz, is running under contract to the logistic group DHL at Leipzig/Halle Airport one of six international aviation hubs. In order to provide maintenance to the new fleet the [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig GmbH] was founded. European Air Transport operates services to Europe, Middle East and Africa. 56 countries are covered in total. A second aviation company, called [http://en.wikipedia.org/wiki/Aerologic AeroLogic], was founded in EDDP. AeroLogic GmbH, a joint-venture between DHL Express and Lufthansa Cargo, is a German cargo airline headquartered in Schkeuditz, Saxony. It operates cargo flights out of Leipzig/Halle Airport and Frankfurt, most of which are on behalf of its parent companies.

{| class="wikitable" cellpadding="3" style="margin-left:auto; margin-right:auto"
|+ '''Fleet of [http://en.wikipedia.org/wiki/Aerologic AeroLogic] and [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig] and others''' (2012)
|-
!Aircraft
!Total
!Orders
!Oparator
|-
|[[Airbus A300|Airbus A300B4-203F]]
|<center>10</center>
|
|Air Contractors
|-
|[[Airbus A300|Airbus A300-600RF]]
|<center>8</center>
|<center>10</center>
|European Air Transport Leipzig
|-
|Boeing 737-300F
|<center>9</center>
|
|European Air Transport Leipzig
|-
|Boeing 737-400F
|<center>1</center>
|
|Europe Airpost
|-
|[[Boeing 757|Boeing 757-236SF]]
|<center>10</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 757|Boeing 757-23APF]]
|<center>1</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 777F]]
|<center>8</center>
|
|AeroLogic
|-
!Total
!47
!10
!colspan=2|
|}

[[File:EDDP-DHL-tank.jpeg|thumb|270px|DHL-Tank at fuel storage area on apron 4]]'''Scenery in TerraSync:''' The hub (warehouse, hangar and aprons) is modelled in the scenery. In 2012 its redesign for TerraSync started. First all lampposts at apron 4 had been replaced with those which fit into the correct layout of every single parking position. Afterwards lots of goods and ground vehicles where placed. As soon as some missing storage buildings are modelled, the new content of apron 4 will be published on TerraSync. Last modifications will take place when the new [[Airport data (apt.dat) update|850-standard layout]] of EDDP will be created in the future.

'''DHL-hub at EDDP in Flightgear:''' Leipzig/Halle Airport offers ground space for more than 70 Boeing [[757-200|757-PF]] or up to 50 [[777F]] as well as space for 10 [[Antonov An-124|An-124]] at Apron 2, 4 and 5. Airmail flights can be flown from and to EDDP. One of the middle sized and highly connected hubs of DHL, the [[Orio al Serio Airport]] (Italy) is also modelled in FlightGear and can be used for realistic flights out of Leipzig/Halle Airport.
In FlighGear apron 4 is equipped with all stands. Additionally to the main apron lightning each stand has one centred lamppost, which will be replaced by a VDGS-signs in the future. Ground markings will come with the new 850-layout. The major storage buildings from DHL are modelled as well as three DHL-tanks south from apron 4.

=== De-icing areas ===
Leipzig/Halle Airport has four special areas, two in the north at taxiway C and two in the south at taxiway N. In FlightGear only the two areas at taxiway C are build into the layout. In 2012 both areas had been equipped with shared models like lampposts, buildings and ground lights.

==== De-icing area 2 - multiplayer ready ====

Based on the Zurich type model "Elephant" - originally modelled by Oliver Thurau - an improved version with full multiplayer support is under development. This version isn't only adapted to the special efforts at EDDP, but its also designed to be controlled by ATC. It will be published via TerraSync in November 2014.

== Surroundings and "Other" ==

=== Kursdorf - the village within the airport ===
There is a village right in middle of the airport. So it's no surprise the number of inhabitants is shrinking each year. Once a thriving village with 537 inhabitants in 1950, they were down to 119 in 2006 [http://de.wikipedia.org/wiki/Kursdorf_%28Schkeuditz%29 (Wikipedia)]. It might be a little loud with the two runways, highway and express railways, but the transport links, hey ... The village is modelled in the scenery.

== Scenery ==
{|
| Authors: ||
* Models: David G., Thomas Großberger
* Airport layout: Christian Schmitt
* Additional models: Don Lavelle, Alex Park, Robert Shearman
* Redesigning & Development 2012: August Geyler, Thomas Großberger
|-
|}

=== Download via GIT ===
With FlightGear 3.0 a new world scenery was published, including a new but incorrect 850-layout for EDDP. Developers started a huge overhaul of the EDDP scenery in April 2014. First a new taxiway layout was programmed. Additionally all buildings and objects are replaced. Some models will be remodelled, others will be added. Due to the fact that airport layouts can't be simply updated via TerraSync in a short way, pilots are asked to use the new EDDP CUSTOM SCENERY as long as things aren't updated at TerraSync.

* Download-Development-Scenery
* updated regularly
** '''git clone''' [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/ https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/]
** or [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/archive/5a25c94d403f09e5b5bf4d72117e297191acb3ce.tar.gz download a ZIP] (101 MB)

=== Download via TerraSync ===
[[TerraSync]] has it all! There is no custom scenery existing (only the GIT-repository for testing the new 850-layout before publishing it). The authors believe on the advantages of TerraSync which makes it easy for every user to have the latest scenery installed automatically. Updates are published regularly via TerraSync.
* Next update in '''<daysuntil in="days">12-August-2014</daysuntil>''' {{Progressbar|height=45|percentage={{#expr: trunc ({{#time: z}} - {{#time: z | May 19 2014 }}) round -1 }}}}

* '''Latest update on TerraSync:'''
** '''2014-04-29''' ''Objects adapted to new (but incorrect) 850-layout''

* Last five updates:
** '''2013-04-21''' ''Rembrandt lights at apron 1''
** 2013-02-13 ''new Messeturm at final approach area of runway 26R''
** 2012-12-21 ''new luggage terminal at apron 1''
** 2012-10-22 ''three new DHL-tanks placed at DHL-area''
** 2012-09-20 ''new VisualGuidingDockingSystem at terminal B''

=== Development ===
Since the Scenery had been modelled by [[User:D-79|D-79]] in 2010, Thomas Großberger and [[User:August|August Geyler]] started enhancements and redesigning in 2012. In 2014 development of a new 850-layout started. Improvements are made on the following objects:

'''Layout''' 
* Taxiway bridges: new Position, improved lightning ''(published 07/2012)'' {{tick}}
* New 850-standard: new Layout with all parking positions and improved taxiways ''(pre-development)'' {{progressbar|80}} (see [[#Download_via_GIT]])

'''Scenery (Shared Models)''' 
* Airport lightning: more than 80 lampposts ([[EDDM]]-model) on Apron 1 and 4 and both northern de-icing areas ''(published 07/2012)'' {{tick}}
* DHL-tanks at apron 4 ''(published 10/2012)'' {{tick}}
* Ground traffic: lots of goods and vehicles (shared) make apron 1 and 4 much more realistic ''(published 08/2012)'' {{tick}}
* Flora and boundaries: Trees and fences on Apron 1, 2 and 4 are added ''(published 08/2012)'' {{tick}}
* New shared ground vehicles
** Container dolly ''(under development)'' {{hourglass}}
** Luggage dolly ''(under development)'' {{hourglass}}
** Pallet dolly ''(planned)''
* New shared Unit Load Devices (ULD)
** Airfreight container - Type AKH ''(pre-development)'' {{hourglass}}
** Airfreight pallet ''(planed)''
* Village and industrial surroundings: Kursdorf within the airport and industrial areas around are created with shared models ''(published 04/2010)'' {{tick}}

'''Buildings and infrastructure (Static models)''' 
* Cargo-hangar apron 3 ''(planned)''
* Cargo-center apron 2 ''(published 2010)'' {{tick}}
* DHL-hangar ''(published 2010)'' {{tick}}
* DHL-terminal ''(published 2010)'' {{tick}}
* Interactive DE-ICING areas (Multiplayer supported) {{hourglass}}
* Interactive luggage dolly traffic between terminal B and lugage terminal ''(planned)''
* Luggage terminal ''(published 12/2012)'' {{tick}}
* Storage buildings at DHL-area ''(pre-development)'' {{hourglass}}
* Terminal B ''(published 04/2010)'' {{tick}}
* Terminal C ''(published 08/2012)'' {{tick}}
* Tower ''(published 2010)'' {{tick}}
* Turbo engine hall ''(pre-development)'' {{hourglass}}
* Old Tower next to terminal B ''(pre-development)'' {{hourglass}}
* Visual Docking Guiding System at Apron 4 ''(planned)''
* Visual Docking Guiding System at Terminal B ''(published 09/2012)'' {{tick}}
* Visual Docking Guiding System: replacement with animated interactive version ''(planned)''
'''Rembrandt lightning improvements'''
* Converting Lightning to [[Project Rembrandt|Rembrandt]]
** Rembrandt lights at apron 1 ''(published 04/2013)'' {{tick}}
** Rembrandt lights at apron 4 {{progressbar|80}}
* Converting Buildings to [[Project Rembrandt|Rembrandt]] Lightning
** Luggage terminal ''(pre-development)'' {{hourglass}}
** Terminal B ''(planned)''
** Terminal C ''(planned)''
** Tower ''(planned)''
** DHL-hangar ''(planned)''
* Lampposts in EDDP-style ''(planned)''

'''Buildings at the city of Leipzig (Static models)''' 
* City-Hochhaus {{progressbar|90}}
* Wintergartenhochhaus ''(published 02/2013)'' {{tick}}
* Völkerschlachtdenkmal (Battle of Nations Monument) {{hourglass}}
* Red-Bull Arena {{hourglass}}
* Gondwanaland (tropical zoo) ''(published 02/2013)'' {{tick}}
* DVB-T-Tower ''(published 02/2013)'' {{tick}}
* Messeturm Leipzig ''(published 02/2013)'' {{tick}}
* Hauptbahnhof (Central Station) ''(planned)''

=== Models since 2012 ===
[[File:EDDP TerminalC.jpeg|Terminal C]] [[File:EDDP VDGS-136 thumbnail.jpg|VDGS at position 136]] [[File:EDDP-DHL-tank.jpeg|DHL-Tank at fuel storage area on apron 4]] [[File:EDDP_luggageterminal_thumb.jpg|Luggage Terminal at Apron 1]]

=== Models since 2010 ===
Here is a selection of the models. [http://www.youtube.com/watch?v=3kNDGiSNUdE YouTube video 2010].

[[File:EDDP10.jpg]] [[File:EDDP11.jpg]] [[File:EDDP12.jpg]] [[File:EDDP13.jpg]] [[File:EDDPbridge1.png]]

== Related content ==
* [[Germany]]
* [[Leipzig/Halle Airspace]]

== External links ==
* [http://www.vacc-sag.org/airport/EDDP Airport Diagrams]
* [http://de.wikipedia.org/wiki/EDDP Leipzig/Halle Airport at Wikipedia] (German)

[[Category:Airports in Germany]]

Leipzig/Halle Airport

2014-06-20T09:01:26Z

August:

{{infobox Airport
|name = Leipzig/Halle Airport
|image =EDDP TerminalC.jpeg
|alt =New terminal C (published 2012)
|iata =LEJ
|icao =EDDP
|type =Public
|city =Between Leipzig and Halle
|owner =Mitteldeutsche Airport Holding
|website =http://www.leipzig-halle-airport.de/
|scenerytile =e012n51
|download =
|terrasync = [[#Download_via_GIT]] for latest scenery
|runway= 08L/26R
|length= 11,811 ft
|material= Concrete (in FG still Asphalt)
|runway2= 08R/26L
|length2= 11,811 ft
|material2= Concrete (in FG still Asphalt)
}}

'''Leipzig/Halle Airport''' is located in Schkeuditz, Saxony and serves both Leipzig, Saxony and Halle, Saxony-Anhalt, [[Germany]]. In Flightgear this airport was published on [[TerraSync|TerraSync]] in 2010 und updated due to new developments 2012. In 2014 according to the new world scenery a complete overhaul started.
EDDP is also the centre of Leipzig/Halle airspace, which provides air traffic control also for the regional airfield [[Leipzig-Altenburg Airport]].

{{Note|Currently users are asked to test the '''beta Version of the new 850-Layout''' (see [[#Download_via_GIT]])}}

However, if you want something to be configurable, one important thing is having an element ID that we can refer to, in order to look up the key and modify the symbol via Nasal. Without having an element id (e.g. for labels) we cannot easily modify such SVG images procedurally.}}
== Flying at Leipzig/Halle airspace ==

=== Charts ===
All [http://www.vacc-sag.org/airport/EDDP diagrams and charts] are available for download.

=== Runways and ILS ===

==== Runway 08L/26R ====
[[File:2012-09 Apron4 Luftbild-at-night.png|thumb|270px|Apron 4 and runway 26L at night]]The northern [[runway]] is 3600m long with a width of 45m. In real life its usually used by passenger airliners. In Flightgear this runway is equipped with Outer Marker and Middle Marker and offers best conditions for '''low visibility operations'''.
* ILS-CAT-III '''08L''' (083°): 108.55
* ILS-CAT-III '''26R''' (263°): 108.35
==== Runway 08R/26L ====
The southern [[runway]] is 3600m long with a width of 60m. In real life its mostly used by freighters due to its proximity to freight areas (Apron 2 and 4). It has no Outer Marker an no Middle Marker.
* ILS-CAT-III '''08R''' (083°): 111.90 (111.75 in FG older than Version 2.0.0)
* ILS-CAT-III '''26L''' (263°): 110.30

=== ATC ===
* Leipzig Ground - frequency 121.800
* Leipzig Tower - frequency 121.100

Leipzig/Halle Airport is regularly served by Air Traffic Control ([[ATC]]).

== Infrastructure ==
[[File:EDDP-overview-daytime.jpg|thumb|270px|Overview 2012]]Connected by terminal C and three taxiway bridges (W1, E7, E8) the airport layout combines the northern part with runway 08L/26L and Apron 3 (new cargo area since 2012) and the southern part with Apron 1 (terminal B), runway 08R/26L, Apron 2, Apron 4 (DHL), Apron 5. Between both parts an airport railway station and the autobahn A14 is connecting to the check-in area of terminal C. Railway and motorway are not modelled in Flightgear.

=== Access and connection ===
[[File:TerminalC-morning.jpg|thumb|270px|Terminal C at dawn]]
==== Terminal C ====
In August 2012 the completely new modelled terminal C was published on TerraSync. It is built as a connection between the check-in building with car-park and train station in the north and the departure area at terminal B in the south. Due to this efforts it stands on piers like a long bridge from apron 1 to apron 3, crossing different car-parks, a rail-track and the autobahn.
On the one hand the FlighGear model tries to give the airport a well designed model with highly detailed structures, but on the other hand it was programmed as simple as possible to save visitors simulation performance.

==== Taxiway bridges ====
[[File:EDDP-Taxibridges-e7e8-night.jpg|thumb|270px|Rampbridges E7, E8 with new lightning in 2012]]A highway and railway lines go straight between the two runways. Three bridges connect the terminal with the northern runway. The western bridge (taxiway W1) is used in both directions. The eastern bridges (taxiways E7 and E8) are used as one way taxiways. Due to safety improvements all bridges are equipped with special taxi lights.
Due to changes in the TerraData the bridges had to be repositioned in 2012.

=== Apron 1 ===

The main apron at Leipzig/Halle Airport is located in the middle of the airport. It houses the commercial aviation area at terminal B in the west and the general aviation area in the eastern part. It is connected by taxiways L, N and W1.

==== Terminal B ====
[[File:EDDP VDGS-134 thumbnail.jpg|thumb|270px|VDGS on each gateway at terminal B]]'''Real world''':
This building is the main terminal for most commercial flights at EDDP. It is connected to terminal C in the north and provides the passenger transfer to Apron 1 via 6 gateways. It also has a connection to the luggage terminal.

'''Scenery in TerraSync''':
In Flightgear the main terminal is modelled very slim and efficiently. 6 unmovable gateways link to park positions 126, 128, 130, 132, 134 and 136. In 2012 it will be improved. Since September 2012 it has been equipped with a non-animated [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System VDGS].

==== Luggage terminal ====
This building was first published in 2004 and remodelled by Thomas Großberger in 2012. The terminal is connected via the old tower next to it to terminal A by a tube, which is used to transport luggage between the checkin- and arrival-area and Apron 1. Both. the connection and the old tower building will be modelled in 2013. The new luggage terminal in FlightGear is offering:
* realistic roof design
* simplified but detailed interior
* 6 clock controlled automatic gates
* complex light design (Rembrandt-Design outstanding)

==== GAT ====

=== Apron 2 ===

=== Apron 3 ===
This Apron in real life went into service with a new cargo hangar in 2012. In Flightgear it is still closed. The corresponding facilities are still under development.

=== Apron 4/5 (DHL-area) ===
[[File:2012-08 Apron4 Pos432 BOX1522-D-STHO-and-DC10.png|thumb|270px|DHL-area at apron 4]]'''Real world:''' Leipzig/Halle is just a small international airport. But in 2008 it became the [http://www.dp-dhl.com/en/logistics_around_us/from_our_divisions/leipzig_hub.html European DHL hub] with up to 60 planes per night. The DHL Hub Leipzig GmbH, place of business in Schkeuditz, is running under contract to the logistic group DHL at Leipzig/Halle Airport one of six international aviation hubs. In order to provide maintenance to the new fleet the [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig GmbH] was founded. European Air Transport operates services to Europe, Middle East and Africa. 56 countries are covered in total. A second aviation company, called [http://en.wikipedia.org/wiki/Aerologic AeroLogic], was founded in EDDP. AeroLogic GmbH, a joint-venture between DHL Express and Lufthansa Cargo, is a German cargo airline headquartered in Schkeuditz, Saxony. It operates cargo flights out of Leipzig/Halle Airport and Frankfurt, most of which are on behalf of its parent companies.

{| class="wikitable" cellpadding="3" style="margin-left:auto; margin-right:auto"
|+ '''Fleet of [http://en.wikipedia.org/wiki/Aerologic AeroLogic] and [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig] and others''' (2012)
|-
!Aircraft
!Total
!Orders
!Oparator
|-
|[[Airbus A300|Airbus A300B4-203F]]
|<center>10</center>
|
|Air Contractors
|-
|[[Airbus A300|Airbus A300-600RF]]
|<center>8</center>
|<center>10</center>
|European Air Transport Leipzig
|-
|Boeing 737-300F
|<center>9</center>
|
|European Air Transport Leipzig
|-
|Boeing 737-400F
|<center>1</center>
|
|Europe Airpost
|-
|[[Boeing 757|Boeing 757-236SF]]
|<center>10</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 757|Boeing 757-23APF]]
|<center>1</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 777F]]
|<center>8</center>
|
|AeroLogic
|-
!Total
!47
!10
!colspan=2|
|}

[[File:EDDP-DHL-tank.jpeg|thumb|270px|DHL-Tank at fuel storage area on apron 4]]'''Scenery in TerraSync:''' The hub (warehouse, hangar and aprons) is modelled in the scenery. In 2012 its redesign for TerraSync started. First all lampposts at apron 4 had been replaced with those which fit into the correct layout of every single parking position. Afterwards lots of goods and ground vehicles where placed. As soon as some missing storage buildings are modelled, the new content of apron 4 will be published on TerraSync. Last modifications will take place when the new [[Airport data (apt.dat) update|850-standard layout]] of EDDP will be created in the future.

'''DHL-hub at EDDP in Flightgear:''' Leipzig/Halle Airport offers ground space for more than 70 Boeing [[757-200|757-PF]] or up to 50 [[777F]] as well as space for 10 [[Antonov An-124|An-124]] at Apron 2, 4 and 5. Airmail flights can be flown from and to EDDP. One of the middle sized and highly connected hubs of DHL, the [[Orio al Serio Airport]] (Italy) is also modelled in FlightGear and can be used for realistic flights out of Leipzig/Halle Airport.
In FlighGear apron 4 is equipped with all stands. Additionally to the main apron lightning each stand has one centred lamppost, which will be replaced by a VDGS-signs in the future. Ground markings will come with the new 850-layout. The major storage buildings from DHL are modelled as well as three DHL-tanks south from apron 4.

=== De-icing areas ===
Leipzig/Halle Airport has four special areas, two in the north at taxiway C and two in the south at taxiway N. In FlightGear only the two areas at taxiway C are build into the layout. In 2012 both areas had been equipped with shared models like lampposts, buildings and ground lights.

==== De-icing area 2 - multiplayer ready ====

Based on the Zurich type model "Elephant" - originally modelled by Oliver Thurau - an improved version with full multiplayer support is under development. This version isn't only adapted to the special efforts at EDDP, but its also designed to be controlled by ATC. It will be published via TerraSync in November 2014.

== Surroundings and "Other" ==

=== Kursdorf - the village within the airport ===
There is a village right in middle of the airport. So it's no surprise the number of inhabitants is shrinking each year. Once a thriving village with 537 inhabitants in 1950, they were down to 119 in 2006 [http://de.wikipedia.org/wiki/Kursdorf_%28Schkeuditz%29 (Wikipedia)]. It might be a little loud with the two runways, highway and express railways, but the transport links, hey ... The village is modelled in the scenery.

== Scenery ==
{|
| Authors: ||
* Models: David G., Thomas Großberger
* Airport layout: Christian Schmitt
* Additional models: Don Lavelle, Alex Park, Robert Shearman
* Redesigning & Development 2012: August Geyler, Thomas Großberger
|-
|}

=== Download via GIT ===
With FlightGear 3.0 a new world scenery was published, including a new but incorrect 850-layout for EDDP. Developers started a huge overhaul of the EDDP scenery in April 2014. First a new taxiway layout was programmed. Additionally all buildings and objects are replaced. Some models will be remodelled, others will be added. Due to the fact that airport layouts can't be simply updated via TerraSync in a short way, pilots are asked to use the new EDDP CUSTOM SCENERY as long as things aren't updated at TerraSync.

* Download-Development-Scenery
* updated regularly
** '''git clone''' [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/ https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/]
** or [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/archive/5a44d12dfc0f41433fd1aedd0f6fadebcf503066.tar.gz download a ZIP] (101 MB)

=== Download via TerraSync ===
[[TerraSync]] has it all! There is no custom scenery existing (only the GIT-repository for testing the new 850-layout before publishing it). The authors believe on the advantages of TerraSync which makes it easy for every user to have the latest scenery installed automatically. Updates are published regularly via TerraSync.
* Next update in '''<daysuntil in="days">12-August-2014</daysuntil>''' {{Progressbar|height=45|percentage={{#expr: trunc ({{#time: z}} - {{#time: z | May 19 2014 }}) round -1 }}}}

* '''Latest update on TerraSync:'''
** '''2014-04-29''' ''Objects adapted to new (but incorrect) 850-layout''

* Last five updates:
** '''2013-04-21''' ''Rembrandt lights at apron 1''
** 2013-02-13 ''new Messeturm at final approach area of runway 26R''
** 2012-12-21 ''new luggage terminal at apron 1''
** 2012-10-22 ''three new DHL-tanks placed at DHL-area''
** 2012-09-20 ''new VisualGuidingDockingSystem at terminal B''

=== Development ===
Since the Scenery had been modelled by [[User:D-79|D-79]] in 2010, Thomas Großberger and [[User:August|August Geyler]] started enhancements and redesigning in 2012. In 2014 development of a new 850-layout started. Improvements are made on the following objects:

'''Layout''' 
* Taxiway bridges: new Position, improved lightning ''(published 07/2012)'' {{tick}}
* New 850-standard: new Layout with all parking positions and improved taxiways ''(pre-development)'' {{progressbar|80}} (see [[#Download_via_GIT]])

'''Scenery (Shared Models)''' 
* Airport lightning: more than 80 lampposts ([[EDDM]]-model) on Apron 1 and 4 and both northern de-icing areas ''(published 07/2012)'' {{tick}}
* DHL-tanks at apron 4 ''(published 10/2012)'' {{tick}}
* Ground traffic: lots of goods and vehicles (shared) make apron 1 and 4 much more realistic ''(published 08/2012)'' {{tick}}
* Flora and boundaries: Trees and fences on Apron 1, 2 and 4 are added ''(published 08/2012)'' {{tick}}
* New shared ground vehicles
** Container dolly ''(under development)'' {{hourglass}}
** Luggage dolly ''(under development)'' {{hourglass}}
** Pallet dolly ''(planned)''
* New shared Unit Load Devices (ULD)
** Airfreight container - Type AKH ''(pre-development)'' {{hourglass}}
** Airfreight pallet ''(planed)''
* Village and industrial surroundings: Kursdorf within the airport and industrial areas around are created with shared models ''(published 04/2010)'' {{tick}}

'''Buildings and infrastructure (Static models)''' 
* Cargo-hangar apron 3 ''(planned)''
* Cargo-center apron 2 ''(published 2010)'' {{tick}}
* DHL-hangar ''(published 2010)'' {{tick}}
* DHL-terminal ''(published 2010)'' {{tick}}
* Interactive DE-ICING areas (Multiplayer supported) {{hourglass}}
* Interactive luggage dolly traffic between terminal B and lugage terminal ''(planned)''
* Luggage terminal ''(published 12/2012)'' {{tick}}
* Storage buildings at DHL-area ''(pre-development)'' {{hourglass}}
* Terminal B ''(published 04/2010)'' {{tick}}
* Terminal C ''(published 08/2012)'' {{tick}}
* Tower ''(published 2010)'' {{tick}}
* Turbo engine hall ''(pre-development)'' {{hourglass}}
* Old Tower next to terminal B ''(pre-development)'' {{hourglass}}
* Visual Docking Guiding System at Apron 4 ''(planned)''
* Visual Docking Guiding System at Terminal B ''(published 09/2012)'' {{tick}}
* Visual Docking Guiding System: replacement with animated interactive version ''(planned)''
'''Rembrandt lightning improvements'''
* Converting Lightning to [[Project Rembrandt|Rembrandt]]
** Rembrandt lights at apron 1 ''(published 04/2013)'' {{tick}}
** Rembrandt lights at apron 4 {{progressbar|80}}
* Converting Buildings to [[Project Rembrandt|Rembrandt]] Lightning
** Luggage terminal ''(pre-development)'' {{hourglass}}
** Terminal B ''(planned)''
** Terminal C ''(planned)''
** Tower ''(planned)''
** DHL-hangar ''(planned)''
* Lampposts in EDDP-style ''(planned)''

'''Buildings at the city of Leipzig (Static models)''' 
* City-Hochhaus {{progressbar|90}}
* Wintergartenhochhaus ''(published 02/2013)'' {{tick}}
* Völkerschlachtdenkmal (Battle of Nations Monument) {{hourglass}}
* Red-Bull Arena {{hourglass}}
* Gondwanaland (tropical zoo) ''(published 02/2013)'' {{tick}}
* DVB-T-Tower ''(published 02/2013)'' {{tick}}
* Messeturm Leipzig ''(published 02/2013)'' {{tick}}
* Hauptbahnhof (Central Station) ''(planned)''

=== Models since 2012 ===
[[File:EDDP TerminalC.jpeg|Terminal C]] [[File:EDDP VDGS-136 thumbnail.jpg|VDGS at position 136]] [[File:EDDP-DHL-tank.jpeg|DHL-Tank at fuel storage area on apron 4]] [[File:EDDP_luggageterminal_thumb.jpg|Luggage Terminal at Apron 1]]

=== Models since 2010 ===
Here is a selection of the models. [http://www.youtube.com/watch?v=3kNDGiSNUdE YouTube video 2010].

[[File:EDDP10.jpg]] [[File:EDDP11.jpg]] [[File:EDDP12.jpg]] [[File:EDDP13.jpg]] [[File:EDDPbridge1.png]]

== Related content ==
* [[Germany]]
* [[Leipzig/Halle Airspace]]

== External links ==
* [http://www.vacc-sag.org/airport/EDDP Airport Diagrams]
* [http://de.wikipedia.org/wiki/EDDP Leipzig/Halle Airport at Wikipedia] (German)

[[Category:Airports in Germany]]

Leipzig/Halle Airport

2014-05-24T13:31:57Z

August: cosmetics

{{infobox Airport
|name = Leipzig/Halle Airport
|image =EDDP TerminalC.jpeg
|alt =New terminal C (published 2012)
|iata =LEJ
|icao =EDDP
|type =Public
|city =Between Leipzig and Halle
|owner =Mitteldeutsche Airport Holding
|website =http://www.leipzig-halle-airport.de/
|scenerytile =e012n51
|download =
|terrasync = [[#Download_via_GIT]] for latest scenery
|runway= 08L/26R
|length= 11,811 ft
|material= Concrete (in FG still Asphalt)
|runway2= 08R/26L
|length2= 11,811 ft
|material2= Concrete (in FG still Asphalt)
}}

'''Leipzig/Halle Airport''' is located in Schkeuditz, Saxony and serves both Leipzig, Saxony and Halle, Saxony-Anhalt, [[Germany]]. In Flightgear this airport was published on [[TerraSync|TerraSync]] in 2010 und updated due to new developments 2012. In 2014 according to the new world scenery a complete overhaul started.
EDDP is also the centre of Leipzig/Halle airspace, which provides air traffic control also for the regional airfield [[Leipzig-Altenburg Airport]].

{{Note|Currently users are asked to test the '''beta Version of the new 850-Layout''' (see [[#Download_via_GIT]])}}

However, if you want something to be configurable, one important thing is having an element ID that we can refer to, in order to look up the key and modify the symbol via Nasal. Without having an element id (e.g. for labels) we cannot easily modify such SVG images procedurally.}}
== Flying at Leipzig/Halle airspace ==

=== Charts ===
All [http://www.vacc-sag.org/airport/EDDP diagrams and charts] are available for download.

=== Runways and ILS ===

==== Runway 08L/26R ====
[[File:2012-09 Apron4 Luftbild-at-night.png|thumb|270px|Apron 4 and runway 26L at night]]The northern [[runway]] is 3600m long with a width of 45m. In real life its usually used by passenger airliners. In Flightgear this runway is equipped with Outer Marker and Middle Marker and offers best conditions for '''low visibility operations'''.
* ILS-CAT-III '''08L''' (083°): 108.55
* ILS-CAT-III '''26R''' (263°): 108.35
==== Runway 08R/26L ====
The southern [[runway]] is 3600m long with a width of 60m. In real life its mostly used by freighters due to its proximity to freight areas (Apron 2 and 4). It has no Outer Marker an no Middle Marker.
* ILS-CAT-III '''08R''' (083°): 111.90 (111.75 in FG older than Version 2.0.0)
* ILS-CAT-III '''26L''' (263°): 110.30

=== ATC ===
* Leipzig Ground - frequency 121.800
* Leipzig Tower - frequency 121.100

Leipzig/Halle Airport is regularly served by Air Traffic Control ([[ATC]]).

== Infrastructure ==
[[File:EDDP-overview-daytime.jpg|thumb|270px|Overview 2012]]Connected by terminal C and three taxiway bridges (W1, E7, E8) the airport layout combines the northern part with runway 08L/26L and Apron 3 (new cargo area since 2012) and the southern part with Apron 1 (terminal B), runway 08R/26L, Apron 2, Apron 4 (DHL), Apron 5. Between both parts an airport railway station and the autobahn A14 is connecting to the check-in area of terminal C. Railway and motorway are not modelled in Flightgear.

=== Access and connection ===
[[File:TerminalC-morning.jpg|thumb|270px|Terminal C at dawn]]
==== Terminal C ====
In August 2012 the completely new modelled terminal C was published on TerraSync. It is built as a connection between the check-in building with car-park and train station in the north and the departure area at terminal B in the south. Due to this efforts it stands on piers like a long bridge from apron 1 to apron 3, crossing different car-parks, a rail-track and the autobahn.
On the one hand the FlighGear model tries to give the airport a well designed model with highly detailed structures, but on the other hand it was programmed as simple as possible to save visitors simulation performance.

==== Taxiway bridges ====
[[File:EDDP-Taxibridges-e7e8-night.jpg|thumb|270px|Rampbridges E7, E8 with new lightning in 2012]]A highway and railway lines go straight between the two runways. Three bridges connect the terminal with the northern runway. The western bridge (taxiway W1) is used in both directions. The eastern bridges (taxiways E7 and E8) are used as one way taxiways. Due to safety improvements all bridges are equipped with special taxi lights.
Due to changes in the TerraData the bridges had to be repositioned in 2012.

=== Apron 1 ===

The main apron at Leipzig/Halle Airport is located in the middle of the airport. It houses the commercial aviation area at terminal B in the west and the general aviation area in the eastern part. It is connected by taxiways L, N and W1.

==== Terminal B ====
[[File:EDDP VDGS-134 thumbnail.jpg|thumb|270px|VDGS on each gateway at terminal B]]'''Real world''':
This building is the main terminal for most commercial flights at EDDP. It is connected to terminal C in the north and provides the passenger transfer to Apron 1 via 6 gateways. It also has a connection to the luggage terminal.

'''Scenery in TerraSync''':
In Flightgear the main terminal is modelled very slim and efficiently. 6 unmovable gateways link to park positions 126, 128, 130, 132, 134 and 136. In 2012 it will be improved. Since September 2012 it has been equipped with a non-animated [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System VDGS].

==== Luggage terminal ====
This building was first published in 2004 and remodelled by Thomas Großberger in 2012. The terminal is connected via the old tower next to it to terminal A by a tube, which is used to transport luggage between the checkin- and arrival-area and Apron 1. Both. the connection and the old tower building will be modelled in 2013. The new luggage terminal in FlightGear is offering:
* realistic roof design
* simplified but detailed interior
* 6 clock controlled automatic gates
* complex light design (Rembrandt-Design outstanding)

==== GAT ====

=== Apron 2 ===

=== Apron 3 ===
This Apron in real life went into service with a new cargo hangar in 2012. In Flightgear it is still closed. The corresponding facilities are still under development.

=== Apron 4/5 (DHL-area) ===
[[File:2012-08 Apron4 Pos432 BOX1522-D-STHO-and-DC10.png|thumb|270px|DHL-area at apron 4]]'''Real world:''' Leipzig/Halle is just a small international airport. But in 2008 it became the [http://www.dp-dhl.com/en/logistics_around_us/from_our_divisions/leipzig_hub.html European DHL hub] with up to 60 planes per night. The DHL Hub Leipzig GmbH, place of business in Schkeuditz, is running under contract to the logistic group DHL at Leipzig/Halle Airport one of six international aviation hubs. In order to provide maintenance to the new fleet the [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig GmbH] was founded. European Air Transport operates services to Europe, Middle East and Africa. 56 countries are covered in total. A second aviation company, called [http://en.wikipedia.org/wiki/Aerologic AeroLogic], was founded in EDDP. AeroLogic GmbH, a joint-venture between DHL Express and Lufthansa Cargo, is a German cargo airline headquartered in Schkeuditz, Saxony. It operates cargo flights out of Leipzig/Halle Airport and Frankfurt, most of which are on behalf of its parent companies.

{| class="wikitable" cellpadding="3" style="margin-left:auto; margin-right:auto"
|+ '''Fleet of [http://en.wikipedia.org/wiki/Aerologic AeroLogic] and [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig] and others''' (2012)
|-
!Aircraft
!Total
!Orders
!Oparator
|-
|[[Airbus A300|Airbus A300B4-203F]]
|<center>10</center>
|
|Air Contractors
|-
|[[Airbus A300|Airbus A300-600RF]]
|<center>8</center>
|<center>10</center>
|European Air Transport Leipzig
|-
|Boeing 737-300F
|<center>9</center>
|
|European Air Transport Leipzig
|-
|Boeing 737-400F
|<center>1</center>
|
|Europe Airpost
|-
|[[Boeing 757|Boeing 757-236SF]]
|<center>10</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 757|Boeing 757-23APF]]
|<center>1</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 777F]]
|<center>8</center>
|
|AeroLogic
|-
!Total
!47
!10
!colspan=2|
|}

[[File:EDDP-DHL-tank.jpeg|thumb|270px|DHL-Tank at fuel storage area on apron 4]]'''Scenery in TerraSync:''' The hub (warehouse, hangar and aprons) is modelled in the scenery. In 2012 its redesign for TerraSync started. First all lampposts at apron 4 had been replaced with those which fit into the correct layout of every single parking position. Afterwards lots of goods and ground vehicles where placed. As soon as some missing storage buildings are modelled, the new content of apron 4 will be published on TerraSync. Last modifications will take place when the new [[Airport data (apt.dat) update|850-standard layout]] of EDDP will be created in the future.

'''DHL-hub at EDDP in Flightgear:''' Leipzig/Halle Airport offers ground space for more than 70 Boeing [[757-200|757-PF]] or up to 50 [[777F]] as well as space for 10 [[Antonov An-124|An-124]] at Apron 2, 4 and 5. Airmail flights can be flown from and to EDDP. One of the middle sized and highly connected hubs of DHL, the [[Orio al Serio Airport]] (Italy) is also modelled in FlightGear and can be used for realistic flights out of Leipzig/Halle Airport.
In FlighGear apron 4 is equipped with all stands. Additionally to the main apron lightning each stand has one centred lamppost, which will be replaced by a VDGS-signs in the future. Ground markings will come with the new 850-layout. The major storage buildings from DHL are modelled as well as three DHL-tanks south from apron 4.

=== De-icing areas ===
Leipzig/Halle Airport has four special areas, two in the north at taxiway C and two in the south at taxiway N. In FlightGear only the two areas at taxiway C are build into the layout. In 2012 both areas had been equipped with shared models like lampposts, buildings and ground lights.

==== De-icing area 2 - multiplayer ready ====

Based on the Zurich type model "Elephant" - originally modelled by Oliver Thurau - an improved version with full multiplayer support is under development. This version isn't only adapted to the special efforts at EDDP, but its also designed to be controlled by ATC. It will be published via TerraSync in November 2014.

== Surroundings and "Other" ==

=== Kursdorf - the village within the airport ===
There is a village right in middle of the airport. So it's no surprise the number of inhabitants is shrinking each year. Once a thriving village with 537 inhabitants in 1950, they were down to 119 in 2006 [http://de.wikipedia.org/wiki/Kursdorf_%28Schkeuditz%29 (Wikipedia)]. It might be a little loud with the two runways, highway and express railways, but the transport links, hey ... The village is modelled in the scenery.

== Scenery ==
{|
| Authors: ||
* Models: David G., Thomas Großberger
* Airport layout: Christian Schmitt
* Additional models: Don Lavelle, Alex Park, Robert Shearman
* Redesigning & Development 2012: August Geyler, Thomas Großberger
|-
|}

=== Download via GIT ===
With FlightGear 3.0 a new world scenery was published, including a new but incorrect 850-layout for EDDP. Developers started a huge overhaul of the EDDP scenery in April 2014. First a new taxiway layout was programmed. Additionally all buildings and objects are replaced. Some models will be remodelled, others will be added. Due to the fact that airport layouts can't be simply updated via TerraSync in a short way, pilots are asked to use the new EDDP CUSTOM SCENERY as long as things aren't updated at TerraSync.

* Download-Development-Scenery
* updated regularly
** '''git clone''' [https://git.gitorious.org/eddp-custom-scenery/eddp-custom-scenery.git https://git.gitorious.org/eddp-custom-scenery/eddp-custom-scenery.git]
** or [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/archive/5a44d12dfc0f41433fd1aedd0f6fadebcf503066.tar.gz download a ZIP] (101 MB)

=== Download via TerraSync ===
[[TerraSync]] has it all! There is no custom scenery existing (only the GIT-repository for testing the new 850-layout before publishing it). The authors believe on the advantages of TerraSync which makes it easy for every user to have the latest scenery installed automatically. Updates are published regularly via TerraSync.
* Next update in '''<daysuntil in="days">12-August-2014</daysuntil>''' {{Progressbar|height=45|percentage={{#expr: trunc ({{#time: z}} - {{#time: z | May 19 2014 }}) round -1 }}}}

* '''Latest update on TerraSync:'''
** '''2014-04-29''' ''Objects adapted to new (but incorrect) 850-layout''

* Last five updates:
** '''2013-04-21''' ''Rembrandt lights at apron 1''
** 2013-02-13 ''new Messeturm at final approach area of runway 26R''
** 2012-12-21 ''new luggage terminal at apron 1''
** 2012-10-22 ''three new DHL-tanks placed at DHL-area''
** 2012-09-20 ''new VisualGuidingDockingSystem at terminal B''

=== Development ===
Since the Scenery had been modelled by [[User:D-79|D-79]] in 2010, Thomas Großberger and [[User:August|August Geyler]] started enhancements and redesigning in 2012. In 2014 development of a new 850-layout started. Improvements are made on the following objects:

'''Layout''' 
* Taxiway bridges: new Position, improved lightning ''(published 07/2012)'' {{tick}}
* New 850-standard: new Layout with all parking positions and improved taxiways ''(pre-development)'' {{progressbar|80}} (see [[#Download_via_GIT]])

'''Scenery (Shared Models)''' 
* Airport lightning: more than 80 lampposts ([[EDDM]]-model) on Apron 1 and 4 and both northern de-icing areas ''(published 07/2012)'' {{tick}}
* DHL-tanks at apron 4 ''(published 10/2012)'' {{tick}}
* Ground traffic: lots of goods and vehicles (shared) make apron 1 and 4 much more realistic ''(published 08/2012)'' {{tick}}
* Flora and boundaries: Trees and fences on Apron 1, 2 and 4 are added ''(published 08/2012)'' {{tick}}
* New shared ground vehicles
** Container dolly ''(under development)'' {{hourglass}}
** Luggage dolly ''(under development)'' {{hourglass}}
** Pallet dolly ''(planned)''
* New shared Unit Load Devices (ULD)
** Airfreight container - Type AKH ''(pre-development)'' {{hourglass}}
** Airfreight pallet ''(planed)''
* Village and industrial surroundings: Kursdorf within the airport and industrial areas around are created with shared models ''(published 04/2010)'' {{tick}}

'''Buildings and infrastructure (Static models)''' 
* Cargo-hangar apron 3 ''(planned)''
* Cargo-center apron 2 ''(published 2010)'' {{tick}}
* DHL-hangar ''(published 2010)'' {{tick}}
* DHL-terminal ''(published 2010)'' {{tick}}
* Interactive DE-ICING areas (Multiplayer supported) {{hourglass}}
* Interactive luggage dolly traffic between terminal B and lugage terminal ''(planned)''
* Luggage terminal ''(published 12/2012)'' {{tick}}
* Storage buildings at DHL-area ''(pre-development)'' {{hourglass}}
* Terminal B ''(published 04/2010)'' {{tick}}
* Terminal C ''(published 08/2012)'' {{tick}}
* Tower ''(published 2010)'' {{tick}}
* Turbo engine hall ''(pre-development)'' {{hourglass}}
* Old Tower next to terminal B ''(pre-development)'' {{hourglass}}
* Visual Docking Guiding System at Apron 4 ''(planned)''
* Visual Docking Guiding System at Terminal B ''(published 09/2012)'' {{tick}}
* Visual Docking Guiding System: replacement with animated interactive version ''(planned)''
'''Rembrandt lightning improvements'''
* Converting Lightning to [[Project Rembrandt|Rembrandt]]
** Rembrandt lights at apron 1 ''(published 04/2013)'' {{tick}}
** Rembrandt lights at apron 4 {{progressbar|80}}
* Converting Buildings to [[Project Rembrandt|Rembrandt]] Lightning
** Luggage terminal ''(pre-development)'' {{hourglass}}
** Terminal B ''(planned)''
** Terminal C ''(planned)''
** Tower ''(planned)''
** DHL-hangar ''(planned)''
* Lampposts in EDDP-style ''(planned)''

'''Buildings at the city of Leipzig (Static models)''' 
* City-Hochhaus {{progressbar|90}}
* Wintergartenhochhaus ''(published 02/2013)'' {{tick}}
* Völkerschlachtdenkmal (Battle of Nations Monument) {{hourglass}}
* Red-Bull Arena {{hourglass}}
* Gondwanaland (tropical zoo) ''(published 02/2013)'' {{tick}}
* DVB-T-Tower ''(published 02/2013)'' {{tick}}
* Messeturm Leipzig ''(published 02/2013)'' {{tick}}
* Hauptbahnhof (Central Station) ''(planned)''

=== Models since 2012 ===
[[File:EDDP TerminalC.jpeg|Terminal C]] [[File:EDDP VDGS-136 thumbnail.jpg|VDGS at position 136]] [[File:EDDP-DHL-tank.jpeg|DHL-Tank at fuel storage area on apron 4]] [[File:EDDP_luggageterminal_thumb.jpg|Luggage Terminal at Apron 1]]

=== Models since 2010 ===
Here is a selection of the models. [http://www.youtube.com/watch?v=3kNDGiSNUdE YouTube video 2010].

[[File:EDDP10.jpg]] [[File:EDDP11.jpg]] [[File:EDDP12.jpg]] [[File:EDDP13.jpg]] [[File:EDDPbridge1.png]]

== Related content ==
* [[Germany]]
* [[Leipzig/Halle Airspace]]

== External links ==
* [http://www.vacc-sag.org/airport/EDDP Airport Diagrams]
* [http://de.wikipedia.org/wiki/EDDP Leipzig/Halle Airport at Wikipedia] (German)

[[Category:Airports in Germany]]

List of developed airports

2014-05-23T12:59:15Z

August: new entry EDDS

This page lists developed airports which are included in FlightGear if two conditions are fulfilled. Airports are listed here if
* at least one building or [[Signs|taxi signs]] have been placed
* the respective objects are represented in the [[FlightGear Scenery Database]].
Every improvement listed here can be downloaded using [[TerraSync]] and it will also be included in the next [[World Scenery]] release.

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]].

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

'''Note:''' You can sort the table by clicking one of the [[File:Sort none.gif]] symbols in the row headers.

== Airports ==

{| class="wikitable sortable" border="0" cellspacing="0"
|-
! style="background:#efefef" | ICAO !! style="background:#efefef" | Name !! style="background:#efefef" | Country !! style="background:#efefef" | Continent !! class="unsortable" style="background:#efefef" | Comment

|-
| [http://mapserver.flightgear.org/map/?lon=13.76716&lat=51.13277&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDC] || [[Dresden Airport]] || Germany || Europe || some models: tower, terminal, animated hangars etc. ''Everything published via TerraSync''

|-
| [http://mapserver.flightgear.org/map/?lon=8.56293&lat=50.03795&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDF] || [[Frankfurt am Main Airport]] || Germany || Europe || Fully modeled with [[Signs]] and [[Interactive Traffic]] and unique scycrapers downtown

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

|-
| [http://mapserver.flightgear.org/map/?lon=13.40379&lat=52.47502&zoom=15&layers=B000000TFFFFTFFFTTFFF EDDI] ||[[Berlin Tempelhof Airport]] || Germany || Europe || Fully modeled

|-
| EDDL || [[Düsseldorf International Airport|Düsseldorf Airport]] || Germany || Europe || Tower and terminal

|-
| [http://mapserver.flightgear.org/map/?lon=11.78609&lat=48.35378&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDM] || [[Munich Airport]] || Germany || Europe || Fully modelled

|-
| [http://mapserver.flightgear.org/map/?lon=12.23603&lat=51.42262&zoom=14&layers=B000000TFFFFTFFFTTFFF EDDP] || [[Leipzig/Halle Airport]] || Germany || Europe || Fully modelled with [[Signs]]

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

|-
| [http://mapserver.flightgear.org/map/?lon=13.28992&lat=52.55917&zoom=15&layers=B000000TFFFFTFFFTTFFF EDDT] || [[Berlin Tegel Airport]] || Germany || Europe || Tower, terminals, [[Signs]] and unique buildings downtown

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

|-
| [http://mapserver.flightgear.org/map/?lon=10.71706&lat=53.80496&zoom=15&layers=B000000TFFFFTFFFTTFFF 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]

|-
| [http://mapserver.flightgear.org/map/?lon=7.16278&lat=50.76767&zoom=15&layers=B000000TFFFFTFFFTTFFF EDKB] || [[Bonn-Hangelar Airport]] || Germany || Europe ||

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

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

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=25.04487&lat=60.25318&zoom=15&layers=B000000TFFFFTFFFTTFFF EFHF] || Helsinki-Malmi Airport || Finland || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=24.95253&lat=60.3206&zoom=14&layers=B000000TFFFFTFFFTTFFF EFHK] || Helsinki-Vantaa Airport || Finland || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=22.26281&lat=60.51412&zoom=14&layers=B000000TFFFFTFFFTFFFF 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 ||

|-
| [http://mapserver.flightgear.org/map/?lon=-0.19224&lat=51.14869&zoom=14&layers=B000000TFFFFTFFFTTFFF 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

|-
| [http://mapserver.flightgear.org/map/?lon=-0.46095&lat=51.47139&zoom=14&layers=B000000TFFFFTFFFTTFFF EGLL] || London Heathrow Airport || United Kingdom || Europe || Basic development only

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

|-
| [http://mapserver.flightgear.org/map/?lon=1.28469&lat=52.67713&zoom=15&layers=B000000TFFFFTFFFTTFFF EGSH] || Norwich Airport || United Kingdom || Europe ||

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

|-
| [http://mapserver.flightgear.org/map/?lon=4.75487&lat=52.31296&zoom=14&layers=B000000TFFFFTFFFTTFFF EHAM] || [[Amsterdam Airport Schiphol]] || Netherlands || Europe || Fully modeled, bussiest AI airport currently

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

|-
| [http://mapserver.flightgear.org/map/?lon=5.51885&lat=52.45717&zoom=15&layers=B000000TFFFFTFFFTTFFF EHLE] || [[Lelystad Airport]] || Netherlands || Europe || Fully modeled

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=6.11017&lat=62.56037&zoom=15&layers=B000000TFFFFTFFFTTFFF ENAL] || Ålesund Airport || Norway || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=6.10949&lat=61.83027&zoom=15&layers=B000000TFFFFTFFFTTFFF ENSD] || Sandane Airport || Norway || Europe ||

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=-106.60912&lat=35.04021&zoom=14&layers=B000000TFFFFTFFFTTFFF KABQ] || Albuquerque Sunport Airport, NM || USA || America || Basic development only

|-
| [http://mapserver.flightgear.org/map/?lon=-84.42809&lat=33.63672&zoom=14&layers=B000000TFFFFTFFFTTFFF KATL] || [[Hartsfield - Jackson Atlanta International Airport]], GA || USA || America || Terminal modeled

|-
| [http://mapserver.flightgear.org/map/?lon=-81.4629595&lat=41.0421187&zoom=15&layers=B000000TFFFFTFFFTTFFF KAKR] || Akron-Fulton Intl Airport, OH || USA || America || Fully modelled

|-
| [http://mapserver.flightgear.org/map/?lon=-81.43676804&lat=40.91510112&zoom=15&layers=B000000TFFFFTFFFTTFFF KCAK] || Akron-Canton Regional Airport, OH || USA || America || Fully modelled

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=-76.66833&lat=39.17535&zoom=14&layers=B000000TFFFFTFFFTTFFF KBWI] || Baltimore-Washington International, MD || USA || America || Terminal modeled with jetways, parking garage, support buildings and [[Signs]]

|-
| [http://mapserver.flightgear.org/map/?lon=-76.92254&lat=38.98062&zoom=15&layers=B000000TFFFFTFFFTTFFF KCGS] || College Park Airport, MD || USA || America ||

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

|-
| [http://mapserver.flightgear.org/map/?lon=-104.67318&lat=39.86166&zoom=13&layers=B000000TFFFFTFFFTTFFF 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 ||

|-
| [http://mapserver.flightgear.org/map/?lon=-90.07589&lat=32.31118&zoom=14&layers=B000000TFFFFTFFFTTFFF KJAN] || Jackson-Evers Airport, MS || USA || America ||

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=-118.40809&lat=33.9425&zoom=14&layers=B000000TFFFFTFFFTTFFF KLAX] || [[Los Angeles International Airport]], CA || USA|| America || Fully modeled

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

|-
| [http://mapserver.flightgear.org/map/?lon=-109.4667&lat=47.04924&zoom=14&layers=B000000TFFFFTFFFTTFFF KLWT] || Lewistown Municipal Airport, MT || USA || America ||

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=-117.69181&lat=35.68565&zoom=14&layers=B000000TFFFFTFFFTTFFF KNID] || China Lake Naval Air Weapons Station, CA || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-122.04918&lat=37.4162&zoom=15&layers=B000000TFFFFTFFFTTFFF KNUQ] || Moffett Federal Airfield, CA || USA || America || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=-122.22062&lat=37.7214&zoom=14&layers=B000000TFFFFTFFFTTFFF KOAK] || [[Oakland International Airport]], CA || USA || America || Realistic terminal, currently undergoing maintenance

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

|-
| [http://mapserver.flightgear.org/map/?lon=-88.55704&lat=43.98436&zoom=14&layers=B000000TFFFFTFFFTTFFF KOSH] || Wittman Regional Airport, Oshkosh, WI || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-75.12398&lat=38.31045&zoom=14&layers=B000000TFFFFTFFFTTFFF KOXB] || Ocean City Municipal Airport, MD || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-122.59751&lat=45.58871&zoom=14&layers=B000000TFFFFTFFFTTFFF 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 ||

|-
| [http://mapserver.flightgear.org/map/?lon=-122.3749&lat=37.61897&zoom=14&layers=B000000TFFFFTFFFTTFFF 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 ||

|-
| 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

|-
| LFEA || Belle-Ile || France || Europe ||

|-
| LFEQ || Quiberon || France || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=-3.66479&lat=48.05247&zoom=15&layers=B000000TFFFFTFFFTTFFF LFES] || Guiscriff Scaër || France || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=2.35465&lat=49.04626&zoom=15&layers=B000000TFFFFTFFFTTFFF LFFE] || Enghien Moisselles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=4.8264&lat=45.25226&zoom=15&layers=B000000TFFFFTFFFTTFFF LFLR] || Saint Rambert d'Albon Airport || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=13.76716&lat=51.13277&zoom=15&layers=B000000TFFFFTFFFTTFFF LFMA] || Aix - Les Milles Airfield || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=0.08816&lat=49.53404&zoom=14&layers=B000000TFFFFTFFFTTFFF LFOH] || Le Havre Octeville Airport || France || Europe || Fully modeled, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=5.36736&lat=43.50499&zoom=14&layers=B000000TFFFFTFFFTTFFF LFPG] || Charles de Gaulle International Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=2.60632&lat=48.89629&zoom=14&layers=B000000TFFFFTFFFTTFFF LFPH] || Chelles Le Pin Airport || France || Europe || Fully modeled, high resolution textures

|-
| LFPL || Lognes Emerainville Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| LFPO || Paris-Orly Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| LFPZ || St-Cyr-l’École Airport || France || Europe || Fully modeled, very detailed, high resolution textures

|-
| [http://mapserver.flightgear.org/map/?lon=-4.41785&lat=48.44413&zoom=12&layers=B00000000000FTFFTFFTFFFTFFFF LFRB] || Brest Bretagne Airport || France || Europe || Modeled airport with static models

|-
| [http://mapserver.flightgear.org/map/?lon=-4.15167&lat=48.53014&zoom=14&layers=B000000TFFFFTFFFTTFFF LFRL] || Lanvéoc Naval Air Base || France || Europe || Airport fitted with shared models (for helos and training)

|-
| [http://mapserver.flightgear.org/map/?lon=-4.15167&lat=48.53014&zoom=14&layers=B000000TFFFFTFFFTTFFF LFRJ] || [[Landivisiau Naval Air Base]] || France || Europe || Modeled airport with arresting cables and [[Signs]]

|-
| LFRQ || Quimper || France || Europe ||

|-
| LFRU || Morlaix || France || Europe ||

|-
| [http://mapserver.flightgear.org/map/?lon=7.531611&lat=47.599621&zoom=14 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 ||

|-
| [http://mapserver.flightgear.org/map/?lon=9.70741&lat=45.66952&zoom=14&layers=B000000TFFFFTFFFTTFFF LIME] || [[Orio al Serio Airport]], Bergamo || Italy || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=9.27521&lat=45.44776&zoom=14&layers=B000000TFFFFTFFFTTFFF LIML] || [[LIML|Milano-Linate Airport]] || Italy || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=7.36789&lat=45.73857&zoom=15&layers=B000000TFFFFTFFFTTFFF LIMW] || Aosta Airport || Italy || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=14.26&lat=50.100833&zoom=15&layers=B000000TFFFFTFFFTTFFF LKPR] || [[Václav Havel Airport Prague]] (Ruzyne) || Czech Republic || Europe || Fully modeled

|-
| [http://mapserver.flightgear.org/map/?lon=11.34397&lat=47.26023&zoom=15&layers=B000000TFFFFTFFFTTFFF LOWI] || [[Innsbruck Airport]] || Austria || Europe ||

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

|-
| 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 ||

|-
| [http://mapserver.flightgear.org/map/?lon=136.80541&lat=34.85841&zoom=14&layers=B000000TFFFFFFFFTTFFF RJGG] || [[Chūbu Centrair International Airport]] || Japan || Asia || Detailed airport buildings, taxiway layout and customized terrain.

|-
| [http://mapserver.flightgear.org/map/?lon=139.78114&lat=35.5533&zoom=14&layers=B000000TFFFFTFFFTTFFF RJTT] || [[Tokyo Haneda International Airport]] || Japan || Asia ||

|-
| [http://mapserver.flightgear.org/map/?lon=126.45051&lat=37.46909&zoom=14&layers=B000000TFFFFTFFFTTFFF RKSI] || Seoul Incheon Airport || South Korea || Asia ||

|-
| [http://mapserver.flightgear.org/map/?lon=121.01349&lat=14.51024&zoom=14&layers=B000000TFFFFTFFFTTFFF RPLL] || Manila Aquino Airport || Philippines || Asia || Tower and three large terminals

|-
| 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 ||

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

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

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

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

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

|-
| [http://mapserver.flightgear.org/map/?lon=113.9183&lat=22.308&zoom=14&layers=B000000TFFFFTFFFTTFFF VHHH] || Hong Kong International Airport || Hong Kong || Asia || Terminals, control towers, some other buildings

|-
| [http://mapserver.flightgear.org/map/?lon=-81.41707414&lat=41.15689289&zoom=15&layers=B000000TFFFFTFFFTTFFF 1G3] || Kent State University Airfield, OH || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-81.76281774&lat=41.13448335&zoom=15&layers=B000000TFFFFTFFFTTFFF 1G5] || Medina Municipal, OH || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-81.24620281&lat=41.20973295&zoom=15&layers=B000000TFFFFTFFFTTFFF 29G] || Portage Co, OH || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-90.13769&lat=43.83872&zoom=15&layers=B000000TFFFFTFFFTTFFF 82C] || Mauston-New Lisbon Union Airport, WI || USA || America ||

|-
| [http://mapserver.flightgear.org/map/?lon=-89.02545&lat=44.50485&zoom=15&layers=B000000TFFFFTFFFTTFFF 68C] || Iola Central County Airport, WI || USA || America ||

|}

{{Suggested}}

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

Flughafen Stuttgart

2014-05-23T12:54:04Z

August: Layout update

{{airport-stub}}

{{infobox Airport
|name = Flughafen Stuttgart
|image =EDDS.jpg
|alt =
|iata =STR
|icao =EDDS
|type =Public
|city =Stuttgart
|owner =Flughafen Stuttgart GmbH
|website =http://www.stuttgart-airport.com/
|terrasync = published
|runway= 07/25
|length= 3,345m
|material= Concrete
}}

Stuttgart Airport (in German '''Flughafen Stuttgart''', formerly Flughafen Stuttgart-Echterdingen) is an international airport located approximately 13 km (8.1 mi) (10 km (6.2 mi) in a straight line) south of Stuttgart, [[Germany]] in the federal state Baden-Würtemberg. The airport lies on the boundary between the nearby town of Leinfelden-Echterdingen, Filderstadt and Stuttgart itself.

== Flying at Stuttgart airspace ==
[[File:EDDS-Terminal1.jpg|thumb|270px|Terminal 1-4]]
=== Charts ===
All [http://www.vacc-sag.org/airport/EDDS diagrams and charts] are available for download.

== Scenery ==
Since FlightGear 3.0 the airports layout is published on 850-standard via [[TerraSync]]. Additionally most buildings have been placed by using the large Shared-Objects database of FlightGear.

== External links ==
* [http://www.vacc-sag.org/airport/EDDP Airport Diagrams]

[[Category:Airports in Germany]]

Leipzig/Halle Airport

2014-05-19T14:24:56Z

August: GIT layout updates

{{infobox Airport
|name = Leipzig/Halle Airport
|image =EDDP TerminalC.jpeg
|alt =New terminal C (published 2012)
|iata =LEJ
|icao =EDDP
|type =Public
|city =Between Leipzig and Halle
|owner =Mitteldeutsche Airport Holding
|website =http://www.leipzig-halle-airport.de/
|scenerytile =e012n51
|download =
|terrasync = [[#Download_via_GIT]] for latest scenery
|runway= 08L/26R
|length= 11,811 ft
|material= Concrete (in FG still Asphalt)
|runway2= 08R/26L
|length2= 11,811 ft
|material2= Concrete (in FG still Asphalt)
}}

'''Leipzig/Halle Airport''' is located in Schkeuditz, Saxony and serves both Leipzig, Saxony and Halle, Saxony-Anhalt, [[Germany]]. In Flightgear this airport was published on [[TerraSync|TerraSync]] in 2010 und updated due to new developments 2012. In 2014 according to the new world scenery a complete overhaul started.
EDDP is also the centre of Leipzig/Halle airspace, which provides air traffic control also for the regional airfield [[Leipzig-Altenburg Airport]].
Currently users are asked to test the '''beta Version of the new 850-Layout''' (see [[#Download_via_GIT]])

== Flying at Leipzig/Halle airspace ==

=== Charts ===
All [http://www.vacc-sag.org/airport/EDDP diagrams and charts] are available for download.

=== Runways and ILS ===

==== Runway 08L/26R ====
[[File:2012-09 Apron4 Luftbild-at-night.png|thumb|270px|Apron 4 and runway 26L at night]]The northern [[runway]] is 3600m long with a width of 45m. In real life its usually used by passenger airliners. In Flightgear this runway is equipped with Outer Marker and Middle Marker and offers best conditions for '''low visibility operations'''.
* ILS-CAT-III '''08L''' (083°): 108.55
* ILS-CAT-III '''26R''' (263°): 108.35
==== Runway 08R/26L ====
The southern [[runway]] is 3600m long with a width of 60m. In real life its mostly used by freighters due to its proximity to freight areas (Apron 2 and 4). It has no Outer Marker an no Middle Marker.
* ILS-CAT-III '''08R''' (083°): 111.90 (111.75 in FG older than Version 2.0.0)
* ILS-CAT-III '''26L''' (263°): 110.30

=== ATC ===
* Leipzig Ground - frequency 121.800
* Leipzig Tower - frequency 121.100

Leipzig/Halle Airport is regularly served by Air Traffic Control ([[ATC]]).

== Infrastructure ==
[[File:EDDP-overview-daytime.jpg|thumb|270px|Overview 2012]]Connected by terminal C and three taxiway bridges (W1, E7, E8) the airport layout combines the northern part with runway 08L/26L and Apron 3 (new cargo area since 2012) and the southern part with Apron 1 (terminal B), runway 08R/26L, Apron 2, Apron 4 (DHL), Apron 5. Between both parts an airport railway station and the autobahn A14 is connecting to the check-in area of terminal C. Railway and motorway are not modelled in Flightgear.

=== Access and connection ===
[[File:TerminalC-morning.jpg|thumb|270px|Terminal C at dawn]]
==== Terminal C ====
In August 2012 the completely new modelled terminal C was published on TerraSync. It is built as a connection between the check-in building with car-park and train station in the north and the departure area at terminal B in the south. Due to this efforts it stands on piers like a long bridge from apron 1 to apron 3, crossing different car-parks, a rail-track and the autobahn.
On the one hand the FlighGear model tries to give the airport a well designed model with highly detailed structures, but on the other hand it was programmed as simple as possible to save visitors simulation performance.

==== Taxiway bridges ====
[[File:EDDP-Taxibridges-e7e8-night.jpg|thumb|270px|Rampbridges E7, E8 with new lightning in 2012]]A highway and railway lines go straight between the two runways. Three bridges connect the terminal with the northern runway. The western bridge (taxiway W1) is used in both directions. The eastern bridges (taxiways E7 and E8) are used as one way taxiways. Due to safety improvements all bridges are equipped with special taxi lights.
Due to changes in the TerraData the bridges had to be repositioned in 2012.

=== Apron 1 ===

The main apron at Leipzig/Halle Airport is located in the middle of the airport. It houses the commercial aviation area at terminal B in the west and the general aviation area in the eastern part. It is connected by taxiways L, N and W1.

==== Terminal B ====
[[File:EDDP VDGS-134 thumbnail.jpg|thumb|270px|VDGS on each gateway at terminal B]]'''Real world''':
This building is the main terminal for most commercial flights at EDDP. It is connected to terminal C in the north and provides the passenger transfer to Apron 1 via 6 gateways. It also has a connection to the luggage terminal.

'''Scenery in TerraSync''':
In Flightgear the main terminal is modelled very slim and efficiently. 6 unmovable gateways link to park positions 126, 128, 130, 132, 134 and 136. In 2012 it will be improved. Since September 2012 it has been equipped with a non-animated [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System VDGS].

==== Luggage terminal ====
This building was first published in 2004 and remodelled by Thomas Großberger in 2012. The terminal is connected via the old tower next to it to terminal A by a tube, which is used to transport luggage between the checkin- and arrival-area and Apron 1. Both. the connection and the old tower building will be modelled in 2013. The new luggage terminal in FlightGear is offering:
* realistic roof design
* simplified but detailed interior
* 6 clock controlled automatic gates
* complex light design (Rembrandt-Design outstanding)

==== GAT ====

=== Apron 2 ===

=== Apron 3 ===
This Apron in real life went into service with a new cargo hangar in 2012. In Flightgear it is still closed. The corresponding facilities are still under development.

=== Apron 4/5 (DHL-area) ===
[[File:2012-08 Apron4 Pos432 BOX1522-D-STHO-and-DC10.png|thumb|270px|DHL-area at apron 4]]'''Real world:''' Leipzig/Halle is just a small international airport. But in 2008 it became the [http://www.dp-dhl.com/en/logistics_around_us/from_our_divisions/leipzig_hub.html European DHL hub] with up to 60 planes per night. The DHL Hub Leipzig GmbH, place of business in Schkeuditz, is running under contract to the logistic group DHL at Leipzig/Halle Airport one of six international aviation hubs. In order to provide maintenance to the new fleet the [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig GmbH] was founded. European Air Transport operates services to Europe, Middle East and Africa. 56 countries are covered in total. A second aviation company, called [http://en.wikipedia.org/wiki/Aerologic AeroLogic], was founded in EDDP. AeroLogic GmbH, a joint-venture between DHL Express and Lufthansa Cargo, is a German cargo airline headquartered in Schkeuditz, Saxony. It operates cargo flights out of Leipzig/Halle Airport and Frankfurt, most of which are on behalf of its parent companies.

{| class="wikitable" cellpadding="3" style="margin-left:auto; margin-right:auto"
|+ '''Fleet of [http://en.wikipedia.org/wiki/Aerologic AeroLogic] and [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig] and others''' (2012)
|-
!Aircraft
!Total
!Orders
!Oparator
|-
|[[Airbus A300|Airbus A300B4-203F]]
|<center>10</center>
|
|Air Contractors
|-
|[[Airbus A300|Airbus A300-600RF]]
|<center>8</center>
|<center>10</center>
|European Air Transport Leipzig
|-
|Boeing 737-300F
|<center>9</center>
|
|European Air Transport Leipzig
|-
|Boeing 737-400F
|<center>1</center>
|
|Europe Airpost
|-
|[[Boeing 757|Boeing 757-236SF]]
|<center>10</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 757|Boeing 757-23APF]]
|<center>1</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 777F]]
|<center>8</center>
|
|AeroLogic
|-
!Total
!47
!10
!colspan=2|
|}

[[File:EDDP-DHL-tank.jpeg|thumb|270px|DHL-Tank at fuel storage area on apron 4]]'''Scenery in TerraSync:''' The hub (warehouse, hangar and aprons) is modelled in the scenery. In 2012 its redesign for TerraSync started. First all lampposts at apron 4 had been replaced with those which fit into the correct layout of every single parking position. Afterwards lots of goods and ground vehicles where placed. As soon as some missing storage buildings are modelled, the new content of apron 4 will be published on TerraSync. Last modifications will take place when the new [[Airport data (apt.dat) update|850-standard layout]] of EDDP will be created in the future.

'''DHL-hub at EDDP in Flightgear:''' Leipzig/Halle Airport offers ground space for more than 70 Boeing [[757-200|757-PF]] or up to 50 [[777F]] as well as space for 10 [[Antonov An-124|An-124]] at Apron 2, 4 and 5. Airmail flights can be flown from and to EDDP. One of the middle sized and highly connected hubs of DHL, the [[Orio al Serio Airport]] (Italy) is also modelled in FlightGear and can be used for realistic flights out of Leipzig/Halle Airport.
In FlighGear apron 4 is equipped with all stands. Additionally to the main apron lightning each stand has one centred lamppost, which will be replaced by a VDGS-signs in the future. Ground markings will come with the new 850-layout. The major storage buildings from DHL are modelled as well as three DHL-tanks south from apron 4.

=== De-icing areas ===
Leipzig/Halle Airport has four special areas, two in the north at taxiway C and two in the south at taxiway N. In FlightGear only the two areas at taxiway C are build into the layout. In 2012 both areas had been equipped with shared models like lampposts, buildings and ground lights.

==== De-icing area 2 - multiplayer ready ====

Based on the Zurich type model "Elephant" - originally modelled by Oliver Thurau - an improved version with full multiplayer support is under development. This version isn't only adapted to the special efforts at EDDP, but its also designed to be controlled by ATC. It will be published via TerraSync in November 2014.

== Surroundings and "Other" ==

=== Kursdorf - the village within the airport ===
Yes, that is weird. There is a village right in middle of the airport. So it's no surprise the number of inhabitants is shrinking each year. Once a thriving village with 537 inhabitants in 1950, they were down to 119 in 2006 [http://de.wikipedia.org/wiki/Kursdorf_%28Schkeuditz%29 (Wikipedia)]. It might be a little loud with the two runways, highway and express railways, but the transport links, hey ... The village is modelled in the scenery.

== Scenery ==
{|
| Authors: ||
* Models: David G., Thomas Großberger
* Airport layout: Christian Schmitt
* Additional models: Don Lavelle, Alex Park, Robert Shearman
* Redesigning & Development 2012: August Geyler, Thomas Großberger
|-
|}

=== Download via GIT ===
With FlightGear 3.0 a new world scenery was published, including a new but incorrect 850-layout for EDDP. Developers started a huge overhaul of the EDDP scenery in April 2014. First a new taxiway layout was programmed. Additionally all buildings and objects are replaced. Some models will be remodelled, others will be added. Due to the fact that airport layouts can't be simply updated via TerraSync in a short way, pilots are asked to use the new EDDP CUSTOM SCENERY as long as things aren't updated at TerraSync.

* Download-Development-Scenery
* updated regularly
** '''git clone''' [https://git.gitorious.org/eddp-custom-scenery/eddp-custom-scenery.git https://git.gitorious.org/eddp-custom-scenery/eddp-custom-scenery.git]
** or [https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/archive/5a44d12dfc0f41433fd1aedd0f6fadebcf503066.tar.gz download a ZIP] (101 MB)

=== Download via TerraSync ===
[[TerraSync]] has it all! There is no custom scenery existing (only the GIT-repository for testing the new 850-layout before publishing it). The authors believe on the advantages of TerraSync which makes it easy for every user to have the latest scenery installed automatically. Updates are published regularly via TerraSync.
* Next update in '''<daysuntil in="days">12-August-2014</daysuntil>'''
* '''Latest update on TerraSync:'''
** '''2014-04-29''' ''Objects adapted to new (but incorrect) 850-layout''

* Last five updates:
** '''2013-04-21''' ''Rembrandt lights at apron 1''
** 2013-02-13 ''new Messeturm at final approach area of runway 26R''
** 2012-12-21 ''new luggage terminal at apron 1''
** 2012-10-22 ''three new DHL-tanks placed at DHL-area''
** 2012-09-20 ''new VisualGuidingDockingSystem at terminal B''

=== Development ===
Since the Scenery had been modelled by [[User:D-79|D-79]] in 2010, Thomas Großberger and [[User:August|August Geyler]] started enhancements and redesigning in 2012. In 2014 development of a new 850-layout started. Improvements are made on the following objects:

'''Layout''' 
* Taxiway bridges: new Position, improved lightning ''(published 07/2012)'' {{tick}}
* New 850-standard: new Layout with all parking positions and improved taxiways ''(pre-development)'' {{progressbar|80}} (see [[#Download_via_GIT]])

'''Scenery (Shared Models)''' 
* Airport lightning: more than 80 lampposts ([[EDDM]]-model) on Apron 1 and 4 and both northern de-icing areas ''(published 07/2012)'' {{tick}}
* DHL-tanks at apron 4 ''(published 10/2012)'' {{tick}}
* Ground traffic: lots of goods and vehicles (shared) make apron 1 and 4 much more realistic ''(published 08/2012)'' {{tick}}
* Flora and boundaries: Trees and fences on Apron 1, 2 and 4 are added ''(published 08/2012)'' {{tick}}
* New shared ground vehicles
** Container dolly ''(under development)'' {{hourglass}}
** Luggage dolly ''(under development)'' {{hourglass}}
** Pallet dolly ''(planned)''
* New shared Unit Load Devices (ULD)
** Airfreight container - Type AKH ''(pre-development)'' {{hourglass}}
** Airfreight pallet ''(planed)''
* Village and industrial surroundings: Kursdorf within the airport and industrial areas around are created with shared models ''(published 04/2010)'' {{tick}}

'''Buildings and infrastructure (Static models)''' 
* Cargo-hangar apron 3 ''(planned)''
* Cargo-center apron 2 ''(published 2010)'' {{tick}}
* DHL-hangar ''(published 2010)'' {{tick}}
* DHL-terminal ''(published 2010)'' {{tick}}
* Interactive DE-ICING areas (Multiplayer supported) {{hourglass}}
* Interactive luggage dolly traffic between terminal B and lugage terminal ''(planned)''
* Luggage terminal ''(published 12/2012)'' {{tick}}
* Storage buildings at DHL-area ''(pre-development)'' {{hourglass}}
* Terminal B ''(published 04/2010)'' {{tick}}
* Terminal C ''(published 08/2012)'' {{tick}}
* Tower ''(published 2010)'' {{tick}}
* Turbo engine hall ''(pre-development)'' {{hourglass}}
* Old Tower next to terminal B ''(pre-development)'' {{hourglass}}
* Visual Docking Guiding System at Apron 4 ''(planned)''
* Visual Docking Guiding System at Terminal B ''(published 09/2012)'' {{tick}}
* Visual Docking Guiding System: replacement with animated interactive version ''(planned)''
'''Rembrandt lightning improvements'''
* Converting Lightning to [[Project Rembrandt|Rembrandt]]
** Rembrandt lights at apron 1 ''(published 04/2013)'' {{tick}}
** Rembrandt lights at apron 4 {{progressbar|80}}
* Converting Buildings to [[Project Rembrandt|Rembrandt]] Lightning
** Luggage terminal ''(pre-development)'' {{hourglass}}
** Terminal B ''(planned)''
** Terminal C ''(planned)''
** Tower ''(planned)''
** DHL-hangar ''(planned)''
* Lampposts in EDDP-style ''(planned)''

'''Buildings at the city of Leipzig (Static models)''' 
* City-Hochhaus {{progressbar|90}}
* Wintergartenhochhaus ''(published 02/2013)'' {{tick}}
* Völkerschlachtdenkmal (Battle of Nations Monument) {{hourglass}}
* Red-Bull Arena {{hourglass}}
* Gondwanaland (tropical zoo) ''(published 02/2013)'' {{tick}}
* DVB-T-Tower ''(published 02/2013)'' {{tick}}
* Messeturm Leipzig ''(published 02/2013)'' {{tick}}
* Hauptbahnhof (Central Station) ''(planned)''

=== Models since 2012 ===
[[File:EDDP TerminalC.jpeg|Terminal C]] [[File:EDDP VDGS-136 thumbnail.jpg|VDGS at position 136]] [[File:EDDP-DHL-tank.jpeg|DHL-Tank at fuel storage area on apron 4]] [[File:EDDP_luggageterminal_thumb.jpg|Luggage Terminal at Apron 1]]

=== Models since 2010 ===
Here is a selection of the models. [http://www.youtube.com/watch?v=3kNDGiSNUdE YouTube video 2010].

[[File:EDDP10.jpg]] [[File:EDDP11.jpg]] [[File:EDDP12.jpg]] [[File:EDDP13.jpg]] [[File:EDDPbridge1.png]]

== Related content ==
* [[Germany]]
* [[Leipzig/Halle Airspace]]

== External links ==
* [http://www.vacc-sag.org/airport/EDDP Airport Diagrams]
* [http://de.wikipedia.org/wiki/EDDP Leipzig/Halle Airport at Wikipedia] (German)

[[Category:Airports in Germany]]

Airports under construction

2014-05-19T14:04:36Z

August: /* Current Activities */ new status at EDDP

== Preface ==

=== Found a beacon in the middle of the runway in [http://mpmap02.flightgear.org/?ll=48.34849178268444,-107.88724422454834&z=16&t=s&fg_server=mpserver02:5000,mpserver02.flightgear.org,5001&update_interval=5&pilot_label=always&icon_mode=normal LMML] or some other faults? ===
First you have to know that 90 % of the airports have "bad layouts" at the moment and at some places even maps are not updated (have a [http://mpmap02.flightgear.org/?ll=48.34849178268444,-107.88724422454834&z=16&t=s&fg_server=mpserver02:5000,mpserver02.flightgear.org,5001&update_interval=5&pilot_label=always&icon_mode=normal look here] i.e.). Most of the airports need updates. This is a lot of work when you think about the 20’000 airports in the database. When you read the tutorials how to build airports you can do it yourself and submit your work. Or someone of the contributors here will once start to work on your "wish" - but please be patient and do not send any messages/mails to contributors. You can go to the forum ([http://forum.flightgear.org/viewforum.php?f=5 Scenery Enhancement]) to discuss some issues.

== Airports under construction ==
In this article you find a list of all airports which currently are under construction. You can also see if an airport is "finished" and if the data is already submited to the current database of the mapserver (apt.dat).

=== Availability of new/changed airports needs some time ===
In FlightGear there is a common workflow to edit airports. First, experienced contributors have to change the airport data with [[Wed]]. Then they submit the new data to the X-Plane community (main scenery data files/airport data file apt.dat). Meantime, other contributors can also submit some scenery to the custom scenery database (for downloading via TerraSync). But for runways, taxiways, beacons, frequencies, the apt.dat file needs an update anyway and maybe also the base scenery around the airport needs an update. Please be patient with updates. It needs more time than you expected.

== Submit your work plans and schedule your activities ==
Please feel free to edit this page and submit your "pending airport" directly.

=== Current Activities ===

{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"
|-
! style="background:#efefef" | ICAO !! style="background:#efefef" | Who !! class="unsortable" style="background:#efefef" | Airport layout !! class="unsortable" style="background:#efefef" | Airport objects !! class="unsortable" style="background:#efefef" | AI Network !! class="unsortable" style="background:#efefef" | Start date !! class="unsortable" style="background:#efefef" | .dat submitted !! class="unsortable" style="background:#efefef" | Comments
|-
|[[EDDP]]||August, D-STHO||x||x||||2012-07-01|||| new 850-layout (will be published 06/2014), ground vehicles and new light concept for Apron 1 and 4 (published 2012-08-05), new Terminal C (published 2012-08-30), new customized buildings on Apron 1, 3 and 4, improved Terminal B and further improvements other buildings
|-
|EDLM||laserman|| ||x|||||2013||||
|-
|EDWG||gral||x||||||2010-02-03||||
|-
|EDWJ||gral||x||||||2010-02-01||2010-02-03||taxiway, runways, positions
|-
|[[EDWL]]||gral||x||||||2010-02-03||||
|-
|[[EDWP]]||TeXnicer||||||||2013-12-05||||First attempts with WED & Co., small airfield
|-
|EDWY||gral||x||||||2010-02-03||||
|-
|EEKE||henrikp||x||||||2010-10||||
|-
|EERU||henrikp||x||||||2010-10||||
|-
|EEKA||henrikp||x||||||2010-10||||
|-
|EGGD||karla||||x||x||2009-07-12||2010-12-02||customized buildings, stock buildings, stock models and vehicles, high detail
|-
|[[London Gatwick Airport|EGKK]]||karla||||x||x||2010-02-13||2010-02-07||fully complete; over 60 customized buildings and other features with highly detailed day and night textures; full taxiway signs; AI traffic, parking and taxiways; available as direct download (see forum) or on Git/Git
|-
! style="background:#efefef" | ICAO !! style="background:#efefef" | Who !! class="unsortable" style="background:#efefef" | Airport layout !! class="unsortable" style="background:#efefef" | Airport objects !! class="unsortable" style="background:#efefef" | AI Network !! class="unsortable" style="background:#efefef" | Start date !! class="unsortable" style="background:#efefef" | .dat submitted !! class="unsortable" style="background:#efefef" | Comments
|-
|EHGG||Gijs||x||x||x||x||x|| || ||
|-
|[[EHAM]]||Gijs||x||x||x||x||x|| || ||
|-
|[[EHLE]]||Gijs||x||x||x||x||x|| || ||
|-
|[[EHVK]]||Gijs||x||x||x||x||x|| || ||
|-
|EHEH||Gijs||x||x||x||x||x|| || ||
|-
|EHKD||Gijs||x||x||x||x||x|| || ||
|-
|EHTX||Gijs||x||x||x||x||x|| || ||
|-
|EHAL||Gijs||x||x||x||x||x|| || ||
|-
|EHRD||Gijs||x||x||x||x||x|| || ||
|-
|EHLW||Gijs||x||x||x||x||x|| || ||
|-
|KCHO||Catchatyou||x|| || ||2010-12-05|| ||The basic structure of the airport is almost complete, and once the airport is correctly modeled, I will be adding the parking lot, hangars...||
|-
|KDMA||gral||x|||| ||2010-02-10||2010-02-10||runways, taxiways
|-
|KDTW||Fgoldbatch||||x||||2011-03-30||||Replacement of McNamara Terminal and addition of North Terminal
|-
|KHND||Armchair Ace|| ||x|| || || ||Hangars and static aircraft added. Terminal still needed.
|-
|KSFO||karla|| ||x|| ||2010-08-06 ||2010-08-27 ||Terminal 2 fully remodelled; new day and night textures; new light masts; jetways included; actual T2 under reconstruction 2010; available as direct download (see forum) or on Git/Git
|-
! style="background:#efefef" | ICAO !! style="background:#efefef" | Who !! class="unsortable" style="background:#efefef" | Airport layout !! class="unsortable" style="background:#efefef" | Airport objects !! class="unsortable" style="background:#efefef" | AI Network !! class="unsortable" style="background:#efefef" | Start date !! class="unsortable" style="background:#efefef" | .dat submitted !! class="unsortable" style="background:#efefef" | Comments
|-
|LHPP||sztamas6||x||||||2011-11-02|| || Changin generic taxiways to realistic ones. Adding paved and unpaved aprons. Moving tower position to actual location
|-
|LIDF||[[User:Bigstones|bigstones]]||x||||||2014-05-18||2014-05-18||Layout from OSM.
|-
|LIPX||elgaton||x||||||2013-12-16||||Redone from scratch using OSM data: runway, taxiways, airport boundary, PAPI, windsocks, radio frequencies. To be done: signs, markings, objects. [http://forum.flightgear.org/viewtopic.php?f=5&t=21576 Beta release available on the forum].
|-
|LIPR||[[User:Bigstones|bigstones]]||x||||||2014-04-25||2014-05-18||Layout from OSM.
|-
|[[LIPY]]||[[User:Bigstones|bigstones]]||x||x||||2014-04-06||2014-05-18||Layout from OSM, models converted from an FS scenery, with author consent ([http://forum.flightgear.org/viewtopic.php?f=5&t=22623 read more])
|-
|LSMA||gral||x||||||2010-04-12||2010-04-12||runways, taxiways, tower position, atc freqs
|-
|OMDB||D-SKY1||||||x||2010-06-25||||added AI traffic (UAE)
|-
|RPLL||D-SKY1||||x||x||2009-12-03||2010-02-11||T1, T2, T3, Tower, AI ground network, AI traffic, ATC freqs. Todo: taxi- and runways redesign
|-
|SBBG||Prestes||x||x|| ||2009-12-26 || ||
|-
|SBPA||Prestes||x||x|| ||2009-12-28 || ||Airport objects by George Luiz
|-
|SBPK||Prestes||x||x|| ||2010-01-31 || ||
|-
|SBRG||Prestes||x||x|| ||2010-01-31 || ||
|-
|SUMU||Prestes||x||x|| ||2010-01-31 || ||
|-
|UEST||gral||x|||| ||2010-01-10||2010-01-12||fixed taxiways and some minor issues
|-
|VTBD||D-SKY1||||x||x||2010-11-27 || ||[http://forum.flightgear.org/viewtopic.php?f=5&t=10075 Work in progress]
|-
|YSSY||scotth1||x||x||x|| ||2011-01-11||adjusted aprons, taxiways, moved windsocks, AI ground network submitted. very basic International terminal yet to be submitted, TODO: domestic terminal, cargo terminal
|}

== Submit your wishes ==
If you wish to add an airport or think this or another airport needs a change '''[http://forum.flightgear.org/viewtopic.php?f=5&t=6749 you have to post in the forum (scenery enhancement)]'''. But first search the forum with the ICAO code of the airport and be sure that you have read all the posts about this airport. And please submit also some links to images and information you have about/from this airport.

== Links ==
* [http://mapserver.flightgear.org/Apt.Dat.txt List of updated airports in apt.dat mapserver] 1)
* [http://mapserver.flightgear.org/apt.dat.gz Updated apt.dat.gz mapserver] 1)
* [http://cvs.flightgear.org/viewvc/data/Airports/apt.dat.gz?view=log Log of apt.dat.gz in FlightGear Git]
* [[Taxidraw|TaxiDraw Tutorial]]
* [http://taxidraw.sourceforge.net/taxidraw/tutorial.html Another (outdated) Tutorial for TaxiDraw]
* [http://taxidraw.sourceforge.net/#download TaxiDraw download - includes also working binaries (i.e. for OSX)]

1) "mapserver.flightgear.org" is NOT "mpmap02.flightgear.org". The mpmap02 is hosted on another server and could reflect an older apt.dat.gz than the current one of the mapserver or of the Git server.

=== Other airport work related pages in the FlightGear wiki ===
* List of [[Developed Airports]] with buildings and [[Signs]] already included in the [[FlightGear Scenery Database]]
* [[Germany|Current work in Germany]]
* [[Current Scenery Projects]]
* [[FlightGear User Created Helipad List]]

[[Category:Airports]]

Extra EA-500

2014-05-13T17:07:07Z

August: /* Operation */ new button template

{{infobox Aircraft
|image =
|name = Extra EA 400-500
|type = Civilian aircraft
|fdm = JSBSim
|status-fdm = 4
|status-systems = 5
|status-cockpit = 4
|status-model = 4
|authors = D-EKEW, D-Leon, D-STHO
|fgname = extra500
}}
[[File:Extra 500.jpg|thumb|250px|The real Extra 500]]
The '''Extra500''' is a six-seat single-engined turboprop aircraft produced by the Extra Aircraft company (based at EDLD).

== Status ==
Current stable release is 1.0 (18.02.2014):

git clone https://git.gitorious.org/extra500/extra500.git
cd extra500
git checkout version/1.0.0

or use the download button on:
[https://www.gitorious.org/extra500/extra500]

For the stable release make sure you are on the version/1.0.0 branch!

Since March 2013 D-EKEW, D-Leon, D-STHO are working on this model. They are making use of original data from the Pilot's Operation Handbook. People who have experienced the aircraft in real life help calibrating the FDM as well as tuning the systems behavior.

== About the airplane ==
=== Extra EA-Series ===
The Extra Aircraft company designed several aerobatic aircraft based on the early experimental EA-230 and EA-260, followed by the FAR-23 certified EA-300 series (EA-300, EA-300/S, EA-300/L, EA-300/200, EA-300/LT, EA-330/LC, EA-330/SC). The company introduced the Extra EA-400 in 2001. This is a cross-country airplane with many exclusive features including carbon fiber construction, pressurized cabin, high strut-less wing, and a seating for six.
The EA 400-500 was introduced as a derivative of the EA-400 replacing the piston engine with a Rolls-Royce Model 250-B17F/2 turboprop producing 450 horsepower (340 kW) and driving a MT-propeller 5 bladed propeller. Walter Extra flew the first Extra500 from Germany to Oshkosh, Wisconsin to illustrate its range and capabilities. The most recent changes to the aircraft come from Avidyne with their latest glass avionics, Entegra R9.

[[File:Extra500 flightgear1.png|thumb|500px|Extra500 flying in clouds]]
[[File:Extra500 flightgear2.png|thumb|500px|Extra500 flying in the clouds (2)]]

=== General characteristics ===
{| class="wikitable" cellpadding="2" style="margin-left:auto; margin-right:auto"
|-
!colspan=2| General
|-
|Min. Crew
|1
|-
|Capacity
|5 PAX or 525 kg payload
|-
|Length
|10.1 m
|-
|Span
|11.7 m
|-
|Height
|3.4 m
|-
|Empty weight
|1,420 kg
|-
|Max takeoff weight
|2,130 kg
|-
!colspan=2| Powerplant
|-
|Engine type
|Turboprop
|-
|Engine
|Rolls-Royce Model 250-B17F/2
|-
!colspan=2| Performance
|-
|Cruise speed
|210 kts
|-
|Stall speed (MTOW, Full flaps)
|61 kts
|-
|Max. Range
|2,963 km
|-
|Endurance
|7.9 hours at cruise speed
|-
|Ceiling
|25,000 ft
|-
|Climb rate (S.L.)
|1,335 ft/min
|}

== Download ==
The development version is available via Gitorious:

git clone https://git.gitorious.org/extra500/extra500.git

The developers will establish a release plan in order to publish stable versions for each FlightGear release as well as actual developer versions for testers.

== Operation ==
'''For full operation instructions, see the official Extra500 POH. It can be downloaded from the manufacturers homepage:
[http://www.extraaircraft.com/techservice.php]''', right at the bottom.

Below is just a quick start and some selected topics.

===Engine starting===

[[File:Extra500 electicmains.png|thumb|400px|Extra500 side switch panel]]

- Parking Brake: Set ( {{key press|Shift|B}} or pull out middle Bowden cable in middle console AND press {{key press|B}} )

- Battery: Switch ON

- Fuel Pump 1 or 2: Switch ON

- Engine Start: START

- at 12-15% N1: Press {{key press|s}} ( or click on condition lever, its the red one )

CAUTION: TOT limit for starting is max. 10sec above 810 °C and below 927 °C

- Standby alternator: Switch ON

- Generator: Switch ON

- Engine start: IGN OFF (only if N1 >= 65%)

===Take-off===

- Flaps: 15 degrees ( ] or use the flap switch )

- Power lever: TRQ 111%
CAUTION: for Take-off (5 minutes) maximum TRQ limit is 111%, TOT 810degC

- Parking Brake: Release ( {{key press|Shift|B}} or push in middle Bowden cable in middle console )

NOTE: For strong sidewind, turn the ailerons against the wind

- At 71KIAS: Rotate
- Gear: Retract ( {{key press|G}} or click the gear switch )

- Flaps: 0 degrees ( [ or use the flap switch )

CAUTION: Flaps need to be retracted before reaching 120KIAS, gear 140KIAS

- Power lever: TRQ 92%

CAUTION: For continuous operation the TRQ limit is 92%, TOT 752degC, watch the TOT while climbing!

===Climb===

Climb with MCP (maximum continuous Power, 92%TRQ or 752degC) at 110 KIAS.

===Descent===

Descent with 50% TRQ and 2000ft/min. Max airspeed is 207 KIAS.

===Landing===
Do not come in too high, too fast.

At 140 KIAS, gear: Extend ({{key press|Shift|G}} or click the gear switch )

At 120 KIAS, flaps: 15 degrees ( ] or use the flap switch )

At 109 KIAS, flaps: 30 degrees ( ] or use the flap switch )

Power for a 3deg descent, 80KIAS and landing configuration is ~30% TRQ

Dont forget to brake. For reverse press {{key press|R}}, will only toggle when power lever is in aft position!

===Engine shut-off===

- Parking Brake: Set ( {{key press|Shift|B}} or pull out middle Bowden cable in middle console AND press {{key press|B}} )

- Fuel Pump 1 and 2: Switch OFF

- Standby alternator: Switch OFF

- Generator: Switch OFF

- Press s ( or click on condition lever )

- Battery: Switch OFF

===Principle Autopilot functionality (currently in place)===

- HDG Follows the heading bug (set HDG bug using the keypad, press to sync)

- NAV Intercepts and tracks VORs, LOCs or your Flight Plan (set course with LH lower rotary knob on IFD)

- NAV/GPSS Intercepts and tracks your Flight Plan and cuts the corners (Press NAV twice)

- HDG+NAV Intercept the course or active flightplan leg with your set heading

- NAV+REV Intercepts and tracks the LOC back course

- GS Is armed and activated automatically when captured on the LOC. You can switch it off by pressing APR, ALT mode will become active. To arm the GS again, press APR for a second time

- VS Follows the VS bug (limited to +/-1600fpm, set with AP rotary knob)

- ALT Holds the current altitude (rounded to 100ft)

- ALT+VS Brings and holds the aircraft to the selected altitude (set ALT bug using the keypad, press to sync) with the selected vertical speed.

- CWS Control Wheel Steering. Follows the turn rate and vertical speed set by controlling the aircraft.

'''To disconnect press: {{key press|d}}'''

General remarks to autopilot operation:

A roll mode (HDG, NAV/GPSS, APR/REV) must be engaged for a pitch mode (ALT, VS, GS) can engage.

A roll mode (HDG, NAV/GPSS, APR/REV) must be engaged for the yaw trim to work

If pitch trim is switched off, autotrim is not available, but the AP will indicate where to (manually) trim to.

For CWS, a roll and pitch mode must be engaged. Press {{key press|c}} (caution: AP servos will disengage!) and with your controls
bring the aircraft at your wished turn and climb rate. Press {{key press|c}} again and the AP will engage and keep those rates.

The AP will disengage when:

- the disconnect switch is pressed ({{key press|d}})

- the stall warner is on

- absolute g-force (disregarding 1-g gravity) exceeds 0.6g

- manual electric pitch trim is used.

===Navigation and Communication===

[[File:Extra500 audiopanel.png|thumb|400px|Extra500 audiopanel: Com1, Nav1 and Marker selected]]

The COM unit (1 or 2 ) is selected on the audiopanel. Just hit the appropriate "XMT" button. Note that FGCOM only works on COM1!
If you want to hear the NAV station morse code or the marker tones, press the appropriate button on the audiopanel also.
The volume can be adjusted using the inner volume knob.

The active COM standby frequency can be inputted on the keypad. The first "1" is not needed and any trailing "0" neither.
Just type in the frequency and switch active/standby with the button just left of the frequencies.

Not-active-COM and NAV standby frequencies are similar, just press the NAV1 / NAV2 button first.

FMS, Nav 1 or Nav 2 may be selected on the IFD or in the NAV dialog (F12)
The DME source can be set using the AUX button on the keypad. Select with the FMS knob. The DME hold switch next to the DME
indicator overrides all NAV frequency switching and holds the frequency to which the DME was tuned when the HOLD button is pressed.

The FMS (Flight Management System) can be used with or without the autopilot. You can put your flightplan in the
autopilot - route manager (dont forget to press "activate"). The autopilot will intercept the active leg.
Direct-To functionality is also included: In the route manager select the waypoint and on the keypad press the "D with arrow" button.
Close to the waypoint direct-to mode will be de-selected automatically or you can do that manually by pressing the same button again.

XPDR squawk can be set on the keypad (press XPDR and squawk code) and in the NAV dialog ({{key press|F12}}). Default is 7000 (Europe VFR).
XPDR modes are selected automatically (GND or ALT), but automatic selection may be switched off
Manual mode selection is then possible.
The MODE button on the keypad will set the mode manually also.

===Pressurization system===

[[File:Extra500 presscontrol.png|thumb|400px|Extra500 pressurization control]]
The extra500 is certified to 25000ft, where the air is pretty thin. So there is pressurization system that keeps the cabin altitude below 8000ft which corresponds to a cabin differential pressure of 5.5psid at 25000ft. So if you are planning to fly above 10000ft, you need to make sure that the ENV AIR and PRESS switches (left lower corner) on the side switch panel are on.
In addition, before take-off you should set the cabin controller (center console) to the airport altitude and just after take-off to your target altitude.
Before descending from cruise, set the controller to your target airport altitude. You can monitor the cabin altitude, differential pressure and cabin climb rate on the instruments next to the controller.

===Night Flying===

For lighted instruments switch on the INSTR switch on the side switch panel. On the same panel you can switch the DAY/NIGHT switch to NIGHT for dimming. The 5 round turn knobs on the panel now can be used to set your dimming level.
The IFD-s have their own dimming switch on the left upper side of the bezel. For taxying use the RECO lights. For landing the LDG light.

[[File:Extra500 final approach.png|thumb|800px|Final approach on 25L of EDDF, B707 outside going for 25R]]

[[Category:Business aircraft]]
[[Category:Civil utility aircraft]]
[[Category:Extra]]
[[Category:High wing aircraft]]
[[Category:Propeller aircraft]]
[[Category:Single-engine aircraft]]

[[de:Extra EA-500]]

Leipzig/Halle Airport

2014-05-02T08:50:59Z

August: New developments 2014

{{infobox Airport
|name = Leipzig/Halle Airport
|image =EDDP TerminalC.jpeg
|alt =New terminal C (published 2012)
|iata =LEJ
|icao =EDDP
|type =Public
|city =Between Leipzig and Halle
|owner =Mitteldeutsche Airport Holding
|website =http://www.leipzig-halle-airport.de/
|scenerytile =e012n51
|download =
|terrasync = [[#Download_via_GIT]] for latest scenery
|runway= 08L/26R
|length= 11,811 ft
|material= Concrete (in FG still Asphalt)
|runway2= 08R/26L
|length2= 11,811 ft
|material2= Concrete (in FG still Asphalt)
}}

'''Leipzig/Halle Airport''' is located in Schkeuditz, Saxony and serves both Leipzig, Saxony and Halle, Saxony-Anhalt, [[Germany]]. In Flightgear this airport was published on [[TerraSync|TerraSync]] in 2010 und updated due to new developments 2012. In 2014 according to the new world scenery a complete overhaul started.
EDDP is also the centre of Leipzig/Halle airspace, which provides air traffic control also for the regional airfield [[Leipzig-Altenburg Airport]].

== Flying at Leipzig/Halle airspace ==

=== Charts ===
All [http://www.vacc-sag.org/airport/EDDP diagrams and charts] are available for download.

=== Runways and ILS ===

==== Runway 08L/26R ====
[[File:2012-09 Apron4 Luftbild-at-night.png|thumb|270px|Apron 4 and runway 26L at night]]The northern [[runway]] is 3600m long with a width of 45m. In real life its usually used by passenger airliners. In Flightgear this runway is equipped with Outer Marker and Middle Marker and offers best conditions for '''low visibility operations'''.
* ILS-CAT-III '''08L''' (083°): 108.55
* ILS-CAT-III '''26R''' (263°): 108.35
==== Runway 08R/26L ====
The southern [[runway]] is 3600m long with a width of 60m. In real life its mostly used by freighters due to its proximity to freight areas (Apron 2 and 4). It has no Outer Marker an no Middle Marker.
* ILS-CAT-III '''08R''' (083°): 111.90 (111.75 in FG older than Version 2.0.0)
* ILS-CAT-III '''26L''' (263°): 110.30

=== ATC ===
* Leipzig Ground - frequency 121.800
* Leipzig Tower - frequency 121.100

Leipzig/Halle Airport is regularly served by Air Traffic Control ([[ATC]]).

== Infrastructure ==
[[File:EDDP-overview-daytime.jpg|thumb|270px|Overview 2012]]Connected by terminal C and three taxiway bridges (W1, E7, E8) the airport layout combines the northern part with runway 08L/26L and Apron 3 (new cargo area since 2012) and the southern part with Apron 1 (terminal B), runway 08R/26L, Apron 2, Apron 4 (DHL), Apron 5. Between both parts an airport railway station and the autobahn A14 is connecting to the check-in area of terminal C. Railway and motorway are not modelled in Flightgear.

=== Access and connection ===
[[File:TerminalC-morning.jpg|thumb|270px|Terminal C at dawn]]
==== Terminal C ====
In August 2012 the completely new modelled terminal C was published on TerraSync. It is built as a connection between the check-in building with car-park and train station in the north and the departure area at terminal B in the south. Due to this efforts it stands on piers like a long bridge from apron 1 to apron 3, crossing different car-parks, a rail-track and the autobahn.
On the one hand the FlighGear model tries to give the airport a well designed model with highly detailed structures, but on the other hand it was programmed as simple as possible to save visitors simulation performance.

==== Taxiway bridges ====
[[File:EDDP-Taxibridges-e7e8-night.jpg|thumb|270px|Rampbridges E7, E8 with new lightning in 2012]]A highway and railway lines go straight between the two runways. Three bridges connect the terminal with the northern runway. The western bridge (taxiway W1) is used in both directions. The eastern bridges (taxiways E7 and E8) are used as one way taxiways. Due to safety improvements all bridges are equipped with special taxi lights.
Due to changes in the TerraData the bridges had to be repositioned in 2012.

=== Apron 1 ===

The main apron at Leipzig/Halle Airport is located in the middle of the airport. It houses the commercial aviation area at terminal B in the west and the general aviation area in the eastern part. It is connected by taxiways L, N and W1.

==== Terminal B ====
[[File:EDDP VDGS-134 thumbnail.jpg|thumb|270px|VDGS on each gateway at terminal B]]'''Real world''':
This building is the main terminal for most commercial flights at EDDP. It is connected to terminal C in the north and provides the passenger transfer to Apron 1 via 6 gateways. It also has a connection to the luggage terminal.

'''Scenery in TerraSync''':
In Flightgear the main terminal is modelled very slim and efficiently. 6 unmovable gateways link to park positions 126, 128, 130, 132, 134 and 136. In 2012 it will be improved. Since September 2012 it has been equipped with a non-animated [http://en.wikipedia.org/wiki/Visual_Docking_Guidance_System VDGS].

==== Luggage terminal ====
This building was first published in 2004 and remodelled by Thomas Großberger in 2012. The terminal is connected via the old tower next to it to terminal A by a tube, which is used to transport luggage between the checkin- and arrival-area and Apron 1. Both. the connection and the old tower building will be modelled in 2013. The new luggage terminal in FlightGear is offering:
* realistic roof design
* simplified but detailed interior
* 6 clock controlled automatic gates
* complex light design (Rembrandt-Design outstanding)

==== GAT ====

=== Apron 2 ===

=== Apron 3 ===
This Apron in real life went into service with a new cargo hangar in 2012. In Flightgear it is still closed. The corresponding facilities are still under development.

=== Apron 4/5 (DHL-area) ===
[[File:2012-08 Apron4 Pos432 BOX1522-D-STHO-and-DC10.png|thumb|270px|DHL-area at apron 4]]'''Real world:''' Leipzig/Halle is just a small international airport. But in 2008 it became the [http://www.dp-dhl.com/en/logistics_around_us/from_our_divisions/leipzig_hub.html European DHL hub] with up to 60 planes per night. The DHL Hub Leipzig GmbH, place of business in Schkeuditz, is running under contract to the logistic group DHL at Leipzig/Halle Airport one of six international aviation hubs. In order to provide maintenance to the new fleet the [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig GmbH] was founded. European Air Transport operates services to Europe, Middle East and Africa. 56 countries are covered in total. A second aviation company, called [http://en.wikipedia.org/wiki/Aerologic AeroLogic], was founded in EDDP. AeroLogic GmbH, a joint-venture between DHL Express and Lufthansa Cargo, is a German cargo airline headquartered in Schkeuditz, Saxony. It operates cargo flights out of Leipzig/Halle Airport and Frankfurt, most of which are on behalf of its parent companies.

{| class="wikitable" cellpadding="3" style="margin-left:auto; margin-right:auto"
|+ '''Fleet of [http://en.wikipedia.org/wiki/Aerologic AeroLogic] and [http://en.wikipedia.org/wiki/European_Air_Transport_Leipzig European Air Transport Leipzig] and others''' (2012)
|-
!Aircraft
!Total
!Orders
!Oparator
|-
|[[Airbus A300|Airbus A300B4-203F]]
|<center>10</center>
|
|Air Contractors
|-
|[[Airbus A300|Airbus A300-600RF]]
|<center>8</center>
|<center>10</center>
|European Air Transport Leipzig
|-
|Boeing 737-300F
|<center>9</center>
|
|European Air Transport Leipzig
|-
|Boeing 737-400F
|<center>1</center>
|
|Europe Airpost
|-
|[[Boeing 757|Boeing 757-236SF]]
|<center>10</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 757|Boeing 757-23APF]]
|<center>1</center>
|
|European Air Transport Leipzig
|-
|[[Boeing 777F]]
|<center>8</center>
|
|AeroLogic
|-
!Total
!47
!10
!colspan=2|
|}

[[File:EDDP-DHL-tank.jpeg|thumb|270px|DHL-Tank at fuel storage area on apron 4]]'''Scenery in TerraSync:''' The hub (warehouse, hangar and aprons) is modelled in the scenery. In 2012 its redesign for TerraSync started. First all lampposts at apron 4 had been replaced with those which fit into the correct layout of every single parking position. Afterwards lots of goods and ground vehicles where placed. As soon as some missing storage buildings are modelled, the new content of apron 4 will be published on TerraSync. Last modifications will take place when the new [[Airport data (apt.dat) update|850-standard layout]] of EDDP will be created in the future.

'''DHL-hub at EDDP in Flightgear:''' Leipzig/Halle Airport offers ground space for more than 70 Boeing [[757-200|757-PF]] or up to 50 [[777F]] as well as space for 10 [[Antonov An-124|An-124]] at Apron 2, 4 and 5. Airmail flights can be flown from and to EDDP. One of the middle sized and highly connected hubs of DHL, the [[Orio al Serio Airport]] (Italy) is also modelled in FlightGear and can be used for realistic flights out of Leipzig/Halle Airport.
In FlighGear apron 4 is equipped with all stands. Additionally to the main apron lightning each stand has one centred lamppost, which will be replaced by a VDGS-signs in the future. Ground markings will come with the new 850-layout. The major storage buildings from DHL are modelled as well as three DHL-tanks south from apron 4.

=== De-icing areas ===
Leipzig/Halle Airport has four special areas, two in the north at taxiway C and two in the south at taxiway N. In FlightGear only the two areas at taxiway C are build into the layout. In 2012 both areas had been equipped with shared models like lampposts, buildings and ground lights.

==== De-icing area 2 - multiplayer ready ====

Based on the Zurich type model "Elephant" - originally modelled by Oliver Thurau - an improved version with full multiplayer support is under development. This version isn't only adapted to the special efforts at EDDP, but its also designed to be controlled by ATC. It will be published via TerraSync in November 2014.

== Surroundings and "Other" ==

=== Kursdorf - the village within the airport ===
Yes, that is weird. There is a village right in middle of the airport. So it's no surprise the number of inhabitants is shrinking each year. Once a thriving village with 537 inhabitants in 1950, they were down to 119 in 2006 [http://de.wikipedia.org/wiki/Kursdorf_%28Schkeuditz%29 (Wikipedia)]. It might be a little loud with the two runways, highway and express railways, but the transport links, hey ... The village is modelled in the scenery.

== Scenery ==
{|
| Authors: ||
* Models: David G., Thomas Großberger
* Airport layout: Christian Schmitt
* Additional models: Don Lavelle, Alex Park, Robert Shearman
* Redesigning & Development 2012: August Geyler, Thomas Großberger
|-
|}

=== Download via GIT ===
With FlightGear 3.0 a new world scenery was published, including a new but incorrect 850-layout for EDDP. Developers started a huge overhaul of the EDDP scenery in April 2014. First a new taxiway layout was programmed. Additionally all buildings and objects are replaced. Some models will be remodelled, others will be added. Due to the fact that airport layouts can't be simply updated via TerraSync in a short way, pilots are asked to use the new EDDP CUSTOM SCENERY as long as things aren't updated at TerraSync.

* Download-Development-Scenery
* updated regularly
** '''git clone''' [https://git.gitorious.org/eddp-custom-scenery/eddp-custom-scenery.git https://git.gitorious.org/eddp-custom-scenery/eddp-custom-scenery.git]

=== Download via TerraSync ===
[[TerraSync]] has it all! There is no custom scenery existing. The authors believe on the advantages of TerraSync which makes it easy for every user always to have the latest scenery installed automatically. Updates during redesigning process in 2012 and 2013 are published every month on TerraSync.
* Next update in '''<daysuntil in="days">12-August-2014</daysuntil>'''
* '''Latest update on TerraSync:'''
** '''2014-04-29''' ''Objects adapted to new (but incorrect) 850-layout''

* Last five updates:
** '''2013-04-21''' ''Rembrandt lights at apron 1''
** 2013-02-13 ''new Messeturm at final approach area of runway 26R''
** 2012-12-21 ''new luggage terminal at apron 1''
** 2012-10-22 ''three new DHL-tanks placed at DHL-area''
** 2012-09-20 ''new VisualGuidingDockingSystem at terminal B''

=== Development ===
Since the Scenery had been modelled by [[User:D-79|D-79]] in 2010, Thomas Großberger and [[User:August|August Geyler]] started enhancements and redesigning in 2012. Improvements are made on the following objects:

'''Layout''' 
* Taxiway bridges: new Position, improved lightning ''(published 07/2012)'' {{tick}}
* New 850-standard: new Layout with all parking positions and improved taxiways ''(pre-development)'' {{progressbar|60}} (see [[#Download_via_GIT]])

'''Scenery (Shared Models)''' 
* Airport lightning: more than 80 lampposts ([[EDDM]]-model) on Apron 1 and 4 and both northern de-icing areas ''(published 07/2012)'' {{tick}}
* DHL-tanks at apron 4 ''(published 10/2012)'' {{tick}}
* Ground traffic: lots of goods and vehicles (shared) make apron 1 and 4 much more realistic ''(published 08/2012)'' {{tick}}
* Flora and boundaries: Trees and fences on Apron 1, 2 and 4 are added ''(published 08/2012)'' {{tick}}
* New shared ground vehicles
** Container dolly ''(under development)'' {{hourglass}}
** Luggage dolly ''(under development)'' {{hourglass}}
** Pallet dolly ''(planned)''
* New shared Unit Load Devices (ULD)
** Airfreight container - Type AKH ''(pre-development)'' {{hourglass}}
** Airfreight pallet ''(planed)''
* Village and industrial surroundings: Kursdorf within the airport and industrial areas around are created with shared models ''(published 04/2010)'' {{tick}}

'''Buildings and infrastructure (Static models)''' 
* Cargo-hangar apron 3 ''(planned)''
* Cargo-center apron 2 ''(published 2010)'' {{tick}}
* DHL-hangar ''(published 2010)'' {{tick}}
* DHL-terminal ''(published 2010)'' {{tick}}
* Interactive DE-ICING areas (Multiplayer supported) {{hourglass}}
* Interactive luggage dolly traffic between terminal B and lugage terminal ''(planned)''
* Luggage terminal ''(published 12/2012)'' {{tick}}
* Storage buildings at DHL-area ''(pre-development)'' {{hourglass}}
* Terminal B ''(published 04/2010)'' {{tick}}
* Terminal C ''(published 08/2012)'' {{tick}}
* Tower ''(published 2010)'' {{tick}}
* Turbo engine hall ''(pre-development)'' {{hourglass}}
* Old Tower next to terminal B ''(pre-development)'' {{hourglass}}
* Visual Docking Guiding System at Apron 4 ''(planned)''
* Visual Docking Guiding System at Terminal B ''(published 09/2012)'' {{tick}}
* Visual Docking Guiding System: replacement with animated interactive version ''(planned)''
'''Rembrandt lightning improvements'''
* Converting Lightning to [[Project Rembrandt|Rembrandt]]
** Rembrandt lights at apron 1 ''(published 04/2013)'' {{tick}}
** Rembrandt lights at apron 4 {{progressbar|80}}
* Converting Buildings to [[Project Rembrandt|Rembrandt]] Lightning
** Luggage terminal ''(pre-development)'' {{hourglass}}
** Terminal B ''(planned)''
** Terminal C ''(planned)''
** Tower ''(planned)''
** DHL-hangar ''(planned)''
* Lampposts in EDDP-style ''(planned)''

'''Buildings at the city of Leipzig (Static models)''' 
* City-Hochhaus {{progressbar|90}}
* Wintergartenhochhaus ''(published 02/2013)'' {{tick}}
* Völkerschlachtdenkmal (Battle of Nations Monument) {{hourglass}}
* Red-Bull Arena {{hourglass}}
* Gondwanaland (tropical zoo) ''(published 02/2013)'' {{tick}}
* DVB-T-Tower ''(published 02/2013)'' {{tick}}
* Messeturm Leipzig ''(published 02/2013)'' {{tick}}
* Hauptbahnhof (Central Station) ''(planned)''

=== Models since 2012 ===
[[File:EDDP TerminalC.jpeg|Terminal C]] [[File:EDDP VDGS-136 thumbnail.jpg|VDGS at position 136]] [[File:EDDP-DHL-tank.jpeg|DHL-Tank at fuel storage area on apron 4]] [[File:EDDP_luggageterminal_thumb.jpg|Luggage Terminal at Apron 1]]

=== Models since 2010 ===
Here is a selection of the models. [http://www.youtube.com/watch?v=3kNDGiSNUdE YouTube video 2010].

[[File:EDDP10.jpg]] [[File:EDDP11.jpg]] [[File:EDDP12.jpg]] [[File:EDDP13.jpg]] [[File:EDDPbridge1.png]]

== Related content ==
* [[Germany]]
* [[Leipzig/Halle Airspace]]

== External links ==
* [http://www.vacc-sag.org/airport/EDDP Airport Diagrams]
* [http://de.wikipedia.org/wiki/EDDP Leipzig/Halle Airport at Wikipedia] (German)

[[Category:Airports in Germany]]

De/Changelog 2.12

2013-09-22T13:13:16Z

August: /* Wichtige Verbesserungen in dieser Version */

{{ draft | Changelog |Diese changelog wird derzeit für das nächste Release FlightGear geschrieben. Fühlen Sie sich frei , um zu helfen ! Wenn Sie Kenntnis von FlightGear Veränderungen sind , tragen Sie diese bitte im Changelog Es ist eine gute Idee zu überprüfen, [[: Kategorie: Changes_after_2.10 | Newsletter die seit der letzten Version .]] , Und die git commit Geschichte .
Um das Changelog für die neueste Version zu sehen, siehe [[Changelog 2.10]] . 
Wir haben auch Menschen zu ermutigen, durch Verschieben der changelog helfen , aber bitte beachten Sie, dass diese Changelog noch nicht endgültig!
}}

Erhältlich in: ''' Deutsch ''', [[Changelog 2.12|Englisch]], [[: pl: Changelog 2.12 | Polnisch]], [[: fr: Changelog 2.12 | Französisch]], Bitte helfen Sie uns in andere Sprachen zu übersetzen !

== Nächsten FlightGear Changelog ==

Aufgrund wirklichen Leben Zwänge und die geringe Zahl der aktiven Kern-Entwickler , haben wir eine Fluktuation , wo so ziemlich jeder mit besetzt ist getroffen
etwas anderes im Moment. Da scheint jeder in irgendeiner realen Leben Probleme gefangen werden , können wir nicht sehen , einen besseren Weg , um die Freilassung raus als verzögert es für eine Weile .
Auch scheint es, dass es länger als üblich dauern, bis alle Probleme in der RCs gefunden anzugehen. So haben wir beschlossen, den kommenden FlightGear 2.12 Release um einen Monat zu verschieben , um eine ausreichende Zeit, um Release-Kandidaten und Prozess- End- Nutzer-Feedback handhaben ist . [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40568.html]

Das FlightGear Entwicklungsteam freut sich, die Veröffentlichung von v2.12 FlightGear , der freien Open-Source- Flugsimulator verkünden. Diese neue Version enthält viele spannende Neuerungen, Verbesserungen und Bugfixes. Höhepunkte in dieser Version sind eine verbesserte Benutzerfreundlichkeit, Weiterentwicklung des Canvas -Rendering -Toolkit und verbesserte Rendering- Landschaft .

Gegründet im Jahre 1997 , ist FlightGear von einem weltweiten Gruppe von Freiwilligen , die durch eine gemeinsame Ehrgeiz zu schaffen gebracht entwickelt
die realistischste Flugsimulator möglich , die kostenlos zu benutzen , zu modifizieren und zu verteilen. FlightGear ist auf der ganzen Welt eingesetzt
von Desktop- Flugsimulator Enthusiasten , für die Forschung an Universitäten und für interaktive Exponate in Museen.

FlightGear verfügt über mehr als 400 Flugzeuge , ein weltweit Landschaft Datenbank , ein Multi-Player -Umgebung , detaillierte Modellierung Himmel , eine flexible und offene Flugmodellsportes System , abwechslungsreiche Vernetzungsmöglichkeiten , mehrere Display-Unterstützung , eine leistungsfähige Skriptsprache und eine offene Architektur . Best of all, ist Open-Source , wird der Simulator von der Community gehört und jeder ist aufgefordert, beitragen .

Laden Sie FlightGear v2.12 kostenlos von [http://www.flightgear.org FlightGear.org]

FlightGear - Fly Free !

=== Wichtige Verbesserungen in dieser Version ===

''' Flugzeug Modelle '''
* Eine neue Tracking-Animation bietet eine einfache Möglichkeit für Flugzeugentwickler komplexe kinematische Systeme wie Getriebe-Schere oder Fahrwerksklappen an Streben zu animieren. Die Animation kann in Blender umgesetzt werden und dann exportiert FlightGear .

''' Umwelt '''

* Eisberge erscheinen jetzt in den arktischen Meeren.
* Laubbäume werfen ihre Blätter, wenn sie sich oberhalb der Schneegrenze befinden, wodurch ein überzeugender Wintereindruck geschaffen wird.
* Die klimatischen Schneegrenzen variieren nach oben und unten, je nachdem wo auf der Welt man fliegt.
* In der Basis-Wettereinstellung ist nun die "Atmosphärische Lichtstreuung" integriert.
* Wolken sind realistischer, wenn Sie detaillierte Wetter-Modellierung aktivieren.

''' Transponder '''

Das Transponder-Instrumenten-System wurde überarbeitet, so dass es leichter in Flugzeugarmaturen eingebaut werden kann. Im Modus-S werden die Höhen-Codierung und die wichtigen Eigenschaften über Multi-Player gesendet. Dies ermöglicht realistischere Wechselwirkungen im Zusammenspiel mit Fluglotsen in kontrollierten Luftträumen!

''' Leistung '''

Viele NavCache Probleme beim Start von Windows-Nutzern (LAG) wurden behoben.

''' Portabilität '''

Portabilität für ältere Systeme ohne GLSL (Shader) Unterstützung wurde wieder restauriert, so dass FlightGear auf älteren Systemen nicht mehr abstürzt.

''' Atmosphärische Lichtstreuung '''
* Ein ultra- hoher Qualität Shader eingeführt worden , algorithmisch erzeugt Detail auf den Zentimeter -Skala.
* Herbstfarben sind jetzt aus der Mitte des Sommers simuliert bis Anfang des Winters.
* kleine Sichtverhältnisse sind jetzt realistischer gemacht .
* Bäume bewegen sich mit dem Wind.
* Die Brandung ist nun sichtbar unten steil Meer - Klippen.

''' Verbesserte Leistung , reduziert Speicherbelegung '''

''' Usability '''
* Die Checkliste Funktion wurde erweitert.
** Artikel sind farblich codiert , um anzuzeigen, ob sie vollständig sind - grün für jene Elemente, die komplett, gelb für diejenigen , die unvollständig sind.
* Um Cockpit
** Eingewöhnung zu erleichtern, kann der Anwender verlangen, dass die betreffende Regelung hervorgehoben.
** Ein virtueller Co-Pilot kann Checklistenpunkte im Namen des Piloten auszuführen.
** Tutorials von Checklisten einen virtuellen Lehrer , die Sie durch das Durchgehen der Checkliste führen automatisch generiert .
* Ein Knopf Animation verallgemeinert die Bedienung von Knöpfen und Schaltern in den Cockpits verschiedener Flugzeuge.

* Das Wetter Dialog wurde verbessert, um es leichter zu verstehen.
* Tooltips (erhältlich unter dem Debug -Menü) Feedback , dass Computer- Piloten zu verpassen wegen Fehlens von Audio-oder haptische Rückmeldung haben . Wenn Sie Ihre Maus über einen Schalter oder Hebel , erzählt ein kleines Fenster Sie den aktuellen Zustand des Schalters.

''' Internationalisierung '''

* Die Menü -und Systemmeldungen haben Portugiesische übersetzt .

''' Canvas -System '''

Die ''Leinwand'' ist FlightGear ist voll scriptable 2D-Rendering-System , das es dem Anwender einfach, neue Instrumente , Glas-Cockpit -Anzeigen, HUDs und sogar Dialoge und benutzerdefinierte GUI-Widgets mit FlightGear das eingebaute Skriptsprache [[ Nasal ]] (welche zu schaffen macht sieht wirklich ähnlich JavaScript) .

Canvas Verbesserungen in dieser Version gehören :
* Der Stil Setter -System wurde überarbeitet , sind Stil -Setter jetzt nur einmal einrichten für jedes Element Typ und nicht für jedes Element Instanz wie zuvor. Eine statische Karte hält die Setter für jedes Element Typ . Auch eine Art Animation gespeichert ist, wird später zu ermöglichen , um die Eigenschaften von Canvas -Elemente ohne Angabe einer Animation Art zu animieren.
* Der Nasal / cppbind Rahmen wurde verbessert, um mehr Canvas Interna zu Nasal Raum aussetzen
* Leinwand Texturen können jetzt nicht nur als Flugzeuge / Cockpit Texturen (Instrumente, Multifunktionsgeräte ) und für das HUD / GUI verwendet werden, aber auch für Landschaften Objekte . Leinwand Texturen können nun auf Landschaft Objekte platziert werden. Dies erlaubt zum Beispiel die Erstellung von animierten Zeichen / Monitore wie ein Visual Docking Guidance System .
* Aktivieren Textur Wiederholung für Leinwand Bilder
* Verbesserte Unterstützung für die Anzeige von GUI-Widgets .

''' Nasal Scripte '''
* Alle Methoden ausgesetzt, um die Requisiten Nasal Modul nehmen jetzt einen optionalen ersten Parameter refering auf einen anderen Knoten durch einen relativen Pfad .
* SimGear die SGTimer Klasse nun vollständig auf Nasal ausgesetzt , finden Sie in der neuen ''' maketimer '''()-API .
* Mehrere Nasal Bugs , die zuvor auslösen könnte einen Absturz behoben wurden .

''' Rembrandt '''

* Eine wachsende Zahl von Flugzeugen sind konform mit der Rembrandt -Rendering-Technik .

''' KI-Verbesserungen '''

* AI Szenarien können nun zur Laufzeit geladen werden.
* Eine breite Palette von KI-Flugzeuge erhalten einen frischen Anstrich . Der Airbus A320 und A330 wurden umgestaltet , während einige andere Modelle haben verbesserte Animationen.
* Air -to- Luftbetankung wurde verbessert:
** Piloten können jetzt haben die Wahl zwischen einer Reihe von KI Luft - zu-Luft- Tankflugzeuge und die Fluggeschwindigkeit des Tankers , ihre eigenen Flugzeuge entsprechen bei Bedarf auszuwählen.
** Tankers sind realistischer , unterstützen mehrere Tankstellen , konfigurierbare Brennstoffströmungsraten und das Tanken " Umschlag " auf der drogue / Ausleger zentriert .
** Position auf der empfangenden Luftfahrzeugs berücksichtigt bei der Berechnung , ob Kontakt hergestellt worden ist .
** Schwierigkeit wird in -sim , indem der Abstand vom drogue / Boom, Betankung erfolgt konfigurierbar.
** Der Tanker ist nun in der Lage Bericht ein erfolgreicher Kontakt zu den Piloten.

''' Regionale Strukturen '''

Die folgenden Bereiche nun auch ihre eigene Region -spezifische Texturierung und automatisch generierte Modelle / Gebäude :
* Indonesien
* Der Nahe Osten
* Das Vereinigte Königreich ,
* The North Atlantic Islands - Färöer , Shetland, Grönland
* Madagaskar

''' Hervorgehoben neuen und verbesserten Flugzeug '''
* Mudry CAP 10C
* Tupolev Tu- 154B -2
* ASW -20

''' Andere '''

* Zusätzliche Joysticks und Pedale sind out-of -the-box :
** GoFlight TQ6 -ADV
** Genius MetalStrike 3D
** Microsoft SideWinder Precision Racing Wheel Pedale

''' Bug fixes '''

* Siehe [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.12.0 unseren Bugtracker] für eine umfassende , aber unvollständig, Liste der Bugs in dieser Version behoben .

[[ Category: FlightGear Changelogs ]]
[[ en: Changelog 2.12 ]]
[[ pl: Changelog 2.12 ]]
[[ fr: Changelog 2.12 ]]

Flughafen Sylt

2013-07-24T12:45:36Z

August:

{{airport-stub}}

{{infobox Airport
|name = Flughafen Sylt
|image =EDXW-terminal1.jpeg
|alt =
|iata =GWT
|icao =EDXW
|type =Public
|city =Westerland (Sylt)
|owner =Flughafen Sylt GmbH
|website =http://www.flughafen-sylt.de/
|scenerytile =
|download =
|terrasync = published
|runway= 06/24
|length= 5,564 ft / 1,696 m
|material= Asphalt
|runway2= 14/32
|length2= 6,955 ft / 2,120 m
|material2= Concrete
}}

Sylt Airport (known as '''Flughafen Sylt''') is the airport on the island of Sylt and in the municipality of Sylt, Germany.

== Flying at Sylt airspace ==

=== Charts ===
All [http://www.vacc-sag.org/airport/EDXW diagrams and charts] are available for download.

=== Runways and ILS ===

==== Runway 06/24 ====
The east-west runway is 1696m long with a width of 45m. In real life its usually used for gliders.
* VFR '''06''' (064°):
* VFR '''24''' (244°): 108.35
==== Runway 14/32 ====
The north-south runway is 2120m long with a width of 45m. In real life its mostly used by airliners.
* NDB/DME '''14''' (144°): 111.50
* ILS-CAT-I '''32''' (324°): 111.50

=== ATC ===

* Sylt Tower - frequency 119.750

== Infrastructure ==

=== Apron 1 ===
==== Terminal ====
[[File:EDXW-terminal1.jpeg|thumb|Terminal at Apron 1 (published 2012)]]

=== Apron 2 ===
==== GAT ====
[[File:EDXW-GAT1.jpeg|thumb|General Aviation Terminal (published 2012)]]

=== Apron 3 ===

=== Hangars ===
[[File:EDXW-hangar1.jpeg|thumb|Hangar (published 2012)]]

== Surroundings and "Other" ==

== Scenery ==
* Author: Thomas Polzer
* Latest update: December 2012

=== Download via TerraSync ===
Finished since December 2012 the author is publishing his scenery on [[TerraSync]].

=== Development ===

== External links ==
* [http://www.vacc-sag.org/airport/EDXW Airport Diagrams]

[[Category:Airports in Germany]]