TerraGear GUI: Difference between revisions

379 bytes removed ,  14 January 2012
Update manual
mNo edit summary
(Update manual)
Line 17: Line 17:


==== For GNU/Linux users ====
==== For GNU/Linux users ====
# Grab the sources and store it where you want:<br/><pre>git clone git://gitorious.org/terragear-addons/terrageargui.git</pre>
# Grab the sources and store it where you want:<br/><pre>git clone git://gitorious.org/terragear-addons/terrageargui.git</pre>
# Then go in the source:<br/><pre>cd terrageargui</pre>
# Then go in the source:<br/><pre>cd terrageargui</pre>
Line 35: Line 34:


==== Downloading data ====
==== Downloading data ====
Specifying boundaries in the boxes on the left will download all [[World Custom Scenery Project|custom scenery]] shapefiles for that area. 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>.
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.
 
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>.


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. Unpack the downloaded elevation file(s) in <tt>{project's directory}/data/SRTM-30</tt>.
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. Unpack the downloaded elevation file(s) in <tt>{project's directory}/data/SRTM-30</tt>.
Line 52: Line 53:


=== OGR Decode ===
=== OGR Decode ===
Now we need to decode the shapefiles into TerraGear format, which we do with OGR Decode. After clicking the "Retrieve shapefiles" button, the left list will be populated with the shapefiles from your project's data directory. On the right list you'll add the materials, per shapefile. Each single shapefile on the left, should have a material assigned on the right.
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.
 
You'll have to run OGR Decode twice:
# with all shapefiles assigned to material "Default", if you don't do this all scenery will be water.
# with shapefile-specific materials. This is where you can try various materials in order to find the ones that best fit your area.


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 65: Line 62:
'''Note: with recent TerraGear builds, it is required to add the used material-names to the default_priorities.txt file.'''
'''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 "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. Note that you must select "Default" in order to generate anything other than water.
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 "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.
 
Then set the boundaries again (probably you want these to be the same as the ones you set on the start page), so the GUI can calculate the center of the to-be-created scenery area; and the radius (all in degrees).


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.
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.