Putting it all together
We assume we calibrated Tangible Landscape setup with a model and now we want to run it.
-
In Scanning tab, input your DEM into Reference DEM and input the correct vertical exaggeration in Z-exaggeration field.
-
Press Start button at the very top.
-
In Output tab, click at the
button, which adds the scanned DEM in the Map Display.
The raster should be slightly changing with each new scan. -
Adjust any scanning parameters for optimal DEM, such as resolution, interpolation, smoothness or number of scans. The settings have impact on the speed, for reference, see Tangible Landscape plugin: Scanning.
-
To add contours, Pause scanning and in tab Analyses enter the name for the contour vector map and the desired contour interval. Resume scanning and press the associated
button to display the contours. -
Now you are ready to play with sand!
Tangible Landscape allows to use pre-defined geospatial analyses (such as water flow, contours, erosion), as well as to develop your own analyses. It uses GRASS GIS Python API to access GRASS GIS functionality.
Here we describe how to access the basic analyses.
-
In Analyses tab, click on Create new file with predefined analyses and create a new Python file (save it as e.g. myanalyses.py) somewhere on your computer.
-
Open it in a text editor and you should see already some import statements and commented Python code. These can be uncommented and adjusted. For example, if we uncomment:
def run_simwe(scanned_elev, env, **kwargs): analyses.simwe(scanned_elev=scanned_elev, depth='depth', rain_value=300, niterations=4, env=env)
This will activate waterflow (specifically, r.sim.water) computation. Once Tangible Landscape runs, after each scanning cycle a raster map 'depth' (you can change this name) is created.
-
You can add that raster map to the Map Display (look for Add raster map layer tool in Layer Manager toolbar.) During scanning you can change the code, for example to change the rain value to adjust the amount of water flow. Once the file is saved the change will be reflected.
See more details in Running analyses and developing workflows.