Changes

Jump to navigation Jump to search
268 bytes added ,  21:23, 25 April 2012
Update
Line 2: Line 2:  
| title                = TerraGear GUI
 
| title                = TerraGear GUI
 
| image                = TerraGearGUI.png
 
| image                = TerraGearGUI.png
 +
| alt                  = The contsruction page
 
| developedby          = Gijs de Rooy (original by Alex Park)
 
| developedby          = Gijs de Rooy (original by Alex Park)
 
| initialrelease        = March 24, 2009 (original)<br>March 27, 2010
 
| initialrelease        = March 24, 2009 (original)<br>March 27, 2010
| latestrelease = 0.9.x (March 31, 2012)
+
| latestrelease = 0.9.x (April 25, 2012)
 
| writtenin            = C++ (Qt)
 
| writtenin            = C++ (Qt)
 
| os                    = Windows, Linux, Mac OS X
 
| os                    = Windows, Linux, Mac OS X
Line 34: Line 35:     
==== Downloading data ====
 
==== Downloading data ====
Specify boundaries in the boxes on the left and select a source to download shapefiles for that area. Note that OpenStreetMap only includes line date (roads, rivers), so you'll need some polygon data for the actual terrain. Both [[World Custom Scenery Project|Custom Scenery]] and [[CORINE]] (only Europe) provide that.
+
Specify boundaries in the boxes on the left and select a source to download shapefiles for that area. Note that OpenStreetMap only includes line date (roads, rivers), so you'll need some polygon data for the actual terrain. Both [[World Custom Scenery Project|Custom Scenery]] and [[CORINE]] (only Europe) provide that. The GUI downloads and unpacks the package to your <tt>{project's directory}/data/</tt>.
    
