Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G


Jump to: navigation, search

TerraGear GUI

5,956 bytes added, 05:36, 23 June 2015
For GNU/Linux users: Add HelpLines for common Errors
{{Infobox Software
| title = TerraGear GUI
| image = TerraGearGUITerraGear GUI download San Francisco.png| alt = The download page with the San Francisco bay area selected.jpg
| developedby = Gijs de Rooy (original by Alex Park)
| initialrelease = March 24, 2009 (original)<br>March 27, 2010| latestrelease = 0.9.x (2012)
| writtenin = C++ (Qt)
| os = Windows, Linux, Mac OS X| website = httphttps://gitorioussourceforge.orgnet/terragearp/flightgear/fgscenery/terrageargui/ci/master/tree/
The '''GUI''' tool for '''[[TerraGear]]''' allows people to create [[scenery]] for [[FlightGear]] without using commandlines.
== Obtaining the GUI ==
You can either build the GUI [https://sourceforge.net/p/flightgear/fgscenery/terrageargui/ci/master/tree/ from source], or download a pre-compiled build:
* [http://liveries.flightgear.org/terrageargui/ Windows builds]
Please note that:
* you need to download/compile a recent version of [[TerraGear]] as well;
* for Windows users, you'll need to add three DLLs to you TerraGear GUI root directory:
** msvcp71.dll (see [[TerraGear_Installation_for_Windows]] to know how to get it)
** mscvr71.dll (see [[TerraGear_Installation_for_Windows]] to know how to get it)
** gdal12.dll (this can be retrieved from ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/terragear-cs-Win32-20101002.zip )
==== For GNU/Linux users ====
# Grab the sources and store it where you want:<br/><pre>git clone git://git.code.sf.net/p/flightgear/fgscenery/terrageargui</pre>
# Then go in the source:<br/><pre>cd terrageargui</pre>
# Create a build dir:<br/><pre>mkdir build && cd build</pre>
# Now build it:<br/><pre>qmake .. </pre> or<pre>qmake-qt4 ..</pre> then<pre>make</pre>
:::<sub>In case of ERRORS You may have to add the following via SYNAPTIC:</sub>
:::*<sub>for "/usr/lib/i386-linux-gnu/qt4/bin/uic: Command not found" add: libqt4-dev-bin</sub>
:::*<sub>for "QtGui/QApplication: No such file or directory" add: qt4-dev-tools</sub>
<br />
# You can now start it with:<br/><pre>"./bin/TerraGUI" or "./build/TerraGUI"</pre>
You're done!
== Using the GUI ==
=== Start ===
# Set the TerraGear directory, in which you'll find ogr-decode, fgfs-construct etcthe subdirectories bin/ and share/. TerraGear must be downloaded/build seperatly from the GUI!
# Set the project's directory. In this directory, all project related stuff will be stored throughout the process. You best choose an empty directory specific to your project.
# Set your FlightGear's root ([[$FG_ROOT]]). This is used to retrieve the list of available terrain materials.
=== HGT chop Download ===This will convert Specify boundaries in the boxes on the left, or select an area on the map.hgtNext select a source to download shapefiles for that area.zip files Note that OpenStreetMap only includes line date (roads, rivers), so you have downloaded earlier on 'll need some polygon data for the actual terrain. Both [[World Custom Scenery Project|Custom Scenery]] and converts them into a form [[CORINE]] (only Europe) provide that TerraGear can read. The GUI downloads and unpacks the package to your <tt>{project's directory}/data/</tt>.
=== Genapts ===What is scenery without airport in a flight simulator? If your tile does not contain any airports, Alternatively you can skip this part and continue with download shapefiles from [[#ogr-decode|ogr-decode]http://mapserver.flightgear.org/download.psp the mapserver by hand]. Unpack the downloaded file(s) to your <tt>{project's directory}/data/</tt>.
First create ==== Elevation data ====Elevation files are optional, but of course required to generate scenery with elevation offsets (even flat countries like the <tt>Netherlands need elevation data/Airports/</tt> directory, since no country is completely at sealevel. Then locate FlightGears <tt>aptSimply select a data source and then click the button to download the HGT files that span your specified area.datThe original source is usgs.gz</tt> filegov, which but a cleaned variant of the same data is usually available from fgx.ch (see [http://downloads.fgx.ch/geodata/data/srtm/README.txt the readme] for more information). The data will be saved in in <tt>[[$FG ROOT]]{project's directory}/Airportsdata/SRTM-3</tt> in the just created directory. Unpack the file before you continue.
Use the button to browse to the (unpacked) ===== By hand =====[[File:HGT tiles example.dat png|thumb|An example of HGT filetiles.]]Downloading tiles by hand is somewhat tricky. If you only want to create the your scenery for has a specific airport you can enter boundary of:{| class="wikitable"!! Min! max|-! Latitude| 33| 37|-! Longitude| -2| 2|}The GUI would display the ICAO name into the relevant fieldrange as <tt>N33W002-N37E002</tt>. If This means you do not enter any information have to download all tiles in any of the boxesthat range, which are all the tool will run through tiles as shown in the image on the entire aptright.dat Unpack the downloaded elevation file, which can take a long time(s) in <tt>{project's directory}/data/SRTM-3</tt>.
=== OGR Decode ===Now we need If you don't know how to decode find the shapefiles into TerraGear format, which we do boundaries range you can use Google Earth with OGR Decodethis KMZ file : [http://clemaez. After clicking the "Retrieve shapefiles" button, the left list will be populated fr/flightgear/grid_1_degree.kmz grid_1_degree.kmz]# Download KMZ file above# Open it with the shapefiles from your project's data directoryGoogle Earth and active it (if not yet active). On the right list A lot of red lines should appears# Zoom where you'll add want know the materials, per shapefile. Each single shapefile boundaries range# Click on the bottom leftboundary wanted and report the displayed value in TerraGear GUI. (i.e: if Google Earth value is "W9_N42", should have a material assigned report Minimum Latitude value "42" and Minimum Longitude value "-9")# Click on the top right. By dragging materials up&down, you can finetune boundary wanted and report the material assignmentsdisplayed value in TerraGear GUI.(i.e: if Google Earth value is "E6_N45", report Maximum Latitude value "45" and Maximum Longitude value "6")
=== Elevation ===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'''Warning: *_landmass MUST s directory}/data/SRTM-3</tt>). Make sure you do set the correct resolution! For the USA this can be mapped onto 1 arcsec, while the material Defaultrest of the world is provided in 3 arcsec resolution.'''
You === Airports ===What is scenery without airports in a flight simulator? If your area does not contain any airports, you can delete shapefiles skip this part and materials from the lists by doublecontinue with [[#ogr-clicking on themdecode|ogr-decode]].
=== FGFS Construct ===You can do two things now:The fgfs*'''Already-construct tool brings all your gathered data togethermade airports:''' use FlightGear's <tt>apt.dat.gz</tt> file, throws it which is usually in a washing machine and spits it out the otherside <tt>[[$FG ROOT]]/Airports/</tt>.*'''Home-made airports:''' if you created an airport in format ready for [[WorldEditor]], use with FlightGear. Click the "Update list" button to populate the field with all decodes shapefiles. In the list you select all types dat file that you'd like to include in your sceneryexported.
Then set Use the center button to browse to the .dat file of your choice. * '''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 tile''' only processes airports that are located on the given tileid.* '''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 ===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 bepopulated 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-created scenery areaclicking 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 width is only used on line-data (like roads, rivers and railroads). If you leave the radiusline width fields empty, a default width of 10 meters is used. ===== Example ===== {| class="wikitable"|-! Shapefile !! Material !! Line width (in meters)|-| osm_canal || Canal || 12|-| osm_motorway || Road-Motorway || 12|-| osm_primary || Road-Primary || 10|-| osm_rail || Railroad || 5|-| osm_river || Canal || 8|-| osm_secondary || Road-Secondary || 8|-| osm_stream || Stream || 3|-| osm_tertiary || Road-Tertiary || 6|-| osm_trunk || Road-Trunk || 18|} === Construct ===[[Image:TerraGearGUI.png|thumb|270px|The construction page.]]'''Note: with recent TerraGear builds, it is required to add the used material-names to the default_priorities.txt file.''' The tg-construct tool brings all your gathered data together, throws it in degreesa washing machine and spits it out the otherside in a format ready for use with FlightGear. Click the "Update list" button to populate the field with all decoded shapefiles. In the list you select all types that you'd like to include in your scenery.
After clicking the "Generate scenery" button, it may take a long time for TerraGear to finish. Depending on the size of the area you are creating the scenery for and the level of detail in your shapefiles. Simple and small sceneries will take a couple of minutes, where larger, more detailed areas can take over an hour! So trying new things on small areas first will save you a lot of time.
=== Running the scenery ===The folders and files in your project's <tt>output/</tt> directory are ready to use as scenery. You can set the [[$FG_SCENERY|scenery path ]] of FlightGear to this directory to check if the scenery is generated correctly.
== GUI development ==
The GUI is currently undergoing a complete rebuild and re-written in current source code can be retrieved [httphttps://qtsourceforge.nokia.com Qtnet/p/flightgear/fgscenery/terrageargui/ci/master/tree/ from SourceForge]. This will allow us to build the GUI on multiple OSes (Mac OS X, UNIX, Windows).
The current source code can be retrieved [http://gitorious.org/terragear/terrageargui/ from Gitorious]. Feel free to add feature requests and/or bug reportsto this page. Anyone interested in helping is invited to contact Gijs at the forum.
=== Requested features ===
* Creating automatically all needed folders for shapefiles and the decoded onesAlso see [[TerraGear scenery build server]] [[File:TerraGear-GUI-Remote-Mode. This includeds automated decoding all shapefiles in png|thumb|Prototyping a directory.remote mode for [[TerraGear]] as part of [[TerraGear GUI]]]] * Maybe error reports possible? So you get a message Multi-threading, so the GUI doesn't freeze when running a certain file isn'process [http://forum.flightgear.org/viewtopic.php?f=5&t found, =25688&p=235873&hilit=#p235623]* Support a new "Setup" page where people can decide if TerraGear is installed locally or remotely {{Not done}} * Add a certain path isn't setcommand handler abstraction so that commands can be easily run over SSH [http://doc. Right now it only appears in the console, but it's hard to read the fast scrolling textqt.digia.com/qtcreator-extending/utils-sshconnection.html] {{Not done}}* File retrieval would ideally be wrapped via SFTP {{Not done}} == External link ==* [http://forum.flightgear.org/viewtopic.php?f=5&t=7485 Forum topic]
[[Category:Scenery enhancement]]

Navigation menu