Commit b0157017 authored by Nikos Alexandris's avatar Nikos Alexandris

Add caveats for bash functions

parent 312b0bce
......@@ -238,6 +238,12 @@ https://archive.org/details/GrassGisUnderTerminology/07_tyraster_example.mp4 "Ex
[screencast 8]:
https://archive.org/details/GrassGisUnderTerminology/08_tyraster_another_example.mp4 "Example of using `tyraster` [Screencast]"
###### One caveat
> GRASS GIS modules feature named input and output options, thus the
order doesn't matter. In this simple bash function, the order matters: the
raster map name must be provided first! The rest of options, then, is passed to
the `d.rast` command and their order does not matter.
#### Vector maps
Likewise, we can do for rendering vector maps:
......@@ -271,6 +277,12 @@ See this related [screencast][screencast 9] on using `tyvector`.
[screencast 9]:
https://archive.org/details/GrassGisUnderTerminology/09_tyvector_example.mp4 "Example of using `tyraster` [Screencast]"
###### Caveat
> Likewise to the `tyraster` function, the vector map name must be provided
first! The rest of options, then, is passed to the `d.vect` command and their
order does not matter.
#### Keep tidy
Using `tyraster` and `tyvector`, creates in time more and more PNG files. Here
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment