240
edits
Michaelfavor (talk | contribs) m (copy edit) |
Michaelfavor (talk | contribs) m (copy edit) |
||
Line 2: | Line 2: | ||
[[Image:Terragearprocesschart.png|thumb|TerraGear Process Flow Chart]] | [[Image:Terragearprocesschart.png|thumb|TerraGear Process Flow Chart]] | ||
[[TerraGear]] is a software project which supports [[FlightGear]], by producing the | [[TerraGear]] is a software project which supports [[FlightGear]], by producing the files used by FlightGear to represent the elevation and texture of Earth, including airports, cities, fields, forests, rivers, roads and so on. The TerraGear software reads data files containing ground elevation, airport locations and layouts, geographical land-cover data, and more, and produces the scenery files used by FlightGear to represent the terrain of the world. | ||
For simplicity and convenience, most FlightGear users simply download the plug-and-play scenery files from the FlightGear scenery server, or use [[TerraSync]] to automatically download scenery automatically as needed. But there are a variety of reasons you might want to use TerraGear to produce your own terrain files, rather than downloading the standard FlightGear scenery. | |||
For instance, if you use [[TaxiDraw]] to modify/improve information about an [[:Category:Airports|airport]]'s taxiway/apron layout, you might wish to see how that modified airport would look in the scenery before deciding you're happy with the results. Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher-resultion vector data (vmap1, Tiger, osm) to get better roads/streams. For all these reasons, learning how to use TerraGear is a good idea. | |||
==Obtaining TerraGear== | ==Obtaining TerraGear== |
edits