[GRASSweb-list]markus: web firsttime.html,1.13,1.14 general.html,1.10,1.11

grass at intevation.de grass at intevation.de
Mon Jun 10 05:09:03 EDT 2002

Author: markus

Update of /grassrepository/web
In directory doto:/tmp/cvs-serv14965

Modified Files:
	firsttime.html general.html 
Log Message:
info added, urls fixed

Index: firsttime.html
RCS file: /grassrepository/web/firsttime.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- firsttime.html	13 May 2002 13:59:54 -0000	1.13
+++ firsttime.html	10 Jun 2002 09:09:01 -0000	1.14
@@ -35,6 +35,7 @@
 <li><a href=#softgrass>Where can I download GRASS software?</a>
 <li><a href=#importgrass>How can I get my data into GRASS?</a>
 <li><a href=#docgrass>Where can I find documentation on GRASS?</a>
+<li><a href=#location>What are LOCATIONs and MAPSETs?</a>
 <li><a href=#tutograss>Are there GRASS tutorials and sample data?</a>
 <li><a href=#progrgrass>I know GRASS already and want to program within
 <br>the GRASS environment</a>
@@ -146,7 +147,35 @@
 If you have additional documents for the GDP, please send a mail to 
-<a href="mailto:neteler at itc.it"><em>Markus Neteler</em></a>. 
+<a href="mailto:weblist at grass.itc.it"><em>GRASS web page team</em></a>. 
+<a NAME="location"></a>
+<h3>What are LOCATIONs and MAPSETs?</h3>
+A LOCATION is some geographic extent of interest that contains data sets
+that [should] all be in the same coordinate system. Every location has a
+PERMANENT directory which stores some basic information about the whole
+location, and is a good place to park base files.  You can think of a
+location as a data library for a region of interest.
+In a MAPSET  you can organize GIS maps thematically or geographically or by
+project or whatever. Every GRASS session runs under the name of a MAPSET. A
+MAPSET may be a geographical subset or as large as the parent LOCATION.
+Technically they are subdirectories under any location. In a networked
+environment with several users working within the same location, mapsets
+play a special role. Users may only select (and thus modify) a mapset that
+they own (i.e., have created). However, data in all mapsets for a given
+location can be read by anyone (unless prevented by UNIX file permissions).
+The "PERMANENT" mapset usually contains the read-only base maps like the
+elevation model, while the other locations are readable and writable by
+their owners. The "PERMANENT" mapset also contains some information about
+the location itself that is not found in other mapsets (projection info
+etc.), thus it must exist in every location.
+Putting LOCATIONs on a central server, a team can work inside this project
+database (usually NFS is used).
 <a NAME="tutograss"></a>

Index: general.html
RCS file: /grassrepository/web/general.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- general.html	13 May 2002 13:59:54 -0000	1.10
+++ general.html	10 Jun 2002 09:09:01 -0000	1.11
@@ -108,6 +108,16 @@
 lets users quickly and easily view, manipulate, and use data. Nearly all
 of the programs available in GRASS are available in the GUI, with the standard
 command line also available, giving users all of the functionality of GRASS.&nbsp;</font>
+<h3><font face="Arial,Helvetica">GRASS and network support for team</font></h3>
+GRASS supports work groups through it's <a href=firsttime.html#location>LOCATION/MAPSET concept</a> which can be
+set up on NFS (Network File System). Keeping LOCATIONs with their underlying 
+MAPSETs on a central server, a team can simultaniously work in the same
+project database.
+[see also:  <a href=gdp/tutorial/grass_info_deu.html><img src=images/dflagge.gif></a>]
 <hr size=4 no shade><font face="Arial,Helvetica"></font>
 <p><a NAME="platforms"></a>

More information about the grass-web mailing list