Changes

TerraGear GUI

3,341 bytes added, 05:36, 23 June 2015
m
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.
| developedby = Gijs de Rooy (original by Alex Park)
| initialrelease = March 24, 2009 (original)<br>March 27, 2010
| latestrelease = 0.7 9.x (January 14, 2012)
| writtenin = C++ (Qt)
| os = Windows, Linux, Mac OS X
| website = httphttps://gitorioussourceforge.orgnet/terragear-addonsp/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 [httphttps://gitorioussourceforge.orgnet/terragear-addonsp/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://gitoriousgit.orgcode.sf.net/terragear-addonsp/flightgear/fgscenery/terrageargui.git</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!
=== 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.
==== Downloading data =Download ===Specifying Specify boundaries in the boxes on the left will , or select an area on the map. Next select a source to download all 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 sceneryCustom Scenery]] shapefiles for that area. Alternatively you can download shapefiles from and [http://mapserver.flightgear.org/download.psp the mapserver by hand[CORINE]]. Unpack the downloaded file(sonly Europe) provide that. The GUI downloads and unpacks the package to your <tt>{project's directory}/data/</tt>.
Elevation files are optional, but ofcourse required to generate scenery with elevation offsets (even flat countries like Alternatively you can download shapefiles from [http://mapserver.flightgear.org/download.psp the Netherlands need elevation data, since a country isn't 100% at sealevelmapserver by hand]. Unpack the downloaded elevation file(s) in to your <tt>{project's directory}/data/SRTM-30</tt>.
=== HGT chop = Elevation data ====This will convert Elevation files are optional, but of course required to generate scenery with elevation offsets (even flat countries like the .hgt.zip files you have downloaded earlier on and converts them into a form that TerraGear can readNetherlands need elevation data, since no country is completely at sealevel. Simply select a data source and then click the directory in which you unpacked button to download the elevation downloadsHGT files that span your specified area. Make sure you do set the correct resolution! For the USA this can be 1 arcsecThe original source is usgs.gov, while the rest but a cleaned variant of the world same data is provided 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>{project's directory}/data/SRTM-3 arcsec resolution</tt>.
=== Genapts == By hand =====[[File:HGT tiles example.png|thumb|An example of HGT file tiles.]]Downloading tiles by hand is somewhat tricky. If your scenery has a boundary of:{| class="wikitable"!! Min! max|-! Latitude| 33| 37|-! Longitude| -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. Unpack the downloaded elevation file(s) in <tt>{project's directory}/data/SRTM-3</tt>. If you don't know how to find the boundaries range you can use Google Earth with this KMZ file : [http://clemaez.fr/flightgear/grid_1_degree.kmz grid_1_degree.kmz]# Download KMZ file above# Open it with Google Earth and active it (if not yet active). A lot of red lines should appears# Zoom where you want know the boundaries range# Click on the bottom left boundary wanted and report the displayed value in TerraGear GUI. (i.e: if Google Earth value is "W9_N42", report Minimum Latitude value "42" and Minimum Longitude value "-9")# Click on the top right boundary wanted and report the displayed 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'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 ===What is scenery without airports in a flight simulator? If your tile area does not contain any airports, you can skip this part and continue with [[#ogr-decode|ogr-decode]].
You can do two things now:
*'''Already-made airports:''' Locate FlightGears use FlightGear's <tt>apt.dat.gz</tt> file, which is usually in <tt>[[$FG ROOT]]/Airports/</tt> in the just created directory. Unpack the file before you continue.*'''Home-made airports:''' if you created an airport in [[TaxiDrawWorldEditor]], just use the .dat file that you exported.
Use the button to browse to the .dat file of your choice. If you only want to create the scenery for a specific airport you can enter the ICAO name into the relevant field. If you do not enter any information in any of the boxes, the tool will run through the entire apt.dat file, which can take a long time when using the default apt.dat from FlightGear.
=== OGR Decode ===* '''All airports in area''' generates all the airports within the boundaries as set on the start tab.Now we need * '''Single airport''' to decode generate the shapefiles into TerraGear format, which we do with OGR Decodescenery for a specific airport. After clicking Enter the "Retrieve shapefiles" button, ICAO code into the left list will be populated with field. * '''Single tile''' only processes airports that are located on the shapefiles from your projectgiven tileid.* 's data directory''All airports in apt. On the right list youdat'''ll add the materials, per shapefile. Each single shapefile on tool will run through the leftentire apt.dat file, should have which can take a material assigned on long (!) time when using the rightdefault apt.dat from FlightGear.
You'll have === Materials ===Now we need to run decode the shapefiles into TerraGear format, which we do with OGR Decode twice:# with all . After clicking the "Retrieve shapefiles assigned to material "Default"button, if you don't do this all scenery the list will be water.# populated with shapefile-specific materialsthe shapefiles from your project's data directory. This is where you can The GUI will try various to assign fitting materials in order . If a shapefile has no material, you'll need to find the ones that best fit your areaassign 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!).
Line width is only used on line-data (like roads, rivers and railroads). If you leave the line width fields empty, a default width of 10 meters is used.
=== FGFS Construct == Example ====='''Note: with recent TerraGear builds, it is required to add the used material-names to the default_priorities.txt file.'''
The fgfs-construct tool brings all your gathered data together, throws it in a washing machine and spits it out the otherside in format ready for use with FlightGear. Click the {| class="Update listwikitable" button to populate the field with all decoded shapefiles. In the list you select all types that you'd like to include |-! Shapefile !! Material !! Line width (in your scenery. Note that you must select "Default" in order to generate anything other than water.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|}
Then set === Construct ===[[Image:TerraGearGUI.png|thumb|270px|The construction page.]]'''Note: with recent TerraGear builds, it is required to add the boundaries again (probably you want these used material-names to be the same as the ones you set on the start page)default_priorities.txt file.''' The tg-construct tool brings all your gathered data together, so throws it in a washing machine and spits it out the GUI can calculate the center of otherside in a format ready for use with FlightGear. Click the "Update list" button to-be-created scenery area; and populate the radius (field with all decoded shapefiles. In the list you select all types that you'd like to include in degrees)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. If you generated scenery, you must copy the files [ICAO].btg.gz file(s) from <tt>{project's directory}/work/AirportObj/</tt> to the corresponding directories in <tt>{project's directory}/output/Terrain</tt>.
== GUI development ==
The current source code can be retrieved [httphttps://gitorioussourceforge.orgnet/terragear-addonsp/flightgear/fgscenery/terrageargui/ci/master/tree/ from GitoriousSourceForge].
Feel free to add feature requests and/or bug reports to this page. Anyone interested in helping is invited to contact Gijs at the forum.
=== Requested features ===
* Visual map Also see [[TerraGear scenery build server]] [[File:TerraGear-GUI-Remote-Mode.png|thumb|Prototyping a remote mode for boundary selection[[TerraGear]] as part of [[TerraGear GUI]]]] * Multi-threading, so the GUI doesn't freeze when running a process [http://forum.flightgear.org/viewtopic.php?f=5&t=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 command handler abstraction so that commands can be easily run over SSH [http://doc.qt.digia.com/qtcreator-extending/utils-sshconnection.html] {{Not done}}* File retrieval would ideally be wrapped via SFTP {{Not done}}
== External links link ==* [http://wwwforum.flightgear.org/forums/viewtopic.php?f=5&t=7485 Forum topic]
[[Category:Scenery enhancement]]
[[Category:SoftwareTerraGear]]
652
edits