The scenery I intend to generate will have the same generic data on infrastructure and landclass, but with updated airport data supplied by D-ECHO and the now available SRTM-1 mesh data. The vector infrastructure data will be extracted from OSM, so it will be also more current than the scenery now available in TerraSync.
For the moment, and using the procedures described in "Using Terragear" and "TerraGear Documentation" wiki page, I have just generated the mesh. In fact, three versions of it:
- SRTM-3 with hgtchop used by Terragear GUI (593kb of data)
- SRTM-3 with gdalchop (1,3Mb of data)
- SRTM-1 with gdalchop (5,3Mb of data)
The data I am referring is the one obtained after running the Terrafit tool. The last version is the one I will use for the final scenery output. It was obtained from the NASA Earthdata page (a login is required).
Concerning the OSM data, I will use the osm export page and the overpass API to extract the data and further process it in QGIS. Here I share just the layers I will use, obtained with the overpass-turbo page:
- Code: Select all
/*
This has been generated by the overpass-turbo wizard.
The original search was:
“highway=primary or highway=secondary or highway=track or water=river or water=stream or natural=coastline or natural=beach or landuse=reservoir or geological=outcrop or geological=volcanic_caldera_rim or geological=volcanic_vent or geological=volcanic_lava_field”
*/
[out:json][timeout:25];
// gather results
(
// query part for: “highway=primary”
node["highway"="primary"]({{bbox}});
way["highway"="primary"]({{bbox}});
relation["highway"="primary"]({{bbox}});
// query part for: “highway=secondary”
node["highway"="secondary"]({{bbox}});
way["highway"="secondary"]({{bbox}});
relation["highway"="secondary"]({{bbox}});
// query part for: “highway=track”
node["highway"="track"]({{bbox}});
way["highway"="track"]({{bbox}});
relation["highway"="track"]({{bbox}});
// query part for: “water=river”
node["water"="river"]({{bbox}});
way["water"="river"]({{bbox}});
relation["water"="river"]({{bbox}});
// query part for: “water=stream”
node["water"="stream"]({{bbox}});
way["water"="stream"]({{bbox}});
relation["water"="stream"]({{bbox}});
// query part for: “natural=coastline”
node["natural"="coastline"]({{bbox}});
way["natural"="coastline"]({{bbox}});
relation["natural"="coastline"]({{bbox}});
// query part for: “natural=beach”
node["natural"="beach"]({{bbox}});
way["natural"="beach"]({{bbox}});
relation["natural"="beach"]({{bbox}});
// query part for: “landuse=reservoir”
node["landuse"="reservoir"]({{bbox}});
way["landuse"="reservoir"]({{bbox}});
relation["landuse"="reservoir"]({{bbox}});
// query part for: “geological=outcrop”
node["geological"="outcrop"]({{bbox}});
way["geological"="outcrop"]({{bbox}});
relation["geological"="outcrop"]({{bbox}});
// query part for: “geological=volcanic_caldera_rim”
node["geological"="volcanic_caldera_rim"]({{bbox}});
way["geological"="volcanic_caldera_rim"]({{bbox}});
relation["geological"="volcanic_caldera_rim"]({{bbox}});
// query part for: “geological=volcanic_vent”
node["geological"="volcanic_vent"]({{bbox}});
way["geological"="volcanic_vent"]({{bbox}});
relation["geological"="volcanic_vent"]({{bbox}});
// query part for: “geological=volcanic_lava_field”
node["geological"="volcanic_lava_field"]({{bbox}});
way["geological"="volcanic_lava_field"]({{bbox}});
relation["geological"="volcanic_lava_field"]({{bbox}});
);
// print results
out body;
>;
out skel qt;
If I manage to get good results from this, then I will report the complete procedure, for a Ubuntu (linux) point of view, in the form of a tutorial. Maybe a series of video screen captures with vokoscreenNG...