Difference between revisions of "Starting GRASS"

From GRASS-Wiki
Jump to: navigation, search
(updated)
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
* See http://grass.itc.it/grass60/manuals/html60_user/grass6.html or http://grass.itc.it/grass60/manuals/html60_user/helptext.html
+
=== What's next after installation? ===
* http://grass.itc.it/gdp/grass5tutor/HTML_en/c626.html contains advice on setting up a directory structure for GRASS projects. 
 
  
It advises:
+
First time users should explore the [http://grass.osgeo.org/documentation/first-time-users/ first steps tutorial] after installation.
 +
 
 +
=== Individual users ===
 +
 
 +
When using GRASS GIS as a single user on your PC, then the /grassdata/ directory may be best stored in your HOME directory.
 +
 
 +
'''GRASS can be invoked with''':
 +
* See also the {{cmd|grass6}} and {{cmd|helptext}} help pages.
 +
<pre>
 +
grass64 --help  # print options
 +
grass64  # start with graphical user interface, presetting the defaults from last session (stored in /home/user/.grassrc6 file)
 +
grass64 /home/user/grassdata/spearfish/david  # a specific mapset
 +
</pre>
 +
 
 +
=== Group users: shared network directory ===
 +
 
 +
Suggested directory structures:
 
<pre>
 
<pre>
 
  /data/            # as a shared directory for team projects with sysop managed group permissions
 
  /data/            # as a shared directory for team projects with sysop managed group permissions
  /data/grassdata  # grass GIS database  
+
                  # this shared directory may stay on a network server
  /data/grassdata/spearfish    # a shared spearfish Location
+
  /data/grassdata  # GRASS GIS database  
  /data/grassdata/spearfish/maria    # a team member's working mapset
+
  /data/grassdata/spearfish60          # a shared spearfish Location (a Location corresponds to a project)
  /data/grassdata/spearfish/david    # another member's working mapset
+
  /data/grassdata/spearfish60/maria    # a team member's mapset
 +
  /data/grassdata/spearfish60/david    # another member's mapset
 
</pre>
 
</pre>
  
For individual use, such a structure is not necessary.  One will need a database, and GRASS can create Location and Mapset directories. Your default database/location/mapset may be stored in your .grass6rc file.
+
Important: do NOT enable group-write access on the location/mapset directories. Let GRASS GIS manage it properly.
  
 
'''GRASS can be invoked with''':
 
'''GRASS can be invoked with''':
 +
* See also the {{cmd|grass6}} and {{cmd|helptext}} help pages.
 
<pre>
 
<pre>
grass --help  # print options
+
grass64 --help  # print options
grass   # start with defaults from .grassrc6
+
grass64   # start with defaults from .grassrc6
grass /data/grassdata/spearfish/david  # a specific mapset
+
grass64 /data/grassdata/spearfish/david  # a specific mapset
 
</pre>
 
</pre>
 +
 +
[[Category: Documentation]]
 +
[[Category: FAQ]]
 +
[[Category: Installation]]

Latest revision as of 13:46, 2 August 2013

What's next after installation?

First time users should explore the first steps tutorial after installation.

Individual users

When using GRASS GIS as a single user on your PC, then the /grassdata/ directory may be best stored in your HOME directory.

GRASS can be invoked with:

grass64 --help  # print options
grass64   # start with graphical user interface, presetting the defaults from last session (stored in /home/user/.grassrc6 file)
grass64 /home/user/grassdata/spearfish/david  # a specific mapset

Group users: shared network directory

Suggested directory structures:

 /data/            # as a shared directory for team projects with sysop managed group permissions
                   # this shared directory may stay on a network server
 /data/grassdata   # GRASS GIS database 
 /data/grassdata/spearfish60          # a shared spearfish Location (a Location corresponds to a project)
 /data/grassdata/spearfish60/maria    # a team member's mapset
 /data/grassdata/spearfish60/david    # another member's mapset

Important: do NOT enable group-write access on the location/mapset directories. Let GRASS GIS manage it properly.

GRASS can be invoked with:

grass64 --help  # print options
grass64   # start with defaults from .grassrc6
grass64 /data/grassdata/spearfish/david  # a specific mapset