FlightGear wiki - User contributions [en]

Custom Spain and Portugal scenery

2021-05-18T22:13:32Z

Ludomo: /* Improvements over the standard scenery */

In 2021, the Spanish community of FlightGear at [http://flightgear.creatuforo.com/viewtopic.php?t=3143 Vive FG!] began a project to enhance the scenario of the Iberian Peninsula. This included an enhancement of the terrain, that was still low detail at the moment the project started, new layouts for many airports and hundreds of objects spread all over the geography.

This custom scenery is no longer available. The publication of the updated [[FlightGear World Scenery 2.0]] made this custom scenery unnecessary, and most buildings were submitted to [[TerraSync]].

== Improvements over the standard scenery ==

The goal of the custom Iberian scenery was to greatly improve the [[World Scenery 1.0.0]] available at the time for the Iberian Peninsula. Specifically:

* Terrain compiled using the last data available from OpenStreetMap and CORINE.
* Improvements on the layouts of many airports (LEBL, LEMG etc.), including many new airports (LESL, LECI etc.)
* Models of lots of buildings, including main airports and some cities: Madrid, Barcelona and many more.
* Parking positions for many the airports. Currently, about 80% of the airports have parking positions.
* Scenery especially suitable for VFR flights: Notification points, cities etc.
* osm2city (real buildings) in Gibraltar (airport: LXGB), Barcelona (airport: LEBL), Pamplona (LEPP) and Bay of Txingudi (airport: LESO-San Sebastian)

Terrain files for the whole Iberian Peninsula are no longer necessary but some minor improvements are not yet in [[TerraSync]]: Airports that depend heavily on the elevation (for example, LEPO), airports already sent to the X-Plane community (for example, LEMG or LEST) after the scenery 2.0 was built, hundreds of buildings everywhere we are still uploading to [[TerraSync]] and even some non-free buildings and airports such as Ibiza-LEIB or Valencia-LEVC.

Most of the buildings and airports are free and can be downloaded from TerraSync.

Some of the changes that are not yet in Terrasync can be dowloaded from: https://mega.nz/file/0MAQVS5A#NvPp639hXgJj1mtTMAyxVIfjr9Q4Vz5aJGvQ4mVKbdM Unfortunately, the authors of a few of the airports did not release the buildings under an open source license. Hence, consider all buildings and textures in the project as private, and use the versions submitted to TerraSync for your opensource projects.

=== Improved and new airports ===

As a result of the project, dozens of airports were modeled. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircraft, such as Alfés (LEAT)

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the airports developed in the project. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The improved layout for most of these airports is already included in [[TerraSync]], as well as most of the custom buildings.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: International and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: Airfields suitable for general aviation, runway longer than 800 m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: Small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800 m.
* Yellow: Heliports.
* Question mark: We are working on them.

== Pre 2.0 scenery ==

Prior to the release of the 2.0 scenery in [[TerraSync]], we maintained a custom scenery for the continental territories of Spain, Portugal, Andorra and Gibraltar. The project used the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti. The scenery files divided the Iberian Peninsula in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

These files are no longer available, since the current scenario in [[TerraSync]] provides a level of detail similar to these old files. More information about these old files can be found at [http://flightgear.creatuforo.com/viewtopic.php?t=3143 Vive FG!]

[[Es:Escenografía personalizada de España y Portugal]]

[[Category:Scenery enhancement projects]]
[[Category:Custom scenery]]

Custom Spain and Portugal scenery

2021-05-18T22:11:10Z

Ludomo: Update the state of the project

In 2021, the Spanish community of FlightGear at [http://flightgear.creatuforo.com/viewtopic.php?t=3143 Vive FG!] began a project to enhance the scenario of the Iberian Peninsula. This included an enhancement of the terrain, that was still low detail at the moment the project started, new layouts for many airports and hundreds of objects spread all over the geography.

This custom scenery is no longer available. The publication of the updated [[FlightGear World Scenery 2.0]] made this custom scenery unnecessary, and most buildings were submitted to [[TerraSync]].

== Improvements over the standard scenery ==

The goal of the custom Iberian scenery was to greatly improve the [[World Scenery 1.0.0]] available at the time for the Iberian Peninsula. Specifically:

* Terrain compiled using the last data available from OpenStreetMap and CORINE.
* Improvements on the layouts of many airports (LEBL, LEMG etc.), including many new airports (LESL, LECI etc.)
* Models of lots of buildings, including main airports and some cities: Madrid, Barcelona and many more.
* Parking positions for many the airports. Currently, about 80% of the airports have parking positions.
* Scenery especially suitable for VFR flights: Notification points, cities etc.
* osm2city (real buildings) in Gibraltar (airport: LXGB), Barcelona (airport: LEBL), Pamplona (LEPP) and Bay of Txingudi (airport: LESO-San Sebastian)

Terrain files for the whole Iberian Peninsula are no longer necessary but some minor improvements are not yet in [[TerraSync]]: Airports that depend heavily on the elevation (for example, LEPO), airports already sent to the X-Plane community (for example, LEMG or LEST) after the scenery 2.0 was built, hundreds of buildings everywhere we are still uploading to [[TerraSync]] and even some non-free buildings and airports such as Ibiza-LEIB or Valencia-LEVC.

Most of the buildings and airports are free and can be downloaded from TerraSync. Unfortunately, the authors of a few of the airports did not release the buildings under an open source license. Hence, consider all buildings and textures in the project as private, and use the versions submitted to TerraSync for your opensource projects.

=== Improved and new airports ===

As a result of the project, dozens of airports were modeled. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircraft, such as Alfés (LEAT)

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the airports developed in the project. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The improved layout for most of these airports is already included in [[TerraSync]], as well as most of the custom buildings.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: International and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: Airfields suitable for general aviation, runway longer than 800 m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: Small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800 m.
* Yellow: Heliports.
* Question mark: We are working on them.

== Pre 2.0 scenery ==

Prior to the release of the 2.0 scenery in [[TerraSync]], we maintained a custom scenery for the continental territories of Spain, Portugal, Andorra and Gibraltar. The project used the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti. The scenery files divided the Iberian Peninsula in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

These files are no longer available, since the current scenario in [[TerraSync]] provides a level of detail similar to these old files. More information about these old files can be found at [http://flightgear.creatuforo.com/viewtopic.php?t=3143 Vive FG!]

[[Es:Escenografía personalizada de España y Portugal]]

[[Category:Scenery enhancement projects]]
[[Category:Custom scenery]]

Howto:Regional texturing

2020-04-01T21:36:32Z

Ludomo: /* Related content */

The FlightGear terrain is created in a largely automated process from a large amount of geodata. The outcome may not necessarily always look like a region appears in reality. '''Regional texturing''' is one of the most powerful tools available to improve the terrain visuals and get a result much closer to reality.

== Background ==

=== Terrain data structures ===

Internally, the terrain is a dense mesh of triangles which determine the elevation at each given point. However, the mesh also encodes what a patch of terrain is supposed to represent by assigning a so-called landclass to a triangle. Landclasses are a concept that is directly inherited from geo databases like CORINE. For instance, the database may tell that a certain patch of terrain is 'Shrubcover'. This information is stored with the terrain mesh.

Flightgear then uses it in-sim in several ways: First, the landclass of a triangle determines how it appears, i.e. what texture and/or effect are assigned. Second, it also determines FDM-relevant properties, for instance whether it will yield when you try to land on it (for instance water), whether you can roll across it, how bumpy rolling will be, and so on. The Advanced Weather system uses the landclass to determine the likelihood of convective cloud formation when the sun heats the terrain. Finally, also the distribution of random overlay objects (such as the density of lights at night or the number of trees or buildings appearing) is also determined by the landclass.

A separate layer for the terrain are static objects which are placed on definite positions onto the mesh by other means - for their placement, no landclass information is used and while they can be placed 'onto' the mesh automatically, they can also be placed to absolute altitudes.

Regional texturing specifically changes the appearance of a landclass and also the placement of overlay objects - it is not a technique capable of altering the outlines of landclasses in the mesh. In other words, using the technique you can make an existing patch of shrubland look more realistic, but you can not change part of a lake that has the wrong shape to be shrubland.

=== Control files ===

The central file responsible for the assignment of textures etc. to landclasses is /Materials/regions/materials.xml (for historical reasons, there are two alternative schemes under /Materials/default/materials.xml and /Materials/dds/materials.xml which are not supposed to be modified by regional definitions). They can be selected in-sim in the rendering dialog.

materials.xml largely serves as an index to include the actual regional definitions. However, hierarchy is important and needs to be considered: Later valid definitions always override earlier definitions. So for instance in texturing Honolulu, Hawaii, first global-summer.xml is considered (which is the world-wide default for summer textures), then the content of hawaii.xml overwrites the global definitions and finally the content of oahu.xml overwrites part of the Hawaii-specific definitions. The wrong order of files can lead to definitions not being used.

Each specific region file has to contain a name, at least one (possible more) area definitions and may contain a condition. The header of the Hawaii region for instance is

<syntaxhighlight lang="xml">
<name>Hawaii</name>
<area>
<lon1>-179.0</lon1>
<lon2>-154.0</lon2>
<lat1>18.8</lat1>
<lat2>28.5</lat2>
</area>

<condition>
<equals>
<property>sim/startup/season</property>
<value>summer</value>
</equals>
</condition>
</syntaxhighlight>

The area tags define rectangles in coordinates - if FG requests a scenery tile to load, and the coordinates of the tile are within the area defined and the condition is met, the landclass definitions of the file are used for the scenery. It follows that regional areas have the minimum size of a scenery tile (dependent on the location in the world, typically a few tens of kilometers).

In practice the condition is used to switch between the summer and winter texture schemes - whether it makes sense to allow the user to select winter textures for Hawaii is in the eye of the beholder.

In each definition file, what follows are the assignments of landclasses to materials, and condition and area holds for all of those in the rest of the file.

=== Material definitions ===

Let's take a look at a single block of material definitions:

<syntaxhighlight lang="xml">
<material>
<name>BarrenCover</name>
<name>Dirt</name>
<name>OpenMining</name>
<name>Rock</name>
<name>Dump</name>
<texture-set>
<texture>Terrain/rocks-lava.png</texture>
<texture n="12">Terrain/rocks-desert.png</texture>
<texture n="14">Terrain/rock_grain01.png</texture>
<texture n="13">Terrain/void.png</texture>
</texture-set>
<parameters>
<grain_strength>0.7</grain_strength>
<transition_model>0.0</transition_model>
</parameters>
<xsize>1000</xsize>
<ysize>1000</ysize>
<solid>1</solid>
<friction-factor>0.9</friction-factor>
<rolling-friction>0.1</rolling-friction>
<bumpiness>0.3</bumpiness>
</material>
</syntaxhighlight>

The first tags are name - they contain a list of landclasses the material refers to (remember that the landclass is stored with the terrain mesh, i.e. the mesh contains the information that a certain triangle is 'Rock').

The next block is the texture set assigned to the landclass - it contains the name of the files to be used for the visuals (to make use of [[Procedural Texturing]] techniques, usually multiple textures are assigned). The parameters block allows to configure procedural techniques by passing control parameters to the Shader generating the composite texture.

<xsize and ysize are important because they determine how large a patch the base texture file is supposed to cover (in the above example, 1000 m x 1000 m is covered by one texture sheet, if the sheet is 1024x1024 pixels, the base resolution is about 1 m).

The final set of parameters is passed to the FDM for ground interactions - we learn that 'Dirt' and 'Rock' are to be treated as solid surfaces and what their rolling friction and bumpiness is supposed to be. Using blocks like this, every landclass as stored in the terrain mesh is assigned characteristics that determine how it looks and behaves in FG when the scenery tile is loaded.

Note that using material definitions it is possible to merge different landclasses - in the above example triangles classified as 'Dirt' and 'Rock' will look and feel the same - but making two separate definitions instead, they could also be made to look differently. Again, a single landclass can not be made two different materials in the same region - later definitions will overwrite earlier ones.

=== Basic workflow ===

To make a regional texture definition for a region then, you need to

* define a region by creating a file with a name, area and condition header
* include this file in materials.xml
* fill it with individual material definitions which are supposed to apply to the region

For the latter task, you may or may not have to

* acquire suitable textures for the region
* configure the procedural texturing parameters to generate good composite textures
* assign random trees, buildings, materials, lights,...
* assign surface properties

== Creating good regional definitions ==

Good terrain texturing is more of an art than of a science, because there are many different factors to consider.

=== What makes a good texture sheet? ===

To get visuals of a region close to reality, you might want to start with aerial imagery of the regions and extract textures from there - but that is not without pitfalls.

The texture needs to be GPL compatible. While there are some public-domain aerial imagery data bases, the most popular (Google Earth) is not. I've also made surprisingly good experience in looking for aerial imagery from local photographers and asking their permission to extract a texture from their work.

The biggest problems of textures are too much structure and lack of structure. If there is lots of structure in a texture, once you map the same sheet to a large area you get pronounced tiling:

[[File:Domains_agro01.jpg|400px|Tiling in agriculture]]

Tiling like this is very prominent from high altitude, it is one of the visually least appealing features and should be avoided at all cost. If the base texture layer has much less structure, tiling is also much less apparent:

[[File:tiling_example.jpg|400px|An example for texture tiling]]

On the other hand, the more the structure inside a texture sheet is de-emphasized, the more prominent is also the appearance of the landclass boundaries where the texture sheets change:

[[File:Egph_egeo3.jpg|400px|An example for landclass seams]]

The ideal texture sheet is a compromise between these two extremes - structured enough to de-emphasize landclass boundaries, not so structured as to lead to bad tiling.

Another thing to consider when extracting a texture from aerial photography is that the land may be often dusty on the photograph. That is problematic because in FGs texturing scheme we want to be able to [http://wiki.flightgear.org/Procedural_Texturing#Dust add dust procedurally] which only works if the base texture is sufficiently clean.

So you may have to work with an image processing software to adjust hue and contrast of a texture sheet after taking it from a photograph, and run a mapping algorithm to make sure it does not generate seams when repeated.

To keep memory occupancy of the graphics card reasonably low (users can not easily opt out of terrain textures), there's a guideline that texture sheet size should not be larger than 1024x1024 for the terrain. In practice, using procedural techniques effectively much higher resolutions can be achieved anyway, so this is not much of a restriction.

=== Understanding the toolkit ===

[[Procedural Texturing]] is the primary tool to counter texture tiling. It works by generating structures from a non-repeating noise function and gives compelling results for both natural landclasses

[[File:overlay02.jpg|400px|Removal of tiling]]

and agriculture

[[File:Domains_agro02.jpg|400px|Overlay de-tiling in agriculture]]

and in addition allows to generate a very high resolution in the centimeter range close to the ground. Basically if you understand and use procedural techniques, even for textures with lots of structure tiling ceases to be a problem and you can focus on dealing with the landclass seams.

One factor to consider is hue blending. If you look at real aerial photographs of a region, you'll notice that soil has the same color everywhere. For instance, North Carolina has a fairly reddish soil. You see that color on bare patches of grass, but also on forest clearings, in gardens - everywhere. Because it's the same soil everywhere. Similarly, vegetation tends to have the same hue in a region, regardless of whether it is in a suburban garden or in the countryside.

Now consider texturing the shrubland of a region with olive green vegetation on reddish patches of soil - and then the suburban regions with ochre soil and lush bright green vegetation - the result is an obvious visual mismatch.

Compare this scene of the French Alps with multiple different hues of green and ground

[[File:Alps-custom-france-scenery.jpg|500px|Lack of hue blending.]]

with a hue-blended scene of the same scenery:

[[File:Procedural01.jpg|500px|Lack of hue blending.]]

to see just how important hue blending is. Procedural overlay texturing techniques are an excellent tool to do such blending, because they allow e.g. to keep the base texture the same across two landclasses and only vary the overlay layers to mark a landclass as different. Usually it is much better to use hue-blended texture sheets than to use the 'right' sheets when there is high contrast between landclasses which is not always there in reality.

By the way, do not aim to remove all vector seams - some of them are there in reality, for instance patches of managed forest in central Europe are characterized by very sharply pronounced boundaries, and so are suburban regions. Aim to de-emphasize only those that have no equivalent in reality.

=== Random vegetation, buildings and objects ===

Inside the <material> tag, it is also possible to declare random vegetation, random buildings or random objects. The difference is that the former two are supported by dedicated shaders which makes their rendering rather optimized, whereas random objects are normal 3d models without dedicated optimization. In general, random vegetation or buildings can hence be drawn in much higher numbers.

The detailed syntax to generate random trees, buildings and objects is beyond the scope of this article, it is explained in the technical specifications of the materials definition in [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.materials README.materials]

The object placement can be made non-random by specifying an object mask (i.e. an additional texture that tells how objects are placed). This allows to place trees on a specific part of the base layer texture if that part shows trees. The green channel mask is used for random vegetation placement, the blue channel for buildings and lights. and the red channel controls the rotation of buildings (0.0 is North, 0.5is South). Fractional colour values can be used to give a probability of placement.

Often, there is a tough choice to be made between placement masks and procedural texturing, because the placement masks are not compatible with the procedurally generated shapes. Placing 3d trees and buildings where they belong on the base texture looks stunning from close-up, but if the area to be covered is too large, tiling may spoil all the visuals. In general, a good idea is to choose placement masks where the landclass patches are small and tiling is not a problem, in particular for urban, suburban and possible small-scale agricultural terrain, use procedural techniques instead where areas covered by the same landclass are large and tiling is an issue.

Also note that the appearance of a large number of buildings does not need to be created by random building placement but can be alternatively done by the urban relief effect.

=== Assigning effects ===

An effect is an instruction for the graphics card how a part of the mesh is to be drawn on screen. Everything on screen has an effect assigned, but to achieve e.g. the sun reflection on water or the relief mapping of urban terrain, a special effect has to be assigned explicitly.

Currently (as of April 2016), Flightgear supports three different rendering schemes, the classical renderer, [[Project Rembrandt]] and [[Atmospheric light scattering]] (ALS).

While ALS has per default support for procedural texturing, the other two have not and support only a limited range of effects which have to be assigned explicitly. For that reason, the focus of most regional texturing development has been on creating ALS procedural definitions, but care has to be taken to create visuals which work for the other renderers as well.

In addition, some situations require also in ALS to assign a special effect because the default terrain effect is ill equipped to handle the visuals (water and urban relief mapping are the prime examples, but there's also the procedural rock shader or the agriculture shader).

Technically, effects are assigned inside a material definition with a tag like

<syntaxhighlight lang="xml">
<effect>Effects/forest</effect>
</syntaxhighlight>

Usually the assignment between ALS-supported effects and effects of the other frameworks is made to be unproblematic:

* assigning an effect like forest of the default rendering framework is ignored by ALS
* assigning ALS supported effects like water or agriculture automatically selects the corresponding classic and Rembrandt effects (water and crop in that case)
* ALS effects usually rely on texture set definitions like

<syntaxhighlight lang="xml">
<texture-set>
<texture>Terrain/deciduous-hires.png</texture>
<texture n="12">Terrain/shrub-hawaii.png</texture>
<texture n="13">Terrain/shrub-hawaii.png</texture>
</texture-set>
</syntaxhighlight>

all the higher index numbers (here 12 and 13) are ignored by the classic renderer and Rembrandt and exclusively used by ALS. It should therefore not be a problem to create a materials definitions which work for all renderers without clashes.

There are some special landclasses, for instance the runway, the taxiways and the airport keep. They have dedicated effects assigned to them which (among other things) render them in especially high resolution since these are terrain parts one usually sees from close-up. Like everything else, they can be regionalized, but do not mix their effects with the standard terrain effects! It may seem tempting to use the airport keep effect also for other grass surfaces, or to render the airport keep as a normal landclass, but this will have unexpected side effects as soon as the terrain is drawn e.g. snowy or wet.

=== Special situations ===

A few extras may be considered:

* ALS supports dynamical autumn coloring. Which part of a texture are vegetation and color reddish in fall is encoded in the texture alpha channel. Currently (April 2016) this is fully worked out for Europe, not for other parts of the world. For a good effect, this has to be done consistently for all materials which have textures with vegetation on them as well as for the tree texture sheets themselves.

* The color of both coastal areas and (in ALS) inland waters is determined at high shader quality by the global water depth map /Textures/Globe/ocean_depth_1.png. In coastal areas, the color encodes the seafloor color and the alpha channel depth, for inland waters the color directly affects water color. Do any modification to the depth map with care!

== Guidelines ==

To create a good regional texture definition set, make sure you take care of and test the following issues:

* All texture sheets need to be GPL compatible - really. Google Earth, no matter how easy, is not acceptable as a source. Be prepared to bring proof of origin before anything is committed.

* Do not assume everyone uses FG like you do. For instance, in some regions of the world, it would look most compelling to assign a sand color to forest landclasses and represent the forest only explicitly via random vegetation. This is a big no, because a user who does not run random vegetation then never recognizes the forest. Any user, no matter how he uses FG, should have the chance to use a VFR map, and that means he has to recognize a forest as forest and a dry lake as a dry lake no matter his rendering settings.

* Test your texture scheme at different altitudes and visibility ranges - what looks very compelling 1500 ft from the ground does not necessarily from 36.000 ft. Usually tiling is much more of a problem from high altitude than from low altitude. Under ALS procedural texturing, tiling should be near absent in a well-done texturing scheme. Under the other renderers it cannot really be avoided, but aim to give compelling visuals to Rembrandt and classic renderer users nevertheless.

* Test your scheme for autumn coloring (if applicable) and snow cover, see whether you get consistent results under all conditions, adapt where applicable.

* If you modify an existing region, or make a sub-region of an existing region, find the maintainer of the region and discuss your proposed changes beforehand and again after you have made them. If someone worked before you, chances are he had a plan, try to work within that plan. Any subregion you define should blend smoothly into the larger region, not create a sudden jarring change in visuals.

* Test your scheme in at least five different locations within the defined area. Often changes which look well in one spot don't at all some 300 km distant. The scheme should work across the whole area - if it can't be made to work, the area is probably too large and sub-dividing it would be the better option.

* Have patience and persistence - creating a good regional texture scheme means balancing many different pros and cons against each other. Having a single stunningly textured landclass is pointless if the blend of the whole region doesn't work.

* Conserve server bandwidth and harddisk space - try re-using existing textures where feasible, add your own only when needed. Often hue and contrast changes to existing textures work surprisingly well.

== Troubleshooting ==

You'll probably frequently end up in a situation in which your changes don't have any visual effect. The following tricks have proven useful:

* check the landclass you're editing in-sim - with the ufo, {{Key press|Ctrl||Alt|click}} on a triangle dumps the material definition briefly on-screen and into the console

* make sure you have the signs of latitude and longitude in your <area> tags correct: 30 degrees western longitude should appear as -30.0 - also make sure that really the smaller number is assigned to <lon1> or <lat1> and the larger number as <lon2> and <lat2>, keeping in mind that -10 is larger than -20.

* check whether any later definition overrides the file you're editing - this is why it's important to have a clear hierarchy of definitions rather than a mess of overlapping definitions which partially override each other

* to check hierarchies, you can gradually comment later definitins in materials.xml and see whether you observe changes

* to check whether you're editing the right file/region, do something obvious, like assign a rock texture to a lake. Change to subtle only once you're sure you're editing the right file.

== Related content ==
* [[Procedural Texturing]]
* Coverage of the regions in FGDATA: https://github.com/Juanvvc/plot_regions/tree/master/regions
* Coverage of the regions that define a material in FGDATA: https://github.com/Juanvvc/plot_regions/tree/master/materials

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

Howto:Regional texturing

2020-03-31T18:34:14Z

Ludomo: link to the coverage of the currently defined regions

The FlightGear terrain is created in a largely automated process from a large amount of geodata. The outcome may not necessarily always look like a region appears in reality. '''Regional texturing''' is one of the most powerful tools available to improve the terrain visuals and get a result much closer to reality.

== Background ==

=== Terrain data structures ===

Internally, the terrain is a dense mesh of triangles which determine the elevation at each given point. However, the mesh also encodes what a patch of terrain is supposed to represent by assigning a so-called landclass to a triangle. Landclasses are a concept that is directly inherited from geo databases like CORINE. For instance, the database may tell that a certain patch of terrain is 'Shrubcover'. This information is stored with the terrain mesh.

Flightgear then uses it in-sim in several ways: First, the landclass of a triangle determines how it appears, i.e. what texture and/or effect are assigned. Second, it also determines FDM-relevant properties, for instance whether it will yield when you try to land on it (for instance water), whether you can roll across it, how bumpy rolling will be, and so on. The Advanced Weather system uses the landclass to determine the likelihood of convective cloud formation when the sun heats the terrain. Finally, also the distribution of random overlay objects (such as the density of lights at night or the number of trees or buildings appearing) is also determined by the landclass.

A separate layer for the terrain are static objects which are placed on definite positions onto the mesh by other means - for their placement, no landclass information is used and while they can be placed 'onto' the mesh automatically, they can also be placed to absolute altitudes.

Regional texturing specifically changes the appearance of a landclass and also the placement of overlay objects - it is not a technique capable of altering the outlines of landclasses in the mesh. In other words, using the technique you can make an existing patch of shrubland look more realistic, but you can not change part of a lake that has the wrong shape to be shrubland.

=== Control files ===

The central file responsible for the assignment of textures etc. to landclasses is /Materials/regions/materials.xml (for historical reasons, there are two alternative schemes under /Materials/default/materials.xml and /Materials/dds/materials.xml which are not supposed to be modified by regional definitions). They can be selected in-sim in the rendering dialog.

materials.xml largely serves as an index to include the actual regional definitions. However, hierarchy is important and needs to be considered: Later valid definitions always override earlier definitions. So for instance in texturing Honolulu, Hawaii, first global-summer.xml is considered (which is the world-wide default for summer textures), then the content of hawaii.xml overwrites the global definitions and finally the content of oahu.xml overwrites part of the Hawaii-specific definitions. The wrong order of files can lead to definitions not being used.

Each specific region file has to contain a name, at least one (possible more) area definitions and may contain a condition. The header of the Hawaii region for instance is

<syntaxhighlight lang="xml">
<name>Hawaii</name>
<area>
<lon1>-179.0</lon1>
<lon2>-154.0</lon2>
<lat1>18.8</lat1>
<lat2>28.5</lat2>
</area>

<condition>
<equals>
<property>sim/startup/season</property>
<value>summer</value>
</equals>
</condition>
</syntaxhighlight>

The area tags define rectangles in coordinates - if FG requests a scenery tile to load, and the coordinates of the tile are within the area defined and the condition is met, the landclass definitions of the file are used for the scenery. It follows that regional areas have the minimum size of a scenery tile (dependent on the location in the world, typically a few tens of kilometers).

In practice the condition is used to switch between the summer and winter texture schemes - whether it makes sense to allow the user to select winter textures for Hawaii is in the eye of the beholder.

In each definition file, what follows are the assignments of landclasses to materials, and condition and area holds for all of those in the rest of the file.

=== Material definitions ===

Let's take a look at a single block of material definitions:

<syntaxhighlight lang="xml">
<material>
<name>BarrenCover</name>
<name>Dirt</name>
<name>OpenMining</name>
<name>Rock</name>
<name>Dump</name>
<texture-set>
<texture>Terrain/rocks-lava.png</texture>
<texture n="12">Terrain/rocks-desert.png</texture>
<texture n="14">Terrain/rock_grain01.png</texture>
<texture n="13">Terrain/void.png</texture>
</texture-set>
<parameters>
<grain_strength>0.7</grain_strength>
<transition_model>0.0</transition_model>
</parameters>
<xsize>1000</xsize>
<ysize>1000</ysize>
<solid>1</solid>
<friction-factor>0.9</friction-factor>
<rolling-friction>0.1</rolling-friction>
<bumpiness>0.3</bumpiness>
</material>
</syntaxhighlight>

The first tags are name - they contain a list of landclasses the material refers to (remember that the landclass is stored with the terrain mesh, i.e. the mesh contains the information that a certain triangle is 'Rock').

The next block is the texture set assigned to the landclass - it contains the name of the files to be used for the visuals (to make use of [[Procedural Texturing]] techniques, usually multiple textures are assigned). The parameters block allows to configure procedural techniques by passing control parameters to the Shader generating the composite texture.

<xsize and ysize are important because they determine how large a patch the base texture file is supposed to cover (in the above example, 1000 m x 1000 m is covered by one texture sheet, if the sheet is 1024x1024 pixels, the base resolution is about 1 m).

The final set of parameters is passed to the FDM for ground interactions - we learn that 'Dirt' and 'Rock' are to be treated as solid surfaces and what their rolling friction and bumpiness is supposed to be. Using blocks like this, every landclass as stored in the terrain mesh is assigned characteristics that determine how it looks and behaves in FG when the scenery tile is loaded.

Note that using material definitions it is possible to merge different landclasses - in the above example triangles classified as 'Dirt' and 'Rock' will look and feel the same - but making two separate definitions instead, they could also be made to look differently. Again, a single landclass can not be made two different materials in the same region - later definitions will overwrite earlier ones.

=== Basic workflow ===

To make a regional texture definition for a region then, you need to

* define a region by creating a file with a name, area and condition header
* include this file in materials.xml
* fill it with individual material definitions which are supposed to apply to the region

For the latter task, you may or may not have to

* acquire suitable textures for the region
* configure the procedural texturing parameters to generate good composite textures
* assign random trees, buildings, materials, lights,...
* assign surface properties

== Creating good regional definitions ==

Good terrain texturing is more of an art than of a science, because there are many different factors to consider.

=== What makes a good texture sheet? ===

To get visuals of a region close to reality, you might want to start with aerial imagery of the regions and extract textures from there - but that is not without pitfalls.

The texture needs to be GPL compatible. While there are some public-domain aerial imagery data bases, the most popular (Google Earth) is not. I've also made surprisingly good experience in looking for aerial imagery from local photographers and asking their permission to extract a texture from their work.

The biggest problems of textures are too much structure and lack of structure. If there is lots of structure in a texture, once you map the same sheet to a large area you get pronounced tiling:

[[File:Domains_agro01.jpg|400px|Tiling in agriculture]]

Tiling like this is very prominent from high altitude, it is one of the visually least appealing features and should be avoided at all cost. If the base texture layer has much less structure, tiling is also much less apparent:

[[File:tiling_example.jpg|400px|An example for texture tiling]]

On the other hand, the more the structure inside a texture sheet is de-emphasized, the more prominent is also the appearance of the landclass boundaries where the texture sheets change:

[[File:Egph_egeo3.jpg|400px|An example for landclass seams]]

The ideal texture sheet is a compromise between these two extremes - structured enough to de-emphasize landclass boundaries, not so structured as to lead to bad tiling.

Another thing to consider when extracting a texture from aerial photography is that the land may be often dusty on the photograph. That is problematic because in FGs texturing scheme we want to be able to [http://wiki.flightgear.org/Procedural_Texturing#Dust add dust procedurally] which only works if the base texture is sufficiently clean.

So you may have to work with an image processing software to adjust hue and contrast of a texture sheet after taking it from a photograph, and run a mapping algorithm to make sure it does not generate seams when repeated.

To keep memory occupancy of the graphics card reasonably low (users can not easily opt out of terrain textures), there's a guideline that texture sheet size should not be larger than 1024x1024 for the terrain. In practice, using procedural techniques effectively much higher resolutions can be achieved anyway, so this is not much of a restriction.

=== Understanding the toolkit ===

[[Procedural Texturing]] is the primary tool to counter texture tiling. It works by generating structures from a non-repeating noise function and gives compelling results for both natural landclasses

[[File:overlay02.jpg|400px|Removal of tiling]]

and agriculture

[[File:Domains_agro02.jpg|400px|Overlay de-tiling in agriculture]]

and in addition allows to generate a very high resolution in the centimeter range close to the ground. Basically if you understand and use procedural techniques, even for textures with lots of structure tiling ceases to be a problem and you can focus on dealing with the landclass seams.

One factor to consider is hue blending. If you look at real aerial photographs of a region, you'll notice that soil has the same color everywhere. For instance, North Carolina has a fairly reddish soil. You see that color on bare patches of grass, but also on forest clearings, in gardens - everywhere. Because it's the same soil everywhere. Similarly, vegetation tends to have the same hue in a region, regardless of whether it is in a suburban garden or in the countryside.

Now consider texturing the shrubland of a region with olive green vegetation on reddish patches of soil - and then the suburban regions with ochre soil and lush bright green vegetation - the result is an obvious visual mismatch.

Compare this scene of the French Alps with multiple different hues of green and ground

[[File:Alps-custom-france-scenery.jpg|500px|Lack of hue blending.]]

with a hue-blended scene of the same scenery:

[[File:Procedural01.jpg|500px|Lack of hue blending.]]

to see just how important hue blending is. Procedural overlay texturing techniques are an excellent tool to do such blending, because they allow e.g. to keep the base texture the same across two landclasses and only vary the overlay layers to mark a landclass as different. Usually it is much better to use hue-blended texture sheets than to use the 'right' sheets when there is high contrast between landclasses which is not always there in reality.

By the way, do not aim to remove all vector seams - some of them are there in reality, for instance patches of managed forest in central Europe are characterized by very sharply pronounced boundaries, and so are suburban regions. Aim to de-emphasize only those that have no equivalent in reality.

=== Random vegetation, buildings and objects ===

Inside the <material> tag, it is also possible to declare random vegetation, random buildings or random objects. The difference is that the former two are supported by dedicated shaders which makes their rendering rather optimized, whereas random objects are normal 3d models without dedicated optimization. In general, random vegetation or buildings can hence be drawn in much higher numbers.

The detailed syntax to generate random trees, buildings and objects is beyond the scope of this article, it is explained in the technical specifications of the materials definition in [https://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.materials README.materials]

The object placement can be made non-random by specifying an object mask (i.e. an additional texture that tells how objects are placed). This allows to place trees on a specific part of the base layer texture if that part shows trees. The green channel mask is used for random vegetation placement, the blue channel for buildings and lights. and the red channel controls the rotation of buildings (0.0 is North, 0.5is South). Fractional colour values can be used to give a probability of placement.

Often, there is a tough choice to be made between placement masks and procedural texturing, because the placement masks are not compatible with the procedurally generated shapes. Placing 3d trees and buildings where they belong on the base texture looks stunning from close-up, but if the area to be covered is too large, tiling may spoil all the visuals. In general, a good idea is to choose placement masks where the landclass patches are small and tiling is not a problem, in particular for urban, suburban and possible small-scale agricultural terrain, use procedural techniques instead where areas covered by the same landclass are large and tiling is an issue.

Also note that the appearance of a large number of buildings does not need to be created by random building placement but can be alternatively done by the urban relief effect.

=== Assigning effects ===

An effect is an instruction for the graphics card how a part of the mesh is to be drawn on screen. Everything on screen has an effect assigned, but to achieve e.g. the sun reflection on water or the relief mapping of urban terrain, a special effect has to be assigned explicitly.

Currently (as of April 2016), Flightgear supports three different rendering schemes, the classical renderer, [[Project Rembrandt]] and [[Atmospheric light scattering]] (ALS).

While ALS has per default support for procedural texturing, the other two have not and support only a limited range of effects which have to be assigned explicitly. For that reason, the focus of most regional texturing development has been on creating ALS procedural definitions, but care has to be taken to create visuals which work for the other renderers as well.

In addition, some situations require also in ALS to assign a special effect because the default terrain effect is ill equipped to handle the visuals (water and urban relief mapping are the prime examples, but there's also the procedural rock shader or the agriculture shader).

Technically, effects are assigned inside a material definition with a tag like

<syntaxhighlight lang="xml">
<effect>Effects/forest</effect>
</syntaxhighlight>

Usually the assignment between ALS-supported effects and effects of the other frameworks is made to be unproblematic:

* assigning an effect like forest of the default rendering framework is ignored by ALS
* assigning ALS supported effects like water or agriculture automatically selects the corresponding classic and Rembrandt effects (water and crop in that case)
* ALS effects usually rely on texture set definitions like

<syntaxhighlight lang="xml">
<texture-set>
<texture>Terrain/deciduous-hires.png</texture>
<texture n="12">Terrain/shrub-hawaii.png</texture>
<texture n="13">Terrain/shrub-hawaii.png</texture>
</texture-set>
</syntaxhighlight>

all the higher index numbers (here 12 and 13) are ignored by the classic renderer and Rembrandt and exclusively used by ALS. It should therefore not be a problem to create a materials definitions which work for all renderers without clashes.

There are some special landclasses, for instance the runway, the taxiways and the airport keep. They have dedicated effects assigned to them which (among other things) render them in especially high resolution since these are terrain parts one usually sees from close-up. Like everything else, they can be regionalized, but do not mix their effects with the standard terrain effects! It may seem tempting to use the airport keep effect also for other grass surfaces, or to render the airport keep as a normal landclass, but this will have unexpected side effects as soon as the terrain is drawn e.g. snowy or wet.

=== Special situations ===

A few extras may be considered:

* ALS supports dynamical autumn coloring. Which part of a texture are vegetation and color reddish in fall is encoded in the texture alpha channel. Currently (April 2016) this is fully worked out for Europe, not for other parts of the world. For a good effect, this has to be done consistently for all materials which have textures with vegetation on them as well as for the tree texture sheets themselves.

* The color of both coastal areas and (in ALS) inland waters is determined at high shader quality by the global water depth map /Textures/Globe/ocean_depth_1.png. In coastal areas, the color encodes the seafloor color and the alpha channel depth, for inland waters the color directly affects water color. Do any modification to the depth map with care!

== Guidelines ==

To create a good regional texture definition set, make sure you take care of and test the following issues:

* All texture sheets need to be GPL compatible - really. Google Earth, no matter how easy, is not acceptable as a source. Be prepared to bring proof of origin before anything is committed.

* Do not assume everyone uses FG like you do. For instance, in some regions of the world, it would look most compelling to assign a sand color to forest landclasses and represent the forest only explicitly via random vegetation. This is a big no, because a user who does not run random vegetation then never recognizes the forest. Any user, no matter how he uses FG, should have the chance to use a VFR map, and that means he has to recognize a forest as forest and a dry lake as a dry lake no matter his rendering settings.

* Test your texture scheme at different altitudes and visibility ranges - what looks very compelling 1500 ft from the ground does not necessarily from 36.000 ft. Usually tiling is much more of a problem from high altitude than from low altitude. Under ALS procedural texturing, tiling should be near absent in a well-done texturing scheme. Under the other renderers it cannot really be avoided, but aim to give compelling visuals to Rembrandt and classic renderer users nevertheless.

* Test your scheme for autumn coloring (if applicable) and snow cover, see whether you get consistent results under all conditions, adapt where applicable.

* If you modify an existing region, or make a sub-region of an existing region, find the maintainer of the region and discuss your proposed changes beforehand and again after you have made them. If someone worked before you, chances are he had a plan, try to work within that plan. Any subregion you define should blend smoothly into the larger region, not create a sudden jarring change in visuals.

* Test your scheme in at least five different locations within the defined area. Often changes which look well in one spot don't at all some 300 km distant. The scheme should work across the whole area - if it can't be made to work, the area is probably too large and sub-dividing it would be the better option.

* Have patience and persistence - creating a good regional texture scheme means balancing many different pros and cons against each other. Having a single stunningly textured landclass is pointless if the blend of the whole region doesn't work.

* Conserve server bandwidth and harddisk space - try re-using existing textures where feasible, add your own only when needed. Often hue and contrast changes to existing textures work surprisingly well.

== Troubleshooting ==

You'll probably frequently end up in a situation in which your changes don't have any visual effect. The following tricks have proven useful:

* check the landclass you're editing in-sim - with the ufo, {{Key press|Ctrl||Alt|click}} on a triangle dumps the material definition briefly on-screen and into the console

* make sure you have the signs of latitude and longitude in your <area> tags correct: 30 degrees western longitude should appear as -30.0 - also make sure that really the smaller number is assigned to <lon1> or <lat1> and the larger number as <lon2> and <lat2>, keeping in mind that -10 is larger than -20.

* check whether any later definition overrides the file you're editing - this is why it's important to have a clear hierarchy of definitions rather than a mess of overlapping definitions which partially override each other

* to check hierarchies, you can gradually comment later definitins in materials.xml and see whether you observe changes

* to check whether you're editing the right file/region, do something obvious, like assign a rock texture to a lake. Change to subtle only once you're sure you're editing the right file.

== Related content ==
* [[Procedural Texturing]]
* Coverage of the regions currently defined in FGDATA: https://github.com/Juanvvc/plot_regions/tree/master/output

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

FGAddon

2015-08-18T10:09:26Z

Ludomo: Update links for fgdata to sourceforge and not gitourious

{{Stub}}

'''FGAddon''' (also '''fgaddon''') is a repository, hosted at [http://sourceforge.net/ SourceForge.net], for extra, optional aircraft. These are aircraft that are not part of the base package. The aircraft that are included in the base package are still kept in [http://sourceforge.net/p/flightgear/fgdata/ci/next/tree/ fgdata] (Git) repository. For users, this means that they can checkout only wanted aircraft, instead of downloading all the aircraft at once. For developers, this means that the base-package is lighter to sync for new contributors and is easier to maintain when a new release is built.

{{FGCquote
|the goal here is to almost get rid of a centralised aircraft repo anyway, and have a decentralised development system with the only central point being the aircraft package manager for end users. Then 99% of people never care where the aircraft is stored while it’s developed.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33413096/
|title=<nowiki>Re: [Flightgear-devel] FGDATA split without Aircraft. Addon in SVN.
(re)Suggesting a Submodule approach. (Re)Proposing a per-Aircraft
repository</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2015-02-13</nowiki>
}}
}}
== Status (12/2014) ==
{{FGCquote
|As we discussed previously, with help from Curt, I've setup the SVN repo who will happily receive our aircraft. 
The new SVN repo is named "FGAddon", because the content of the repo is *optional* for FlightGear. 
http://sourceforge.net/p/flightgear/fgaddon 
 
Right now I would like that every people enjoying commit access on fgdata repo creates an account on sourceforge.org 
Then tell me your username (ideally the same than on gitorious.org) that way I can give required commit access to the fgaddon repo. 
 
The repo is ready to receive aircraft in the dedicated Aircraft directory 
http://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Aircraft/
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32809711/
|title=<nowiki>[Flightgear-devel] Moving aircraft out of fgdata (was size of
flightgear-data)</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-09-08</nowiki>
}}
}}

{{FGCquote
|FGAddon repository is awake ! 
Write permission have been granted to people who already sent me their SF (SourceForge) username. 
 
For those who usually maintain aircraft here is some guidance:
* you have to use this new repository: https://sourceforge.net/p/flightgear/fgaddon/
* read the SVN documentation: http://svnbook.red-bean.com/
* checkout only *your* aircraft with read/right permission
* checkout other aircraft with *only* read permission
About fgdata/Aircraft I would handle the cleanup during the next feature freeze (December 17th) 
it would leave us enough time to be sure that FGAddon is on the good way.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32824511/
|title=<nowiki>Re: [Flightgear-devel] Moving aircraft out of fgdata (was size of
flightgear-data)</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-09-12</nowiki>
}}
}}

{{FGCquote
|I hope to receive lot of sourceforge.org username to add in fgaddon commiter list
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32809711/
|title=<nowiki>[Flightgear-devel] Moving aircraft out of fgdata (was size of
flightgear-data)</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-09-08</nowiki>
}}
}}

{{FGCquote
|there still some aircraft developer/maintainer who didn't send me their SF username. 
Please take some minutes to sign up account on sourceforge.net then tell me your username for commit rights in FGAddon. 
 
@aircraft developer/maintainer: you must *stop* to commit your change in fgdata 
We have switched to SVN since some days and future change must go in this new SVN repo 
 
I know, all of this has been already said previously (certainly with different words) 
but moving from FGData to FGAddon is an important step 
so I would be sure that all people concerned understood what is happening.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/32831003/
|title=<nowiki>Re: [Flightgear-devel] Moving aircraft out of fgdata (was size of
flightgear-data)</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-09-14</nowiki>
}}
}}