Alternatively you can download shapefiles from [http://mapserver.flightgear.org/download.psp the mapserver by hand]. Unpack the downloaded file(s) to your <tt>{project's directory}/data/</tt>.
 
Alternatively you can download shapefiles from [http://mapserver.flightgear.org/download.psp the mapserver by hand]. Unpack the downloaded file(s) to your <tt>{project's directory}/data/</tt>.
Line 40: Line 41:  
===== Elevation =====
 
===== Elevation =====
 
[[File:HGT tiles example.png|thumb|An example of HGT file tiles.]]
 
[[File:HGT tiles example.png|thumb|An example of HGT file tiles.]]
Elevation files are optional, but ofcourse required to generate scenery with elevation offsets (even flat countries like the Netherlands need elevation data, since a country isn't 100% at sealevel. Elevation data (in the form of HGT files) is somewhat tricky, as you have to download each single tile by hand. If your scenery has a boundary of:
+
Elevation files are optional, but of course required to generate scenery with elevation offsets (even flat countries like the Netherlands need elevation data, since no country is completely at sealevel. Simply click the button to download the HGT files that span your specified area. They'll be saved in in <tt>{project's directory}/data/SRTM-3</tt
 +
 
 +
Downloading tiles by hand is somewhat tricky. If your scenery has a boundary of:
 
{| class="wikitable"
 
{| class="wikitable"
 
!
 
!
Line 54: Line 57:  
| 2
 
| 2
 
|}
 
|}
The GUI would display the range as <tt>N33W002-N37E002</tt>. This means you have to download all tiles in that range, which are all the tiles as shown in the image on the right.
+
The GUI would display the range as <tt>N33W002-N37E002</tt>. This means you have to download all tiles in that range, which are all the tiles as shown in the image on the right. Unpack the downloaded elevation file(s) in <tt>{project's directory}/data/SRTM-3</tt>.
 
  −
Unpack the downloaded elevation file(s) in <tt>{project's directory}/data/SRTM-30</tt>.
      
=== Elevation ===
 
=== Elevation ===
This will convert the .hgt.zip files you have downloaded earlier on and converts them into a form that TerraGear can read. Simply select the directory in which you placed the elevation downloads. Make sure you do set the correct resolution! For the USA this can be 1 arcsec, while the rest of the world is provided in 3 arcsec resolution.
+
This will convert the .hgt.zip files (that you have downloaded earlier) into a form that TerraGear can read. Simply select the directory in which you placed the elevation downloads (probably <tt>{project's directory}/data/SRTM-3</tt>). Make sure you do set the correct resolution! For the USA this can be 1 arcsec, while the rest of the world is provided in 3 arcsec resolution.
    
=== Airports ===
 
=== Airports ===
What is scenery without airports in a flight simulator? If your tile does not contain any airports, you can skip this part and continue with [[#ogr-decode|ogr-decode]].
+
What is scenery without airports in a flight simulator? If your area does not contain any airports, you can skip this part and continue with [[#ogr-decode|ogr-decode]].
    
You can do two things now:
 
You can do two things now:
*'''Already-made airports:''' Locate FlightGears <tt>apt.dat.gz</tt> file, which is usually in <tt>[[$FG ROOT]]/Airports/</tt> in the just created directory.
+
*'''Already-made airports:''' use FlightGear's <tt>apt.dat.gz</tt> file, which is usually in <tt>[[$FG ROOT]]/Airports/</tt>.
*'''Home-made airports:''' if you created an airport in [[TaxiDraw]] or [[WorldEditor]], just use the .dat file that you exported.
+
*'''Home-made airports:''' if you created an airport in [[TaxiDraw]] or [[WorldEditor]], use the .dat file that you exported.
   −
Use the button to browse to the .dat file of your choice. Select the format of your .dat file from the dropdown. TaxiDraw created 810 format, while WorldEditor does the 850 format.
+
Use the button to browse to the .dat file of your choice. Select the format of your .dat file from the dropdown. TaxiDraw created 810 format, while WorldEditor does the 850 format. Apt.dat.gz packaged with FlightGear is currently still in the 810 format.
    
* '''All airports in area''' generates all the airports within the boundaries as set on the start tab.
 
* '''All airports in area''' generates all the airports within the boundaries as set on the start tab.
 
* '''Single airport''' to generate the scenery for a specific airport. Enter the ICAO code into the field.  
 
* '''Single airport''' to generate the scenery for a specific airport. Enter the ICAO code into the field.  
 
* '''Single tile''' only processes airports that are located on the given tileid.
 
* '''Single tile''' only processes airports that are located on the given tileid.
* '''All airports in apt.da''' the tool will run through the entire apt.dat file, which can take a long (!) time when using the default apt.dat from FlightGear.
+
* '''All airports in apt.dat''' the tool will run through the entire apt.dat file, which can take a long (!) time when using the default apt.dat from FlightGear.
    
=== Materials ===
 
=== Materials ===
Now we need to decode the shapefiles into TerraGear format, which we do with OGR Decode. After clicking the "Retrieve shapefiles" button, the list will be populated with the shapefiles from your project's data directory. The GUI will try to assign fitting materials. IF a shapefile has no material, you'll need to assign it by hand. Each single shapefile must have a material.
+
Now we need to decode the shapefiles into TerraGear format, which we do with OGR/Shape Decode. After clicking the "Retrieve shapefiles" button, the list will be populated with the shapefiles from your project's data directory. The GUI will try to assign fitting materials. If a shapefile has no material, you'll need to assign it by hand. Each single shapefile must have a material.
    
You can delete shapefiles from the list by double-clicking on them. A single click on a material will allow you to edit it; to create custom materials that are not (yet) in materials.xml (do note that FlightGear will apply the default material to those landclasses, untill you create the material in materials.xml!).  
 
You can delete shapefiles from the list by double-clicking on them. A single click on a material will allow you to edit it; to create custom materials that are not (yet) in materials.xml (do note that FlightGear will apply the default material to those landclasses, untill you create the material in materials.xml!).  
Line 100: Line 101:     
=== Requested features ===
 
=== Requested features ===
* Automatic downloading and unzipping of data.
   
* Visual map for boundary selection.
 
* Visual map for boundary selection.
* Unlimited process time (currently 30 seconds per tile).
+
* Multi-threading, so the GUI doesn't freeze when running a process.
    
== External link ==
 
== External link ==

Navigation menu