8,567
edits
Using TerraGear: Difference between revisions
Jump to navigation
Jump to search
Update to FlightGear 2.8.0 and recent TerraGear builds
(Those tutorials were either already converted into wiki articles, or they belong to Howto:Create custom terrain) |
(Update to FlightGear 2.8.0 and recent TerraGear builds) |
||
| Line 43: | Line 43: | ||
==== Elevation data ==== | ==== Elevation data ==== | ||
The best elevation data currently available is from the Shuttle Radar Topography Mission (SRTM). There are two types of SRTM data: | The best worldwide elevation data currently available is from the Shuttle Radar Topography Mission (SRTM). There are two types of SRTM data: | ||
* Highly accurate 1-arcsecond resolution data, known as SRTM-1, for the USA | * Highly accurate 1-arcsecond resolution data, known as SRTM-1, for the USA | ||
* Less accurate 3-arcsecond data, known as SRTM-3, for the rest of the world. | * Less accurate 3-arcsecond data, known as SRTM-3, for the rest of the world. | ||
| Line 85: | Line 85: | ||
Genapts will create two sub-directories in your work directory: | Genapts will create two sub-directories in your work directory: | ||
* AirportArea/ | * <tt>AirportArea/</tt> | ||
* AirportObj/ | * <tt>AirportObj/</tt> | ||
These contain the definitions of the airport layout and any objects present (e.g. windsocks and beacons). | |||
These contain the definitions of the airport layout and any objects present (e.g. windsocks). | |||
==== Landuse data ==== | ==== Landuse data ==== | ||
| Line 94: | Line 93: | ||
The landuse data can be split into a number of different types: | The landuse data can be split into a number of different types: | ||
* '''Landmass''' separates the land from the sea. It can be used as a mask for all other data. The most commonly used is the VMAP0 Landmass, but GSHHS can also be used. When running fgfs-construct with <code>--ignore-landmass</code>, all input shapefiles will be taken into consideration, so no landmass mask is required then. | |||
* '''Landmass''' separates the land from the sea. It | |||
* '''Land use data:''' defines whether a piece of land is forest, urban, sand, lava, glacier etc. These are usually VMAP0 data, defined as polygons. | * '''Land use data:''' defines whether a piece of land is forest, urban, sand, lava, glacier etc. These are usually VMAP0 data, defined as polygons. | ||
* '''Line data:''' includes railroads, streams, roads. Typically VMAP0, but also Open Street Map for roads. | * '''Line data:''' includes railroads, streams, roads. Typically VMAP0, but also Open Street Map for roads. | ||
| Line 113: | Line 111: | ||
* the material type | * the material type | ||
Each shape-file corresponds with one of the material types defined in the materials.xml files. The mapping is pretty obvious. For example, v0_mixedcroppasturecover maps to MixedCropPastureCover. Note that the material types are case-sensitive, so it is a good idea to refer to the <tt>[[$FG ROOT]]/materials.xml</tt> | Each shape-file corresponds with one of the material types defined in the materials.xml files. The mapping is pretty obvious. For example, v0_mixedcroppasturecover maps to MixedCropPastureCover. Note that the material types are case-sensitive, so it is a good idea to refer to the <tt>[[$FG_ROOT]]/Materials/default/materials.xml file (<tt>[[$FG ROOT]]/materials.xml</tt> in FlightGear 2.6.0 and older) to hand so you can check. The exception is landmass, which - when used - MUST be mapped onto the type Default. | ||
Additionally, there are a number of optional arguments, to indicate the width of line data (for roads, streams, railways), how large to make point data (for towns) and how long the longest straight line is allowed to be. | Additionally, there are a number of optional arguments, to indicate the width of line data (for roads, streams, railways), how large to make point data (for towns) and how long the longest straight line is allowed to be. | ||