== Background ==
The Git/SVN repositories are intended more for developers, DIYers and people wanting to jump ahead and see the newest features. Most "average" users won't need to worry about which repository the aircraft are coming from.

{{FGCquote
|Some months ago, here, I asked to people to contact me in private in order to get commit access to the FGAddon repository.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33154193/
|title=<nowiki>Re: [Flightgear-devel] Wrong commits in FGAddon repository</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-12-16</nowiki>
}}
}}

{{FGCquote
|This is really important - we have had recurring issues with non-coders using CVS, Git and now Svn without thinking about the results. None of these systems are like Dropbox or and FTP server, and what you do with them has long-term consequences and potentially even implications for support the projects receives. I.e if we abuse the severs we get kicked off.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33154284/
|title=<nowiki>Re: [Flightgear-devel] Wrong commits in FGAddon repository</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-12-16</nowiki>
}}
}}

{{FGCquote
|I’m glad Clement is ensuring the quality of commits to the SVN repository is high, because unfortunately the Git repository suffered from that very badly. And in all these systems, there is often no ‘undo’ - once things are done, they are done forever, or require days of careful planning to make safe corrections.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33154284/
|title=<nowiki>Re: [Flightgear-devel] Wrong commits in FGAddon repository</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-12-16</nowiki>
}}
}}

== Todo ==
{{FGCquote
|We may wish to filter which 
aircraft are packaged and distributed with each new release. That would 
require some thought and discussion and work to make an effective filter 
system, but it might be the direction we could ultimately go with.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33042882/
|title=<nowiki>Re: [Flightgear-devel] New SVN Aircraft repo at SourceForge</nowiki>
|author=<nowiki>Curtis Olson</nowiki>
|date=<nowiki>2014-11-15</nowiki>
}}
}}

{{FGCquote
|when someone contact me to get commit access to FGAddon I usually send him some instructions about 'what to do' or 'what to not do' and 'how to do'.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33154193/
|title=<nowiki>Re: [Flightgear-devel] Wrong commits in FGAddon repository</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-12-16</nowiki>
}}
}}

{{FGCquote
|One thing we need to do is document this up-front (on the Wiki I guess), since it hasn’t changed from CVS or Git days either. In the beginning you had to convince Curt to get CVS access, then you had to convince any of the Git admins (me, Anders, Torsten, Clement, Curt, etc) - and now it’s basically the same group for SVN.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33154284/
|title=<nowiki>Re: [Flightgear-devel] Wrong commits in FGAddon repository</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2014-12-16</nowiki>
}}
}}

{{FGCquote
|Even though the full history of the aircraft were not migrated over to the 
new svn fgaddon repository, the original git repository still remains. 
After our 3.4 release branch is created, we will take steps to shrink the 
fgdata git repository as well. *BUT* do not fear because we will preserve 
the current git repository as it is (and any one who has ever cloned the 
fgdata git repository has the entire history themselves already.) So 
perhaps it will involve a few extra steps to investigate past aircraft 
development history (and be slightly less convenient), but the past history 
will still be available for anyone who wishes to review it. This may not 
be a fully satisfactory answer for everyone, but there will still be a way 
to examine the complete history of an aircraft in cases where it is 
required. 
 
Hopefully the times where we need to address changes to abandoned aircraft 
will be rare and special and we can figure out how to address some of these 
odd situations on a case by case basis.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33042832/
|title=<nowiki>Re: [Flightgear-devel] Write access policy for Subversion</nowiki>
|author=<nowiki>Curtis Olson</nowiki>
|date=<nowiki>2014-11-15</nowiki>
}}
}}

== Obtaining Access ==
{{FGCquote
|About "how I decide who can or can't contribute" it's as simple as this: when someone contact me, I'm looking at who is this person, is it a long term contributor ? is it an active forum member ?
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33154193/
|title=<nowiki>Re: [Flightgear-devel] Wrong commits in FGAddon repository</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-12-16</nowiki>
}}
}}

{{FGCquote
|If he is not a long term contributor but an active forum member - "active" mean: a user who is member for long time (more than 3 months) and someone who posted more than 100 posts - I'm checking that this person is aware of how works FlightGear (by reading his posts) and his spirit (it's easy to know if someone is on the same wave or not by reading his posts) is in accordance with the FG spirit (I'm contributing to FlightGear and discussing with long term core dev since more than 4 years now so I can say that I know what is the spirit of FG)
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33154193/
|title=<nowiki>Re: [Flightgear-devel] Wrong commits in FGAddon repository</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-12-16</nowiki>
}}
}}

{{FGCquote
|Also, I'm not the only one person who can give commit access, I give "admin" access to the FGAddon repo to 4 persons (Curt, Anders, Gijs, Torsten) so you can be sure that the FGAddon repo is not 'only in my hand' but also in the hand of other persons.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33154193/
|title=<nowiki>Re: [Flightgear-devel] Wrong commits in FGAddon repository</nowiki>
|author=<nowiki>Clement de l'Hamaide</nowiki>
|date=<nowiki>2014-12-16</nowiki>
}}
}}

== Using FGAddon ==

=== Users ===
The following was taken from [http://forum.flightgear.org/viewtopic.php?f=28&t=24045 Aircraft are now hosted on SVN]

==== Step 1: Preparation ====
* Windows: Install [http://tortoisesvn.net/ TortoiseSVN]
* Linux/Mac: Install SVN

==== Step 2: Get aircraft ====
Pick an aircraft (in this example the DR400-dauphin):
<syntaxhighlight lang="bash">
svn co https://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/DR400-dauphin
</syntaxhighlight>

If you prefer to get all aircraft from the repo, use the following command. Beware that this means a huge download! Hundreds of aircrafts will be downloaded.
<syntaxhighlight lang="bash">
svn checkout svn://svn.code.sf.net/p/flightgear/fgaddon/trunk flightgear-fgaddon
</syntaxhighlight>

==== Regularly ====
You can regularly pick the last update using this command:
<syntaxhighlight lang="bash">
svn up
</syntaxhighlight>

=== Using git with FGAddon (by Hooray)  ===

{{FGCquote
|On a related note: for the aircraft maintainers that do like to work with 
git it is not that hard to connect a per-aircraft git repository 
(either your own or one split of from fgdata.git using the wiki 
instructions) with the FGAddon SVN using the git-svn gateway.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33042564/
|title=<nowiki>Re: [Flightgear-devel] Write access policy for Subversion</nowiki>
|author=<nowiki>Anders Gidenstam</nowiki>
|date=<nowiki>2014-11-15</nowiki>
}}
}}

The following description assumes you already have a single-aircraft git
repository for your aircraft. It also describes a somewhat more
complicated pull/push to SVN than necessary that I use since I want my
private development history to be unaffected by whatever strangeness that
may happen in fgdata/FGAddon.

==== Step 1 ====
Setup git-svn to FGAddon in your per-aircraft repository:

<syntaxhighlight lang="bash">
% git svn init
svn+ssh://<user>@svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/<aircraft>;
</syntaxhighlight>

==== Step 2 ====
Fetch its current state from FGAddon/SVN:

<syntaxhighlight lang="bash">
% git svn fetch
</syntaxhighlight>

==== Step 3 ====
The downloaded SVN history is in the remote branch remotes/git-svn.
To commit changes to SVN you need a local branch that tracks this remote branch. Create a local FGAddon branch that you will use to commit updates. You could use this branch as your new master branch, but I would do this since the branch used to pull/push from/to SVN will be rebased on SVN updates and gets ugly SVN user names etc. in the commits. However, point 4. below would be much shorter if you do all your development on the SVN interface branch.

<syntaxhighlight lang="bash">
% git branch fgaddon remotes/git-svn
</syntaxhighlight>

==== Step 4 ====
When you have committed new stuff on your master branch that you want to push to FGAddon, you checkout your FGAddon branch:

<syntaxhighlight lang="bash">
% git checkout FGAddon
</syntaxhighlight>

Update it from SVN in case someone else has touched your aircraft in the FGAddon SVN.

<syntaxhighlight lang="bash">
% git svn rebase
</syntaxhighlight>

Cherry-pick your new stuff from master to FGAddon:

<syntaxhighlight lang="bash">
% git cherry-pick <commit id>
</syntaxhighlight>

Commit the local commits on your FGAddon branch to the FGAddon SVN:

<syntaxhighlight lang="bash">
% git svn dcommit
</syntaxhighlight>

Checkout your master branch again for local development:

<syntaxhighlight lang="bash">
% git checkout master
</syntaxhighlight>

==== Step 5 ====
To get changes from upstream you can either just download them with

<syntaxhighlight lang="bash">
% git svn fetch
</syntaxhighlight>

or download them and rebase your FGAddon branch onto them:

<syntaxhighlight lang="bash">
% git checkout FGAddon
% git svn rebase
</syntaxhighlight>

If you keep your local master separate from FGAddon you would need to cherry-pick upstream updates you want to your master branch. These days I always use git-svn rather than the ordinary SVN tools when working with SVN repositories. It is just so much nicer to me.

Custom Spain and Portugal scenery

2014-10-27T17:58:17Z

Ludomo:

The Spanish community of FlightGear started in 2012 a project to enhance the scenario of the Iberian Peninsula. This included an enhacement of the terrain, that was still low detail at the moment the project started, new layouts for many airports and hundred of objects spread on all the geography.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/viewtopic.php?t=3347 Vive FG!]

= Download and Installation =

The "update package" can be found at: [http://goo.gl/UYElgD Iberian Peninsula] This is an enhancement of the current scenery in [[TerraSync]] and must be used in addition to [[TerraSync]]. See the next section for a list of changes.

Download the and uncompress the file in a local directory. For example, under Windows, ''My Documents\Games\IBE''. Then, add this directory to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

If you download the file after an update, first remove the existing directory and then install again.

= Improvements over the standard scenery =

The goals of the Iberian scenery were:

* Terrain compiled using the last data available from OpenStreetMap and CORINE. This terrain is no longer necessary after scenery 2.0 in [[TerraSync]].
* Improvements on the layouts of many airports (LEBL, LEMG...), including many new airports (LESL, LECI...)
* Models of lots of buildings, including main airports and some cities: Madrid, Barcelona and many more.
* Parking positions for many the airports. Currently, about 80% of the airports have parking positions.
* Scenery especially suitable for VFR flights: notification points, cities...
* osm2city (real buildings) in Gibraltar (airport: LXGB), Barcelona (airport: LEBL), Pamplona (LEPP) and Bay of Txingudi (airport: LESO-San Sebastian)

Terrain files for the whole Iberian Peninsula are no longer necessary but many improvements are not yet in [[TerraSync]]: airports that depend heavily on the elevation (for example, LEPO), airports already sent to the X-Plane community (for example, LEMG or LEST) after the scenery 2.0, hundreds of buildings everywhere we are still uploading to [[TerraSync]] and even some non-free buildings and airports such as Ibiza-LEIB or Valencia-LEVC.

Most of the buildings and airports are free and can be downloaded from terrasync. Unfortunately, the authors of a few of the airports did not release the buildings under an open source license. Hence, consider all buildings and textures in this file private, and use the versions submitted to Terrasync for your opensource projects.

== Improved and new airports ==

As a result of the project, dozens of airports have been modeled. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the airports developed in the project. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The improved layout for most of these airports are already included in [[TerraSync]], and we are still uploading the remaining airports and their buildings.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

= Pre 2.0 scenery =

Prior to the release of the 2.0 scenery in [[TerraSync]], we maintained a custom scenery for the continental territories of Spain, Portugal, Andorra and Gibraltar. The project used the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti. The scenery files divided the Iberian Peninsula in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

These files are no longer available, since the current scenario in [[TerraSync]] provides a level of detail similar to these old files. More information about these old files can be found at [http://flightgear.creatuforo.com/viewtopic.php?t=3143 Vive FG!]

[[Category:Scenery]]

Custom Spain and Portugal scenery

2014-09-28T21:48:27Z

Ludomo:

The Spanish community of FlightGear started in 2012 a project to enhance the scenario of the Iberian Peninsula. This included an enhacement of the terrain, that was still low detail at the moment the project started, new layouts for many airports and hundred of objects spread on all the geography.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/viewtopic.php?t=3347 Vive FG!]

= Download and Installation =

The "update package" can be found at: [http://goo.gl/viiVFb Iberian Peninsula] This is an enhancement of the current scenery in [[TerraSync]] and must be used in addition to [[TerraSync]]. See the next section for a list of changes.

Download the and uncompress the file in a local directory. For example, under Windows, ''My Documents\Games\IBE''. Then, add this directory to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

If you download the file after an update, first remove the existing directory and then install again.

= Improvements over the standard scenery =

The goals of the Iberian scenery were:

* Terrain compiled using the last data available from OpenStreetMap and CORINE. This terrain is no longer necessary after scenery 2.0 in [[TerraSync]].
* Improvements on the layouts of many airports (LEBL, LEMG...), including many new airports (LESL, LECI...)
* Models of lots of buildings, including main airports and some cities: Madrid, Barcelona and many more.
* Parking positions for many the airports. Currently, about 80% of the airports have parking positions.
* Scenery especially suitable for VFR flights: notification points, cities...
* osm2city (real buildings) in Gibraltar (airport: LXGB), Barcelona (airport: LEBL) and Bay of Txingudi (airport: LESO-San Sebastian)

Currently, the terrain files are no longer necessary but many improvements are not yet in [[TerraSync]]: airports that depend heavily on the elevation (for example, LEPO), airports already sent to the X-Plane community (for example, LEMG or LEST) after the scenery 2.0, hundreds of buildings everywhere we are still uploading to [[TerraSync]] and even some non-free buildings and airports such as Ibiza-LEIB or Valencia-LEVC.

Most of the buildings and airports are free and can be downloaded from terrasync. Unfortunately, the authors of a few of the airports did not release the buildings under an open source license. Hence, consider all buildings and textures in this file private, and use the versions submitted to Terrasync for your opensource projects.

== Improved and new airports ==

As a result of the project, dozens of airports have been modeled. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the airports developed in the project. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The improved layout for most of these airports are already included in [[TerraSync]], and we are still uploading the remaining airports and their buildings.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

= Pre 2.0 scenery =

Prior to the release of the 2.0 scenery in [[TerraSync]], we maintained a custom scenery for the continental territories of Spain, Portugal, Andorra and Gibraltar. The project used the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti. The scenery files divided the Iberian Peninsula in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

These files are no longer available, since the current scenario in [[TerraSync]] provides a level of detail similar to these old files. More information about these old files can be found at [http://flightgear.creatuforo.com/viewtopic.php?t=3143 Vive FG!]

[[Category:Scenery]]

Talk:TerraGear scenery build server

2014-07-27T12:00:25Z

Ludomo: /* Terragear Build Issues */

== Server & Hosting (D-YETI) ==
By the way I personally would give some computing time and IO /Diskspace, at the server listed below, too, because I hope much more pople will benefit from it than running it for me alone. Since Terragear is not so easy to install and even with the gui doesn't always give the result I was expecting.

* Intel® Core™ i5-4570 CPU @ 3.20GHz × 4
* 32GB RAM
* SSD + RAID
* but rather slow Internet connection. (600kbit/s dn / 128kbit/s up)

== Potential TerraGear Issues (psadro_gm) ==
An issue you will may hit is that some terragear tools don't behave very well when run at the same time (genapt and ogrdecode, in particular). this may work with two separate work directories, but I have not tried it. If using the same work directory, You can hit some directory / file creation collisions. To recitify these, I added a Boost global mutex so one can write at a time. With multiple users, this may become a bottleneck.

== Packaging (saiarcot895 ) ==
'''Hooray:'''Obviously, one major part of this would involve installing/packaging SimGear and TerraGear as *.deb files.
This would greatly simplify the installation - we do have several instructions related to this, and even a script - so we could change the script to build SG/TG and then package things afterwards.

Ideally, SimGear would be built in "headless" mode - i.e. minus all the OSG dependencies, no sound etc required: http://wiki.flightgear.org/Building_using_CMake#SimGear_Build_Options

So we would first of all end up with something like "libsimgear-headless-dev" which could be used to build TerraGear.
The next step would be creating a package for TerraGear itself that depends on SimGear-headless-dev

Once these two steps are completed, setting up TerraGear on Linux should become much more straightforward.
And we could use these packages to set up a TerraGear build server.

All this will be based on TurnKeyLinux, which is a debian/wheezy based distro, intended for "remastering" - so that new virtual appliances can be easily created, and exported - so that others can install an ISO file to get a working TG setup.

For now, I simply built SG headless (libsimgearcore) and installed it system-wide and it's working properly.

But obviously it would be better to come up with packages for both, SG and TG (64bit).
Which would be useful for all debian/ubuntu users, not just this particular effort.

Also, we would need to publish those packages, so that people only need to add the repo to download updates automatically.

Overall, this would help greatly simplify TG deployment obviously, no matter if it's about having a build server or not.

Looking at SG/FG, the best option seems to be to use cmake's cpack support to create packages: http://www.cmake.org/Wiki/CMake:CPackPackageGenerators

:'''saiarcot895''': I think I can help here.

:Part of the work may have been already done. We are distributing simgear in two packages (since there are two libraries): libsimgearcore and libsimgearscene. libsimgearcore doesn't have any graphical dependencies; it only depends on libc6. libexpat, libgcc1, libstdc++6, and zlib1g. The only drawback here is that the -dev package includes headers for both libraries, which would require both libraries be installed. Would libsimgearcore be equivalent to the library produced by SIMGEAR_HEADLESS?

:'''saiarcot895''': I just uploaded the terragear package to my [https://launchpad.net/~saiarcot895/+archive/flightgear-edge flightgear-edge PPA]. It should be built and available in about 20-30 minutes for users of Ubuntu Precise, Quantal, and Trusty, but ''not'' Saucy (someone decided to place the Boost libraries on Saucy at a weird place, and so I get to find a fix to that). If you use Debian, I ''think'' you can download the debs for the Quantal version and use that.

:: '''Hooray:''' There seems to be a dependency issue regarding libtiff according to [https://launchpadlibrarian.net/166371092/buildlog_ubuntu-precise-amd64.terragear_2.1.0~1196%2Bgitf089559-0ubuntu1~ppa1~precise1_MANUALDEPWAIT.txt.gz] ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 19:15, 15 February 2014 (UTC)

:::'''saiarcot895''': Already on it. I got another dependency issue with libgdal (apparently, they changed the development package name right after Precise). [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 21:10, 15 February 2014 (UTC)

:::: '''Hooray:''' Would it be a lot of work to set up launchpad such that it also provides a debian wheezy (64bit) package ? That's what I am currently using - otherwise, I'd need to change some things here - so it depends on the amount of work involved obviously. Thanks for looking into it! --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 04:09, 16 February 2014 (UTC)

::::: '''saiarcot895''': Sorry for the delay. The Launchpad PPAs are Ubuntu-only, but I can easily create deb files for Wheezy. It's just a matter of publishing it somewhere. Also, I might have a patch to send regarding having an explicit #include <std::string> line in a file. Something is different in Precise that an explicit #include is necessary. Also, I finally fixed the annoying bug in Saucy; it was actually a bug in CGAL having the incorrect Boost location in its config file. [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 16:14, 8 March 2014 (UTC)

::::: '''saiarcot895''': I've built simgear and terragear for the unstable/sid repo, and the packages are available at http://128.61.105.135/apt. To get it down to wheezy, however, I'll have to bump up (at least) OpenSceneGraph from unstable because wheezy still has 3.0. [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 15:30, 9 March 2014 (UTC)

: '''Hooray:''' Sorry for not getting back to this earlier, thanks for the updates and all your work here. You raised a few good points - I am wondering if we can avoid the OSG issue in this particular instance for now, because we really only require the "headless" part of SimGear for TG, i.e. OSG should not even be required normally, right ? Otherwise, you're right that it would make sense to also provide deb packages for wheezy. But just for TG, I think, we don't need to touch any OSG related stuff ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 16:13, 9 March 2014 (UTC)

:: '''saiarcot895''': You're right, I forgot about that. I've built simgear (in headless mode) for unstable and will build it for testing (jessie) and stable (wheezy), and will build terragear for all three releases once simgear is done. This should be done in a few hours. [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 21:36, 10 March 2014 (UTC)

:: '''saiarcot895''': Simgear for all releases is done, and Terragear for unstable is done. However, Terragear on testing failed with an error in a boost include saying uintptr_t wasn't found...which doesn't make sense to me since boost is from the main Debian archives. [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 00:28, 11 March 2014 (UTC)

::: '''Hooray:''' Thank you, I will be testing this shortly and have forwarded instructions to D-YETI who offered to provide hosting for this.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:32, 11 March 2014 (UTC)

Ok, I added your URL to apt/source.lst on Deb Wheezy (64 bit) and ran apt-get update, when doing "apt-cache search" (simgear/terragear) your repo shows up correctly with the SG packages:
* core
* dev
* dbg

And installation worked without problems, however terragear does not currently show up as a separate package yet, and also isn't listed [http://128.61.105.135/apt/dists/wheezy/main/binary-amd64/Packages in the files on the server] apparently ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 20:02, 11 March 2014 (UTC)

: '''saiarcot895''': Refresh it and check it now. It should be there. [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 20:37, 11 March 2014 (UTC)

::: '''Hooray:''' Confirmed, this works now properly - just took 3 seconds to install TG here now on a fresh system, surprisingly not even SG was required (static build?) Very good job indeed! Now, we'll need to document this and spread the good news (article/newsletter). I'll also try to get in touch with D-YETI to see if he still can contribute hosting, which would also be a good way to host the actual TG packages. I guess we could ask Curt to set up a subdomain like packages.flightgear.org to host deb/ppa packages there for i386/amd64. Did you prepare those packages manually, or where you able to use cmake's cpack support for this ? I am asking because I guess it would be a good idea to strive towards using cmake/cpack for this, so that package creation can be automatically supported for SG/FG/TG for each upcoming release, without involving manual work - possibly by running things via the build server (nightly snapshots/prereleases).--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 20:58, 11 March 2014 (UTC)

:::: '''saiarcot895''': Strange; it has a dependency on libsimgearcore3.1.0, and it's not a static build. Ah well; if it works, you're fine. I did a mix of both manual stuff and scripts, but updates can be fully scripted (which is what I'm doing for my edge PPA). I used scripts from the debhelper package to generate the source package (I think you can get the source package and the debian folder using "sudo apt-get source terragear"), and then used sbuild to recreate a Debian Wheezy chroot and build it in that chroot. It looks like CPack asks for much of the same things as the debian/control file. Also, I'm not sure if CPack generates the .dsc and .changes file, which is necessary for publishing it to a repo. [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 21:33, 11 March 2014 (UTC)

'''saiarcot895''': I'm getting a build failure with TerraGear git commit 25294ee and simgear git commit 1948198.

<code>
<blockquote>
/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1144:9: error: 'class SGBinObject' has no member named 'set_pts_v'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1145:9: error: 'class SGBinObject' has no member named 'set_pts_n'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1146:9: error: 'class SGBinObject' has no member named 'set_pt_materials'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1147:9: error: 'class SGBinObject' has no member named 'set_tris_v'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1148:9: error: 'class SGBinObject' has no member named 'set_tris_n'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1149:9: error: 'class SGBinObject' has no member named 'set_tris_tc'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1150:9: error: 'class SGBinObject' has no member named 'set_tri_materials'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1151:9: error: 'class SGBinObject' has no member named 'set_strips_v'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1152:9: error: 'class SGBinObject' has no member named 'set_strips_n'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1153:9: error: 'class SGBinObject' has no member named 'set_strips_tc'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1154:9: error: 'class SGBinObject' has no member named 'set_strip_materials'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1155:9: error: 'class SGBinObject' has no member named 'set_fans_v'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1156:9: error: 'class SGBinObject' has no member named 'set_fans_n'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1157:9: error: 'class SGBinObject' has no member named 'set_fans_tc'

/build/buildd/terragear-2.1.0~1200+git25294ee/src/Airports/GenAirports850/airport.cxx:1158:9: error: 'class SGBinObject' has no member named 'set_fan_materials'
</blockquote>
</code>

Does someone need to update the code here? (cause of error is SG commit 5b2b420) [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 01:27, 8 April 2014 (UTC)

Please use git branch scenery/ws2.0 for building packages - it is the current stable branch. We are working on new features that need some simgear coordination in master. This work is temporarily stalled for Simgear feature freeze. --[[User:Psadro gm|Psadro gm]] ([[User talk:Psadro gm|talk]]) 13:03, 7 July 2014 (UTC)

Thank you for the update, Psadro gm. Currently, I'm bringing up-to-date both simgear and terragear. The latest simgear is in sid and jessie (testing), and terragear will be going in soon. I'll need to build a few additional packages in sid (stable), since OpenSceneGraph 3.2 isn't in sid. [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 02:20, 9 July 2014 (UTC)

:: Just keep in mind: as per our discussion above, TG/SG can be built in "headless" mode and shouldn't require OSG necessarily. Thanks again for your efforts here, really appreciated ! --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 02:55, 9 July 2014 (UTC)

== TerraGear & TerraGear GUI (reeed) ==
this damned build server idea doesn't want to go away!

very quickly now, to get me up to speed:
* is a hosting server available for our use right away? or who are the probable candidate(s)?
* who maintains the latest, compileable and functional TerraGear?
* Is the above TG packaged with Gijs' GUI? If not, which one is packaged?

== TurnkeyLinux (Hooray) ==
* http://www.turnkeylinux.org/blog/introducing-tkldev
* http://www.turnkeylinux.org/forum/support/20120507/how-create-customized-appliance
* https://github.com/turnkeylinux-apps/tkldev/tree/master/docs

== WebService / UI (F-JJTH, Gijs, Hooray, reeed ) ==

{{Progressbar|40}} (proof-of-concept by F-JJTH)

'''Gijs:'''It'd be nicer/better to have a web interface. That'll allow you to keep the interface and backend in sync (without asking people to recompile/redownload the GUI om each change), save people from downloading yet another tool and make it work/look the same on all systems.

: '''Hooray:''' As I mentioned on the forum, I am not at all opposed to having a webservice, I just consider it much more straightforward to modify [[TerraGear GUI]] for now. if there's anybody interested in working on a web interface that would obviously be great, but short of that, I would simply modify TerraGear GUI to support two modes local (default) and remote (build server) over SSH. I already looked at the code briefly and the main issue is the amount of Qt code that runs locally, i.e. to download stuff for example - if that could be moved out into external programs, preferably part of TerraGear itself, then it would be trivial to support both, local AND remote TG installations. Currently, there's just too much stuff directly done, without calling external tools - so that would need to be factored out.
: Overall, the TerraGear GUI is not such a complex code base, so I am not sure if keeping the frontend/backends in sync is such a huge issue ?? I mean, people ALREADY need to have a matching TG/TGGUI versions after all ...
: I am certainly not going to stop anybody from coming up with a webservice - it's just something that I am probably not going to work on anytime soon - while modifying TGGUI accordingly would just take a few hours and involve well-understood steps.
: So I wasn't thinking of forking TGGUI, but more about extending it to support local AND remote installations - selected/configured during startup.

: Obviously you are much more familiar with the code in question here - but based on what I've seen, it would not be such a difficult undertaking to turn TGGUI into a "remote control" for a TG build server setup.

: If frontend changes are such an issue, I would actually suggest to get rid of the hardcoded GUI and use Qt's scripting support for those *.ui files instead - that would allow you to automatically download QtScript while booting.

: Finally, coming up with a working web service is in my opinion more difficult than using SSH to teach TGGUI to run a handful of commands remotely and fetch the results via SFTP - so yeah, I am kinda lazy here

== Standalone GUI (via SSH) ==

If the consensus should end up being not to use [[TerraGear GUI]], the most straightforward option for coming up with a simple GUI would be Python using SSH and GUI bindings:

* http://docs.fabfile.org/en/1.4.2/index.html
* http://hackerific.net/2009/02/06/paramiko-scripting-ssh-with-python/
* http://jessenoller.com/2009/02/05/ssh-programming-with-paramiko-completely-different/
* https://github.com/paramiko/paramiko
* http://www.pythonforbeginners.com/code-snippets-source-code/ssh-connection-with-python/
* http://sourceforge.net/projects/pexpect/

== Terragear Build Issues ==

(I decided to create a new section instead of continuing in an off-topic section)

I found another build error, although this might be due to changes in upstream. Here's the build log:

<pre>cd "/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/src/Prep/DemChop" && /usr/bin/cmake -E cmake_link_script CMakeFiles/hgtchop.dir/link.txt --verbose=1
/usr/bin/c++ -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -frounding-math -Wall -D_REENTRANT -DNO_OPENSCENEGRAPH_INTERFACE -O3 -DNDEBUG -Wl,-z,relro -Wl,--as-needed CMakeFiles/hgtchop.dir/hgtchop.cxx.o -o hgtchop -rdynamic -lmpfr -lgmp -lCGAL_Core -lCGAL -lboost_thread -lboost_system -lpthread ../../Lib/HGT/libHGT.a -lz -lSimGearCore -lpthread -lz -lrt -lmpfr -lgmp -lCGAL_Core -lCGAL -lboost_thread -lboost_system -lpthread -lSimGearCore -lpthread -lrt
In file included from /«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_contour.hxx:12:0,
from /«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_polygon.hxx:64,
from /«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_chopper.hxx:3,
from /«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_chopper.cxx:9:
/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_unique_geod.hxx: In constructor 'SGGeodIndex::SGGeodIndex(SGGeod)':
/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_unique_geod.hxx:44:27: warning: large integer implicitly truncated to unsigned type [-Woverflow]
FNV_prime = 1099511628211ULL;
^
/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_unique_geod.hxx:45:30: warning: large integer implicitly truncated to unsigned type [-Woverflow]
offset_basis = 14695981039346656037ULL;
^
make[3]: Leaving directory '/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build'
/usr/bin/cmake -E cmake_progress_report "/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/CMakeFiles" 33
[ 25%] Built target hgtchop
/usr/bin/cmake -E cmake_progress_report "/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/CMakeFiles" 46
[ 26%] Building CXX object src/Lib/terragear/CMakeFiles/terragear.dir/tg_contour.cxx.o
cd "/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/src/Lib/terragear" && /usr/bin/c++ -DCGAL_USE_GMP -DCGAL_USE_MPFR -DHAVE_CONFIG_H -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -frounding-math -Wall -D_REENTRANT -DNO_OPENSCENEGRAPH_INTERFACE -O3 -DNDEBUG -isystem /usr/include/i386-linux-gnu -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build" -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src" -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/src" -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/src/Include" -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib" -I/usr/include/gdal -o CMakeFiles/terragear.dir/tg_contour.cxx.o -c "/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_contour.cxx"
/usr/bin/cmake -E cmake_progress_report "/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/CMakeFiles" 47
[ 28%] Building CXX object src/Lib/terragear/CMakeFiles/terragear.dir/tg_misc.cxx.o
cd "/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/src/Lib/terragear" && /usr/bin/c++ -DCGAL_USE_GMP -DCGAL_USE_MPFR -DHAVE_CONFIG_H -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -frounding-math -Wall -D_REENTRANT -DNO_OPENSCENEGRAPH_INTERFACE -O3 -DNDEBUG -isystem /usr/include/i386-linux-gnu -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build" -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src" -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/src" -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/src/Include" -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib" -I/usr/include/gdal -o CMakeFiles/terragear.dir/tg_misc.cxx.o -c "/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_misc.cxx"
/usr/bin/cmake -E cmake_progress_report "/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/CMakeFiles" 48
[ 29%] Building CXX object src/Lib/terragear/CMakeFiles/terragear.dir/tg_nodes.cxx.o
cd "/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/src/Lib/terragear" && /usr/bin/c++ -DCGAL_USE_GMP -DCGAL_USE_MPFR -DHAVE_CONFIG_H -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -frounding-math -Wall -D_REENTRANT -DNO_OPENSCENEGRAPH_INTERFACE -O3 -DNDEBUG -isystem /usr/include/i386-linux-gnu -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build" -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src" -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/src" -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/build/src/Include" -I"/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib" -I/usr/include/gdal -o CMakeFiles/terragear.dir/tg_nodes.cxx.o -c "/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_nodes.cxx"
In file included from /«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_contour.hxx:12:0,
from /«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_polygon.hxx:64,
from /«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_accumulator.hxx:4,
from /«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_contour.cxx:6:
/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_unique_geod.hxx: In constructor 'SGGeodIndex::SGGeodIndex(SGGeod)':
/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_unique_geod.hxx:44:27: warning: large integer implicitly truncated to unsigned type [-Woverflow]
FNV_prime = 1099511628211ULL;
^
/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_unique_geod.hxx:45:30: warning: large integer implicitly truncated to unsigned type [-Woverflow]
offset_basis = 14695981039346656037ULL;
^
In file included from /usr/include/CGAL/assertions.h:36:0,
from /usr/include/CGAL/basic.h:42,
from /usr/include/CGAL/Cartesian/Cartesian_base.h:28,
from /usr/include/CGAL/Simple_cartesian.h:28,
from /«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_nodes.hxx:10,
from /«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_nodes.cxx:2:
/usr/include/CGAL/Search_traits_adapter.h: In instantiation of 'class CGAL::Search_traits_adapter<boost::tuples::tuple<CGAL::Point_2<CGAL::Simple_cartesian<double> >, double>, My_point_property_map, CGAL::Search_traits_2<CGAL::Simple_cartesian<double> > >':
/«BUILDDIR»/terragear-2.1.0~1202+git47db776/src/Lib/terragear/tg_nodes.hxx:35:29: required from here
/usr/include/CGAL/Search_traits_adapter.h:75:3: error: invalid application of 'sizeof' to incomplete type 'boost::STATIC_ASSERTION_FAILURE<false>'
BOOST_STATIC_ASSERT( ( boost::is_same< boost::lvalue_property_map_tag,</pre>

The version of CGAL is 4.4-1+b1, and the version of Boost is 1.55.0+dfsg-2. This actually might be an incompatibility in CGAL with Boost.

I'm also having this issue with CGAL 4.4 from thee Debian repositories and the official CGAL website. I tried downloading and installing CGAL 4.3 and everything worked as expected. It seems it is an incompatibility of CGAL 4.4 with Boost 1.55 --[[User:Ludomo|Ludomo]] ([[User talk:Ludomo|talk]]) 12:00, 27 July 2014 (UTC)

Aeronautical information publication

2014-04-08T18:53:37Z

Ludomo:

The '''Aeronautical Information Publication''' ('''AIP''') contains most of the information about the regulations, air ways, navigation aids etc. in a nations air space. The AIP is published by that nations air authority or agency at regular intervals and together with notices to air men (NOTAMs) it contains all the information needed, except for the weather, for flying in that airspace unless it states otherwise.

== Main contents ==
The AIP consists of three main parts, ''General'' (''GEN''), containing some general information, ''En route'' (''ENR''), containing information about the airspace, air routes and navigation aids, and ''Aerodromes'' (''AD''), with information about the airports, airfields and helipads. Sometimes there is also amendments and supplements, and the AIP can also point to other sources for example for aerodrome information and charts.

=== GEN ===
* '''GEN 1.''' National aviation authorities, national regulations regarding entry and exit of the air space and required instrumentation and radios
* '''GEN 2.''' Measuring systems, time zones, abbreviations, map legends, lists with positions of fixes and navigation aids, conversion and sunrise/sunset tables
* '''GEN 3.''' Aeronautical information, air traffic communication and meteorological services, where to get maps and search and rescue routines
* '''GEN 4.''' Fees and charges

An important section is GEN 1.7, ''Differences from ICAO Standards, recommended practices and procedures'', as there can sometimes be important differences between countries.

=== ENR ===
* '''ENR 1.''' Instrument and visual flight rules (IFR and VFR), altimeter setting procedures, flight planning and filing of flight plans, and time zones
* '''ENR 2.''' ATC air spaces
* '''ENR 3.''' Air routes
* '''ENR 4.''' Navigation aids
* '''ENR 5.''' Prohibited, restricted and dangerous areas, military training areas, bird migration areas and other hazards

=== AD ===
* '''AD 1.''' Everything about airports, taxi procedures, traffic patterns, lightening etc.
* '''AD 2.''' Listings of public airports, airfields and helipads together with charts and other information

== Related content ==
* [[Navigation references]]
* [[Getting aeronautical charts]]

== External links ==
A complete list of European AIPs can be found [http://www.eurocontrol.int/aim/public/standard_page/web_eur.html here].

* [http://ais.anac.gov.ar/aip Argentina]
* [http://www.aisweb.aer.mil.br/index.cfm?i=home&lingua=en Brazil]
* [http://www.aerocivil.gov.co/AIS/AIP/Paginas/Inicio.aspx Colombia]
* [http://www.slv.dk/Dokumenter/dscgi/ds.py/View/Collection-94 Denmark] (also includes Greenland and the Faeroe Islands)
* [http://www.sia.aviation-civile.gouv.fr/aip/enligne/fr/home.htm France]
* [http://www.ais.fi/ais/eaip/en/ Finland]
* [http://www.ais-netherlands.nl/aim/index.html the Netherlands]
* [http://www.aena.es/csee/Satellite/navegacion-aerea/en/Page/1078418725020/ Spain]
* [http://www.lfv.se/en/FPC/IAIP/ Sweden]
* [http://www.nats-uk.ead-it.com/public/index.php%3Foption=com_content&task=blogcategory&id=165&Itemid=3.html United Kingdom]

[[Category:Aviation]]

Custom Spain and Portugal scenery

2014-03-03T23:38:48Z

Ludomo:

The Spanish community of FlightGear started in 2012 a project to enhance the scenario of the Iberian Peninsula. This included an enhacement of the terrain, that was still low detail at the moment the project started, new layouts for many airports and hundred of objects spread on all the geography.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/viewtopic.php?t=3347 Vive FG!]

= Download and Installation =

The "update package" can be found at: [https://mega.co.nz/#!scIERIyR!_kXe4zpkH2GI4cwIRzzASSgI0EgNK6-Rh5gCntDDaZc Iberian Peninsula] This is an enhancement of the current scenery in [[TerraSync]] and must be used in addition to [[TerraSync]]. See the next section for a list of changes.

Download the and uncompress the file in a local directory. For example, under Windows, ''My Documents\Games\IBE''. Then, add this directory to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

If you download the file after an update, first remove the existing directory and then install again.

= Improvements over the standard scenery =

The goals of the Iberian scenery were:

* Terrain compiled using the last data available from OpenStreetMap and CORINE. This terrain is no longer necessary from the introduction of the scenery 2.0 in [[TerraSync]].
* Improvements on the layouts of many airports (LEBL, LEMG...), including many new airports (LESL, LECI...)
* Models of lots of buildings, including main airports and some cities: Madrid, Barcelona and many more.
* Parking points for many the airports. Currently, about 80% of the airports have parking points.
* Scenery especially suitable for VFR flights: notification points, cities...
* osm2city (real buildings) in Gibraltar (airport: LXGB) and Bay of Txingudi (airport: LESO-San Sebastian)

Currently, the terrain files are no longer necessary but many improvements are not yet in [[TerraSync]]: airports that depend heavily on the elevation (for example, LEPO), or airports not yet sent to the X-Plane community (for example, LEMG or LEST), as well as hundred of buildings everywhere we are still uploading to [[TerraSync]] and even some non-free buildings.

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 license [http://creativecommons.org/licenses/by-sa/3.0/], and under the terms of the GPL License. Use the license more suitable for your needs.

== Improved and new airports ==

As a result of the project, dozens of airports have been modeled. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the airports developed in the project. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The improved layout for most of these airports are already included in [[TerraSync]], and we are still uploading the remaining airports and their buildings.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

= Pre 2.0 scenery =

Prior to the release of the 2.0 scenery in [[TerraSync]], we maintained a custom scenery for the continental territories of Spain, Portugal, Andorra and Gibraltar. The project used the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti. The scenery files divided the Iberian Peninsula in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

These files are no longer available, since the current scenario in [[TerraSync]] provides a level of detail similar to these old files. More information about these old files can be found at [http://flightgear.creatuforo.com/viewtopic.php?t=3143 Vive FG!]

[[Category:Scenery]]

FlightGear World Scenery 2.0

2014-02-18T15:38:13Z

Ludomo: /* Known bugs and limitations */

:''Follow the dedicated forum thread: [http://forum.flightgear.org/viewtopic.php?f=5&t=21294 FG Worldwide scenery 2.0 - Return of experience]''

The '''FlightGear World Scenery 2.0''' was released during [[FSweekend]] November 2013. This new scenery reflects a major improvement over the existing default world scenery and has taken over five years to complete. A [http://mapserver.flightgear.org/map/?lon=14.56652&lat=-25.18458&zoom=1&layers=B00000000000FTFFTFFTFFFFFFFF much higher level of detail] and internal consistency characterizes this new release, in addition to the fact that it will serve as a stepping-stone for further incremental refinements.

== Source data ==
This FlightGear World Scenery was compiled from:
* ViewFinderPanoramas elevation model by Jonathan de Ferranti (using 20m accuracy with terrafit.py -e 20),
* VMap0 Ed.5 Worldwide Land Cover
* CORINE Land Cover 2006v16 for Europe (Source : European Union, SOeS, CORINE Land Cover, 2006 - [http://www.ifen.fr/index.php?id=88]). See [http://wiki.osgeo.org/wiki/LandcoverDB_CS_Detail|here] for the correspondance between CORINE and FG textures
* Several custom land cover enhancements (to be listed here...)
* The latest airports (2013.10), maintained by Robin Peel of X-Plane
* Road, rail and rivers courses line data by OpenStreetMap [http://www.openstreetmap.org]

== Distribution ==
World Scenery 2.0 is available through the usual channels:
* [[TerraSync]]
* [http://terasaur.org/item/downloads/flightgear-v2-12/6697 Torrent]
* FlightGear main website
* [[TerraSync_by_hand_using_svn|TerraSync by hand using svn]]

== Side note ==
Note that all objects elevation were recomputed. Thus, if some objects were defined with a bad elevation or bad offset, they may have taken a bit of elevation. Use [http://scenemodels.flightgear.org our webforms], if necessary, to fix this.

== Screenshots ==

== Known bugs and limitations ==
# clipping of OSM roads on water showing height glitches (due to bad coast/river lines definitions and bad clipping): clip roads against landmass or add landmass where required? Should roads over bridges get removed, even in places where a 3D bridge model is missing?
# some z-fighting (clipper is generating the correct number of contours, but the airport hole is wound as a boundary, not a hole) and/or triangles on airports (LFRH, EDWJ (partially submerged)...);
# some troubles on very dense cities (such as Paris) leading to grey-white triangles on cities - see also yellow lines @LFPG;
# some line issues on small airfield with LTA specific runways (LFNH, LFLI...) - the small centerlines on the runways are "floating" over the runway (20 cm to 1m), leading to some gear destructions ;-) (they didn't use lines, but surfaces that are defined as transparent and borders defined as the line type. This way you limit the number of "line features"). Probably "hot" = false would solve it. See [http://uppix.net/y1H1NB.png 1] [http://uppix.net/sMdg17.png 2] [http://uppix.net/kAXrdF.png 3] [http://uppix.net/vYuReF.png 4] [http://uppix.net/DQ4NHr.png 5]. Thanks Clément for noticing;
# airport being located over two different tiles sometimes renders bad, leading to z-fighting (LEJR, UKKE...);
# on sharp cliffs, water sometimes climb over the cliffs (see e000n40/e000n49/2958056 and [http://img809.imageshack.us/img809/2082/9n96.jpg this picture] for instance). Thanks clm76 for reporting;
# terrain and ocean z-fighting such as [http://mapserver.flightgear.org/map/?lon=12.73312&lat=55.60834&zoom=15 east of EKCH]. See tile 3155042 and EDWJ;
# clipping between river and terrain is somewhat strange, making the river "climb" over the terrain, noticeably under bridges - probably due to the presence of the roads. See [http://img809.imageshack.us/img809/2082/9n96.jpg this example];
# the Moss Landing airport (on the coast a little bit south of KSFO) is partly submerged into the water and the airport's north end is elevated above the terrain around it. There is an area on the coast just to the north of the Moss Landing airport that is above sea level if you are up above 1000ft but is covered in water is you are on the deck. When flying over this you can see trees sticking up out of the water so the code that is placing random trees thinks this is above sea level. The old scenery didn't have either of these problems. Also if you fly over this at just the right altitude you can see this area switching back and forth between being water and land (thanks hvengel);
# on many airports where the taxiway signs are now taken from the apt.dat and put in the Terrain folder, the old signs still remain in the Object folder. See EDDF, ELLX;
# on ELLX there are some problems with "holes" in the pavement that flicker between grass and tarmac. I saw this (if I remember correctly) with an older development version of terragear, but this was fixed some time ago.
# on EHAM some vertice seems to be inverted [http://uppix.net/AVUaZt.jpg see this picture]
# at LFLI the taxiway is not correctly drawn
# the taxiway signs are not rendered correctly with transition shader set to its maximum in ALS. Quoting ThorstenB, "It occurs because you're using the terrain shader effect on something that isn't part of the terrain but in reality an artificial object placed onto the terrain. The terrain shader effect concludes correctly that a natural vertical surface cannot be anything but rock, so it replaces the default texture with the default steep gradient texture - which is rock. In my view, the proper solution would be to *not* render signs as part of the terrain but to let a different effect handle them (model-default.eff should do the trick for instance, but one could also run a lower quality terrain shader). If that is not acceptable a workaround is to declare the gradient texture for the signs as void.png as described in http://wiki.flightgear.org/Procedural_Texturing#The_gradient_texture which continues to use the terrain-specific effect but instructs the shader not to use a separate texture for steep gradients."
# sometimes some strange water width transitions, like [http://i217.photobucket.com/albums/cc283/oliunterderbruecke/flightgear/TG%20bugs/fgfs2013-11-0822-18-06-03_zpsf3527850.jpg for the Rhein] - reported by ot-666
# triangle winding appears inconsistent - especially when a vertex is shared by 4+ edges. Issue can be visualized here: [https://dl.dropboxusercontent.com/u/29968727/fgfs-screen-116.png messed up binormals and tangents] This may be the root cause of the urban shader issue - reported by i4dnf. Issue understood - Winding is not the issue, duplicate nodes per triangle (zero area triangles) are possible when converting the CGAL exact triangle back to nodes using double floats.
# In a few airports (LEVT, LEGE are two examples), taxiways are defined in using a stack of layers: the bottom layer for the asphalt surface and the upper layer (defined as transparent) is only used to define the lines. Current tools do not support stacks of layers and the upper layer is "transparent" all the way down to the ground. See [http://i.imgur.com/AkOd5Zo.png 1] and [http://forum.flightgear.org/viewtopic.php?f=5&t=21294&p=201132#p201126 2] This is easily fixable in the data by changing transparent layers to asphalt, but it involves a manual intervention in each airport and sending the data back to Robin. And actually, there is not anything wrong with the original data. Other airports such as LFLR do take advantage of transparent taxiways.

Fixed:
* [FIXED] near EHAM there is a pylon under terrain [http://uppix.net/7rFkTR.jpg see this picture]
* [FIXED] # glacier landcover is missing, leading to some holes in high moutains, as seen in Switzerland (SW [http://mapserver.flightgear.org/map/?lon=8.12304&lat=46.07741&zoom=9&layers=B00000000000FTFFTFFTFFFFFFFF LSMM]), Austria ([http://mapserver.flightgear.org/map/?lon=11.3527&lat=47.25782&zoom=10&layers=B00000000000FTFFTFFTFFFFFFFF south of LOWI]) and Northern Norway (i.e. [http://mapserver.flightgear.org/map/?lon=14.210&lat=65.974&zoom=9&layers=B00000000000FTFFTFFTFFFFFFFF near ENMS]);

== Features enhancement ==
# enhance landcover data for the rest of the world (OSM? vectorize US-American NLCD2006?) and add more custom scenery and fixes;
# complete CORINE coverage, fix overlaps in CLC2000 and merge with CLC2006;
# use latest ViewFinderPanoramas DEM's;
# find a new svn hosting solution;
# compute the next terrain with textures-lines option;
# add some more OSM data (secondary...);
# descent airports priority below roads, so roads and railroads can be shown over airports; have a proper solution for roads running over terrain classified as airfield, maybe extract administrative boundaries from apt.dat;
# retry multi-thread;
# enhance the "random" tree and builds placement to take OSM into account;
# .SPT file support - push Mathias' LOD ideas forward;
# landclass border blurring - Several ideas on this - It would be really nice to be able to do it;
# osm motorway_link (and the other _link) roads should probably have their own width. Perhaps grouped into a separate shapefile, or handled in ogr-decode - single lane is most likely;
# osm line data simplification / preprocessing. - We've done some experimenting, and the results are promising. This should reduce the number of triangles generated. It could create longer continuous roads, which allows better control of the generated texture coordinates - so we could, theoretically, populate the roads with traffic in the future.

== External link ==
* World Scenery 2.0 release announcement on the forum: [http://forum.flightgear.org/viewtopic.php?f=5&t=21226& FlightGear World Scenery 2.0 released]

[[Category:Scenery]]

FlightGear World Scenery 2.0

2014-02-18T15:37:02Z

Ludomo: /* Known bugs and limitations */

:''Follow the dedicated forum thread: [http://forum.flightgear.org/viewtopic.php?f=5&t=21294 FG Worldwide scenery 2.0 - Return of experience]''

The '''FlightGear World Scenery 2.0''' was released during [[FSweekend]] November 2013. This new scenery reflects a major improvement over the existing default world scenery and has taken over five years to complete. A [http://mapserver.flightgear.org/map/?lon=14.56652&lat=-25.18458&zoom=1&layers=B00000000000FTFFTFFTFFFFFFFF much higher level of detail] and internal consistency characterizes this new release, in addition to the fact that it will serve as a stepping-stone for further incremental refinements.

== Source data ==
This FlightGear World Scenery was compiled from:
* ViewFinderPanoramas elevation model by Jonathan de Ferranti (using 20m accuracy with terrafit.py -e 20),
* VMap0 Ed.5 Worldwide Land Cover
* CORINE Land Cover 2006v16 for Europe (Source : European Union, SOeS, CORINE Land Cover, 2006 - [http://www.ifen.fr/index.php?id=88]). See [http://wiki.osgeo.org/wiki/LandcoverDB_CS_Detail|here] for the correspondance between CORINE and FG textures
* Several custom land cover enhancements (to be listed here...)
* The latest airports (2013.10), maintained by Robin Peel of X-Plane
* Road, rail and rivers courses line data by OpenStreetMap [http://www.openstreetmap.org]

== Distribution ==
World Scenery 2.0 is available through the usual channels:
* [[TerraSync]]
* [http://terasaur.org/item/downloads/flightgear-v2-12/6697 Torrent]
* FlightGear main website
* [[TerraSync_by_hand_using_svn|TerraSync by hand using svn]]

== Side note ==
Note that all objects elevation were recomputed. Thus, if some objects were defined with a bad elevation or bad offset, they may have taken a bit of elevation. Use [http://scenemodels.flightgear.org our webforms], if necessary, to fix this.

== Screenshots ==

== Known bugs and limitations ==
# clipping of OSM roads on water showing height glitches (due to bad coast/river lines definitions and bad clipping): clip roads against landmass or add landmass where required? Should roads over bridges get removed, even in places where a 3D bridge model is missing?
# some z-fighting (clipper is generating the correct number of contours, but the airport hole is wound as a boundary, not a hole) and/or triangles on airports (LFRH, EDWJ (partially submerged)...);
# some troubles on very dense cities (such as Paris) leading to grey-white triangles on cities - see also yellow lines @LFPG;
# some line issues on small airfield with LTA specific runways (LFNH, LFLI...) - the small centerlines on the runways are "floating" over the runway (20 cm to 1m), leading to some gear destructions ;-) (they didn't use lines, but surfaces that are defined as transparent and borders defined as the line type. This way you limit the number of "line features"). Probably "hot" = false would solve it. See [http://uppix.net/y1H1NB.png 1] [http://uppix.net/sMdg17.png 2] [http://uppix.net/kAXrdF.png 3] [http://uppix.net/vYuReF.png 4] [http://uppix.net/DQ4NHr.png 5]. Thanks Clément for noticing;
# airport being located over two different tiles sometimes renders bad, leading to z-fighting (LEJR, UKKE...);
# on sharp cliffs, water sometimes climb over the cliffs (see e000n40/e000n49/2958056 and [http://img809.imageshack.us/img809/2082/9n96.jpg this picture] for instance). Thanks clm76 for reporting;
# terrain and ocean z-fighting such as [http://mapserver.flightgear.org/map/?lon=12.73312&lat=55.60834&zoom=15 east of EKCH]. See tile 3155042 and EDWJ;
# clipping between river and terrain is somewhat strange, making the river "climb" over the terrain, noticeably under bridges - probably due to the presence of the roads. See [http://img809.imageshack.us/img809/2082/9n96.jpg this example];
# the Moss Landing airport (on the coast a little bit south of KSFO) is partly submerged into the water and the airport's north end is elevated above the terrain around it. There is an area on the coast just to the north of the Moss Landing airport that is above sea level if you are up above 1000ft but is covered in water is you are on the deck. When flying over this you can see trees sticking up out of the water so the code that is placing random trees thinks this is above sea level. The old scenery didn't have either of these problems. Also if you fly over this at just the right altitude you can see this area switching back and forth between being water and land (thanks hvengel);
# on many airports where the taxiway signs are now taken from the apt.dat and put in the Terrain folder, the old signs still remain in the Object folder. See EDDF, ELLX;
# on ELLX there are some problems with "holes" in the pavement that flicker between grass and tarmac. I saw this (if I remember correctly) with an older development version of terragear, but this was fixed some time ago.
# on EHAM some vertice seems to be inverted [http://uppix.net/AVUaZt.jpg see this picture]
# at LFLI the taxiway is not correctly drawn
# the taxiway signs are not rendered correctly with transition shader set to its maximum in ALS. Quoting ThorstenB, "It occurs because you're using the terrain shader effect on something that isn't part of the terrain but in reality an artificial object placed onto the terrain. The terrain shader effect concludes correctly that a natural vertical surface cannot be anything but rock, so it replaces the default texture with the default steep gradient texture - which is rock. In my view, the proper solution would be to *not* render signs as part of the terrain but to let a different effect handle them (model-default.eff should do the trick for instance, but one could also run a lower quality terrain shader). If that is not acceptable a workaround is to declare the gradient texture for the signs as void.png as described in http://wiki.flightgear.org/Procedural_Texturing#The_gradient_texture which continues to use the terrain-specific effect but instructs the shader not to use a separate texture for steep gradients."
# sometimes some strange water width transitions, like [http://i217.photobucket.com/albums/cc283/oliunterderbruecke/flightgear/TG%20bugs/fgfs2013-11-0822-18-06-03_zpsf3527850.jpg for the Rhein] - reported by ot-666
# triangle winding appears inconsistent - especially when a vertex is shared by 4+ edges. Issue can be visualized here: [https://dl.dropboxusercontent.com/u/29968727/fgfs-screen-116.png messed up binormals and tangents] This may be the root cause of the urban shader issue - reported by i4dnf. Issue understood - Winding is not the issue, duplicate nodes per triangle (zero area triangles) are possible when converting the CGAL exact triangle back to nodes using double floats.
# In a few airports (LEVT, LEGE are two examples), taxiways are defined in using a stack of layers: the bottom layer for the asphalt surface and the upper layer (defined as transparent) is only used to define the lines. Current tools do not support stacks of layers and the upper layer is "transparent" all the way down to the ground. See [http://i.imgur.com/AkOd5Zo.png 1] and [http://forum.flightgear.org/viewtopic.php?f=5&t=21294&p=201132#p201126 2] This is easily fixable in the data by changing transparent layers to asphalt, but it involves a manual intervention in each airport and sending the data back to Robin. And actually, there is not anything wrong with the original the data. Other airports such as LFLR do take advantage of transparent taxiways.

Fixed:
* [FIXED] near EHAM there is a pylon under terrain [http://uppix.net/7rFkTR.jpg see this picture]
* [FIXED] # glacier landcover is missing, leading to some holes in high moutains, as seen in Switzerland (SW [http://mapserver.flightgear.org/map/?lon=8.12304&lat=46.07741&zoom=9&layers=B00000000000FTFFTFFTFFFFFFFF LSMM]), Austria ([http://mapserver.flightgear.org/map/?lon=11.3527&lat=47.25782&zoom=10&layers=B00000000000FTFFTFFTFFFFFFFF south of LOWI]) and Northern Norway (i.e. [http://mapserver.flightgear.org/map/?lon=14.210&lat=65.974&zoom=9&layers=B00000000000FTFFTFFTFFFFFFFF near ENMS]);

== Features enhancement ==
# enhance landcover data for the rest of the world (OSM? vectorize US-American NLCD2006?) and add more custom scenery and fixes;
# complete CORINE coverage, fix overlaps in CLC2000 and merge with CLC2006;
# use latest ViewFinderPanoramas DEM's;
# find a new svn hosting solution;
# compute the next terrain with textures-lines option;
# add some more OSM data (secondary...);
# descent airports priority below roads, so roads and railroads can be shown over airports; have a proper solution for roads running over terrain classified as airfield, maybe extract administrative boundaries from apt.dat;
# retry multi-thread;
# enhance the "random" tree and builds placement to take OSM into account;
# .SPT file support - push Mathias' LOD ideas forward;
# landclass border blurring - Several ideas on this - It would be really nice to be able to do it;
# osm motorway_link (and the other _link) roads should probably have their own width. Perhaps grouped into a separate shapefile, or handled in ogr-decode - single lane is most likely;
# osm line data simplification / preprocessing. - We've done some experimenting, and the results are promising. This should reduce the number of triangles generated. It could create longer continuous roads, which allows better control of the generated texture coordinates - so we could, theoretically, populate the roads with traffic in the future.

== External link ==
* World Scenery 2.0 release announcement on the forum: [http://forum.flightgear.org/viewtopic.php?f=5&t=21226& FlightGear World Scenery 2.0 released]

[[Category:Scenery]]

User:Ludomo

2014-02-10T17:01:18Z

Ludomo: Created page with "{{User |name = Ludomo |location = Spain |interests = General Aviation, free software |callsign = EC-ICE }} == Projects == I'm based in Spain and I find very ups..."

{{User
|name = Ludomo
|location = Spain
|interests = General Aviation, free software
|callsign = EC-ICE
}}

== Projects ==

I'm based in Spain and I find very upsetting to arrive to an empty airport. My goals include:

* populating all the airports I visited, planning to visit or may visit in real life. This includes mainly small, general aviation airports but also a few of regional and international airports in my area. I have already modeled the airports [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 in this map] Many of them are already available using [[TerraSync]], other airports are still in the process to be submitted. Check the project's main page: [[Custom Spain and Portugal Scenery]]

* adding visual reference points to the FlightGear world, specially in my area: castles, big churches, power mills... either directly in [[TerraSync]] or labeling them in [[OpenStreetMap]]

* modeling interesting airports around the world. For example: SKRG, SAWO, SAWB, VQPR. All of them are distributed using [[Terrasync]].

* modeling interesting areas around the world. For example, [http://flightgear.creatuforo.com/viewtopic.php?t=3330 Tierra del Fuego] (Chile and Argentina)

[[Category:Developer Plans]]

Custom Spain and Portugal scenery

2014-01-25T20:05:41Z

Ludomo: /* Download and Installation */

The Spanish community of FlightGear started in 2012 a project to enhance the scenario of the Iberian Peninsula. This included an enhacement of the terrain, that was still low detail at the moment the project started, new layouts for many airports and hundred of objects spread on all the geography.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/viewtopic.php?t=3347 Vive FG!]

= Download and Installation =

The "update package" can be found at: [https://mega.co.nz/#!UMBizJJR!DlWiSwUWA0z2xaYm1AWjNwN9rzmGDSd8i7rWRJbjmqo Iberian Peninsula] This is an enhancement of the current scenery in [[TerraSync]] and must be used in addition to [[TerraSync]]. See the next section for a list of changes.

Download the and uncompress the file in a local directory. For example, under Windows, ''My Documents\Games\IBE''. Then, add this directory to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

If you download the file after an update, first remove the existing directory and then install again.

= Improvements over the standard scenery =

The goals of the Iberian scenery were:

* Terrain compiled using the last data available from OpenStreetMap and CORINE. This terrain is no longer necessary from the introduction of the scenery 2.0 in [[TerraSync]].
* Improvements on the layouts of many airports (LEBL, LEMG...), including many new airports (LESL, LECI...)
* Models of lots of buildings, including main airports and some cities: Madrid, Barcelona and many more.
* Parking points for many the airports. Currently, about 80% of the airports have parking points.
* Scenery especially suitable for VFR flights: notification points, cities...

Currently, the terrain files are no longer necessary but many improvements are not yet in [[TerraSync]]: airports that depend heavily on the elevation (for example, LEPO), or airports not yet sent to the X-Plane community (for example, LEMG or LEST), as well as hundred of buildings everywhere we are still uploading to [[TerraSync]] and even some non-free buildings.

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 license [http://creativecommons.org/licenses/by-sa/3.0/], and under the terms of the GPL License. Use the license more suitable for your needs.

== Improved and new airports ==

As a result of the project, dozens of airports have been modeled. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the airports developed in the project. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The improved layout for most of these airports are already included in [[TerraSync]], and we are still uploading the remaining airports and their buildings.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

= Pre 2.0 scenery =

Prior to the release of the 2.0 scenery in [[TerraSync]], we maintained a custom scenery for the continental territories of Spain, Portugal, Andorra and Gibraltar. The project used the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti. The scenery files divided the Iberian Peninsula in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

These files are no longer available, since the current scenario in [[TerraSync]] provides a level of detail similar to these old files. More information about these old files can be found at [http://flightgear.creatuforo.com/viewtopic.php?t=3143 Vive FG!]

[[Category:Scenery]]

Building FlightGear - Debian

2013-12-26T09:50:32Z

Ludomo: /* Requirements and Preparations */

HowTo build [[FlightGear]] [[Changelog_2.12|2.12]] or bleeding edge development version, hereinafter simply called [[GIT]], on GNU/Linux [http://www.debian.org/ Debian] Oldstable/Squeeze. Users of Stable/Wheezy, Testing or Unstable at least have to change package names (version numbering) accordingly.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands may cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install automake cmake g++ gcc git make sed subversion"
: Additionally install "fluid" if you intend to use [[FlightGear_Admin_Wizard|fgadmin]].

; Dependencies
Command for Squeeze, users of other releases are advised to check package versions:
su -c "apt-get install \
freeglut3-dev libboost-dev libcurl4-openssl-dev libgtkglext1-dev \
libjpeg62-dev libopenal-dev librsvg2-dev libsvn-dev \
libxml2-dev libxrandr-dev"
: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
: If "libjpeg62-dev" breaks package dependencies, just install one of the other versions' -dev.
: Add "libudev-dev" if you need FG's feature <code>-D EVENT_INPUT=ON</code>.
: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely here these might be "libplib-dev", "libfltk1.1-dev", "libopenscenegraph-dev" and "simgear-dev".


; Versions

Finally, you have to chose which version of FlightGear you are building. This article uses two version names:

* '''GIT''': it is the name of the last development version. It is dynamic and it changes several times every week. The development version may content new features and a few bugs.
* '''2.12''': is the name of the current stable release. This version is frozen in time and it won't change.

A "git clone" command will download all versions of the source code. After that, you use "git checkout" to select a specific version. The commands to select a version will be listed in the next sections. For further information about the available branches and tags, check the [[Git]] article.

== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-2.12</code> or <code>$HOME/FG-2.12</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make -j2 install</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a placeholder for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-2.12 && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT more than 7 GB and growing / 2.12 960 MB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 
To have a build with debugging symbols add <code>-D CMAKE_BUILD_TYPE="RelWithDebInfo"</code> to SimGear's and FlightGear's cmake options.

=== libfltk ===
[http://www.fltk.org/ FLTK] is required for [[fgadmin]], which is content with libfltk-1.1, and fgrun, which minimum is libfltk-1.3.

Wheezy: Just install package "libfltk1.3-dev" if you're planning to use either of them. 
Squeeze: For fgadmin just install package "libfltk1.1-dev". To compile fgrun, too, build and install FLTK-1.3 instead:

<nowiki>cd $FG_SRC_DIR
wget http://ftp.easysw.com/pub/fltk/1.3.2/fltk-1.3.2-source.tar.gz
tar xzf fltk-1.3.2-source.tar.gz
cd fltk-1.3.2
./configure --enable-shared --prefix=$FG_INSTALL_DIR
make -j2 install</nowiki>

[[Fgadmin]] is an optional tool in FlightGear to manually download scenery in case you can't use [[terrasync]], the preferred scenery management tool. Fgadmin will be automatically built if libfltk is found. To force not to build fgadmin even if libfltk is in your system, add "-DENABLE_FGADMIN=OFF" to the cmake command while building flightgear (see below)

=== [[plib]] ===
2.12 and GIT:
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html required].
cd $FG_SRC_DIR
svn co https://svn.code.sf.net/p/plib/code/trunk plib.svn
cd plib
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR
make -j2 install

=== [[OpenSceneGraph]] ===
On Wheezy skip that step and install package "libopenscenegraph-dev" instead. 
Last version known to work for 2.12 is OpenSceneGraph 3.1.4. 

2.12 and GIT:
cd $FG_SRC_DIR
svn co http://svn.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-3.1.4 OpenSceneGraph-3.1.4.svn
mkdir build-osg; cd build-osg
cmake -D CMAKE_BUILD_TYPE="Release" -DLIB_POSTFIX="" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/OpenSceneGraph-3.1.4.svn
make -j2 install

=== [[SimGear]] ===
2.12 and GIT:
cd $FG_SRC_DIR
git clone git://mapserver.flightgear.org/simgear simgear.git

2.12 only:
cd simgear.git
git checkout -b 2.12 origin/release/2.12.0

2.12 and GIT:
mkdir $FG_SRC_DIR/build-sg; cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j2 install

=== FlightGear source ===
2.12 and GIT:
cd $FG_SRC_DIR
git clone git://mapserver.flightgear.org/flightgear flightgear.git

2.12 only:
cd flightgear.git
git checkout -b 2.12 origin/release/2.12.0

2.12 and GIT:
mkdir $FG_SRC_DIR/build-fg; cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j2 install

=== FlightGear data ===
2.12 only: Please have a look at the [http://www.flightgear.org/download/mirror/ mirror list] for a server close to your location.
cd $FG_INSTALL_DIR
wget http://www.flightgear.wo0t.de/Shared/FlightGear-data-2.12.0.tar.bz
tar xjf FlightGear-data-2.12.0.tar.bz

GIT only:
For slow/unstable internet connections it is recommended to download the [[FlightGear_Git:_data_developers#Bundle|fgdata.bundle]] instead of cloning the data. 
cd $FG_INSTALL_DIR
git clone git://mapserver.flightgear.org/fgdata fgdata

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --fg-root=$FG_INSTALL_DIR/fgdata
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

For the future, if you want to start FlightGear from command line have a look at [[fgfsrc]], if you prefer a graphical user interface continue with [[#fgrun|compiling fgrun]] or check out another [http://wiki.flightgear.org/Category:FlightGear_front_ends launcher].

== Optional Software ==
[[File:Zeichen_101_icon.png|21px]] Some of the below instructions possibly are not up to date. Please feel free to revise them.

Feel free to add the commands to install other FlightGear related projects.

=== [[Atlas]] ===
One more Package has to be installed: "libglew1.5-dev"
cd $FG_SRC_DIR
git clone http://mapserver.flightgear.org/git/atlas
cd atlas
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR --with-fgbase=$FG_INSTALL_DIR/data
make -j2 install
cp -R $FG_SRC_DIR/atlas/src/data/* $FG_INSTALL_DIR/data/Atlas


$FG_INSTALL_DIR/bin/Atlas

=== fgcom ===
For [[fgcom]] install package "libasound2-dev".
cd $FG_SRC_DIR
git clone http://mapserver.flightgear.org/git/fgcom fgcom.git

cd fgcom.git
git checkout -b next origin/next
mkdir $FG_SRC_DIR/build-fgcom; cd $FG_SRC_DIR/build-fgcom
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/fgcom.git
make -j2 install
Create an .alsoftrc file as shown in [[FGCOM_Testing#Special_for_Linux_.28.alsoftrc.29|FGCOM Testing]].

=== fgrun ===
To build [[fgrun]] libfltk1.3 is required, see [[#libfltk|libfltk above]]. 
2.12 and GIT:
cd $FG_SRC_DIR
git clone git://gitorious.org/fg/fgrun.git fgrun.git

2.12 only:
cd fgrun.git
git checkout -b 2.12 origin/release/2.12

2.12 and GIT:
mkdir $FG_SRC_DIR/build-fgrun; cd $FG_SRC_DIR/build-fgrun
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/fgrun.git
make -j2 install

Execute it:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgrun

=== TaxiDraw ===
[[File:Zeichen_101_icon.png|21px]] Obsolete for airport creation, use [[WorldEditor]] instead. It is still useful for working on [[Interactive_traffic#Ground_networks|ground networks]]. 
To compile [[Taxidraw|TaxiDraw]] we need to install some more packages:
* either "libcurl4-gnutls-dev" or "libcurl4-openssl-dev" for curl.h
* "wx2.8-headers" (at least, maybe even more than just that one. Please [http://wiki.flightgear.org/index.php?title=Talk:Building_FlightGear_-_Debian&action=edit&redlink=1 report]!
su -c "aptitude install [libcurl4-gnutls-dev|libcurl4-openssl-dev]"
cd $FG_SRC_DIR
git clone git://mapserver.flightgear.org/taxidraw
cd taxidraw
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR
make -j2 install

=== [[TerraGear]] ===
==== Automatic Installation ====
[[BuildingTerraGear_in_Ubuntu_910_(32-_or_64-bit)#Automatic Installation|link]]
If you are familiar with "download_and_compile.sh" script from Brisa you can donwload this script: http://clemaez.dyndns.org/download_and_compile_tg.sh
This script is similar to Brisa's one (only usable for Debian/Mint/Ubuntu). This script installs TerraGear (latest version) and terragear-gui.

; ''How to use it?''
sh terragear_download_and_compile.sh -j 2 ALL

; ''Need some help?''
Look at forum topics: http://forum.flightgear.org/viewtopic.php?f=20&t=14849

After success installation you can exectute this command line in the terragear/bin directory in order to display every --help for each binary files:
cd terragear/bin && for i in `ls`; do echo ""; echo "################# "$i" ##############"; ./$i --help; done

==== Basic Installation ====
To resolve some of the dependencies of TerraGear the GIT sections of steps [[#plib|plib]], [[#OpenSceneGraph|OpenSceneGraph]] and [[#SimGear|SimGear]] have to be done first. Additionally some packages and their dependencies have to be installed:
su -c "apt-get install \
libgdal-dev libtiff4-dev libboost-signals-dev libboost-system-dev libboost-thread-dev"

Squeeze users have to compile the CGAL dependency.
On Wheezy just install package "libcgal-dev" instead.
cd $FG_SRC_DIR
wget https://gforge.inria.fr/frs/download.php/31174/CGAL-4.0.2.tar.bz2
tar xjf CGAL-4.0.2.tar.bz2
mkdir $FG_SRC_DIR/build-cgal; cd $FG_SRC_DIR/build-cgal
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/CGAL-4.0.2
make -j2 install


Compile TerraGear:
cd $FG_SRC_DIR
git clone git://git.gitorious.org/fg/terragear.git
mkdir $FG_SRC_DIR/build-tg; cd $FG_SRC_DIR/build-tg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/terragear
make -j2 install

=== WorldEditor (WED) ===
Because this is the same for all Linux distributions the instructions are not listed here separately. Please refer to our [[WorldEditor#Linux|lead WED article]].

{{Building}}

[[de:FlightGear bauen - Debian]]

Building FlightGear - Debian

2013-12-26T09:48:03Z

Ludomo: /* Requirements and Preparations */

HowTo build [[FlightGear]] [[Changelog_2.12|2.12]] or bleeding edge development version, hereinafter simply called [[GIT]], on GNU/Linux [http://www.debian.org/ Debian] Oldstable/Squeeze. Users of Stable/Wheezy, Testing or Unstable at least have to change package names (version numbering) accordingly.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands may cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install automake cmake g++ gcc git make sed subversion"
: Additionally install "fluid" if you intend to use [[FlightGear_Admin_Wizard|fgadmin]].

; Dependencies
Command for Squeeze, users of other releases are advised to check package versions:
su -c "apt-get install \
freeglut3-dev libboost-dev libcurl4-openssl-dev libgtkglext1-dev \
libjpeg62-dev libopenal-dev librsvg2-dev libsvn-dev \
libxml2-dev libxrandr-dev"
: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
: If "libjpeg62-dev" breaks package dependencies, just install one of the other versions' -dev.
: Add "libudev-dev" if you need FG's feature <code>-D EVENT_INPUT=ON</code>.
: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely here these might be "libplib-dev", "libfltk1.1-dev", "libopenscenegraph-dev" and "simgear-dev".


; Versions

Finally, you have to chose which version of FlightGear your are building. This article uses two version names:

* '''GIT''': it is the name of the last development version. It is dynamic and it changes several times every week. The development version may content new features and a few bugs.
* '''2.12''': is the name of the current stable release. This version is frozen in time and it won't change.

A "git clone" command will download all versions of the source code. After that, you use "git checkout" to select a specific version. The commands to select a version will be listed in the next sections. For further information about the available branches and tags, check the [[Git]] article.

== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-2.12</code> or <code>$HOME/FG-2.12</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make -j2 install</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a placeholder for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-2.12 && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT more than 7 GB and growing / 2.12 960 MB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 
To have a build with debugging symbols add <code>-D CMAKE_BUILD_TYPE="RelWithDebInfo"</code> to SimGear's and FlightGear's cmake options.

=== libfltk ===
[http://www.fltk.org/ FLTK] is required for [[fgadmin]], which is content with libfltk-1.1, and fgrun, which minimum is libfltk-1.3.

Wheezy: Just install package "libfltk1.3-dev" if you're planning to use either of them. 
Squeeze: For fgadmin just install package "libfltk1.1-dev". To compile fgrun, too, build and install FLTK-1.3 instead:

<nowiki>cd $FG_SRC_DIR
wget http://ftp.easysw.com/pub/fltk/1.3.2/fltk-1.3.2-source.tar.gz
tar xzf fltk-1.3.2-source.tar.gz
cd fltk-1.3.2
./configure --enable-shared --prefix=$FG_INSTALL_DIR
make -j2 install</nowiki>

[[Fgadmin]] is an optional tool in FlightGear to manually download scenery in case you can't use [[terrasync]], the preferred scenery management tool. Fgadmin will be automatically built if libfltk is found. To force not to build fgadmin even if libfltk is in your system, add "-DENABLE_FGADMIN=OFF" to the cmake command while building flightgear (see below)

=== [[plib]] ===
2.12 and GIT:
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html required].
cd $FG_SRC_DIR
svn co https://svn.code.sf.net/p/plib/code/trunk plib.svn
cd plib
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR
make -j2 install

=== [[OpenSceneGraph]] ===
On Wheezy skip that step and install package "libopenscenegraph-dev" instead. 
Last version known to work for 2.12 is OpenSceneGraph 3.1.4. 

2.12 and GIT:
cd $FG_SRC_DIR
svn co http://svn.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-3.1.4 OpenSceneGraph-3.1.4.svn
mkdir build-osg; cd build-osg
cmake -D CMAKE_BUILD_TYPE="Release" -DLIB_POSTFIX="" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/OpenSceneGraph-3.1.4.svn
make -j2 install

=== [[SimGear]] ===
2.12 and GIT:
cd $FG_SRC_DIR
git clone git://mapserver.flightgear.org/simgear simgear.git

2.12 only:
cd simgear.git
git checkout -b 2.12 origin/release/2.12.0

2.12 and GIT:
mkdir $FG_SRC_DIR/build-sg; cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j2 install

=== FlightGear source ===
2.12 and GIT:
cd $FG_SRC_DIR
git clone git://mapserver.flightgear.org/flightgear flightgear.git

2.12 only:
cd flightgear.git
git checkout -b 2.12 origin/release/2.12.0

2.12 and GIT:
mkdir $FG_SRC_DIR/build-fg; cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j2 install

=== FlightGear data ===
2.12 only: Please have a look at the [http://www.flightgear.org/download/mirror/ mirror list] for a server close to your location.
cd $FG_INSTALL_DIR
wget http://www.flightgear.wo0t.de/Shared/FlightGear-data-2.12.0.tar.bz
tar xjf FlightGear-data-2.12.0.tar.bz

GIT only:
For slow/unstable internet connections it is recommended to download the [[FlightGear_Git:_data_developers#Bundle|fgdata.bundle]] instead of cloning the data. 
cd $FG_INSTALL_DIR
git clone git://mapserver.flightgear.org/fgdata fgdata

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --fg-root=$FG_INSTALL_DIR/fgdata
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

For the future, if you want to start FlightGear from command line have a look at [[fgfsrc]], if you prefer a graphical user interface continue with [[#fgrun|compiling fgrun]] or check out another [http://wiki.flightgear.org/Category:FlightGear_front_ends launcher].

== Optional Software ==
[[File:Zeichen_101_icon.png|21px]] Some of the below instructions possibly are not up to date. Please feel free to revise them.

Feel free to add the commands to install other FlightGear related projects.

=== [[Atlas]] ===
One more Package has to be installed: "libglew1.5-dev"
cd $FG_SRC_DIR
git clone http://mapserver.flightgear.org/git/atlas
cd atlas
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR --with-fgbase=$FG_INSTALL_DIR/data
make -j2 install
cp -R $FG_SRC_DIR/atlas/src/data/* $FG_INSTALL_DIR/data/Atlas


$FG_INSTALL_DIR/bin/Atlas

=== fgcom ===
For [[fgcom]] install package "libasound2-dev".
cd $FG_SRC_DIR
git clone http://mapserver.flightgear.org/git/fgcom fgcom.git

cd fgcom.git
git checkout -b next origin/next
mkdir $FG_SRC_DIR/build-fgcom; cd $FG_SRC_DIR/build-fgcom
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/fgcom.git
make -j2 install
Create an .alsoftrc file as shown in [[FGCOM_Testing#Special_for_Linux_.28.alsoftrc.29|FGCOM Testing]].

=== fgrun ===
To build [[fgrun]] libfltk1.3 is required, see [[#libfltk|libfltk above]]. 
2.12 and GIT:
cd $FG_SRC_DIR
git clone git://gitorious.org/fg/fgrun.git fgrun.git

2.12 only:
cd fgrun.git
git checkout -b 2.12 origin/release/2.12

2.12 and GIT:
mkdir $FG_SRC_DIR/build-fgrun; cd $FG_SRC_DIR/build-fgrun
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/fgrun.git
make -j2 install

Execute it:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgrun

=== TaxiDraw ===
[[File:Zeichen_101_icon.png|21px]] Obsolete for airport creation, use [[WorldEditor]] instead. It is still useful for working on [[Interactive_traffic#Ground_networks|ground networks]]. 
To compile [[Taxidraw|TaxiDraw]] we need to install some more packages:
* either "libcurl4-gnutls-dev" or "libcurl4-openssl-dev" for curl.h
* "wx2.8-headers" (at least, maybe even more than just that one. Please [http://wiki.flightgear.org/index.php?title=Talk:Building_FlightGear_-_Debian&action=edit&redlink=1 report]!
su -c "aptitude install [libcurl4-gnutls-dev|libcurl4-openssl-dev]"
cd $FG_SRC_DIR
git clone git://mapserver.flightgear.org/taxidraw
cd taxidraw
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR
make -j2 install

=== [[TerraGear]] ===
==== Automatic Installation ====
[[BuildingTerraGear_in_Ubuntu_910_(32-_or_64-bit)#Automatic Installation|link]]
If you are familiar with "download_and_compile.sh" script from Brisa you can donwload this script: http://clemaez.dyndns.org/download_and_compile_tg.sh
This script is similar to Brisa's one (only usable for Debian/Mint/Ubuntu). This script installs TerraGear (latest version) and terragear-gui.

; ''How to use it?''
sh terragear_download_and_compile.sh -j 2 ALL

; ''Need some help?''
Look at forum topics: http://forum.flightgear.org/viewtopic.php?f=20&t=14849

After success installation you can exectute this command line in the terragear/bin directory in order to display every --help for each binary files:
cd terragear/bin && for i in `ls`; do echo ""; echo "################# "$i" ##############"; ./$i --help; done

==== Basic Installation ====
To resolve some of the dependencies of TerraGear the GIT sections of steps [[#plib|plib]], [[#OpenSceneGraph|OpenSceneGraph]] and [[#SimGear|SimGear]] have to be done first. Additionally some packages and their dependencies have to be installed:
su -c "apt-get install \
libgdal-dev libtiff4-dev libboost-signals-dev libboost-system-dev libboost-thread-dev"

Squeeze users have to compile the CGAL dependency.
On Wheezy just install package "libcgal-dev" instead.
cd $FG_SRC_DIR
wget https://gforge.inria.fr/frs/download.php/31174/CGAL-4.0.2.tar.bz2
tar xjf CGAL-4.0.2.tar.bz2
mkdir $FG_SRC_DIR/build-cgal; cd $FG_SRC_DIR/build-cgal
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/CGAL-4.0.2
make -j2 install


Compile TerraGear:
cd $FG_SRC_DIR
git clone git://git.gitorious.org/fg/terragear.git
mkdir $FG_SRC_DIR/build-tg; cd $FG_SRC_DIR/build-tg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/terragear
make -j2 install

=== WorldEditor (WED) ===
Because this is the same for all Linux distributions the instructions are not listed here separately. Please refer to our [[WorldEditor#Linux|lead WED article]].

{{Building}}

[[de:FlightGear bauen - Debian]]

Building FlightGear - Debian

2013-12-26T09:46:30Z

Ludomo: /* Requirements and Preparations */

HowTo build [[FlightGear]] [[Changelog_2.12|2.12]] or bleeding edge development version, hereinafter simply called [[GIT]], on GNU/Linux [http://www.debian.org/ Debian] Oldstable/Squeeze. Users of Stable/Wheezy, Testing or Unstable at least have to change package names (version numbering) accordingly.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands may cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install automake cmake g++ gcc git make sed subversion"
: Additionally install "fluid" if you intend to use [[FlightGear_Admin_Wizard|fgadmin]].

; Dependencies
Command for Squeeze, users of other releases are advised to check package versions:
su -c "apt-get install \
freeglut3-dev libboost-dev libcurl4-openssl-dev libgtkglext1-dev \
libjpeg62-dev libopenal-dev librsvg2-dev libsvn-dev \
libxml2-dev libxrandr-dev"
: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
: If "libjpeg62-dev" breaks package dependencies, just install one of the other versions' -dev.
: Add "libudev-dev" if you need FG's feature <code>-D EVENT_INPUT=ON</code>.
: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely here these might be "libplib-dev", "libfltk1.1-dev", "libopenscenegraph-dev" and "simgear-dev".


; Versions

Finally, you have to chose which version of FlightGear your are building. This article uses two version names:

* '''GIT''': it is the name of the last development version. It is dynamic and it changes several times every week. The development version may content new features and a few bugs.
* '''2.12''': is the name of the current stable release. This version is frozen in time and it won't change.

A "git clone" command will download all versions of the source code. After that, you use "git checkout" to select a specific version. The commands to select a version will be listed in the next sections.

== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-2.12</code> or <code>$HOME/FG-2.12</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make -j2 install</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a placeholder for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-2.12 && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT more than 7 GB and growing / 2.12 960 MB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 
To have a build with debugging symbols add <code>-D CMAKE_BUILD_TYPE="RelWithDebInfo"</code> to SimGear's and FlightGear's cmake options.

=== libfltk ===
[http://www.fltk.org/ FLTK] is required for [[fgadmin]], which is content with libfltk-1.1, and fgrun, which minimum is libfltk-1.3.

Wheezy: Just install package "libfltk1.3-dev" if you're planning to use either of them. 
Squeeze: For fgadmin just install package "libfltk1.1-dev". To compile fgrun, too, build and install FLTK-1.3 instead:

<nowiki>cd $FG_SRC_DIR
wget http://ftp.easysw.com/pub/fltk/1.3.2/fltk-1.3.2-source.tar.gz
tar xzf fltk-1.3.2-source.tar.gz
cd fltk-1.3.2
./configure --enable-shared --prefix=$FG_INSTALL_DIR
make -j2 install</nowiki>

[[Fgadmin]] is an optional tool in FlightGear to manually download scenery in case you can't use [[terrasync]], the preferred scenery management tool. Fgadmin will be automatically built if libfltk is found. To force not to build fgadmin even if libfltk is in your system, add "-DENABLE_FGADMIN=OFF" to the cmake command while building flightgear (see below)

=== [[plib]] ===
2.12 and GIT:
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html required].
cd $FG_SRC_DIR
svn co https://svn.code.sf.net/p/plib/code/trunk plib.svn
cd plib
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR
make -j2 install

=== [[OpenSceneGraph]] ===
On Wheezy skip that step and install package "libopenscenegraph-dev" instead. 
Last version known to work for 2.12 is OpenSceneGraph 3.1.4. 

2.12 and GIT:
cd $FG_SRC_DIR
svn co http://svn.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-3.1.4 OpenSceneGraph-3.1.4.svn
mkdir build-osg; cd build-osg
cmake -D CMAKE_BUILD_TYPE="Release" -DLIB_POSTFIX="" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/OpenSceneGraph-3.1.4.svn
make -j2 install

=== [[SimGear]] ===
2.12 and GIT:
cd $FG_SRC_DIR
git clone git://mapserver.flightgear.org/simgear simgear.git

2.12 only:
cd simgear.git
git checkout -b 2.12 origin/release/2.12.0

2.12 and GIT:
mkdir $FG_SRC_DIR/build-sg; cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j2 install

=== FlightGear source ===
2.12 and GIT:
cd $FG_SRC_DIR
git clone git://mapserver.flightgear.org/flightgear flightgear.git

2.12 only:
cd flightgear.git
git checkout -b 2.12 origin/release/2.12.0

2.12 and GIT:
mkdir $FG_SRC_DIR/build-fg; cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j2 install

=== FlightGear data ===
2.12 only: Please have a look at the [http://www.flightgear.org/download/mirror/ mirror list] for a server close to your location.
cd $FG_INSTALL_DIR
wget http://www.flightgear.wo0t.de/Shared/FlightGear-data-2.12.0.tar.bz
tar xjf FlightGear-data-2.12.0.tar.bz

GIT only:
For slow/unstable internet connections it is recommended to download the [[FlightGear_Git:_data_developers#Bundle|fgdata.bundle]] instead of cloning the data. 
cd $FG_INSTALL_DIR
git clone git://mapserver.flightgear.org/fgdata fgdata

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --fg-root=$FG_INSTALL_DIR/fgdata
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

For the future, if you want to start FlightGear from command line have a look at [[fgfsrc]], if you prefer a graphical user interface continue with [[#fgrun|compiling fgrun]] or check out another [http://wiki.flightgear.org/Category:FlightGear_front_ends launcher].

== Optional Software ==
[[File:Zeichen_101_icon.png|21px]] Some of the below instructions possibly are not up to date. Please feel free to revise them.

Feel free to add the commands to install other FlightGear related projects.

=== [[Atlas]] ===
One more Package has to be installed: "libglew1.5-dev"
cd $FG_SRC_DIR
git clone http://mapserver.flightgear.org/git/atlas
cd atlas
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR --with-fgbase=$FG_INSTALL_DIR/data
make -j2 install
cp -R $FG_SRC_DIR/atlas/src/data/* $FG_INSTALL_DIR/data/Atlas


$FG_INSTALL_DIR/bin/Atlas

=== fgcom ===
For [[fgcom]] install package "libasound2-dev".
cd $FG_SRC_DIR
git clone http://mapserver.flightgear.org/git/fgcom fgcom.git

cd fgcom.git
git checkout -b next origin/next
mkdir $FG_SRC_DIR/build-fgcom; cd $FG_SRC_DIR/build-fgcom
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/fgcom.git
make -j2 install
Create an .alsoftrc file as shown in [[FGCOM_Testing#Special_for_Linux_.28.alsoftrc.29|FGCOM Testing]].

=== fgrun ===
To build [[fgrun]] libfltk1.3 is required, see [[#libfltk|libfltk above]]. 
2.12 and GIT:
cd $FG_SRC_DIR
git clone git://gitorious.org/fg/fgrun.git fgrun.git

2.12 only:
cd fgrun.git
git checkout -b 2.12 origin/release/2.12

2.12 and GIT:
mkdir $FG_SRC_DIR/build-fgrun; cd $FG_SRC_DIR/build-fgrun
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/fgrun.git
make -j2 install

Execute it:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgrun

=== TaxiDraw ===
[[File:Zeichen_101_icon.png|21px]] Obsolete for airport creation, use [[WorldEditor]] instead. It is still useful for working on [[Interactive_traffic#Ground_networks|ground networks]]. 
To compile [[Taxidraw|TaxiDraw]] we need to install some more packages:
* either "libcurl4-gnutls-dev" or "libcurl4-openssl-dev" for curl.h
* "wx2.8-headers" (at least, maybe even more than just that one. Please [http://wiki.flightgear.org/index.php?title=Talk:Building_FlightGear_-_Debian&action=edit&redlink=1 report]!
su -c "aptitude install [libcurl4-gnutls-dev|libcurl4-openssl-dev]"
cd $FG_SRC_DIR
git clone git://mapserver.flightgear.org/taxidraw
cd taxidraw
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR
make -j2 install

=== [[TerraGear]] ===
==== Automatic Installation ====
[[BuildingTerraGear_in_Ubuntu_910_(32-_or_64-bit)#Automatic Installation|link]]
If you are familiar with "download_and_compile.sh" script from Brisa you can donwload this script: http://clemaez.dyndns.org/download_and_compile_tg.sh
This script is similar to Brisa's one (only usable for Debian/Mint/Ubuntu). This script installs TerraGear (latest version) and terragear-gui.

; ''How to use it?''
sh terragear_download_and_compile.sh -j 2 ALL

; ''Need some help?''
Look at forum topics: http://forum.flightgear.org/viewtopic.php?f=20&t=14849

After success installation you can exectute this command line in the terragear/bin directory in order to display every --help for each binary files:
cd terragear/bin && for i in `ls`; do echo ""; echo "################# "$i" ##############"; ./$i --help; done

==== Basic Installation ====
To resolve some of the dependencies of TerraGear the GIT sections of steps [[#plib|plib]], [[#OpenSceneGraph|OpenSceneGraph]] and [[#SimGear|SimGear]] have to be done first. Additionally some packages and their dependencies have to be installed:
su -c "apt-get install \
libgdal-dev libtiff4-dev libboost-signals-dev libboost-system-dev libboost-thread-dev"

Squeeze users have to compile the CGAL dependency.
On Wheezy just install package "libcgal-dev" instead.
cd $FG_SRC_DIR
wget https://gforge.inria.fr/frs/download.php/31174/CGAL-4.0.2.tar.bz2
tar xjf CGAL-4.0.2.tar.bz2
mkdir $FG_SRC_DIR/build-cgal; cd $FG_SRC_DIR/build-cgal
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/CGAL-4.0.2
make -j2 install


Compile TerraGear:
cd $FG_SRC_DIR
git clone git://git.gitorious.org/fg/terragear.git
mkdir $FG_SRC_DIR/build-tg; cd $FG_SRC_DIR/build-tg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/terragear
make -j2 install

=== WorldEditor (WED) ===
Because this is the same for all Linux distributions the instructions are not listed here separately. Please refer to our [[WorldEditor#Linux|lead WED article]].

{{Building}}

[[de:FlightGear bauen - Debian]]

Building FlightGear - Debian

2013-12-26T09:26:33Z

Ludomo: /* libfltk */

HowTo build [[FlightGear]] [[Changelog_2.12|2.12]] or bleeding edge development version, hereinafter simply called [[GIT]], on GNU/Linux [http://www.debian.org/ Debian] Oldstable/Squeeze. Users of Stable/Wheezy, Testing or Unstable at least have to change package names (version numbering) accordingly.

The meaning of this article is to be a short, '''checklist''' like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

If you don't want to get your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].

[[File:Zeichen_144_icon.png|21px]] For beginners with compiling it is highly recommended to follow this guide step by step. Any modification to most of the here used commands may cause trouble.

== Requirements and Preparations ==
A bunch of packages (as well as some of their dependencies) are required to compile FlightGear:

; Tools
su -c "apt-get install automake cmake g++ gcc git make sed subversion"
: Additionally install "fluid" if you intend to use [[FlightGear_Admin_Wizard|fgadmin]].

; Dependencies
Command for Squeeze, users of other releases are advised to check package versions:
su -c "apt-get install \
freeglut3-dev libboost-dev libcurl4-openssl-dev libgtkglext1-dev \
libjpeg62-dev libopenal-dev librsvg2-dev libsvn-dev \
libxml2-dev libxrandr-dev"
: If you prefer you might replace "libcurl4-openssl-dev" by "libcurl4-gnutls-dev".
: If "libjpeg62-dev" breaks package dependencies, just install one of the other versions' -dev.
: Add "libudev-dev" if you need FG's feature <code>-D EVENT_INPUT=ON</code>.
: [[File:Zeichen_144_icon.png|21px]] During installation development packages of libraries which are going to be compiled ''must not'' be installed. They can safely be re-installed after compilation. Namely here these might be "libplib-dev", "libfltk1.1-dev", "libopenscenegraph-dev" and "simgear-dev".


== Build and install ==
Because we are going to install versions different to the ones in the Debian repositories, it is recommended to install FlightGear in a place independent of the base system, such as <code>/usr/local/FG-2.12</code> or <code>$HOME/FG-2.12</code>. This way also has the advantage of easily managing several FlightGear versions, even with different versions of OpenSceneGraph and/or plib, simply by altering the installation prefix. I suggest to make this directory writeable by the user so there is no need to become root for the <code>make -j2 install</code> commands. We'll use <code>$FG_INSTALL_DIR</code> as a placeholder for this directory. 
Another placeholder will be <code>$FG_SRC_DIR</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the instructions below, you have to replace these with the local paths or even <code>export</code> them (in every terminal you're using them) for the process:
export FG_INSTALL_DIR=$HOME/FG-2.12 && mkdir $FG_INSTALL_DIR
export FG_SRC_DIR=$HOME/src && mkdir $FG_SRC_DIR

Have in mind that the data is a relatively large download (GIT more than 7 GB and growing / 2.12 960 MB). So, to save some time, it is a good idea to [[#FlightGear data|fetch]] it while building the sources. 
For some basic info on git commands for FlightGear users we have a [[Git_for_Laymen#How_do_I_use_the_git_repository_to_update_Flightgear_stuff.3F|git for laymen]] section. 
To have a build with debugging symbols add <code>-D CMAKE_BUILD_TYPE="RelWithDebInfo"</code> to SimGear's and FlightGear's cmake options.

=== libfltk ===
[http://www.fltk.org/ FLTK] is required for [[fgadmin]], which is content with libfltk-1.1, and fgrun, which minimum is libfltk-1.3.

Wheezy: Just install package "libfltk1.3-dev" if you're planning to use either of them. 
Squeeze: For fgadmin just install package "libfltk1.1-dev". To compile fgrun, too, build and install FLTK-1.3 instead:

<nowiki>cd $FG_SRC_DIR
wget http://ftp.easysw.com/pub/fltk/1.3.2/fltk-1.3.2-source.tar.gz
tar xzf fltk-1.3.2-source.tar.gz
cd fltk-1.3.2
./configure --enable-shared --prefix=$FG_INSTALL_DIR
make -j2 install</nowiki>

[[Fgadmin]] is an optional tool in FlightGear to manually download scenery in case you can't use [[terrasync]], the preferred scenery management tool. Fgadmin will be automatically built if libfltk is found. To force not to build fgadmin even if libfltk is in your system, add "-DENABLE_FGADMIN=OFF" to the cmake command while building flightgear (see below)

=== [[plib]] ===
2.12 and GIT:
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html required].
cd $FG_SRC_DIR
svn co https://svn.code.sf.net/p/plib/code/trunk plib.svn
cd plib
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR
make -j2 install

=== [[OpenSceneGraph]] ===
On Wheezy skip that step and install package "libopenscenegraph-dev" instead. 
Last version known to work for 2.12 is OpenSceneGraph 3.1.4. 

2.12 and GIT:
cd $FG_SRC_DIR
svn co http://svn.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-3.1.4 OpenSceneGraph-3.1.4.svn
mkdir build-osg; cd build-osg
cmake -D CMAKE_BUILD_TYPE="Release" -DLIB_POSTFIX="" \
-D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/OpenSceneGraph-3.1.4.svn
make -j2 install

=== [[SimGear]] ===
2.12 and GIT:
cd $FG_SRC_DIR
git clone git://mapserver.flightgear.org/simgear simgear.git

2.12 only:
cd simgear.git
git checkout -b 2.12 origin/release/2.12.0

2.12 and GIT:
mkdir $FG_SRC_DIR/build-sg; cd $FG_SRC_DIR/build-sg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/simgear.git
make -j2 install

=== FlightGear source ===
2.12 and GIT:
cd $FG_SRC_DIR
git clone git://mapserver.flightgear.org/flightgear flightgear.git

2.12 only:
cd flightgear.git
git checkout -b 2.12 origin/release/2.12.0

2.12 and GIT:
mkdir $FG_SRC_DIR/build-fg; cd $FG_SRC_DIR/build-fg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/flightgear.git
make -j2 install

=== FlightGear data ===
2.12 only: Please have a look at the [http://www.flightgear.org/download/mirror/ mirror list] for a server close to your location.
cd $FG_INSTALL_DIR
wget http://www.flightgear.wo0t.de/Shared/FlightGear-data-2.12.0.tar.bz
tar xjf FlightGear-data-2.12.0.tar.bz

GIT only:
For slow/unstable internet connections it is recommended to download the [[FlightGear_Git:_data_developers#Bundle|fgdata.bundle]] instead of cloning the data. 
cd $FG_INSTALL_DIR
git clone git://mapserver.flightgear.org/fgdata fgdata

== Trial run and finishing process ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgfs --fg-root=$FG_INSTALL_DIR/fgdata
: The <code>fgfs</code> binary needs to find our self compiled libraries at runtime and therefore we have to tell the linker (ld) where to find them. That is what the first line here does. You might want to add this line to your <code>$HOME/.bashrc</code> to have this as a persistent setting (may cause problems, if one has installed more than one version of FlightGear!).
: Have in mind, the <code>$FG_INSTALL_DIR</code> and <code>$FG_SRC_DIR</code> variables are available for this session only. For future use of these lines, replace them by the real paths.

To avoid the need to give the path to the <code>fgfs</code> command each time, you might consider to create a symlink at a place that is listed in $PATH:
ln -s $FG_INSTALL_DIR/bin/fgfs $HOME/bin/fgfs

For the future, if you want to start FlightGear from command line have a look at [[fgfsrc]], if you prefer a graphical user interface continue with [[#fgrun|compiling fgrun]] or check out another [http://wiki.flightgear.org/Category:FlightGear_front_ends launcher].

== Optional Software ==
[[File:Zeichen_101_icon.png|21px]] Some of the below instructions possibly are not up to date. Please feel free to revise them.

Feel free to add the commands to install other FlightGear related projects.

=== [[Atlas]] ===
One more Package has to be installed: "libglew1.5-dev"
cd $FG_SRC_DIR
git clone http://mapserver.flightgear.org/git/atlas
cd atlas
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR --with-fgbase=$FG_INSTALL_DIR/data
make -j2 install
cp -R $FG_SRC_DIR/atlas/src/data/* $FG_INSTALL_DIR/data/Atlas


$FG_INSTALL_DIR/bin/Atlas

=== fgcom ===
For [[fgcom]] install package "libasound2-dev".
cd $FG_SRC_DIR
git clone http://mapserver.flightgear.org/git/fgcom fgcom.git

cd fgcom.git
git checkout -b next origin/next
mkdir $FG_SRC_DIR/build-fgcom; cd $FG_SRC_DIR/build-fgcom
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/fgcom.git
make -j2 install
Create an .alsoftrc file as shown in [[FGCOM_Testing#Special_for_Linux_.28.alsoftrc.29|FGCOM Testing]].

=== fgrun ===
To build [[fgrun]] libfltk1.3 is required, see [[#libfltk|libfltk above]]. 
2.12 and GIT:
cd $FG_SRC_DIR
git clone git://gitorious.org/fg/fgrun.git fgrun.git

2.12 only:
cd fgrun.git
git checkout -b 2.12 origin/release/2.12

2.12 and GIT:
mkdir $FG_SRC_DIR/build-fgrun; cd $FG_SRC_DIR/build-fgrun
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/fgrun.git
make -j2 install

Execute it:
export LD_LIBRARY_PATH=$FG_INSTALL_DIR/lib/:$LD_LIBRARY_PATH
$FG_INSTALL_DIR/bin/fgrun

=== TaxiDraw ===
[[File:Zeichen_101_icon.png|21px]] Obsolete for airport creation, use [[WorldEditor]] instead. It is still useful for working on [[Interactive_traffic#Ground_networks|ground networks]]. 
To compile [[Taxidraw|TaxiDraw]] we need to install some more packages:
* either "libcurl4-gnutls-dev" or "libcurl4-openssl-dev" for curl.h
* "wx2.8-headers" (at least, maybe even more than just that one. Please [http://wiki.flightgear.org/index.php?title=Talk:Building_FlightGear_-_Debian&action=edit&redlink=1 report]!
su -c "aptitude install [libcurl4-gnutls-dev|libcurl4-openssl-dev]"
cd $FG_SRC_DIR
git clone git://mapserver.flightgear.org/taxidraw
cd taxidraw
./autogen.sh
./configure --prefix=$FG_INSTALL_DIR
make -j2 install

=== [[TerraGear]] ===
==== Automatic Installation ====
[[BuildingTerraGear_in_Ubuntu_910_(32-_or_64-bit)#Automatic Installation|link]]
If you are familiar with "download_and_compile.sh" script from Brisa you can donwload this script: http://clemaez.dyndns.org/download_and_compile_tg.sh
This script is similar to Brisa's one (only usable for Debian/Mint/Ubuntu). This script installs TerraGear (latest version) and terragear-gui.

; ''How to use it?''
sh terragear_download_and_compile.sh -j 2 ALL

; ''Need some help?''
Look at forum topics: http://forum.flightgear.org/viewtopic.php?f=20&t=14849

After success installation you can exectute this command line in the terragear/bin directory in order to display every --help for each binary files:
cd terragear/bin && for i in `ls`; do echo ""; echo "################# "$i" ##############"; ./$i --help; done

==== Basic Installation ====
To resolve some of the dependencies of TerraGear the GIT sections of steps [[#plib|plib]], [[#OpenSceneGraph|OpenSceneGraph]] and [[#SimGear|SimGear]] have to be done first. Additionally some packages and their dependencies have to be installed:
su -c "apt-get install \
libgdal-dev libtiff4-dev libboost-signals-dev libboost-system-dev libboost-thread-dev"

Squeeze users have to compile the CGAL dependency.
On Wheezy just install package "libcgal-dev" instead.
cd $FG_SRC_DIR
wget https://gforge.inria.fr/frs/download.php/31174/CGAL-4.0.2.tar.bz2
tar xjf CGAL-4.0.2.tar.bz2
mkdir $FG_SRC_DIR/build-cgal; cd $FG_SRC_DIR/build-cgal
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/CGAL-4.0.2
make -j2 install


Compile TerraGear:
cd $FG_SRC_DIR
git clone git://git.gitorious.org/fg/terragear.git
mkdir $FG_SRC_DIR/build-tg; cd $FG_SRC_DIR/build-tg
cmake -D CMAKE_INSTALL_PREFIX:PATH="$FG_INSTALL_DIR" $FG_SRC_DIR/terragear
make -j2 install

=== WorldEditor (WED) ===
Because this is the same for all Linux distributions the instructions are not listed here separately. Please refer to our [[WorldEditor#Linux|lead WED article]].

{{Building}}

[[de:FlightGear bauen - Debian]]

Custom Spain and Portugal scenery

2013-12-09T17:00:23Z

Ludomo:

The Spanish community of FlightGear started in 2012 a project to enhance the scenario of the Iberian Peninsula. This included an enhacement of the terrain, that was still low detail at the moment the project started, new layouts for many airports and hundred of objects spread on all the geography.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/viewtopic.php?t=3347 Vive FG!]

= Download and Installation =

The "update package" can be found at: [https://mega.co.nz/#!1FgjlLhR!CnEoDTq_JWBrPa7RFk4AwERxxzI_yix4UKZNmyEIpIo|Improved Iberian Peninsula] This is an enhacement of the current scenery in [[TerraSync]], and must be used in addition to [[TerraSync]]. See the next section for a list of changes.

Download the and uncompress the file in a local directory. For example, under Windows, ''My Documents\Games\IBE''. Then, add this directory to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

If you download the file after an update, first remove the existing directory and then install again.

= Improvements over the standard scenery =

The goals of the Iberian scenery were:

* Terrain compiled using the last data available from OpenStreetMap and CORINE. This terrain is no longer necessary from the introduction of the scenery 2.0 in [[TerraSync]].
* Improvements on the layouts of many airports (LEBL, LEMG...), including many new airports (LESL, LECI...)
* Models of lots of buildings, including main airports and some cities: Madrid, Barcelona and many more.
* Parking points for many the airports. Currently, about 80% of the airports have parking points.
* Scenery especially suitable for VFR flights: notification points, cities...

Currently, the terrain files are no longer necessary but many improvements are not yet in [[TerraSync]]: airports that depend heavily on the elevation (for example, LEPO), or airports not yet sent to the X-Plane community (for example, LEMG or LEST), as well as hundred of buildings everywhere we are still uploading to [[TerraSync]] and even some non-free buildings.

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 license [http://creativecommons.org/licenses/by-sa/3.0/], and under the terms of the GPL License. Use the license more suitable for your needs.

== Improved and new airports ==

As a result of the project, dozens of airports have been modeled. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the airports developed in the project. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The improved layout for most of these airports are already included in [[TerraSync]], and we are still uploading the remaining airports and their buildings.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

= Pre 2.0 scenery =

Prior to the release of the 2.0 scenery in [[TerraSync]], we maintained a custom scenery for the continental territories of Spain, Portugal, Andorra and Gibraltar. The project used the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti. The scenery files divided the Iberian Peninsula in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

These files are no longer available, since the current scenario in [[TerraSync]] provides a level of detail similar to these old files. More information about these old files can be found at [http://flightgear.creatuforo.com/viewtopic.php?t=3143 Vive FG!]

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-12-09T16:55:24Z

Ludomo:

The Spanish community of FlightGear started in 2012 a project to enhance the scenario of the Iberian Peninsula. This included an enhacement of the terrain, that was still low detail at the moment the project started, new layouts for many airports and hundred of objects spread on all the geography.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

= Download and Installation =

The "update package" can be found at: [https://mega.co.nz/#!1FgjlLhR!CnEoDTq_JWBrPa7RFk4AwERxxzI_yix4UKZNmyEIpIo|Improved Iberian Peninsula] This is an enhacement of the current scenery in [[TerraSync]], and must be used in addition to [[TerraSync]]. See the next section for the changes.

Download the and uncompress the file in a local directory. For example, under Windows, ''My Documents\Games\IBE''. Then, add this directory to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

If you download the file after an update, first remove the existing directory and then install again.

= Improvements over the standard scenery =

The goals of the Iberian scenery were:

* Terrain compiled using the last data available from OpenStreetMap and CORINE. This terrain is no longer necessary from the introduction of the scenery 2.0 in [[TerraSync]].
* Improvements on the layouts of many airports (LEBL, LEMG...), including many new airports (LESL, LECI...)
* Models of lots of buildings, including main airports and some cities: Madrid, Barcelona and many more.
* Parking points for many the airports. Currently, about 80% of the airports have parking points.
* Scenery especially suitable for VFR flights: notification points, cities...

Currently, the terrain files are no longer necessary but many improvements are not yet in [[TerraSync]]: airports that depend heavily on the elevation (for example, LEPO), or airports not yet sent to the X-Plane community (for example, LEMG or LEST), as well as hundred of buildings everywhere we are still uploading to [[TerraSync]] and even some non-free buildings.

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 license [http://creativecommons.org/licenses/by-sa/3.0/], and under the terms of the GPL License. Use the license more suitable for your needs.

== Improved and new airports ==

As a result of the project, dozens of airports have been modeled. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the airports developed in the project. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The improved layout for most of these airports are already included in [[TerraSync]], and we are still uploading the remaining airports and their buildings.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

= Pre 2.0 scenery =

Prior to the release of the 2.0 scenery in [[TerraSync]], we maintained a custom scenery for the continental territories of Spain, Portugal, Andorra and Gibraltar. The project used the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti. The scenery files divided the Iberian Peninsula in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

These files are no longer available, since the current scenario in [[TerraSync]] provides a level of detail similar to these old files.

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-10-14T18:03:27Z

Ludomo: /* Distribution */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

Warning! '''This scenery only works correctly in FlightGear 2.11 and up'''. It is extremely unstable in FlightGear 2.10 and older versions!

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.
* Lots of buildings added, especially suitable for VFR flights: notification points, cities...

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

* IBE01 (Catalonia): https://mega.co.nz/#!BM4WUDiI!aff4k1CBBYUyzRfWFbe_mH6pwaQ4SmypSVNaOHosWYE (348.3 MB)
* IBE02 (Balearic Islands): https://mega.co.nz/#!1BgyQKqI!eOvcFA_70bEERvXMMIFaxSojECIFVWqQPreXzRqa56g (43.3 MB)
* IBE03 (Valencia): https://mega.co.nz/#!cIBxhJiB!WzJs8GlxV_jXLKJacNtljmAoQK4mBSjP-SyYThwTRxU (197.9 MB)
* IBE04 (Madrid): https://mega.co.nz/#!1No23JBI!U8Id3lQ7xNAJ66CmR_-Gnj8seJBdEbE9CVq-qD4RRBY (110.4 MB)
* IBE05 (Basque Country, Aragon): https://mega.co.nz/#!9UAEVTJb!I7HTSlMJQBihjQzrnmy8ZmdgYId3yv3f-2zwv94ETDs (317.4 MB)
* IBE06 (Galiza): https://mega.co.nz/#!sBZBQBQb!PVnFU1P-eVPGfbqGL3tqSSz5nPojNpBjxaGc2CMG70g (303.9 MB)
* IBE07 (Coast of Portugal): https://mega.co.nz/#!hFQgRAYb!WbJs4Q4gItiuIXTFYNJkpUGthpcd9Bbsxe0fcDU0NW8 (157.0 MB)
* IBE08 (East Andalusia): https://mega.co.nz/#!YNA1gLyY!A0edtQC-ryogA8iLvWcyrBAyZVx5r5jWduQccY8WmjE (265.2 MB)
* IBE09 (West Andalusia, South of Portugal): https://mega.co.nz/#!YcBU1IpR!ayFgMRQ2OAv-T_IQBlulJyjCPDFCkWWB-hKZ10EVmHM (167.5 MB)
* IBE10 (East Portugal, Leon): https://mega.co.nz/#!JQggGY7D!I0gi5UeSPverIYVO2siGRCRWDR0taAJP7ntlWYMApgo (321.3 MB)
* Extra zone: GC: (Canary islands): https://mega.co.nz/#!AQBnRDza!foAgxzkjzJ90s1vO50Juv0zXR-YCpATiN5gpk-VyW9c (70.4 MB)

These files are intended to be stable, and regular updates will be published in https://dl.dropboxusercontent.com/u/13130748/IBE-Update.zip This file includes updates for all zones.

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 license [http://creativecommons.org/licenses/by-sa/3.0/], and under the terms of the GPL License. Use the more suitable license for your needs.

== Installation ==

Download the area you are interested in (or all of them!) and uncompress the file in a local directory. The best option is using a separate directory for each area. For example, under Windows, ''My Documents\Games\IBE01'', ''My Documents\Games\IBE02''..., under Linux ''$HOME/Documents/IBE/IBE01'', ''$HOME/Documents/IBE/IBE02''... and so on. Then, add these directories to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

If you download the updates, install them in the same directory than the zones, overwriting any existing file.

[[File:Scenery ibe configuration.png|thumb|Recommended configuration of this scenery]]

== Improved and new airports ==

Dozens of airports have been modeled using specific buildings. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the improved airports in the scenery. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The airports that are not in this map but are included in v850 of apt.dat are also compiled, but they do not include buildings. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-09-19T14:23:37Z

Ludomo:

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

Warning! '''This scenery only works correctly in FlightGear 2.11 and up'''. It is extremely unstable in FlightGear 2.10 and older versions!

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.
* Lots of buildings added, especially suitable for VFR flights: notification points, cities...

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

* IBE01 (Catalonia): https://mega.co.nz/#!BM4WUDiI!aff4k1CBBYUyzRfWFbe_mH6pwaQ4SmypSVNaOHosWYE (348.3 MB)
* IBE02 (Balearic Islands): https://mega.co.nz/#!UAg0FLRC!cSiPZFMLelRicB-HsFN8gk8sXKBMClV9E8UWDaCVivk (39.6 MB)
* IBE03 (Valencia): https://mega.co.nz/#!cIBxhJiB!WzJs8GlxV_jXLKJacNtljmAoQK4mBSjP-SyYThwTRxU (197.9 MB)
* IBE04 (Madrid): https://mega.co.nz/#!1No23JBI!U8Id3lQ7xNAJ66CmR_-Gnj8seJBdEbE9CVq-qD4RRBY (110.4 MB)
* IBE05 (Basque Country, Aragon): https://mega.co.nz/#!9UAEVTJb!I7HTSlMJQBihjQzrnmy8ZmdgYId3yv3f-2zwv94ETDs (317.4 MB)
* IBE06 (Galiza): https://mega.co.nz/#!sBZBQBQb!PVnFU1P-eVPGfbqGL3tqSSz5nPojNpBjxaGc2CMG70g (303.9 MB)
* IBE07 (Coast of Portugal): https://mega.co.nz/#!hFQgRAYb!WbJs4Q4gItiuIXTFYNJkpUGthpcd9Bbsxe0fcDU0NW8 (157.0 MB)
* IBE08 (East Andalusia): https://mega.co.nz/#!YNA1gLyY!A0edtQC-ryogA8iLvWcyrBAyZVx5r5jWduQccY8WmjE (265.2 MB)
* IBE09 (West Andalusia, South of Portugal): https://mega.co.nz/#!YcBU1IpR!ayFgMRQ2OAv-T_IQBlulJyjCPDFCkWWB-hKZ10EVmHM (167.5 MB)
* IBE10 (East Portugal, Leon): https://mega.co.nz/#!JQggGY7D!I0gi5UeSPverIYVO2siGRCRWDR0taAJP7ntlWYMApgo (321.3 MB)
* Extra zone: GC: (Canary islands): https://mega.co.nz/#!AQBnRDza!foAgxzkjzJ90s1vO50Juv0zXR-YCpATiN5gpk-VyW9c (70.4 MB)

These files are intended to be stable, and regular updates will be published in https://dl.dropboxusercontent.com/u/13130748/IBE-Update.zip This file includes updates for all zones.

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Installation ==

Download the area you are interested in (or all of them!) and uncompress the file in a local directory. The best option is using a separate directory for each area. For example, under Windows, ''My Documents\Games\IBE01'', ''My Documents\Games\IBE02''..., under Linux ''$HOME/Documents/IBE/IBE01'', ''$HOME/Documents/IBE/IBE02''... and so on. Then, add these directories to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

If you download the updates, install them in the same directory than the zones, overwriting any existing file.

[[File:Scenery ibe configuration.png|thumb|Recommended configuration of this scenery]]

== Improved and new airports ==

Dozens of airports have been modeled using specific buildings. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the improved airports in the scenery. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The airports that are not in this map but are included in v850 of apt.dat are also compiled, but they do not include buildings. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-09-05T20:43:40Z

Ludomo: /* Distribution */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.
* Lots of buildings added, especially suitable for VFR flights: notification points, cities...

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

* IBE01 (Catalonia): https://mega.co.nz/#!BM4WUDiI!aff4k1CBBYUyzRfWFbe_mH6pwaQ4SmypSVNaOHosWYE (348.3 MB)
* IBE02 (Balearic Islands): https://mega.co.nz/#!UAg0FLRC!cSiPZFMLelRicB-HsFN8gk8sXKBMClV9E8UWDaCVivk (39.6 MB)
* IBE03 (Valencia): https://mega.co.nz/#!cIBxhJiB!WzJs8GlxV_jXLKJacNtljmAoQK4mBSjP-SyYThwTRxU (197.9 MB)
* IBE04 (Madrid): https://mega.co.nz/#!1No23JBI!U8Id3lQ7xNAJ66CmR_-Gnj8seJBdEbE9CVq-qD4RRBY (110.4 MB)
* IBE05 (Basque Country, Aragon): https://mega.co.nz/#!9UAEVTJb!I7HTSlMJQBihjQzrnmy8ZmdgYId3yv3f-2zwv94ETDs (317.4 MB)
* IBE06 (Galiza): https://mega.co.nz/#!sBZBQBQb!PVnFU1P-eVPGfbqGL3tqSSz5nPojNpBjxaGc2CMG70g (303.9 MB)
* IBE07 (Coast of Portugal): https://mega.co.nz/#!hFQgRAYb!WbJs4Q4gItiuIXTFYNJkpUGthpcd9Bbsxe0fcDU0NW8 (157.0 MB)
* IBE08 (East Andalusia): https://mega.co.nz/#!YNA1gLyY!A0edtQC-ryogA8iLvWcyrBAyZVx5r5jWduQccY8WmjE (265.2 MB)
* IBE09 (West Andalusia, South of Portugal): https://mega.co.nz/#!YcBU1IpR!ayFgMRQ2OAv-T_IQBlulJyjCPDFCkWWB-hKZ10EVmHM (167.5 MB)
* IBE10 (East Portugal, Leon): https://mega.co.nz/#!JQggGY7D!I0gi5UeSPverIYVO2siGRCRWDR0taAJP7ntlWYMApgo (321.3 MB)
* Extra zone: GC: (Canary islands): https://mega.co.nz/#!AQBnRDza!foAgxzkjzJ90s1vO50Juv0zXR-YCpATiN5gpk-VyW9c (70.4 MB)

These files are intended to be stable, and regular updates will be published in https://dl.dropboxusercontent.com/u/13130748/IBE-Update.zip This file includes updates for all zones.

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Installation ==

Download the area you are interested in (or all of them!) and uncompress the file in a local directory. The best option is using a separate directory for each area. For example, under Windows, ''My Documents\Games\IBE01'', ''My Documents\Games\IBE02''..., under Linux ''$HOME/Documents/IBE/IBE01'', ''$HOME/Documents/IBE/IBE02''... and so on. Then, add these directories to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

If you download the updates, install them in the same directory than the zones, overwriting any existing file.

[[File:Scenery ibe configuration.png|thumb|Recommended configuration of this scenery]]

== Improved and new airports ==

Dozens of airports have been modeled using specific buildings. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the improved airports in the scenery. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The airports that are not in this map but are included in v850 of apt.dat are also compiled, but they do not include buildings. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-09-01T13:24:55Z

Ludomo: /* Distribution */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.
* Lots of buildings added, especially suitable for VFR flights: notification points, cities...

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

* IBE01 (Catalonia): https://mega.co.nz/#!BM4WUDiI!aff4k1CBBYUyzRfWFbe_mH6pwaQ4SmypSVNaOHosWYE (348.3 MB)
* IBE02 (Balearic Islands): https://mega.co.nz/#!UAg0FLRC!cSiPZFMLelRicB-HsFN8gk8sXKBMClV9E8UWDaCVivk (39.6 MB)
* IBE03 (Valencia): https://mega.co.nz/#!cIBxhJiB!WzJs8GlxV_jXLKJacNtljmAoQK4mBSjP-SyYThwTRxU (197.9 MB)
* IBE04 (Madrid): https://mega.co.nz/#!1No23JBI!U8Id3lQ7xNAJ66CmR_-Gnj8seJBdEbE9CVq-qD4RRBY (110.4 MB)
* IBE05 (Basque Country, Aragon): https://mega.co.nz/#!IdA31R7Z!BNnsHxCZ4-hIpy0QPf-gq06uwH8jquhnLLcCljk5D50 (350.4 MB)
* IBE06 (Galiza): https://mega.co.nz/#!sBZBQBQb!PVnFU1P-eVPGfbqGL3tqSSz5nPojNpBjxaGc2CMG70g (303.9 MB)
* IBE07 (Coast of Portugal): https://mega.co.nz/#!hFQgRAYb!WbJs4Q4gItiuIXTFYNJkpUGthpcd9Bbsxe0fcDU0NW8 (157.0 MB)
* IBE08 (East Andalusia): https://mega.co.nz/#!YNA1gLyY!A0edtQC-ryogA8iLvWcyrBAyZVx5r5jWduQccY8WmjE (265.2 MB)
* IBE09 (West Andalusia, South of Portugal): https://mega.co.nz/#!YcBU1IpR!ayFgMRQ2OAv-T_IQBlulJyjCPDFCkWWB-hKZ10EVmHM (167.5 MB)
* IBE10 (East Portugal, Leon): https://mega.co.nz/#!JQggGY7D!I0gi5UeSPverIYVO2siGRCRWDR0taAJP7ntlWYMApgo (321.3 MB)
* Extra zone: GC: (Canary islands): https://mega.co.nz/#!AQBnRDza!foAgxzkjzJ90s1vO50Juv0zXR-YCpATiN5gpk-VyW9c (70.4 MB)

These files are intended to be stable, and regular updates will be published in https://dl.dropboxusercontent.com/u/13130748/IBE-Update.zip This file includes updates for all zones.

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Installation ==

Download the area you are interested in (or all of them!) and uncompress the file in a local directory. The best option is using a separate directory for each area. For example, under Windows, ''My Documents\Games\IBE01'', ''My Documents\Games\IBE02''..., under Linux ''$HOME/Documents/IBE/IBE01'', ''$HOME/Documents/IBE/IBE02''... and so on. Then, add these directories to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

If you download the updates, install them in the same directory than the zones, overwriting any existing file.

[[File:Scenery ibe configuration.png|thumb|Recommended configuration of this scenery]]

== Improved and new airports ==

Dozens of airports have been modeled using specific buildings. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the improved airports in the scenery. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The airports that are not in this map but are included in v850 of apt.dat are also compiled, but they do not include buildings. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-08-31T15:16:49Z

Ludomo: /* Distribution */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.
* Lots of buildings added, especially suitable for VFR flights: notification points, cities...

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

* IBE01 (Catalonia): https://mega.co.nz/#!BM4WUDiI!aff4k1CBBYUyzRfWFbe_mH6pwaQ4SmypSVNaOHosWYE (348.3 MB)
* IBE02 (Balearic Islands): https://mega.co.nz/#!UAg0FLRC!cSiPZFMLelRicB-HsFN8gk8sXKBMClV9E8UWDaCVivk (39.6 MB)
* IBE03 (Valencia): https://mega.co.nz/#!pB5niJ4K!Yv0IEB1abuezmw92vGk0QkcvGJczTnd0-YhsO49-CVk (192.9 MB)
* IBE04 (Madrid): https://mega.co.nz/#!1No23JBI!U8Id3lQ7xNAJ66CmR_-Gnj8seJBdEbE9CVq-qD4RRBY (110.4 MB)
* IBE05 (Basque Country, Aragon): https://mega.co.nz/#!IdA31R7Z!BNnsHxCZ4-hIpy0QPf-gq06uwH8jquhnLLcCljk5D50 (350.4 MB)
* IBE06 (Galiza): https://mega.co.nz/#!sBZBQBQb!PVnFU1P-eVPGfbqGL3tqSSz5nPojNpBjxaGc2CMG70g (303.9 MB)
* IBE07 (Coast of Portugal): https://mega.co.nz/#!hFQgRAYb!WbJs4Q4gItiuIXTFYNJkpUGthpcd9Bbsxe0fcDU0NW8 (157.0 MB)
* IBE08 (East Andalusia): https://mega.co.nz/#!YNA1gLyY!A0edtQC-ryogA8iLvWcyrBAyZVx5r5jWduQccY8WmjE (265.2 MB)
* IBE09 (West Andalusia, South of Portugal): https://mega.co.nz/#!YcBU1IpR!ayFgMRQ2OAv-T_IQBlulJyjCPDFCkWWB-hKZ10EVmHM (167.5 MB)
* IBE10 (East Portugal, Leon): https://mega.co.nz/#!JQggGY7D!I0gi5UeSPverIYVO2siGRCRWDR0taAJP7ntlWYMApgo (321.3 MB)
* Extra zone: GC: (Canary islands): https://mega.co.nz/#!AQBnRDza!foAgxzkjzJ90s1vO50Juv0zXR-YCpATiN5gpk-VyW9c (70.4 MB)

These files are intended to be stable, and regular updates will be published in https://dl.dropboxusercontent.com/u/13130748/IBE-Update.zip This file includes updates for all zones.

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Installation ==

Download the area you are interested in (or all of them!) and uncompress the file in a local directory. The best option is using a separate directory for each area. For example, under Windows, ''My Documents\Games\IBE01'', ''My Documents\Games\IBE02''..., under Linux ''$HOME/Documents/IBE/IBE01'', ''$HOME/Documents/IBE/IBE02''... and so on. Then, add these directories to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

If you download the updates, install them in the same directory than the zones, overwriting any existing file.

[[File:Scenery ibe configuration.png|thumb|Recommended configuration of this scenery]]

== Improved and new airports ==

Dozens of airports have been modeled using specific buildings. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the improved airports in the scenery. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The airports that are not in this map but are included in v850 of apt.dat are also compiled, but they do not include buildings. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-08-24T12:59:00Z

Ludomo: /* Installation */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.
* Lots of buildings added, especially suitable for VFR flights: notification points, cities...

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

* IBE01 (Catalonia): https://mega.co.nz/#!BM4WUDiI!aff4k1CBBYUyzRfWFbe_mH6pwaQ4SmypSVNaOHosWYE (348.3 MB)
* IBE02 (Balearic Islands): https://mega.co.nz/#!UAg0FLRC!cSiPZFMLelRicB-HsFN8gk8sXKBMClV9E8UWDaCVivk (39.6 MB)
* IBE03 (Valencia): https://mega.co.nz/#!cE5jXYyY!RkxuCQMGXqhz3XnQybmWzwtOg71q54sMZYThycYZC0Y (184.9 MB)
* IBE04 (Madrid): https://mega.co.nz/#!1No23JBI!U8Id3lQ7xNAJ66CmR_-Gnj8seJBdEbE9CVq-qD4RRBY (110.4 MB)
* IBE05 (Basque Country, Aragon): https://mega.co.nz/#!IdA31R7Z!BNnsHxCZ4-hIpy0QPf-gq06uwH8jquhnLLcCljk5D50 (350.4 MB)
* IBE06 (Galiza): https://mega.co.nz/#!sBZBQBQb!PVnFU1P-eVPGfbqGL3tqSSz5nPojNpBjxaGc2CMG70g (303.9 MB)
* IBE07 (Coast of Portugal): https://mega.co.nz/#!hFQgRAYb!WbJs4Q4gItiuIXTFYNJkpUGthpcd9Bbsxe0fcDU0NW8 (157.0 MB)
* IBE08 (East Andalusia): https://mega.co.nz/#!YNA1gLyY!A0edtQC-ryogA8iLvWcyrBAyZVx5r5jWduQccY8WmjE (265.2 MB)
* IBE09 (West Andalusia, South of Portugal): https://mega.co.nz/#!YcBU1IpR!ayFgMRQ2OAv-T_IQBlulJyjCPDFCkWWB-hKZ10EVmHM (167.5 MB)
* IBE10 (East Portugal, Leon): https://mega.co.nz/#!JQggGY7D!I0gi5UeSPverIYVO2siGRCRWDR0taAJP7ntlWYMApgo (321.3 MB)
* Extra zone: GC: (Canary islands): https://mega.co.nz/#!AQBnRDza!foAgxzkjzJ90s1vO50Juv0zXR-YCpATiN5gpk-VyW9c (70.4 MB)

These files are intended to be stable, and regular updates will be published in https://dl.dropboxusercontent.com/u/13130748/IBE-Update.zip This file includes updates for all zones.

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Installation ==

Download the area you are interested in (or all of them!) and uncompress the file in a local directory. The best option is using a separate directory for each area. For example, under Windows, ''My Documents\Games\IBE01'', ''My Documents\Games\IBE02''..., under Linux ''$HOME/Documents/IBE/IBE01'', ''$HOME/Documents/IBE/IBE02''... and so on. Then, add these directories to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

If you download the updates, install them in the same directory than the zones, overwriting any existing file.

[[File:Scenery ibe configuration.png|thumb|Recommended configuration of this scenery]]

== Improved and new airports ==

Dozens of airports have been modeled using specific buildings. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the improved airports in the scenery. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The airports that are not in this map but are included in v850 of apt.dat are also compiled, but they do not include buildings. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-08-24T12:57:36Z

Ludomo: /* Distribution */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.
* Lots of buildings added, especially suitable for VFR flights: notification points, cities...

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

* IBE01 (Catalonia): https://mega.co.nz/#!BM4WUDiI!aff4k1CBBYUyzRfWFbe_mH6pwaQ4SmypSVNaOHosWYE (348.3 MB)
* IBE02 (Balearic Islands): https://mega.co.nz/#!UAg0FLRC!cSiPZFMLelRicB-HsFN8gk8sXKBMClV9E8UWDaCVivk (39.6 MB)
* IBE03 (Valencia): https://mega.co.nz/#!cE5jXYyY!RkxuCQMGXqhz3XnQybmWzwtOg71q54sMZYThycYZC0Y (184.9 MB)
* IBE04 (Madrid): https://mega.co.nz/#!1No23JBI!U8Id3lQ7xNAJ66CmR_-Gnj8seJBdEbE9CVq-qD4RRBY (110.4 MB)
* IBE05 (Basque Country, Aragon): https://mega.co.nz/#!IdA31R7Z!BNnsHxCZ4-hIpy0QPf-gq06uwH8jquhnLLcCljk5D50 (350.4 MB)
* IBE06 (Galiza): https://mega.co.nz/#!sBZBQBQb!PVnFU1P-eVPGfbqGL3tqSSz5nPojNpBjxaGc2CMG70g (303.9 MB)
* IBE07 (Coast of Portugal): https://mega.co.nz/#!hFQgRAYb!WbJs4Q4gItiuIXTFYNJkpUGthpcd9Bbsxe0fcDU0NW8 (157.0 MB)
* IBE08 (East Andalusia): https://mega.co.nz/#!YNA1gLyY!A0edtQC-ryogA8iLvWcyrBAyZVx5r5jWduQccY8WmjE (265.2 MB)
* IBE09 (West Andalusia, South of Portugal): https://mega.co.nz/#!YcBU1IpR!ayFgMRQ2OAv-T_IQBlulJyjCPDFCkWWB-hKZ10EVmHM (167.5 MB)
* IBE10 (East Portugal, Leon): https://mega.co.nz/#!JQggGY7D!I0gi5UeSPverIYVO2siGRCRWDR0taAJP7ntlWYMApgo (321.3 MB)
* Extra zone: GC: (Canary islands): https://mega.co.nz/#!AQBnRDza!foAgxzkjzJ90s1vO50Juv0zXR-YCpATiN5gpk-VyW9c (70.4 MB)

These files are intended to be stable, and regular updates will be published in https://dl.dropboxusercontent.com/u/13130748/IBE-Update.zip This file includes updates for all zones.

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Installation ==

Download the area you are interested in (or all of them!) and uncompress the file in a local directory. The best option is using a separate directory for each area. For example, under Windows, ''My Documents\Games\IBE01'', ''My Documents\Games\IBE02''..., under Linux ''$HOME/Documents/IBE/IBE01'', ''$HOME/Documents/IBE/IBE02''... and so on. Then, add these directories to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

[[File:Scenery ibe configuration.png|thumb|Recommended configuration of this scenery]]

== Improved and new airports ==

Dozens of airports have been modeled using specific buildings. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the improved airports in the scenery. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The airports that are not in this map but are included in v850 of apt.dat are also compiled, but they do not include buildings. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-08-06T20:45:58Z

Ludomo: /* Improved and new airports */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.
* Lots of buildings added, especially suitable for VFR flights: notification points, cities...

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

* IBE01 (Catalonia): https://mega.co.nz/#!BM4WUDiI!aff4k1CBBYUyzRfWFbe_mH6pwaQ4SmypSVNaOHosWYE (348.3 MB)
* IBE02 (Balearic Islands): https://mega.co.nz/#!UAg0FLRC!cSiPZFMLelRicB-HsFN8gk8sXKBMClV9E8UWDaCVivk (39.6 MB)
* IBE03 (Valencia): https://mega.co.nz/#!cE5jXYyY!RkxuCQMGXqhz3XnQybmWzwtOg71q54sMZYThycYZC0Y (184.9 MB)
* IBE04 (Madrid): https://mega.co.nz/#!1No23JBI!U8Id3lQ7xNAJ66CmR_-Gnj8seJBdEbE9CVq-qD4RRBY (110.4 MB)
* IBE05 (Basque Country, Aragon): https://mega.co.nz/#!IdA31R7Z!BNnsHxCZ4-hIpy0QPf-gq06uwH8jquhnLLcCljk5D50 (350.4 MB)
* IBE06 (Galiza): https://mega.co.nz/#!sBZBQBQb!PVnFU1P-eVPGfbqGL3tqSSz5nPojNpBjxaGc2CMG70g (303.9 MB)
* IBE07 (Coast of Portugal): https://mega.co.nz/#!hFQgRAYb!WbJs4Q4gItiuIXTFYNJkpUGthpcd9Bbsxe0fcDU0NW8 (157.0 MB)
* IBE08 (East Andalusia): https://mega.co.nz/#!YNA1gLyY!A0edtQC-ryogA8iLvWcyrBAyZVx5r5jWduQccY8WmjE (265.2 MB)
* IBE09 (West Andalusia, South of Portugal): https://mega.co.nz/#!YcBU1IpR!ayFgMRQ2OAv-T_IQBlulJyjCPDFCkWWB-hKZ10EVmHM (167.5 MB)
* IBE10 (East Portugal, Leon): https://mega.co.nz/#!JQggGY7D!I0gi5UeSPverIYVO2siGRCRWDR0taAJP7ntlWYMApgo (321.3 MB)
* Extra zone: GC: (Canary islands): https://mega.co.nz/#!AQBnRDza!foAgxzkjzJ90s1vO50Juv0zXR-YCpATiN5gpk-VyW9c (70.4 MB)

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Installation ==

Download the area you are interested in (or all of them!) and uncompress the file in a local directory. The best option is using a separate directory for each area. For example, under Windows, ''My Documents\Games\IBE01'', ''My Documents\Games\IBE02''..., under Linux ''$HOME/Documents/IBE/IBE01'', ''$HOME/Documents/IBE/IBE02''... and so on. Then, add these directories to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

[[File:Scenery ibe configuration.png|thumb|Recommended configuration of this scenery]]

== Improved and new airports ==

Dozens of airports have been modeled using specific buildings. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

The map [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0] shows the improved airports in the scenery. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The airports that are not in this map but are included in v850 of apt.dat are also compiled, but they do not include buildings. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-08-06T20:44:47Z

Ludomo: /* Instalation */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.
* Lots of buildings added, especially suitable for VFR flights: notification points, cities...

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

* IBE01 (Catalonia): https://mega.co.nz/#!BM4WUDiI!aff4k1CBBYUyzRfWFbe_mH6pwaQ4SmypSVNaOHosWYE (348.3 MB)
* IBE02 (Balearic Islands): https://mega.co.nz/#!UAg0FLRC!cSiPZFMLelRicB-HsFN8gk8sXKBMClV9E8UWDaCVivk (39.6 MB)
* IBE03 (Valencia): https://mega.co.nz/#!cE5jXYyY!RkxuCQMGXqhz3XnQybmWzwtOg71q54sMZYThycYZC0Y (184.9 MB)
* IBE04 (Madrid): https://mega.co.nz/#!1No23JBI!U8Id3lQ7xNAJ66CmR_-Gnj8seJBdEbE9CVq-qD4RRBY (110.4 MB)
* IBE05 (Basque Country, Aragon): https://mega.co.nz/#!IdA31R7Z!BNnsHxCZ4-hIpy0QPf-gq06uwH8jquhnLLcCljk5D50 (350.4 MB)
* IBE06 (Galiza): https://mega.co.nz/#!sBZBQBQb!PVnFU1P-eVPGfbqGL3tqSSz5nPojNpBjxaGc2CMG70g (303.9 MB)
* IBE07 (Coast of Portugal): https://mega.co.nz/#!hFQgRAYb!WbJs4Q4gItiuIXTFYNJkpUGthpcd9Bbsxe0fcDU0NW8 (157.0 MB)
* IBE08 (East Andalusia): https://mega.co.nz/#!YNA1gLyY!A0edtQC-ryogA8iLvWcyrBAyZVx5r5jWduQccY8WmjE (265.2 MB)
* IBE09 (West Andalusia, South of Portugal): https://mega.co.nz/#!YcBU1IpR!ayFgMRQ2OAv-T_IQBlulJyjCPDFCkWWB-hKZ10EVmHM (167.5 MB)
* IBE10 (East Portugal, Leon): https://mega.co.nz/#!JQggGY7D!I0gi5UeSPverIYVO2siGRCRWDR0taAJP7ntlWYMApgo (321.3 MB)
* Extra zone: GC: (Canary islands): https://mega.co.nz/#!AQBnRDza!foAgxzkjzJ90s1vO50Juv0zXR-YCpATiN5gpk-VyW9c (70.4 MB)

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Installation ==

Download the area you are interested in (or all of them!) and uncompress the file in a local directory. The best option is using a separate directory for each area. For example, under Windows, ''My Documents\Games\IBE01'', ''My Documents\Games\IBE02''..., under Linux ''$HOME/Documents/IBE/IBE01'', ''$HOME/Documents/IBE/IBE02''... and so on. Then, add these directories to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

[[File:Scenery ibe configuration.png|thumb|Recommended configuration of this scenery]]

== Improved and new airports ==

Dozens of airports have been modeled using specific buildings. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

The map shows the improved airports in the scenery. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The airports that are not in this map but are included in v850 of apt.dat are also compiled, but they do not include buildings. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-08-06T20:44:18Z

Ludomo:

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.
* Lots of buildings added, especially suitable for VFR flights: notification points, cities...

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|512px|Zones of the scenery]]

* IBE01 (Catalonia): https://mega.co.nz/#!BM4WUDiI!aff4k1CBBYUyzRfWFbe_mH6pwaQ4SmypSVNaOHosWYE (348.3 MB)
* IBE02 (Balearic Islands): https://mega.co.nz/#!UAg0FLRC!cSiPZFMLelRicB-HsFN8gk8sXKBMClV9E8UWDaCVivk (39.6 MB)
* IBE03 (Valencia): https://mega.co.nz/#!cE5jXYyY!RkxuCQMGXqhz3XnQybmWzwtOg71q54sMZYThycYZC0Y (184.9 MB)
* IBE04 (Madrid): https://mega.co.nz/#!1No23JBI!U8Id3lQ7xNAJ66CmR_-Gnj8seJBdEbE9CVq-qD4RRBY (110.4 MB)
* IBE05 (Basque Country, Aragon): https://mega.co.nz/#!IdA31R7Z!BNnsHxCZ4-hIpy0QPf-gq06uwH8jquhnLLcCljk5D50 (350.4 MB)
* IBE06 (Galiza): https://mega.co.nz/#!sBZBQBQb!PVnFU1P-eVPGfbqGL3tqSSz5nPojNpBjxaGc2CMG70g (303.9 MB)
* IBE07 (Coast of Portugal): https://mega.co.nz/#!hFQgRAYb!WbJs4Q4gItiuIXTFYNJkpUGthpcd9Bbsxe0fcDU0NW8 (157.0 MB)
* IBE08 (East Andalusia): https://mega.co.nz/#!YNA1gLyY!A0edtQC-ryogA8iLvWcyrBAyZVx5r5jWduQccY8WmjE (265.2 MB)
* IBE09 (West Andalusia, South of Portugal): https://mega.co.nz/#!YcBU1IpR!ayFgMRQ2OAv-T_IQBlulJyjCPDFCkWWB-hKZ10EVmHM (167.5 MB)
* IBE10 (East Portugal, Leon): https://mega.co.nz/#!JQggGY7D!I0gi5UeSPverIYVO2siGRCRWDR0taAJP7ntlWYMApgo (321.3 MB)
* Extra zone: GC: (Canary islands): https://mega.co.nz/#!AQBnRDza!foAgxzkjzJ90s1vO50Juv0zXR-YCpATiN5gpk-VyW9c (70.4 MB)

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Instalation ==

Download the area you are interested in (or all of them!) and uncompress the file in a local directory. The best option is using a separate directory for each area. For example, under Windows, ''My Documents\Games\IBE01'', ''My Documents\Games\IBE02''..., under Linux ''$HOME/Documents/IBE/IBE01'', ''$HOME/Documents/IBE/IBE02''... and so on. Then, add these directories to the first tab of the simulator launcher, section ''FG_SCENERY''. If you use a terrasync directory, move the terrasync directory to the last position on the list.

[[File:Scenery ibe configuration.png|thumb|Recommended configuration of this scenery]]

== Improved and new airports ==

Dozens of airports have been modeled using specific buildings. This includes large international airports, such as Madrid (LEMD) and Barcelona (LEBL), medium-size regional airports such as Reus (LERS) or Cordoba (LEBA), small airfields for general aviation such as San Luis (LESL) or Cerdanya (LECD) and tiny airfields for ultralight aircrafts, such as Alfés (LEAT)

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

The map shows the improved airports in the scenery. All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The airports that are not in this map but are included in v850 of apt.dat are also compiled, but they do not include buildings. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

Color code [https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 of the airport map]

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

[[Category:Scenery]]

File:Scenery ibe configuration.png

2013-08-06T20:36:09Z

Ludomo: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Example of a configuration of the IBE scenery}}
|date=2013-08-06 22:34:21
|source={{own}}
|author=[[User:Ludomo|Ludomo]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

Custom Spain and Portugal scenery

2013-08-06T20:21:41Z

Ludomo: /* Distribution */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.
* Lots of buildings added, especially suitable for VFR flights: notification points, cities...

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|Zones of the scenery]]

* IBE01 (Catalonia): https://mega.co.nz/#!BM4WUDiI!aff4k1CBBYUyzRfWFbe_mH6pwaQ4SmypSVNaOHosWYE (348.3 MB)
* IBE02 (Balearic Islands): https://mega.co.nz/#!UAg0FLRC!cSiPZFMLelRicB-HsFN8gk8sXKBMClV9E8UWDaCVivk (39.6 MB)
* IBE03 (Valencia): https://mega.co.nz/#!cE5jXYyY!RkxuCQMGXqhz3XnQybmWzwtOg71q54sMZYThycYZC0Y (184.9 MB)
* IBE04 (Madrid): https://mega.co.nz/#!1No23JBI!U8Id3lQ7xNAJ66CmR_-Gnj8seJBdEbE9CVq-qD4RRBY (110.4 MB)
* IBE05 (Basque Country, Aragon): https://mega.co.nz/#!IdA31R7Z!BNnsHxCZ4-hIpy0QPf-gq06uwH8jquhnLLcCljk5D50 (350.4 MB)
* IBE06 (Galiza): https://mega.co.nz/#!sBZBQBQb!PVnFU1P-eVPGfbqGL3tqSSz5nPojNpBjxaGc2CMG70g (303.9 MB)
* IBE07 (Coast of Portugal): https://mega.co.nz/#!hFQgRAYb!WbJs4Q4gItiuIXTFYNJkpUGthpcd9Bbsxe0fcDU0NW8 (157.0 MB)
* IBE08 (East Andalusia): https://mega.co.nz/#!YNA1gLyY!A0edtQC-ryogA8iLvWcyrBAyZVx5r5jWduQccY8WmjE (265.2 MB)
* IBE09 (West Andalusia, South of Portugal): https://mega.co.nz/#!YcBU1IpR!ayFgMRQ2OAv-T_IQBlulJyjCPDFCkWWB-hKZ10EVmHM (167.5 MB)
* IBE10 (East Portugal, Leon): https://mega.co.nz/#!JQggGY7D!I0gi5UeSPverIYVO2siGRCRWDR0taAJP7ntlWYMApgo (321.3 MB)
* Extra zone: GC: (Canary islands): https://mega.co.nz/#!AQBnRDza!foAgxzkjzJ90s1vO50Juv0zXR-YCpATiN5gpk-VyW9c (70.4 MB)

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Improved and new airports ==

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

The next map shows the improved airports in the scenery: https://maps.google.com/maps/ms?msid=200770868570711495874.0004dc0d380de0bb19925&msa=0 All these airports include custom buildings, some of them have enhanced runways and a few are completely new. The airports that are not in this map but are included in v850 of apt.dat are also compiled, but they do not include buildings. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

Color code:

* Blue: international and regional airports, usually controlled. Only airliners and general aviation. No ultralights allowed.
* Red: airfields suitable for general aviation, runway longer than 800m, usually uncontrolled and paved surface. There may be ultralights, gliders and parachutes in the area.
* Green: small airfields for ultralights. Usually uncontrolled and dirty surfaces. Runway less than 800m.
* Yellow: heliports.
* Question mark: we are working on them.

[[Category:Scenery]]

FlightGearMap

2013-05-21T17:03:50Z

Ludomo: /* Use */

{{Infobox Software
| title = FlightGearMap
| image = FlightGearMap map and simple panel at KSFO.png
| alt = The map & simple panel at [[KSFO]].
| developedby = Juan Vera del Campo
| initialrelease = 1.0 (April 25, 2012)
| latestrelease = 1.5 (June 9, 2012)
| writtenin =
| os = Android
| developmentstatus = Active (2012-)
| license = [[GNU General Public License]]
| website = https://sites.google.com/site/lettersfromthecloud/follow-me/blog/flightgearmap
}}
[[File:FlightGearMap Cessna 172 panel.png|thumb|270px|The [[Cessna 172P]] panel.]]
'''FlightGearMap''' is an Android application that displays live [[FlightGear]] data in the form of some basic instruments and a moving map.

== Use ==
# On your computer, copy [https://raw.github.com/Juanvvc/FlightGearMap/master/andatlas.xml andatlas.xml] to the directory <tt>[[$FG_ROOT]]/Protocol</tt>. Always use the last version of this file, it will probably change after an update of the application.
# Connect your Android device to the local Wifi network and run the application. A dialog should appear with the IP of your device after few seconds.
# Run FlightGear with the following command, where
#* <code>--generic=socket,out,5,the-ip-of-your-android-device,5501,udp,andatlas --telnet=9000</code> (when using [[FGRun]], this can be set via <tt>Advanced > Input/Output</tt>. See figure.).
#: '''the-ip-of-your-android-device:''' the IP shown by your Android device.
#: '''5:''' the rate in Hz at which data is transmitted. Increasing this value will lead to smoother movements of the map and instruments.
# If you want to modify the instruments from your device (for example, frequencies, radials, switches...), enter the IP of your computer in the <tt>Settings</tt> menu of FlightGearMap.

[[File:The_advance_settings_of_FGRun_showing_a_configuration_of_two_devices_for_FlightGearMap.png|thumb|270px|Configuration using FGRun in the advance settings panel, sending data to two devices.]]
[[File:deployment_flightgearmap_3devices.jpg|thumb|270px|A possible deployment using three devices, a tablet and two mobile phones: instrument panel, comm panel and map.]]

It is strongly recommended to connect several Android devices. My preferred configuration includes a tablet on the table to show the instrument panel and two mobile phones, one to show the current position on a map and the other showing the communication panel. This can be achieved using this configuration:

<code>--generic=socket,out,10,192.168.127.127,5501,udp,andatlas --generic=socket,out,1,192.168.127.128,5501,udp,andatlas --telnet=9000</code>

Where 10,192.168.0.2 is the IP of my tablet receiving 10 updates per second, and 192.168.127.128 the IP of the phone showing the map receiving one position every second. The phone showing the communication panel doesn't receive anything and doesn't need a --generic line, but the computer's IP must be set in the Settings menu.

== Features ==

There are several panels available:

# Only a map showing the position of the aircraft
# A map and some basic controls, including a [[HSI]]
# A generic panel for single engine aircrafts, especially the [[Cessna 172P]]. You can configure some instruments of this panel using the <tt>Setting</tt> menu: the type of [http://en.wikipedia.org/wiki/Airspeed_indicator ASI], the type of heading indicator (simple heading, [[RMI]], [[HSI]]) and the additional instrument (manifold pressure or radar altimeter). The Radio Magnetic Indicator (RMI) shows the course to the NDB and NAV1 stations. The HSI is coupled to NAV1. The additional instrument appears when the RMI or the HSI are selected.
# A [[Cessna 337G Skymaster]] panel.

== Known Issues ==

# In the different heading indicators, you cannot calibrate the heading to match the magnetic compass when decoupled.
# In the [[HSI]], HDG warning flag and TO/FROM indicators are not included. The [[glideslope]] pointers are always visible, even if there is no ILS approach available.
# In the [http://en.wikipedia.org/wiki/Radar_altimeter radar altimeter], you can move the bug but there is no warning light when flying under the selected height.
# Some aircraft models, such as the [[Cessna 172]], filter the movement of the NAV indicators to smooth them. Most of the aircrafts do not filter these movements, and in these cases the smoothed values are not available. The provided andatlas.xml file uses unfiltered values, but if you fly mainly on the [[Cessna 172]], you might prefer modifying andatlas.xml to send the filtered properties instead of raw data.
# The [[DME]] instrument shows distance and ground speed to the selected station. You cannot select time to the station.
# The [[Cessna 337G Skymaster]] model includes lots of additional instruments that do not fit on the screen. The main missing switches are the magnet selectors and start engine buttons, but you will also miss the cowl flap switches. Some other instruments are not included, as the EGT and the fuel flow indicators.
# Since there are many different autopilot models and they are not compatible between them, they are not simulated. The [[Heading bug]] indicator is the only exception, if supported by your autopilot.

== Related content ==
* [[Atlas]]

== External links ==
* [https://play.google.com/store/apps/details?id=com.juanvvc.flightgear FlightGearMap] (Google Play)
* [http://www.flightgear.org/forums/viewtopic.php?f=31&t=16136 Forum topic]

[[Category:Software]]
[[fr:FlightGearMap]]

File:Deployment flightgearmap 3devices.jpg

2013-05-21T17:03:02Z

Ludomo:

=={{int:filedesc}}==
{{Information
|description={{en|1=A deployment of FlighGearMap using three devices: a tablet as an instrument panel, a mobile phone as a comm panel and another mobile phone showing the map.}}
|date=2013-05-21
|source={{own}}
|author=[[User:Ludomo|Ludomo]]
|permission=
|other_versions=
|other_fields=
}}

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

FlightGearMap

2013-05-21T17:01:32Z

Ludomo:

{{Infobox Software
| title = FlightGearMap
| image = FlightGearMap map and simple panel at KSFO.png
| alt = The map & simple panel at [[KSFO]].
| developedby = Juan Vera del Campo
| initialrelease = 1.0 (April 25, 2012)
| latestrelease = 1.5 (June 9, 2012)
| writtenin =
| os = Android
| developmentstatus = Active (2012-)
| license = [[GNU General Public License]]
| website = https://sites.google.com/site/lettersfromthecloud/follow-me/blog/flightgearmap
}}
[[File:FlightGearMap Cessna 172 panel.png|thumb|270px|The [[Cessna 172P]] panel.]]
'''FlightGearMap''' is an Android application that displays live [[FlightGear]] data in the form of some basic instruments and a moving map.

== Use ==
# On your computer, copy [https://raw.github.com/Juanvvc/FlightGearMap/master/andatlas.xml andatlas.xml] to the directory <tt>[[$FG_ROOT]]/Protocol</tt>. Always use the last version of this file, it will probably change after an update of the application.
# Connect your Android device to the local Wifi network and run the application. A dialog should appear with the IP of your device after few seconds.
# Run FlightGear with the following command, where
#* <code>--generic=socket,out,5,the-ip-of-your-android-device,5501,udp,andatlas --telnet=9000</code> (when using [[FGRun]], this can be set via <tt>Advanced > Input/Output</tt>. See figure.).
#: '''the-ip-of-your-android-device:''' the IP shown by your Android device.
#: '''5:''' the rate in Hz at which data is transmitted. Increasing this value will lead to smoother movements of the map and instruments.
# If you want to modify the instruments from your device (for example, frequencies, radials, switches...), enter the IP of your computer in the <tt>Settings</tt> menu of FlightGearMap.

[[File:The_advance_settings_of_FGRun_showing_a_configuration_of_two_devices_for_FlightGearMap.png|thumb|270px|Configuration using FGRun in the advance settings panel, sending data to two devices.]]
[[File:deployment_flightgearmap_3devices.png|thumb|270px|A possible deployment using three devices, a tablet and two mobile phones: instrument panel, comm panel and map.]]

It is strongly recommended to connect several Android devices. My preferred configuration includes a tablet on the table to show the instrument panel and two mobile phones, one to show the current position on a map and the other showing the communication panel. This can be achieved using this configuration:

<code>--generic=socket,out,10,192.168.127.127,5501,udp,andatlas --generic=socket,out,1,192.168.127.128,5501,udp,andatlas --telnet=9000</code>

Where 10,192.168.0.2 is the IP of my tablet receiving 10 updates per second, and 192.168.127.128 the IP of the phone showing the map receiving one position every second. The phone showing the communication panel doesn't receive anything and doesn't need a --generic line, but the computer's IP must be set in the Settings menu.

== Features ==

There are several panels available:

# Only a map showing the position of the aircraft
# A map and some basic controls, including a [[HSI]]
# A generic panel for single engine aircrafts, especially the [[Cessna 172P]]. You can configure some instruments of this panel using the <tt>Setting</tt> menu: the type of [http://en.wikipedia.org/wiki/Airspeed_indicator ASI], the type of heading indicator (simple heading, [[RMI]], [[HSI]]) and the additional instrument (manifold pressure or radar altimeter). The Radio Magnetic Indicator (RMI) shows the course to the NDB and NAV1 stations. The HSI is coupled to NAV1. The additional instrument appears when the RMI or the HSI are selected.
# A [[Cessna 337G Skymaster]] panel.

== Known Issues ==

# In the different heading indicators, you cannot calibrate the heading to match the magnetic compass when decoupled.
# In the [[HSI]], HDG warning flag and TO/FROM indicators are not included. The [[glideslope]] pointers are always visible, even if there is no ILS approach available.
# In the [http://en.wikipedia.org/wiki/Radar_altimeter radar altimeter], you can move the bug but there is no warning light when flying under the selected height.
# Some aircraft models, such as the [[Cessna 172]], filter the movement of the NAV indicators to smooth them. Most of the aircrafts do not filter these movements, and in these cases the smoothed values are not available. The provided andatlas.xml file uses unfiltered values, but if you fly mainly on the [[Cessna 172]], you might prefer modifying andatlas.xml to send the filtered properties instead of raw data.
# The [[DME]] instrument shows distance and ground speed to the selected station. You cannot select time to the station.
# The [[Cessna 337G Skymaster]] model includes lots of additional instruments that do not fit on the screen. The main missing switches are the magnet selectors and start engine buttons, but you will also miss the cowl flap switches. Some other instruments are not included, as the EGT and the fuel flow indicators.
# Since there are many different autopilot models and they are not compatible between them, they are not simulated. The [[Heading bug]] indicator is the only exception, if supported by your autopilot.

== Related content ==
* [[Atlas]]

== External links ==
* [https://play.google.com/store/apps/details?id=com.juanvvc.flightgear FlightGearMap] (Google Play)
* [http://www.flightgear.org/forums/viewtopic.php?f=31&t=16136 Forum topic]

[[Category:Software]]
[[fr:FlightGearMap]]

FlightGearMap

2013-05-18T19:45:02Z

Ludomo:

{{Infobox Software
| title = FlightGearMap
| image = FlightGearMap map and simple panel at KSFO.png
| alt = The map & simple panel at [[KSFO]].
| developedby = Juan Vera del Campo
| initialrelease = 1.0 (April 25, 2012)
| latestrelease = 1.5 (June 9, 2012)
| writtenin =
| os = Android
| developmentstatus = Active (2012-)
| license = [[GNU General Public License]]
| website = https://sites.google.com/site/lettersfromthecloud/follow-me/blog/flightgearmap
}}
[[File:FlightGearMap Cessna 172 panel.png|thumb|270px|The [[Cessna 172P]] panel.]]
'''FlightGearMap''' is an Android application that displays live [[FlightGear]] data in the form of some basic instruments and a moving map.

== Use ==
# On your computer, copy [https://raw.github.com/Juanvvc/FlightGearMap/master/andatlas.xml andatlas.xml] to the directory <tt>[[$FG_ROOT]]/Protocol</tt>. Always use the last version of this file, it will probably change after an update of the application.
# Connect your Android device to the local Wifi network and run the application. A dialog should appear with the IP of your device after few seconds.
# Run FlightGear with the following command, where
#* <code>--generic=socket,out,5,the-ip-of-your-android-device,5501,udp,andatlas --telnet=9000</code> (when using [[FGRun]], this can be set via <tt>Advanced > Input/Output</tt>. See figure.).
#: '''the-ip-of-your-android-device:''' the IP shown by your Android device.
#: '''5:''' the rate in Hz at which data is transmitted. Increasing this value will lead to smoother movements of the map and instruments.
# If you want to modify the instruments from your device (for example, frequencies, radials, switches...), enter the IP of your computer in the <tt>Settings</tt> menu of FlightGearMap.

[[File:The_advance_settings_of_FGRun_showing_a_configuration_of_two_devices_for_FlightGearMap.png|thumb|270px|Configuration using FGRun in the advance settings panel, sending data to two devices.]]

It is strongly recommended to connect several Android devices. My preferred configuration includes a tablet on the table to show the instrument panel and two mobile phones, one to show the current position on a map and the other showing the communication panel. This can be achieved using this configuration:

<code>--generic=socket,out,10,192.168.127.127,5501,udp,andatlas --generic=socket,out,1,192.168.127.128,5501,udp,andatlas --telnet=9000</code>

Where 10,192.168.0.2 is the IP of my tablet receiving 10 updates per second, and 192.168.127.128 the IP of the phone showing the map receiving one position every second. The phone showing the communication panel doesn't receive anything and doesn't need a --generic line, but the computer's IP must be set in the Settings menu.

== Features ==

There are several panels available:

# Only a map showing the position of the aircraft
# A map and some basic controls, including a [[HSI]]
# A generic panel for single engine aircrafts, especially the [[Cessna 172P]]. You can configure some instruments of this panel using the <tt>Setting</tt> menu: the type of [http://en.wikipedia.org/wiki/Airspeed_indicator ASI], the type of heading indicator (simple heading, [[RMI]], [[HSI]]) and the additional instrument (manifold pressure or radar altimeter). The Radio Magnetic Indicator (RMI) shows the course to the NDB and NAV1 stations. The HSI is coupled to NAV1. The additional instrument appears when the RMI or the HSI are selected.
# A [[Cessna 337G Skymaster]] panel.

== Known Issues ==

# In the different heading indicators, you cannot calibrate the heading to match the magnetic compass when decoupled.
# In the [[HSI]], HDG warning flag and TO/FROM indicators are not included. The [[glideslope]] pointers are always visible, even if there is no ILS approach available.
# In the [http://en.wikipedia.org/wiki/Radar_altimeter radar altimeter], you can move the bug but there is no warning light when flying under the selected height.
# Some aircraft models, such as the [[Cessna 172]], filter the movement of the NAV indicators to smooth them. Most of the aircrafts do not filter these movements, and in these cases the smoothed values are not available. The provided andatlas.xml file uses unfiltered values, but if you fly mainly on the [[Cessna 172]], you might prefer modifying andatlas.xml to send the filtered properties instead of raw data.
# The [[DME]] instrument shows distance and ground speed to the selected station. You cannot select time to the station.
# The [[Cessna 337G Skymaster]] model includes lots of additional instruments that do not fit on the screen. The main missing switches are the magnet selectors and start engine buttons, but you will also miss the cowl flap switches. Some other instruments are not included, as the EGT and the fuel flow indicators.
# Since there are many different autopilot models and they are not compatible between them, they are not simulated. The [[Heading bug]] indicator is the only exception, if supported by your autopilot.

== Related content ==
* [[Atlas]]

== External links ==
* [https://play.google.com/store/apps/details?id=com.juanvvc.flightgear FlightGearMap] (Google Play)
* [http://www.flightgear.org/forums/viewtopic.php?f=31&t=16136 Forum topic]

[[Category:Software]]
[[fr:FlightGearMap]]

File:The advance settings of FGRun showing a configuration of two devices for FlightGearMap.png

2013-05-18T19:42:37Z

Ludomo:

=={{int:filedesc}}==
{{Information
|description={{en|1=The advance settings of FGRun showing a configuration of two devices for FlightGearMap}}
|date=2013-05-18
|source={{own}}
|author=[[User:Ludomo|Ludomo]]
|permission=
|other_versions=
|other_fields=
}}

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

FlightGearMap

2013-05-18T19:40:47Z

Ludomo:

{{Infobox Software
| title = FlightGearMap
| image = FlightGearMap map and simple panel at KSFO.png
| alt = The map & simple panel at [[KSFO]].
| developedby = Juan Vera del Campo
| initialrelease = 1.0 (April 25, 2012)
| latestrelease = 1.5 (June 9, 2012)
| writtenin =
| os = Android
| developmentstatus = Active (2012-)
| license = [[GNU General Public License]]
| website = https://sites.google.com/site/lettersfromthecloud/follow-me/blog/flightgearmap
}}
[[File:FlightGearMap Cessna 172 panel.png|thumb|270px|The [[Cessna 172P]] panel.]]
'''FlightGearMap''' is an Android application that displays live [[FlightGear]] data in the form of some basic instruments and a moving map.

== Use ==
# On your computer, copy [https://raw.github.com/Juanvvc/FlightGearMap/master/andatlas.xml andatlas.xml] to the directory <tt>[[$FG_ROOT]]/Protocol</tt>. Always use the last version of this file, it will probably change after an update of the application.
# Connect your Android device to the local Wifi network and run the application. A dialog should appear with the IP of your device after few seconds.
# Run FlightGear with the following command, where
#* <code>--generic=socket,out,5,the-ip-of-your-android-device,5501,udp,andatlas --telnet=9000</code> (when using [[FGRun]], this can be set via <tt>Advanced > Input/Output</tt>. See figure.).
#: '''the-ip-of-your-android-device:''' the IP shown by your Android device.
#: '''5:''' the rate in Hz at which data is transmitted. Increasing this value will lead to smoother movements of the map and instruments.
# If you want to modify the instruments from your device (for example, frequencies, radials, switches...), enter the IP of your computer in the <tt>Settings</tt> menu of FlightGearMap.

[[File:fgrun-flightgearmap.png|thumb|270px|Configuration using FGRun in the advance settings panel, sending data to two devices.]]

It is strongly recommended to connect several Android devices. My preferred configuration includes a tablet on the table to show the instrument panel and two mobile phones, one to show the current position on a map and the other showing the communication panel. This can be achieved using this configuration:

<code>--generic=socket,out,10,192.168.127.127,5501,udp,andatlas --generic=socket,out,1,192.168.127.128,5501,udp,andatlas --telnet=9000</code>

Where 10,192.168.0.2 is the IP of my tablet receiving 10 updates per second, and 192.168.127.128 the IP of the phone showing the map receiving one position every second. The phone showing the communication panel doesn't receive anything and doesn't need a --generic line, but the computer's IP must be set in the Settings menu.

== Features ==

There are several panels available:

# Only a map showing the position of the aircraft
# A map and some basic controls, including a [[HSI]]
# A generic panel for single engine aircrafts, especially the [[Cessna 172P]]. You can configure some instruments of this panel using the <tt>Setting</tt> menu: the type of [http://en.wikipedia.org/wiki/Airspeed_indicator ASI], the type of heading indicator (simple heading, [[RMI]], [[HSI]]) and the additional instrument (manifold pressure or radar altimeter). The Radio Magnetic Indicator (RMI) shows the course to the NDB and NAV1 stations. The HSI is coupled to NAV1. The additional instrument appears when the RMI or the HSI are selected.
# A [[Cessna 337G Skymaster]] panel.

== Known Issues ==

# In the different heading indicators, you cannot calibrate the heading to match the magnetic compass when decoupled.
# In the [[HSI]], HDG warning flag and TO/FROM indicators are not included. The [[glideslope]] pointers are always visible, even if there is no ILS approach available.
# In the [http://en.wikipedia.org/wiki/Radar_altimeter radar altimeter], you can move the bug but there is no warning light when flying under the selected height.
# Some aircraft models, such as the [[Cessna 172]], filter the movement of the NAV indicators to smooth them. Most of the aircrafts do not filter these movements, and in these cases the smoothed values are not available. The provided andatlas.xml file uses unfiltered values, but if you fly mainly on the [[Cessna 172]], you might prefer modifying andatlas.xml to send the filtered properties instead of raw data.
# The [[DME]] instrument shows distance and ground speed to the selected station. You cannot select time to the station.
# The [[Cessna 337G Skymaster]] model includes lots of additional instruments that do not fit on the screen. The main missing switches are the magnet selectors and start engine buttons, but you will also miss the cowl flap switches. Some other instruments are not included, as the EGT and the fuel flow indicators.
# Since there are many different autopilot models and they are not compatible between them, they are not simulated. The [[Heading bug]] indicator is the only exception, if supported by your autopilot.

== Related content ==
* [[Atlas]]

== External links ==
* [https://play.google.com/store/apps/details?id=com.juanvvc.flightgear FlightGearMap] (Google Play)
* [http://www.flightgear.org/forums/viewtopic.php?f=31&t=16136 Forum topic]

[[Category:Software]]
[[fr:FlightGearMap]]

File:FlightGearMap Cessna 172 panel.png

2013-05-18T18:44:34Z

Ludomo: uploaded a new version of "File:FlightGearMap Cessna 172 panel.png"

{{File information
|Description = [[FlightGearMap]] with the [[Cessna 172P]] panel.
|Source = {{own}}
|Date = 2012-05-6
|Author = [[User:Gijs|Gijs]]
}}

== Licensing ==
{{self|cc-by-sa-3.0}}

[[Category:Screenshots]]

Custom Spain and Portugal scenery

2013-05-16T15:30:23Z

Ludomo: /* Improvements over the standard scenery */

Custom Spain and Portugal scenery

2013-05-16T15:28:57Z

Ludomo: /* Improved and new airports */

FlightGear as Bluetooth NMEA GPS provider

2013-05-16T12:23:23Z

Ludomo: /* Linux on the PC, Android on the mobile device */

[http://www.dixdouze.com/xample/index.php/airnavigation Air Navigation] is a real-time aircraft moving map navigation application for iPhone, iPad and Android by Xample. It contains free maps of the entire world as well as official IFR and VFR charts for many countries for an extra fee. It includes thousands of airports and waypoints, elevation information and features route planning and DIRECT-TO orders.

Air Navigation was developed to be used as a support instrument for general aviation in the real world. Nevertheless, it can be linked to flight simulators. As the authors say, "this is a great feature for training at home when bad weather prevents real flying! Also, simulator enthusiasts can add a full moving map system to their Sim setup."

Xample provides plug-ins to connect X-Plane and Microsoft Flight Simulator to Air Navigation. This article explains how connect FlighGear to Air Navigation Pro using Bluetooth.

= Linux on the PC, Android on the mobile device =

This guide uses Debian Linux. Other distributions such as Ubuntu should be similar.

Note: at the end of the guide, your Android device will believe that your PC is an external GPS unit. Hence, you can use any map application of your choice. Air Navigation is especially focused on aircrafts during real trips so it is exactly the real thing, but you can also try cheaper alternatives such as [https://play.google.com/store/apps/details?id=net.osmand OSMAnd], [https://play.google.com/store/apps/details?id=com.orux.oruxmaps OruxMaps] or Google Maps/Earth.

'''Preparations (only once):'''

* Install Air Navigation on the mobile device. This guide will use Air Navigation Pro (the paid version of Air Navigation)
* Install bluez on your PC, and a suitable GUI for your window manager (bluedevil for KDE, gnome-bluetooth for Gnome)

<pre>sudo apt-get install bluez-tools bluedevil</pre>

* Switch on Bluetooth communications on your mobile device and your PC
* Pair your mobile and your PC, if they are not paired yet. In Android: Configuration->Wireless->Bluetooth settings->Make device discoverable. In your PC, use a GUI such as BlueDevil (KDE) or gnome-bluetooth (Gnome) to locate and pair your device. You probably have to enter a PIN number on both devices.
* Install a Bluetooth GPS on your mobile device, such as [https://play.google.com/store/apps/details?id=googoo.android.btgps Bluetooth GPS] or [https://play.google.com/store/apps/details?id=com.turboirc.bgp.v1 Bluetooth GPS Provider]
* Allow mock locations in your phone: Settings->Applications->Development->Allow mock locations. Note: for security reasons, you probably want to switch mock locations off while not using FlighGear.

'''Setup (every time):'''

* Switch on Bluetooth communications on your mobile device and your PC. In the Android device, switch mock locations on if they are not active (Settings->Applications->Development->Allow mock locations)
* Register the PC as a GPS provider and listen to incoming communications. From the command line (the port number can be any port not in use. In this example port 23 is used, and this is usally a safe value):

<pre>sdptool add --channel 23 SP
sudo rfcomm listen rfcomm0 23</pre>

* Establish a connection from your mobile device to your PC: open the Bluetooth GPS application in your mobile device and connect to your PC. In the console, a "connection established" message must appear. If the mobile fails with a message similar to "Service Discovery failed", try to reboot your mobile device. If the PC fails with a message similar to "not authorized", check that you are running rfcomm as root (using sudo) Check if your Bluetooh GPS application sends mock locations to the system.
* If the connection is established, check permissions in /dev/rfcomm0 Usually, members of the group dialup are allowed to write /dev/rfcomm0. If the user running FlighGear is not in the dialup group, either add the user to the group or change the permissions of /dev/rfcomm0

<pre>sudo chmod 766 /dev/rfcomm0</pre>

Note: if necessary, the group of /dev/rfcomm0 can be set using udev rules: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/374782

* Run FlightGear using this option. If you run FlightGear from the launcher fgrun, you can set this option in the Advanced tabs, section "Input/Output" (Protocol: nmea, Medium: file, Direction: out, Hz: 5, File: /dev/rfcomm0)

<pre>--nmea=file,out,5,/dev/rfcomm0</pre>

* Open Air Navigation or any other map application supporting mock locations and enjoy.

[[:Category:Software]]

FlightGear as Bluetooth NMEA GPS provider

2013-05-16T12:19:41Z

Ludomo: Created page with "[http://www.dixdouze.com/xample/index.php/airnavigation Air Navigation] is a real-time aircraft moving map navigation application for iPhone, iPad and Android by Xample. It co..."

[http://www.dixdouze.com/xample/index.php/airnavigation Air Navigation] is a real-time aircraft moving map navigation application for iPhone, iPad and Android by Xample. It contains free maps of the entire world as well as official IFR and VFR charts for many countries for an extra fee. It includes thousands of airports and waypoints, elevation information and features route planning and DIRECT-TO orders.

Air Navigation was developed to be used as a support instrument for general aviation in the real world. Nevertheless, it can be linked to flight simulators. As the authors say, "this is a great feature for training at home when bad weather prevents real flying! Also, simulator enthusiasts can add a full moving map system to their Sim setup."

Xample provides plug-ins to connect X-Plane and Microsoft Flight Simulator to Air Navigation. This article explains how connect FlighGear to Air Navigation Pro using Bluetooth.

= Linux on the PC, Android on the mobile device =

This guide uses Debian Linux. Other distributions such as Ubuntu should be similar.

Note: at the end of the guide, your Android device will believe that your PC is an external GPS unit. Hence, you can use any map application of your choice. Air Navigation is especially focused on aircrafts during real trips so it is exactly the real thing, but you can also try cheapest alternatives such as [https://play.google.com/store/apps/details?id=net.osmand OSMAnd], [https://play.google.com/store/apps/details?id=com.orux.oruxmaps OruxMaps] or Google Maps/Earth.

'''Preparations (only once):'''

* Install Air Navigation on the mobile device. This guide will use Air Navigation Pro (the paid version of Air Navigation)
* Install bluez on your PC, and a suitable GUI for your window manager (bluedevil for KDE, gnome-bluetooth for Gnome)

<pre>sudo apt-get install bluez-tools bluedevil</pre>

* Switch on Bluetooth communications on your mobile device and your PC
* Pair your mobile and your PC, if they are not paired yet. In Android: Configuration->Wireless->Bluetooth settings->Make device discoverable. In your PC, use a GUI such as BlueDevil (KDE) or gnome-bluetooth (Gnome) to locate and pair your device. You probably have to enter a PIN number on both devices.
* Install a Bluetooth GPS on your mobile device, such as [https://play.google.com/store/apps/details?id=googoo.android.btgps Bluetooth GPS] or [https://play.google.com/store/apps/details?id=com.turboirc.bgp.v1 Bluetooth GPS Provider]
* Allow mock locations in your phone: Settings->Applications->Development->Allow mock locations. Note: for security reasons, you probably want to switch mock locations off while not using FlighGear.

'''Setup (every time):'''

* Switch on Bluetooth communications on your mobile device and your PC. In the Android device, switch mock locations on if they are not active (Settings->Applications->Development->Allow mock locations)
* Register the PC as a GPS provider and listen to incoming communications. From the command line (the port number can be any port not in use. In this example port 23 is used, and this is usally a safe value):

<pre>sdptool add --channel 23 SP
sudo rfcomm listen rfcomm0 23</pre>

* Establish a connection from your mobile device to your PC: open the Bluetooth GPS application in your mobile device and connect to your PC. In the console, a "connection established" message must appear. If the mobile fails with a message similar to "Service Discovery failed", try to reboot your mobile device. If the PC fails with a message similar to "not authorized", check that you are running rfcomm as root (using sudo) Check if your Bluetooh GPS application sends mock locations to the system.
* If the connection is established, check permissions in /dev/rfcomm0 Usually, members of the group dialup are allowed to write /dev/rfcomm0. If the user running FlighGear is not in the dialup group, either add the user to the group or change the permissions of /dev/rfcomm0

<pre>sudo chmod 766 /dev/rfcomm0</pre>

Note: if necessary, the group of /dev/rfcomm0 can be set using udev rules: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/374782

* Run FlightGear using this option. If you run FlightGear from the launcher fgrun, you can set this option in the Advanced tabs, section "Input/Output" (Protocol: nmea, Medium: file, Direction: out, Hz: 5, File: /dev/rfcomm0)

<pre>--nmea=file,out,5,/dev/rfcomm0</pre>

* Open Air Navigation or any other map application supporting mock locations and enjoy.

[[:Category:Software]]

Custom Spain and Portugal scenery

2013-04-02T11:40:43Z

Ludomo: /* IBE03 */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|Zones of the scenery]]

* IBE01 (Catalonia): http://dl.dropbox.com/u/13130748/IBE01.zip (260MB)
* IBE01-Objects. http://dl.dropbox.com/u/13130748/IBE01-Objects.zip (7MB) Additional buildings for IBE01.
* IBE02 (Balearic Islands): http://dl.dropbox.com/u/13130748/IBE02.zip (26MB)
* IBE03 (Valencia): http://dl.dropbox.com/u/13130748/IBE03.zip (144MB)
* IBE04 (Madrid): http://dl.dropbox.com/u/13130748/IBE04.zip (100MB)
* IBE05 (Basc Country, Aragon): http://dl.dropbox.com/u/13130748/IBE05.zip (230MB)
* IBE06 (Galicia, Asturias): http://dl.dropbox.com/u/13130748/IBE06.zip (166MB)
* IBE07 (Coast of Portugal): http://dl.dropbox.com/u/13130748/IBE07.zip (143MB)
* IBE08 (East Andalucia): http://dl.dropbox.com/u/13130748/IBE08.zip (190MB)
* IBE09 (West Andalucia, South of Portugal): http://dl.dropbox.com/u/13130748/IBE09.zip (130MB)
* IBE10 (East Portugal, Leon, Valladolid): http://dl.dropbox.com/u/13130748/IBE10.zip (230MB)
* Extra zone: GC: (Canary Islands): http://dl.dropbox.com/u/13130748/GC.zip (40MB)

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Improved and new airports ==

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

In addition, many airports have been improved and a others are completely new, including their buildings, runways, taxiways and navaids. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

=== IBE01 ===

* '''Barcelona - LEBL''': complete reconstruction of the old airport by ELS [http://flightgear.creatuforo.com/-temas30915.html#30915]. Tower by Codolar, Terminal 2 by NiTuS, Terminal 1 by ludomo [http://flightgear.creatuforo.com/-temas30923.html#30923]. The updated navaids for runways 07L and 02 need manual installation. See [http://flightgear.creatuforo.com/-temas31075.html#31075].
* '''Reus - LERS''': additional taxiways, all buildings modeled, area of the flight club included, notification points for VFR flights modeled. [http://flightgear.creatuforo.com/-temas30790.html#30790] Historic hangar for general aviation: --lat=41.144055 --lon=1.147302 --heading=70
* '''Lleida Alguaire - LEDA''': new airport. Runway, taxiways, platform and main buildings [http://flightgear.creatuforo.com/-temas30813.html#30813]. Platform: --lat=41.7290031 --lon=0.5407769 --heading=220
* '''La Cerdanya - LECN''': buildings by ludomo
* '''Igualada - LEIG''': generic buildings
* '''Avinyonet - LE01''': complete reconstruction of the airfield and new models for all buildings [http://flightgear.creatuforo.com/-temas30781.html#30781]. Platform: --lat=41.3681 --lon=1.7675 --heading=180
* '''Lleida Alfés - LEAT''': complete reconstruction of the airfield [http://flightgear.creatuforo.com/-temas30872.html#30872] Platform: --lat=41.54945190 --lon=0.65171187 --heading=150
* '''Huesca Benabarre - LENA''': new small airfield. Runway, taxiways, platform and all buildings. Platform: --lat=42.02227 --lon=0.47853

=== IBE02 ===

* '''Menorca - LEMH''': buildings by Codolar [http://flightgear.creatuforo.com/viewtopic.php?t=937]
* '''Ibiza - LEIB''': buildings by Lukas [http://lukashangar.jimdo.com/]:

=== IBE03 ===

* '''Valencia - LEVC''': buildings by Codolar
* '''Castellón Costa Azahar - LECS''': new airport. Runway, taxiways, platform and buildings [http://flightgear.creatuforo.com/-temas31018.html#31018] Not yet functional in real life. Platform: --lat=40.205735486 --lon=0.064476113 --heading=0
* '''Teruel PLATA - LETL''': new airport. Runway, taxiways, platform and buildings. Focused on space for long-term parking, recycling and maintenance of large aircrafts: "the biggest MRO platform in Europe" [http://www.aeropuertodeteruel.com/index.php/en/] Runway 36: --lat=40.4155 --lon=-1.2191 --heading=358

=== IBE04 ===

* '''Madrid Torrejon - LETO''': complete reconstruction of the airport [http://flightgear.creatuforo.com/-temas30793.html#30793]

=== IBE05 ===

* '''Bilbao - LEBB''': buildings by Antonio Rodriguez/blcyus [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14724]
* '''Huesca Pirineos - LEHC''': main buildings including the terminal and its area. By ludomo. Platform: --lat=42.02653 --lon=-0.32852 --heading=125

=== IBE08 ===

* '''Granada - LEGR''': buildings by Codolar
* '''Malaga - LEMG''': complete reconstruction of the airport by ELS. Main buildings by Boeing 787-8. [http://flightgear.creatuforo.com/-temas31146.html#31146]

=== GC ===

* '''Tenerife - GCXO''': buildings by Lukas
* '''La Palma - GCLA''': buildings by Lukas

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-02-10T23:03:26Z

Ludomo: /* IBE08 */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|Zones of the scenery]]

* IBE01 (Catalonia): http://dl.dropbox.com/u/13130748/IBE01.zip (260MB)
* IBE01-Objects. http://dl.dropbox.com/u/13130748/IBE01-Objects.zip (7MB) Additional buildings for IBE01.
* IBE02 (Balearic Islands): http://dl.dropbox.com/u/13130748/IBE02.zip (26MB)
* IBE03 (Valencia): http://dl.dropbox.com/u/13130748/IBE03.zip (144MB)
* IBE04 (Madrid): http://dl.dropbox.com/u/13130748/IBE04.zip (100MB)
* IBE05 (Basc Country, Aragon): http://dl.dropbox.com/u/13130748/IBE05.zip (230MB)
* IBE06 (Galicia, Asturias): http://dl.dropbox.com/u/13130748/IBE06.zip (166MB)
* IBE07 (Coast of Portugal): http://dl.dropbox.com/u/13130748/IBE07.zip (143MB)
* IBE08 (East Andalucia): http://dl.dropbox.com/u/13130748/IBE08.zip (190MB)
* IBE09 (West Andalucia, South of Portugal): http://dl.dropbox.com/u/13130748/IBE09.zip (130MB)
* IBE10 (East Portugal, Leon, Valladolid): http://dl.dropbox.com/u/13130748/IBE10.zip (230MB)
* Extra zone: GC: (Canary Islands): http://dl.dropbox.com/u/13130748/GC.zip (40MB)

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Improved and new airports ==

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

In addition, many airports have been improved and a others are completely new, including their buildings, runways, taxiways and navaids. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

=== IBE01 ===

* '''Barcelona - LEBL''': complete reconstruction of the old airport by ELS [http://flightgear.creatuforo.com/-temas30915.html#30915]. Tower by Codolar, Terminal 2 by NiTuS, Terminal 1 by ludomo [http://flightgear.creatuforo.com/-temas30923.html#30923]. The updated navaids for runways 07L and 02 need manual installation. See [http://flightgear.creatuforo.com/-temas31075.html#31075].
* '''Reus - LERS''': additional taxiways, all buildings modeled, area of the flight club included, notification points for VFR flights modeled. [http://flightgear.creatuforo.com/-temas30790.html#30790] Historic hangar for general aviation: --lat=41.144055 --lon=1.147302 --heading=70
* '''Lleida Alguaire - LEDA''': new airport. Runway, taxiways, platform and main buildings [http://flightgear.creatuforo.com/-temas30813.html#30813]. Platform: --lat=41.7290031 --lon=0.5407769 --heading=220
* '''La Cerdanya - LECN''': buildings by ludomo
* '''Igualada - LEIG''': generic buildings
* '''Avinyonet - LE01''': complete reconstruction of the airfield and new models for all buildings [http://flightgear.creatuforo.com/-temas30781.html#30781]. Platform: --lat=41.3681 --lon=1.7675 --heading=180
* '''Lleida Alfés - LEAT''': complete reconstruction of the airfield [http://flightgear.creatuforo.com/-temas30872.html#30872] Platform: --lat=41.54945190 --lon=0.65171187 --heading=150
* '''Huesca Benabarre - LENA''': new small airfield. Runway, taxiways, platform and all buildings. Platform: --lat=42.02227 --lon=0.47853

=== IBE02 ===

* '''Menorca - LEMH''': buildings by Codolar [http://flightgear.creatuforo.com/viewtopic.php?t=937]
* '''Ibiza - LEIB''': buildings by Lukas [http://lukashangar.jimdo.com/]:

=== IBE03 ===

* '''Castellón Costa Azahar - LECS''': new airport. Runway, taxiways, platform and buildings [http://flightgear.creatuforo.com/-temas31018.html#31018] Platform: --lat=40.205735486 --lon=0.064476113 --heading=0
* '''Valencia - LEVC''': buildings by Codolar

=== IBE04 ===

* '''Madrid Torrejon - LETO''': complete reconstruction of the airport [http://flightgear.creatuforo.com/-temas30793.html#30793]

=== IBE05 ===

* '''Bilbao - LEBB''': buildings by Antonio Rodriguez/blcyus [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14724]
* '''Huesca Pirineos - LEHC''': main buildings including the terminal and its area. By ludomo. Platform: --lat=42.02653 --lon=-0.32852 --heading=125

=== IBE08 ===

* '''Granada - LEGR''': buildings by Codolar
* '''Malaga - LEMG''': complete reconstruction of the airport by ELS. Main buildings by Boeing 787-8. [http://flightgear.creatuforo.com/-temas31146.html#31146]

=== GC ===

* '''Tenerife - GCXO''': buildings by Lukas
* '''La Palma - GCLA''': buildings by Lukas

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-01-31T09:12:12Z

Ludomo: /* IBE01 */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|Zones of the scenery]]

* IBE01 (Catalonia): http://dl.dropbox.com/u/13130748/IBE01.zip (260MB)
* IBE01-Objects. http://dl.dropbox.com/u/13130748/IBE01-Objects.zip (7MB) Additional buildings for IBE01.
* IBE02 (Balearic Islands): http://dl.dropbox.com/u/13130748/IBE02.zip (26MB)
* IBE03 (Valencia): http://dl.dropbox.com/u/13130748/IBE03.zip (144MB)
* IBE04 (Madrid): http://dl.dropbox.com/u/13130748/IBE04.zip (100MB)
* IBE05 (Basc Country, Aragon): http://dl.dropbox.com/u/13130748/IBE05.zip (230MB)
* IBE06 (Galicia, Asturias): http://dl.dropbox.com/u/13130748/IBE06.zip (166MB)
* IBE07 (Coast of Portugal): http://dl.dropbox.com/u/13130748/IBE07.zip (143MB)
* IBE08 (East Andalucia): http://dl.dropbox.com/u/13130748/IBE08.zip (190MB)
* IBE09 (West Andalucia, South of Portugal): http://dl.dropbox.com/u/13130748/IBE09.zip (130MB)
* IBE10 (East Portugal, Leon, Valladolid): http://dl.dropbox.com/u/13130748/IBE10.zip (230MB)
* Extra zone: GC: (Canary Islands): http://dl.dropbox.com/u/13130748/GC.zip (40MB)

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Improved and new airports ==

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

In addition, many airports have been improved and a others are completely new, including their buildings, runways, taxiways and navaids. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

=== IBE01 ===

* '''Barcelona - LEBL''': complete reconstruction of the old airport by ELS [http://flightgear.creatuforo.com/-temas30915.html#30915]. Tower by Codolar, Terminal 2 by NiTuS, Terminal 1 by ludomo [http://flightgear.creatuforo.com/-temas30923.html#30923]. The updated navaids for runways 07L and 02 need manual installation. See [http://flightgear.creatuforo.com/-temas31075.html#31075].
* '''Reus - LERS''': additional taxiways, all buildings modeled, area of the flight club included, notification points for VFR flights modeled. [http://flightgear.creatuforo.com/-temas30790.html#30790] Historic hangar for general aviation: --lat=41.144055 --lon=1.147302 --heading=70
* '''Lleida Alguaire - LEDA''': new airport. Runway, taxiways, platform and main buildings [http://flightgear.creatuforo.com/-temas30813.html#30813]. Platform: --lat=41.7290031 --lon=0.5407769 --heading=220
* '''La Cerdanya - LECN''': buildings by ludomo
* '''Igualada - LEIG''': generic buildings
* '''Avinyonet - LE01''': complete reconstruction of the airfield and new models for all buildings [http://flightgear.creatuforo.com/-temas30781.html#30781]. Platform: --lat=41.3681 --lon=1.7675 --heading=180
* '''Lleida Alfés - LEAT''': complete reconstruction of the airfield [http://flightgear.creatuforo.com/-temas30872.html#30872] Platform: --lat=41.54945190 --lon=0.65171187 --heading=150
* '''Huesca Benabarre - LENA''': new small airfield. Runway, taxiways, platform and all buildings. Platform: --lat=42.02227 --lon=0.47853

=== IBE02 ===

* '''Menorca - LEMH''': buildings by Codolar [http://flightgear.creatuforo.com/viewtopic.php?t=937]
* '''Ibiza - LEIB''': buildings by Lukas [http://lukashangar.jimdo.com/]:

=== IBE03 ===

* '''Castellón Costa Azahar - LECS''': new airport. Runway, taxiways, platform and buildings [http://flightgear.creatuforo.com/-temas31018.html#31018] Platform: --lat=40.205735486 --lon=0.064476113 --heading=0
* '''Valencia - LEVC''': buildings by Codolar

=== IBE04 ===

* '''Madrid Torrejon - LETO''': complete reconstruction of the airport [http://flightgear.creatuforo.com/-temas30793.html#30793]

=== IBE05 ===

* '''Bilbao - LEBB''': buildings by Antonio Rodriguez/blcyus [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14724]
* '''Huesca Pirineos - LEHC''': main buildings including the terminal and its area. By ludomo. Platform: --lat=42.02653 --lon=-0.32852 --heading=125

=== IBE08 ===

* '''Granada - LEGR''': buildings by Codolar

=== GC ===

* '''Tenerife - GCXO''': buildings by Lukas
* '''La Palma - GCLA''': buildings by Lukas

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-01-29T17:14:06Z

Ludomo: /* IBE05 */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|Zones of the scenery]]

* IBE01 (Catalonia): http://dl.dropbox.com/u/13130748/IBE01.zip (260MB)
* IBE01-Objects. http://dl.dropbox.com/u/13130748/IBE01-Objects.zip (7MB) Additional buildings for IBE01.
* IBE02 (Balearic Islands): http://dl.dropbox.com/u/13130748/IBE02.zip (26MB)
* IBE03 (Valencia): http://dl.dropbox.com/u/13130748/IBE03.zip (144MB)
* IBE04 (Madrid): http://dl.dropbox.com/u/13130748/IBE04.zip (100MB)
* IBE05 (Basc Country, Aragon): http://dl.dropbox.com/u/13130748/IBE05.zip (230MB)
* IBE06 (Galicia, Asturias): http://dl.dropbox.com/u/13130748/IBE06.zip (166MB)
* IBE07 (Coast of Portugal): http://dl.dropbox.com/u/13130748/IBE07.zip (143MB)
* IBE08 (East Andalucia): http://dl.dropbox.com/u/13130748/IBE08.zip (190MB)
* IBE09 (West Andalucia, South of Portugal): http://dl.dropbox.com/u/13130748/IBE09.zip (130MB)
* IBE10 (East Portugal, Leon, Valladolid): http://dl.dropbox.com/u/13130748/IBE10.zip (230MB)
* Extra zone: GC: (Canary Islands): http://dl.dropbox.com/u/13130748/GC.zip (40MB)

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Improved and new airports ==

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

In addition, many airports have been improved and a others are completely new, including their buildings, runways, taxiways and navaids. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

=== IBE01 ===

* '''Barcelona - LEBL''': complete reconstruction the airport by ELS [http://flightgear.creatuforo.com/-temas30915.html#30915]. Tower by Codolar, Terminal 2 by NiTuS, Terminal 1 by ludomo [http://flightgear.creatuforo.com/-temas30923.html#30923]. The updated navaids for runways 07L and 02 need manual installation. See [http://flightgear.creatuforo.com/-temas31075.html#31075].
* '''Reus - LERS''': additional taxiways, all buildings modeled, area of the flight club included, notification points for VFR flights modeled. [http://flightgear.creatuforo.com/-temas30790.html#30790] Historic hangar for general aviation: --lat=41.144055 --lon=1.147302 --heading=70
* '''Lleida Alguaire - LEDA''': new airport. Runway, taxiways, platform and buildings [http://flightgear.creatuforo.com/-temas30813.html#30813]. Platform: --lat=41.7290031 --lon=0.5407769 --heading=220
* '''La Cerdanya - LECN''': buildings by ludomo
* '''Igualada - LEIG''': generic buildings
* '''Avinyonet - LE01''': complete reconstruction of the airfield and new models for all buildings [http://flightgear.creatuforo.com/-temas30781.html#30781]. Platform: --lat=41.3681 --lon=1.7675 --heading=180
* '''Lleida Alfés - LEAT''': complete reconstruction of the airfield [http://flightgear.creatuforo.com/-temas30872.html#30872] Platform: --lat=41.54945190 --lon=0.65171187 --heading=150
* '''Huesca Benabarre - LENA''': new small airfield. Runway, taxiways, platform and buildings. Platform: --lat=42.02227 --lon=0.47853

=== IBE02 ===

* '''Menorca - LEMH''': buildings by Codolar [http://flightgear.creatuforo.com/viewtopic.php?t=937]
* '''Ibiza - LEIB''': buildings by Lukas [http://lukashangar.jimdo.com/]:

=== IBE03 ===

* '''Castellón Costa Azahar - LECS''': new airport. Runway, taxiways, platform and buildings [http://flightgear.creatuforo.com/-temas31018.html#31018] Platform: --lat=40.205735486 --lon=0.064476113 --heading=0
* '''Valencia - LEVC''': buildings by Codolar

=== IBE04 ===

* '''Madrid Torrejon - LETO''': complete reconstruction of the airport [http://flightgear.creatuforo.com/-temas30793.html#30793]

=== IBE05 ===

* '''Bilbao - LEBB''': buildings by Antonio Rodriguez/blcyus [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14724]
* '''Huesca Pirineos - LEHC''': main buildings including the terminal and its area. By ludomo. Platform: --lat=42.02653 --lon=-0.32852 --heading=125

=== IBE08 ===

* '''Granada - LEGR''': buildings by Codolar

=== GC ===

* '''Tenerife - GCXO''': buildings by Lukas
* '''La Palma - GCLA''': buildings by Lukas

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-01-28T16:40:13Z

Ludomo: /* Improved and new airports */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|Zones of the scenery]]

* IBE01 (Catalonia): http://dl.dropbox.com/u/13130748/IBE01.zip (260MB)
* IBE01-Objects. http://dl.dropbox.com/u/13130748/IBE01-Objects.zip (7MB) Additional buildings for IBE01.
* IBE02 (Balearic Islands): http://dl.dropbox.com/u/13130748/IBE02.zip (26MB)
* IBE03 (Valencia): http://dl.dropbox.com/u/13130748/IBE03.zip (144MB)
* IBE04 (Madrid): http://dl.dropbox.com/u/13130748/IBE04.zip (100MB)
* IBE05 (Basc Country, Aragon): http://dl.dropbox.com/u/13130748/IBE05.zip (230MB)
* IBE06 (Galicia, Asturias): http://dl.dropbox.com/u/13130748/IBE06.zip (166MB)
* IBE07 (Coast of Portugal): http://dl.dropbox.com/u/13130748/IBE07.zip (143MB)
* IBE08 (East Andalucia): http://dl.dropbox.com/u/13130748/IBE08.zip (190MB)
* IBE09 (West Andalucia, South of Portugal): http://dl.dropbox.com/u/13130748/IBE09.zip (130MB)
* IBE10 (East Portugal, Leon, Valladolid): http://dl.dropbox.com/u/13130748/IBE10.zip (230MB)
* Extra zone: GC: (Canary Islands): http://dl.dropbox.com/u/13130748/GC.zip (40MB)

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Improved and new airports ==

All airports haven been compiled using v850 of the database. This means that the taxiways of most airports are hugely improved over the current scenery available from terrasync, which uses v810 of the airport data. Unfortunately, FlightGear still uses v810 to calculate positions and navaids, and hence some of the airports will be apparently displaced up to a hundred meters. We are still doing our best to fix this, but aircrafts and buildings may still appear in wrong positions after selecting some small airports.

In addition, many airports have been improved and a others are completely new, including their buildings, runways, taxiways and navaids. Most of the new buildings are not yet uploaded to terrasync since it still uses the old positions and elevations from v810. Some of the new starting positions are already included in the scenery files.

=== IBE01 ===

* '''Barcelona - LEBL''': complete reconstruction the airport by ELS [http://flightgear.creatuforo.com/-temas30915.html#30915]. Tower by Codolar, Terminal 2 by NiTuS, Terminal 1 by ludomo [http://flightgear.creatuforo.com/-temas30923.html#30923]. The updated navaids for runways 07L and 02 need manual installation. See [http://flightgear.creatuforo.com/-temas31075.html#31075].
* '''Reus - LERS''': additional taxiways, all buildings modeled, area of the flight club included, notification points for VFR flights modeled. [http://flightgear.creatuforo.com/-temas30790.html#30790] Historic hangar for general aviation: --lat=41.144055 --lon=1.147302 --heading=70
* '''Lleida Alguaire - LEDA''': new airport. Runway, taxiways, platform and buildings [http://flightgear.creatuforo.com/-temas30813.html#30813]. Platform: --lat=41.7290031 --lon=0.5407769 --heading=220
* '''La Cerdanya - LECN''': buildings by ludomo
* '''Igualada - LEIG''': generic buildings
* '''Avinyonet - LE01''': complete reconstruction of the airfield and new models for all buildings [http://flightgear.creatuforo.com/-temas30781.html#30781]. Platform: --lat=41.3681 --lon=1.7675 --heading=180
* '''Lleida Alfés - LEAT''': complete reconstruction of the airfield [http://flightgear.creatuforo.com/-temas30872.html#30872] Platform: --lat=41.54945190 --lon=0.65171187 --heading=150
* '''Huesca Benabarre - LENA''': new small airfield. Runway, taxiways, platform and buildings. Platform: --lat=42.02227 --lon=0.47853

=== IBE02 ===

* '''Menorca - LEMH''': buildings by Codolar [http://flightgear.creatuforo.com/viewtopic.php?t=937]
* '''Ibiza - LEIB''': buildings by Lukas [http://lukashangar.jimdo.com/]:

=== IBE03 ===

* '''Castellón Costa Azahar - LECS''': new airport. Runway, taxiways, platform and buildings [http://flightgear.creatuforo.com/-temas31018.html#31018] Platform: --lat=40.205735486 --lon=0.064476113 --heading=0
* '''Valencia - LEVC''': buildings by Codolar

=== IBE04 ===

* '''Madrid Torrejon - LETO''': complete reconstruction of the airport [http://flightgear.creatuforo.com/-temas30793.html#30793]

=== IBE05 ===

* '''Bilbao - LEBB''': buildings by Antonio Rodriguez/blcyus [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14724]

=== IBE08 ===

* '''Granada - LEGR''': buildings by Codolar

=== GC ===

* '''Tenerife - GCXO''': buildings by Lukas
* '''La Palma - GCLA''': buildings by Lukas

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-01-28T16:30:42Z

Ludomo: /* Improvements over the standard scenery */

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* All airports have been compiled using v850 of apt.dat
* New airports are modeled, and many existing airports and airfields have been improved.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|Zones of the scenery]]

* IBE01 (Catalonia): http://dl.dropbox.com/u/13130748/IBE01.zip (260MB)
* IBE01-Objects. http://dl.dropbox.com/u/13130748/IBE01-Objects.zip (7MB) Additional buildings for IBE01.
* IBE02 (Balearic Islands): http://dl.dropbox.com/u/13130748/IBE02.zip (26MB)
* IBE03 (Valencia): http://dl.dropbox.com/u/13130748/IBE03.zip (144MB)
* IBE04 (Madrid): http://dl.dropbox.com/u/13130748/IBE04.zip (100MB)
* IBE05 (Basc Country, Aragon): http://dl.dropbox.com/u/13130748/IBE05.zip (230MB)
* IBE06 (Galicia, Asturias): http://dl.dropbox.com/u/13130748/IBE06.zip (166MB)
* IBE07 (Coast of Portugal): http://dl.dropbox.com/u/13130748/IBE07.zip (143MB)
* IBE08 (East Andalucia): http://dl.dropbox.com/u/13130748/IBE08.zip (190MB)
* IBE09 (West Andalucia, South of Portugal): http://dl.dropbox.com/u/13130748/IBE09.zip (130MB)
* IBE10 (East Portugal, Leon, Valladolid): http://dl.dropbox.com/u/13130748/IBE10.zip (230MB)
* Extra zone: GC: (Canary Islands): http://dl.dropbox.com/u/13130748/GC.zip (40MB)

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Improved and new airports ==

The scenery files already include many enhanced and new airports, including their buildings, runways, taxiways and navaids. Most of the new buildings are not yet uploaded to terrasync since it still uses old airport positions. Some of the new starting positions are already included in the scenery files.

=== IBE01 ===

* '''Barcelona - LEBL''': complete reconstruction the airport by ELS [http://flightgear.creatuforo.com/-temas30915.html#30915]. Tower by Codolar, Terminal 2 by NiTuS, Terminal 1 by ludomo [http://flightgear.creatuforo.com/-temas30923.html#30923]. The updated navaids for runways 07L and 02 need manual installation. See [http://flightgear.creatuforo.com/-temas31075.html#31075].
* '''Reus - LERS''': additional taxiways, all buildings modeled, area of the flight club included, notification points for VFR flights modeled. [http://flightgear.creatuforo.com/-temas30790.html#30790] Historic hangar for general aviation: --lat=41.144055 --lon=1.147302 --heading=70
* '''Lleida Alguaire - LEDA''': new airport. Runway, taxiways, platform and buildings [http://flightgear.creatuforo.com/-temas30813.html#30813]. Platform: --lat=41.7290031 --lon=0.5407769 --heading=220
* '''La Cerdanya - LECN''': buildings by ludomo
* '''Igualada - LEIG''': generic buildings
* '''Avinyonet - LE01''': complete reconstruction of the airfield and new models for all buildings [http://flightgear.creatuforo.com/-temas30781.html#30781]. Platform: --lat=41.3681 --lon=1.7675 --heading=180
* '''Lleida Alfés - LEAT''': complete reconstruction of the airfield [http://flightgear.creatuforo.com/-temas30872.html#30872] Platform: --lat=41.54945190 --lon=0.65171187 --heading=150
* '''Huesca Benabarre - LENA''': new small airfield. Runway, taxiways, platform and buildings. Platform: --lat=42.02227 --lon=0.47853

=== IBE02 ===

* '''Menorca - LEMH''': buildings by Codolar [http://flightgear.creatuforo.com/viewtopic.php?t=937]
* '''Ibiza - LEIB''': buildings by Lukas [http://lukashangar.jimdo.com/]:

=== IBE03 ===

* '''Castellón Costa Azahar - LECS''': new airport. Runway, taxiways, platform and buildings [http://flightgear.creatuforo.com/-temas31018.html#31018] Platform: --lat=40.205735486 --lon=0.064476113 --heading=0
* '''Valencia - LEVC''': buildings by Codolar

=== IBE04 ===

* '''Madrid Torrejon - LETO''': complete reconstruction of the airport [http://flightgear.creatuforo.com/-temas30793.html#30793]

=== IBE05 ===

* '''Bilbao - LEBB''': buildings by Antonio Rodriguez/blcyus [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14724]

=== IBE08 ===

* '''Granada - LEGR''': buildings by Codolar

=== GC ===

* '''Tenerife - GCXO''': buildings by Lukas
* '''La Palma - GCLA''': buildings by Lukas

[[Category:Scenery]]

Custom Spain and Portugal scenery

2013-01-28T16:27:41Z

Ludomo: Created page with "Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from..."

Custom scenery for the Iberian Peninsula is available. This area includes the continental territories of Spain, Portugal, Andorra and Gibraltar. The project uses the data from CORINE database for the land classes, OpenStreetMap for the landmass and roads and the enhanced altitudes by Jonathan de Ferranti.

== Improvements over the standard scenery ==

The following data sources have been used and processed to generate this scenery:

* landcover information from the CORINE program. See [[CORINE to materials mapping|here]] for the correspondence between CORINE and FG textures. Additional cities and details were manually added, specially in Catalonia.
* landmass and coastline updated according to OpenStreetMaps data,
* digital elevation data by Jonathan de Ferranti for Canary Islands, Gredos and Picos de Europa [http://www.viewfinderpanoramas.org/dem3.html],
* Road and rail information from OpenStreetMap [http://www.openstreetmap.org/].
* New airports and enhancements to many existing airports and airfields, including LEBL, LEDA, LETO, LECS.

The creation of the scenery is still an on-going project. Additional information and temporary data files can be found at [http://flightgear.creatuforo.com/-temas30521.html?sid=976c97a07264ae7e75b15fbee03373a0#30521 Vive FG!]

== Distribution ==

The scenery files has been divided in 10+1 zones for an efficient management of the data and updates.

[[File:Zones of the Iberian scenary.png|Zones of the scenery]]

* IBE01 (Catalonia): http://dl.dropbox.com/u/13130748/IBE01.zip (260MB)
* IBE01-Objects. http://dl.dropbox.com/u/13130748/IBE01-Objects.zip (7MB) Additional buildings for IBE01.
* IBE02 (Balearic Islands): http://dl.dropbox.com/u/13130748/IBE02.zip (26MB)
* IBE03 (Valencia): http://dl.dropbox.com/u/13130748/IBE03.zip (144MB)
* IBE04 (Madrid): http://dl.dropbox.com/u/13130748/IBE04.zip (100MB)
* IBE05 (Basc Country, Aragon): http://dl.dropbox.com/u/13130748/IBE05.zip (230MB)
* IBE06 (Galicia, Asturias): http://dl.dropbox.com/u/13130748/IBE06.zip (166MB)
* IBE07 (Coast of Portugal): http://dl.dropbox.com/u/13130748/IBE07.zip (143MB)
* IBE08 (East Andalucia): http://dl.dropbox.com/u/13130748/IBE08.zip (190MB)
* IBE09 (West Andalucia, South of Portugal): http://dl.dropbox.com/u/13130748/IBE09.zip (130MB)
* IBE10 (East Portugal, Leon, Valladolid): http://dl.dropbox.com/u/13130748/IBE10.zip (230MB)
* Extra zone: GC: (Canary Islands): http://dl.dropbox.com/u/13130748/GC.zip (40MB)

{|
| [[File:San Sebastian.png|x250px|San Sebastian Bay (ICAO: LESO)]]
| [[File:Camp de Tarragona.png|x250px|Costa Daurada (ICAO: LERS)]]
|-
| [http://en.wikipedia.org/wiki/San_Sebasti%C3%A1n Bay of La Concha] (Airport: LESO)
| [http://en.wikipedia.org/wiki/Costa_Daurada Costa Daurada] (Airport: LERS)
|}

This work is released under the terms of the Creative Commons Attribution-ShareAlike 3.0 Unported license [http://creativecommons.org/licenses/by-sa/3.0/].

== Improved and new airports ==

The scenery files already include many enhanced and new airports, including their buildings, runways, taxiways and navaids. Most of the new buildings are not yet uploaded to terrasync since it still uses old airport positions. Some of the new starting positions are already included in the scenery files.

=== IBE01 ===

* '''Barcelona - LEBL''': complete reconstruction the airport by ELS [http://flightgear.creatuforo.com/-temas30915.html#30915]. Tower by Codolar, Terminal 2 by NiTuS, Terminal 1 by ludomo [http://flightgear.creatuforo.com/-temas30923.html#30923]. The updated navaids for runways 07L and 02 need manual installation. See [http://flightgear.creatuforo.com/-temas31075.html#31075].
* '''Reus - LERS''': additional taxiways, all buildings modeled, area of the flight club included, notification points for VFR flights modeled. [http://flightgear.creatuforo.com/-temas30790.html#30790] Historic hangar for general aviation: --lat=41.144055 --lon=1.147302 --heading=70
* '''Lleida Alguaire - LEDA''': new airport. Runway, taxiways, platform and buildings [http://flightgear.creatuforo.com/-temas30813.html#30813]. Platform: --lat=41.7290031 --lon=0.5407769 --heading=220
* '''La Cerdanya - LECN''': buildings by ludomo
* '''Igualada - LEIG''': generic buildings
* '''Avinyonet - LE01''': complete reconstruction of the airfield and new models for all buildings [http://flightgear.creatuforo.com/-temas30781.html#30781]. Platform: --lat=41.3681 --lon=1.7675 --heading=180
* '''Lleida Alfés - LEAT''': complete reconstruction of the airfield [http://flightgear.creatuforo.com/-temas30872.html#30872] Platform: --lat=41.54945190 --lon=0.65171187 --heading=150
* '''Huesca Benabarre - LENA''': new small airfield. Runway, taxiways, platform and buildings. Platform: --lat=42.02227 --lon=0.47853

=== IBE02 ===

* '''Menorca - LEMH''': buildings by Codolar [http://flightgear.creatuforo.com/viewtopic.php?t=937]
* '''Ibiza - LEIB''': buildings by Lukas [http://lukashangar.jimdo.com/]:

=== IBE03 ===

* '''Castellón Costa Azahar - LECS''': new airport. Runway, taxiways, platform and buildings [http://flightgear.creatuforo.com/-temas31018.html#31018] Platform: --lat=40.205735486 --lon=0.064476113 --heading=0
* '''Valencia - LEVC''': buildings by Codolar

=== IBE04 ===

* '''Madrid Torrejon - LETO''': complete reconstruction of the airport [http://flightgear.creatuforo.com/-temas30793.html#30793]

=== IBE05 ===

* '''Bilbao - LEBB''': buildings by Antonio Rodriguez/blcyus [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14724]

=== IBE08 ===

* '''Granada - LEGR''': buildings by Codolar

=== GC ===

* '''Tenerife - GCXO''': buildings by Lukas
* '''La Palma - GCLA''': buildings by Lukas

[[Category:Scenery]]