doc: continue renaming location to project in documentation (#3570)

display/d.barscale/d.barscale.html

@@ -10,8 +10,8 @@ <h2>DESCRIPTION</h2>
 
 <h2>NOTE</h2>
 
-<em>d.barscale</em> will not work in Lat/Lon locations as the horizontal
-scale distance changes with latitude.
+<em>d.barscale</em> will not work with Lat/Lon coordinate reference system
+as the horizontal scale distance changes with latitude.
 Try <em><a href="d.grid.html">d.grid</a></em> instead.
 
 <h2>SEE ALSO</h2>

display/d.geodesic/d.geodesic.html

@@ -39,7 +39,7 @@ <h2>EXAMPLE</h2>
 
 <h2>NOTES</h2>
 
-This program works only in GRASS locations with longitude/latitude
+This program works only with longitude/latitude
 coordinate system.
 
 <h2>SEE ALSO</h2>

display/d.labels/d.labels.html

@@ -6,7 +6,7 @@ <h2>DESCRIPTION</h2>
 size, and the background for the text. This file can be generated with
 the <em><a href="v.label.html">v.label</a></em> program or simply created
 by the user as an ASCII file (using a text editor) and placed in the
-appropriate directory under the user's current mapset and location
+appropriate directory under the user's current mapset and project
 (i.e. <tt>$MAPSET/paint/labels/</tt>).
 
 <h2>NOTES</h2>

display/d.legend.vect/d.legend.vect.html

@@ -50,7 +50,7 @@ <h2>NOTES</h2>
 User can create custom legend file and then use
 <em>export GRASS_LEGEND_FILE=path/to/file</em> in shell.
 GRASS GUI and MONITORS create the legend file automatically.
-By default the legend file is stored in grassdata/location/mapset/.tmp/user
+By default the legend file is stored in grassdata/project/mapset/.tmp/user
 directory (in case of d.mon deeper in /monitor_name directory).<br>
 <p>
 Legend file has this format:

display/d.rhumbline/d.rhumbline.html

@@ -40,7 +40,7 @@ <h2>EXAMPLE</h2>
 
 <h2>NOTES</h2>
 
-This program works only in GRASS locations with longitude/latitude
+This program works only with longitude/latitude
 coordinate system.
 
 <h2>SEE ALSO</h2>

display/d.where/d.where.html

@@ -32,7 +32,7 @@ <h2>NOTES</h2>
 frame before running <em>d.where</em>. The <b>-d</b> flag allows the user to
 optionally output latitude/longitude coordinates pair(s) in decimal degree
 rather than DD:MM:SS format. The <b>-w</b> flag is only valid
-if a datum is defined for the current location.
+if a datum is defined for the current project's coordinate reference system.
 
 If the <b>-f</b> flag is given the x,y frame coordinates of the active display
 monitor will be returned (as a percentage, 0,0 is bottom left).

general/g.access/g.access.html

@@ -19,7 +19,7 @@ <h2>NOTES</h2>
 
 <p> Under GRASS, access to the mapset PERMANENT must be open to
 all users.  This is because GRASS looks for the user's default geographic
-region definition settings and the location TITLE in files that are stored
+region definition settings and the project TITLE in files that are stored
 under the PERMANENT mapset directory.  The <em>g.access</em> command,
 therefore, will not allow you to restrict access to the PERMANENT mapset.
 

general/g.copy/g.copy.html

@@ -20,7 +20,7 @@ <h3>Relation to mapsets</h3>
 under their own current mapset. <em>g.copy</em> allows the user to copy
 existing data files <b>from</b> other mapsets <b>to</b> the user's
 current mapset (<code>g.mapset -p</code>). The files to be copied must exist in the
-user's current mapset search path (<code>g.mapsets -p</code>) and location;
+user's current mapset search path (<code>g.mapsets -p</code>) and project;
 output is sent to the
 relevant data element directory(ies) under the user's current mapset.
 

general/g.gisenv/g.gisenv.html

@@ -1,7 +1,7 @@
 <h2>DESCRIPTION</h2>
 
 When a user runs GRASS, certain variables are set specifying the GRASS
-data base, location, mapset, peripheral device drivers, etc., being
+data base, project, mapset, peripheral device drivers, etc., being
 used in the current GRASS session. These variable name settings are
 recognized as long as the user is running a GRASS session.
 
@@ -41,9 +41,9 @@ <h2>OPTIONS</h2>
 <dt><em>GISDBASE</em>
 <dd>The <em>GISDBASE</em> is a directory in which all users' GRASS
 data are stored. Within the <em>GISDBASE</em>, data are segregated
-into subdirectories (called &quot;locations&quot;) based on the map
+into subdirectories (called &quot;projects&quot;) based on the map
 coordinate system used and the geographic extent of the data.  Each
-&quot;location&quot; directory itself contains subdirectories called
+&quot;project&quot; directory itself contains subdirectories called
 &quot;mapsets&quot;; each &quot;mapset&quot; stores &quot;data base
 elements&quot; - the directories (e.g.,
 the <tt>cell</tt>, <tt>cellhd</tt>, <tt>vector</tt>, etc., directories)
@@ -52,17 +52,18 @@ <h2>OPTIONS</h2>
 <dt><em>LOCATION_NAME</em>
 
 <dd>The user must choose to work with the data under a single GRASS
-location within any given GRASS session; this location is then called
-the <em>current GRASS location</em>, and is specified by the variable
+project (previously called &quot;location&quot;) within any given
+GRASS session; this project is then called
+the <em>current GRASS project</em>, and is specified by the variable
 <em>LOCATION_NAME</em>. The <em>LOCATION_NAME</em> is the GRASS data
 base location whose data will be affected by any GRASS commands issued
 during the user's current GRASS session, and is a subdirectory of the
-current <em>GISDBASE</em>. Each &quot;location&quot; directory can
+current <em>GISDBASE</em>. Each &quot;project&quot; directory can
 contain multiple &quot;mapset&quot; directories (including the special
 mapset <em>PERMANENT</em>).  Maps stored under the same
 GRASS <em>LOCATION_NAME</em> (and/or within the same <em>MAPSET</em>)
 must use the same coordinate system and typically fall within the
-boundaries of the same geographic region (aka, &quot;location&quot;).
+boundaries of the same geographic region.
 
 <dt><em>MAPSET</em>
 
@@ -98,7 +99,7 @@ <h2>OPTIONS</h2>
 Once within a GRASS session, GRASS users have access only to the data
 under a single GRASS data base directory (the <em>current GRASS data
 base</em>, specified by the variable <em>GISDBASE</em>), and to a
-single GRASS location directory (the <em>current location</em>,
+single GRASS project directory (the <em>current project</em>,
 specified by the variable <em>LOCATION_NAME</em>).  Within a single
 session, the user may only <em>modify</em> the data in the
 <em>current mapset</em> (specified by the variable
@@ -145,7 +146,7 @@ <h2>NOTES</h2>
 By default the GRASS variables are stored in <em>gisrc</em> file
 (defined by environmental
 variable <em>GISRC</em>). If <b>store=mapset</b> is given then the
-variables are stored in <tt>&lt;gisdbase&gt;/&lt;location&gt;/&lt;mapset&gt;/VAR</tt>
+variables are stored in <tt>&lt;gisdbase&gt;/&lt;project&gt;/&lt;mapset&gt;/VAR</tt>
 after the current GRASS session is closed.
 
 <h3>GRASS Debugging</h3>

general/g.list/g.list.html

@@ -172,7 +172,7 @@ <h3>Maps whose region overlaps with a saved region</h3>
 </pre></div>
 
 List all raster and vector maps whose region overlaps with the default region
-of the PERMANENT mapset in the current location (DEFAULT_WIND):
+of the PERMANENT mapset in the current project (DEFAULT_WIND):
 <div class="code"><pre>
 g.list type=rast,vect region=*
 </pre></div>

general/g.mapset/g.mapset.html

@@ -2,11 +2,10 @@ <h2>DESCRIPTION</h2>
 
 <em>g.mapset</em> changes the current working mapset, project (formerly known
 as location), or GISDBASE (directory with one or more projects).
-This is a fairly radical maneuver to run mid-session, take care when running
-the GUI at the same time.
+
 <p>
 With <em>g.mapset</em>, the shell history (i.e. <tt>.bash_history</tt> file
-of the initial location will be used to record the command history.
+of the initial project will be used to record the command history.
 
 <h2>NOTES</h2>
 

general/g.mapsets/g.mapsets.html

@@ -1,16 +1,17 @@
 <h2>DESCRIPTION</h2>
 
-For basic information about GRASS <em>mapset</em>, <em>location</em>
+For basic information about GRASS <em>mapset</em>, <em>project</em>
 and <em>data base</em> refer to <a href="helptext.html">GRASS
 Quickstart</a>.
 
 <p>
 A <em>mapset</em> holds a distinct set of data layers, each relevant
 to the same (or a subset of the same) geographic region, and each
 drawn in the same map coordinate system.  At the outset of every GRASS
-session, the user identifies a GRASS data base, location, and mapset
+session, the user identifies a GRASS data base, project (previosuly
+called location), and mapset
 that are to be the user's <em>current data base</em>, <em>current
-location</em>, and <em>current mapset</em> for the duration of the
+project</em>, and <em>current mapset</em> for the duration of the
 session; any maps created by the user during the session will be
 stored under the <em>current mapset</em> set at the session's outset
 (see <em><a href="g.mapset.html">g.mapset</a></em> [without an "s"]
@@ -21,12 +22,12 @@ <h2>DESCRIPTION</h2>
 The user can add, modify, and delete data layers that exist under
 their <em>current mapset</em>. Although the user can
 also <em>access</em> (i.e., use) data that are stored under
-<em>other</em> mapsets in the same GRASS location using the
+<em>other</em> mapsets in the same GRASS project using the
 <tt>mapname@mapsetname</tt> notation or mapset search path, the user
 can only make permanent changes (create or modify data)
 located in the <em>current mapset</em>.  The user's
 <em>mapset search path</em> lists the order in which other mapsets in
-the same GRASS location can be searched and their data accessed by the
+the same GRASS project can be searched and their data accessed by the
 user. The user can modify the listing and order in which these mapsets
 are accessed by modifying the mapset search path; this can be done
 using the <em>g.mapsets</em> command. This program allows the user to
@@ -39,7 +40,7 @@ <h2>DESCRIPTION</h2>
 
 <p>
 <em>g.mapsets</em> shows the user available mapsets under the current
-GRASS location, lists mapsets to which the user currently has access,
+GRASS project, lists mapsets to which the user currently has access,
 and lists the order in which accessible mapsets will be accessed by
 GRASS programs searching for data files.  The user is then given the
 opportunity to add or delete mapset names from the search path, or
@@ -63,7 +64,7 @@ <h2>DESCRIPTION</h2>
 the file <tt>soils</tt> from the mapset PERMANENT.
 
 <p>
-In each location there is the special mapset <b>PERMANENT</b> included
+In each project there is the special mapset <b>PERMANENT</b> included
 in the mapset search path, as this mapset typically contains base maps
 relevant to many applications. Often, other mapsets which contain sets
 of interpreted maps will be likewise included in the user's mapset search path.
@@ -109,7 +110,7 @@ <h3>Selecting mapsets with the graphical mapset manager</h3>
 </center>
 
 <h3>Print available mapsets</h3>
-All available mapsets in the current location can be printed out by
+All available mapsets in the current project can be printed out by
 
 <div class="code"><pre>
 g.mapsets -l