8,567
edits
Using TerraGear: Difference between revisions
Jump to navigation
Jump to search
m
→Obtaining and processing data: Link to CORINE
(default_priorities.txt is in the archive generated by Jenkins) |
m (→Obtaining and processing data: Link to CORINE) |
||
| Line 33: | Line 33: | ||
# The elevation of the land (provided by SRTM) | # The elevation of the land (provided by SRTM) | ||
# The location and layout of airports (provided by apt.dat or a custom .dat) | # The location and layout of airports (provided by apt.dat or a custom .dat) | ||
# Whether a given lat/lon is sea, land, city, forest, town, road, railway (provided by VMAP0, CORINE etc. or custom shapefiles) | # Whether a given lat/lon is sea, land, city, forest, town, road, railway (provided by VMAP0, [[CORINE]] etc. or custom shapefiles) | ||
This article describes how obtain and process each of these types of data in order, and bring it together for use by FlightGear. The order of these steps is important. For example, the airport data step needs the elevation data to determine the elevation of the airports and thus you should start with preparing elevation data. | This article describes how obtain and process each of these types of data in order, and bring it together for use by FlightGear. The order of these steps is important. For example, the airport data step needs the elevation data to determine the elevation of the airports and thus you should start with preparing elevation data. | ||