|
|
@@ -2,7 +2,7 @@
|
|
|
|
|
|
<h2>SYNOPSIS</h2>
|
|
|
|
|
|
-<b>grass77</b> [<b>-h</b> | <b>-help</b> | <b>--help</b>] [<b>-v</b> | <b>--version</b>]
|
|
|
+<b>grass78</b> [<b>-h</b> | <b>-help</b> | <b>--help</b>] [<b>-v</b> | <b>--version</b>]
|
|
|
[<b>-c</b> | <b>-c geofile</b> | <b>-c EPSG:code[:datum_trans]</b>]
|
|
|
[<b>--text</b> | <b>--gtext</b> | <b>--gui</b>]
|
|
|
[[[<b><GISDBASE>/</b>]<b><LOCATION>/</b>]
|
|
|
@@ -94,13 +94,13 @@ user interface, as well as the desired mapset to work on.
|
|
|
|
|
|
<p>The startup program will remember both the desired user interface
|
|
|
and mapset. Thus, the next time the user runs GRASS, typing
|
|
|
-<em>grass77</em> (without any options) will start GRASS with the
|
|
|
+<em>grass78</em> (without any options) will start GRASS with the
|
|
|
previous settings for the user interface and mapset selected.
|
|
|
|
|
|
<p>If you specify a graphical user interface (<b>--gui</b>)
|
|
|
-the <em>grass77</em> program will try to verify that the system you
|
|
|
+the <em>grass78</em> program will try to verify that the system you
|
|
|
specified exists and that you can access it successfully. If any of
|
|
|
-these checks fail then <em>grass77</em> will automatically switch back
|
|
|
+these checks fail then <em>grass78</em> will automatically switch back
|
|
|
to the text user interface mode.
|
|
|
|
|
|
<h2>SAMPLE DATA</h2>
|
|
|
@@ -136,14 +136,14 @@ propagate).
|
|
|
|
|
|
<h3>User Interface Environment Variable</h3>
|
|
|
|
|
|
-<p>The <em>grass77</em> program will check for the existence of an
|
|
|
+<p>The <em>grass78</em> program will check for the existence of an
|
|
|
environment variable called GRASS_GUI which indicates the type of user
|
|
|
interface for GRASS to use. If this variable is not set
|
|
|
-when <em>grass77</em> is run, then it will be created and then saved
|
|
|
+when <em>grass78</em> is run, then it will be created and then saved
|
|
|
in the <tt>$HOME/.grass7/rc</tt> file for the next time GRASS is
|
|
|
run. It can be set to <tt>text</tt>, <tt>gtext</tt> or <tt>gui</tt>.
|
|
|
|
|
|
-<p>There is an order of precedence in the way <em>grass77</em>
|
|
|
+<p>There is an order of precedence in the way <em>grass78</em>
|
|
|
determines the user interface to use. The following is the hierarchy
|
|
|
from highest precedence to lowest.
|
|
|
<ol>
|
|
|
@@ -219,49 +219,49 @@ script. The script file must have its executable bit set.
|
|
|
<p>The following are some examples of how you could start GRASS
|
|
|
|
|
|
<dl>
|
|
|
-<dt><b>grass77</b>
|
|
|
+<dt><b>grass78</b>
|
|
|
<dd> Start GRASS using the default user interface. The user will be
|
|
|
prompted to choose the appropriate location and mapset.
|
|
|
|
|
|
-<dt><b>grass77 --gui</b>
|
|
|
+<dt><b>grass78 --gui</b>
|
|
|
<dd> Start GRASS using the graphical user interface. The user will be
|
|
|
prompted to choose the appropriate location and mapset.
|
|
|
|
|
|
-<dt><b>grass77 --text</b>
|
|
|
+<dt><b>grass78 --text</b>
|
|
|
<dd> Start GRASS using the text-based user interface. Appropriate
|
|
|
location and mapset must be set by environmental variables (see
|
|
|
examples below) otherwise taken from the last GRASS session.</dd>
|
|
|
|
|
|
-<dt><b>grass77 --gtext</b>
|
|
|
+<dt><b>grass78 --gtext</b>
|
|
|
<dd> Start GRASS using the text-based user interface. The user will be
|
|
|
prompted to choose the appropriate location and mapset.
|
|
|
|
|
|
-<dt><b>grass77 $HOME/grassdata/spearfish70/user1</b>
|
|
|
+<dt><b>grass78 $HOME/grassdata/spearfish70/user1</b>
|
|
|
<dd> Start GRASS using the default user interface and automatically
|
|
|
launch into the given mapset, bypassing the mapset selection menu.
|
|
|
|
|
|
-<dt><b>grass77 --gui -</b>
|
|
|
+<dt><b>grass78 --gui -</b>
|
|
|
<dd> Start GRASS using the graphical user interface and try to
|
|
|
obtain the location and mapset from environment variables.
|
|
|
|
|
|
-<dt><b>grass77 -c EPSG:4326 $HOME/grassdata/mylocation</b>
|
|
|
+<dt><b>grass78 -c EPSG:4326 $HOME/grassdata/mylocation</b>
|
|
|
<dd> Creates a new GRASS location with EPSG code 4326 (latitude-longitude, WGS84)
|
|
|
in the specified GISDBASE
|
|
|
|
|
|
-<dt><b>grass77 -c EPSG:5514:3 $HOME/grassdata/mylocation</b>
|
|
|
+<dt><b>grass78 -c EPSG:5514:3 $HOME/grassdata/mylocation</b>
|
|
|
<dd> Creates a new GRASS location with EPSG code 5514 (S-JTSK / Krovak
|
|
|
East North - SJTSK) with datum transformation parameters used in
|
|
|
Czech Republic in the specified GISDBASE
|
|
|
|
|
|
-<dt><b>grass77 -c XY $HOME/grassdata/gnomonic --exec g.proj -c proj4='+proj=gnom +lat_0=90 +lon_0=-50'</b>
|
|
|
+<dt><b>grass78 -c XY $HOME/grassdata/gnomonic --exec g.proj -c proj4='+proj=gnom +lat_0=90 +lon_0=-50'</b>
|
|
|
<dd> Creates a new GRASS location from PROJ definition string
|
|
|
(here: <a href="https://proj4.org/operations/projections/gnom.html">gnomonic</a>)
|
|
|
in the specified GISDBASE
|
|
|
|
|
|
-<dt><b>grass77 -c myvector.shp $HOME/grassdata/mylocation</b>
|
|
|
+<dt><b>grass78 -c myvector.shp $HOME/grassdata/mylocation</b>
|
|
|
<dd> Creates a new GRASS location based on georeferenced Shapefile
|
|
|
|
|
|
-<dt><b>grass77 -c myraster.tif $HOME/grassdata/mylocation</b>
|
|
|
+<dt><b>grass78 -c myraster.tif $HOME/grassdata/mylocation</b>
|
|
|
<dd> Creates a new GRASS location based on georeferenced GeoTIFF file
|
|
|
</dl>
|
|
|
|
|
|
@@ -278,26 +278,26 @@ Creating a new Location based on a geodata file's projection (<b>-c</b>)
|
|
|
and exit (<b>-e</b>) immediately:
|
|
|
|
|
|
<div class="code"><pre>
|
|
|
-grass77 -c elevation.tiff -e /path/to/grassdata/test1/
|
|
|
+grass78 -c elevation.tiff -e /path/to/grassdata/test1/
|
|
|
</pre></div>
|
|
|
|
|
|
Linking external raster data to PERMANENT Mapset:
|
|
|
|
|
|
<div class="code"><pre>
|
|
|
-grass77 /path/to/grassdata/test1/PERMANENT/ --exec r.external input=basins.tiff output=basins
|
|
|
-grass77 /path/to/grassdata/test1/PERMANENT/ --exec r.external input=elevation.tiff output=elevation
|
|
|
+grass78 /path/to/grassdata/test1/PERMANENT/ --exec r.external input=basins.tiff output=basins
|
|
|
+grass78 /path/to/grassdata/test1/PERMANENT/ --exec r.external input=elevation.tiff output=elevation
|
|
|
</pre></div>
|
|
|
|
|
|
Get statistics for one raster map:
|
|
|
|
|
|
<div class="code"><pre>
|
|
|
-grass77 /path/to/grassdata/test1/PERMANENT/ --exec r.univar map=elevation
|
|
|
+grass78 /path/to/grassdata/test1/PERMANENT/ --exec r.univar map=elevation
|
|
|
</pre></div>
|
|
|
|
|
|
Compare the rasters visually:
|
|
|
|
|
|
<div class="code"><pre>
|
|
|
-grass77 /path/to/grassdata/test1/PERMANENT/ --exec g.gui.mapswipe first=elevation second=basins
|
|
|
+grass78 /path/to/grassdata/test1/PERMANENT/ --exec g.gui.mapswipe first=elevation second=basins
|
|
|
</pre></div>
|
|
|
|
|
|
<h4>Execution of shell and Python scripts instead of single commands</h4>
|
|
|
@@ -308,7 +308,7 @@ exec interface.
|
|
|
<b>Shell script example:</b> the command to execute a shell script might be:
|
|
|
|
|
|
<div class="code"><pre>
|
|
|
-grass77 /path/to/grassdata/test1/PERMANENT/ --exec sh test.sh
|
|
|
+grass78 /path/to/grassdata/test1/PERMANENT/ --exec sh test.sh
|
|
|
</pre></div>
|
|
|
|
|
|
A very simple bash script ("test.sh") may look like this:
|
|
|
@@ -325,7 +325,7 @@ r.info elevation
|
|
|
<b>Python script example:</b> the command to execute a Python script might be:
|
|
|
|
|
|
<div class="code"><pre>
|
|
|
-grass77 /path/to/grassdata/test1/PERMANENT/ --exec python test.py
|
|
|
+grass78 /path/to/grassdata/test1/PERMANENT/ --exec python test.py
|
|
|
</pre></div>
|
|
|
|
|
|
A very simple Python script ("test.py") may look like this:
|
|
|
@@ -356,19 +356,19 @@ projection coordinate reference system (CRS) and simultaneously starting
|
|
|
computation in a shell script:
|
|
|
|
|
|
<div class="code"><pre>
|
|
|
-grass77 --tmp-location elevation.tiff --exec test.sh
|
|
|
+grass78 --tmp-location elevation.tiff --exec test.sh
|
|
|
</pre></div>
|
|
|
|
|
|
The same, but using an EPSG code and a Python script:
|
|
|
|
|
|
<div class="code"><pre>
|
|
|
-grass77 --tmp-location EPSG:3358 --exec test.py
|
|
|
+grass78 --tmp-location EPSG:3358 --exec test.py
|
|
|
</pre></div>
|
|
|
|
|
|
Finally, for special cases, we can create an XY location without any CRS:
|
|
|
|
|
|
<div class="code"><pre>
|
|
|
-grass77 --tmp-location XY --exec test.py
|
|
|
+grass78 --tmp-location XY --exec test.py
|
|
|
</pre></div>
|
|
|
|
|
|
Temporary location is automatically deleted after computation,
|
|
|
@@ -380,14 +380,14 @@ A single command can be also executed, e.g. to examine properties of the
|
|
|
temporary location:
|
|
|
|
|
|
<div class="code"><pre>
|
|
|
-grass77 --tmp-location EPSG:3358 --exec g.proj -p
|
|
|
+grass78 --tmp-location EPSG:3358 --exec g.proj -p
|
|
|
</pre></div>
|
|
|
|
|
|
A temporary XY location with single command is useful, e.g. to show
|
|
|
help text of a module:
|
|
|
|
|
|
<div class="code"><pre>
|
|
|
-grass77 --tmp-location XY --exec r.neighbors --help
|
|
|
+grass78 --tmp-location XY --exec r.neighbors --help
|
|
|
</pre></div>
|
|
|
|
|
|
<h4>Troubleshooting</h4>
|
Markus Neteler