Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: continue renaming location to project in documentation #3570

Merged
merged 6 commits into from
Apr 17, 2024
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions display/d.barscale/d.barscale.html
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down
2 changes: 1 addition & 1 deletion display/d.geodesic/d.geodesic.html
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down
2 changes: 1 addition & 1 deletion display/d.labels/d.labels.html
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down
2 changes: 1 addition & 1 deletion display/d.legend.vect/d.legend.vect.html
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
2 changes: 1 addition & 1 deletion display/d.rhumbline/d.rhumbline.html
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down
2 changes: 1 addition & 1 deletion display/d.where/d.where.html
Original file line number Diff line number Diff line change
Expand Up @@ -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 coordinate reference system.
petrasovaa marked this conversation as resolved.
Show resolved Hide resolved

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).
Expand Down
2 changes: 1 addition & 1 deletion general/g.access/g.access.html
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion general/g.copy/g.copy.html
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
19 changes: 10 additions & 9 deletions general/g.gisenv/g.gisenv.html
Original file line number Diff line number Diff line change
@@ -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.

Expand Down Expand Up @@ -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)
Expand All @@ -52,17 +52,18 @@ <h2>OPTIONS</h2>
<dt><em>LOCATION_NAME</em>
petrasovaa marked this conversation as resolved.
Show resolved Hide resolved

<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>

Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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>
Expand Down
2 changes: 1 addition & 1 deletion general/g.list/g.list.html
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down
5 changes: 2 additions & 3 deletions general/g.mapset/g.mapset.html
Original file line number Diff line number Diff line change
Expand Up @@ -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>

Expand Down
17 changes: 9 additions & 8 deletions general/g.mapsets/g.mapsets.html
Original file line number Diff line number Diff line change
@@ -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"]
Expand All @@ -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
Expand All @@ -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
Expand All @@ -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.
Expand Down Expand Up @@ -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
Expand Down
39 changes: 20 additions & 19 deletions general/g.proj/g.proj.html
Original file line number Diff line number Diff line change
Expand Up @@ -11,17 +11,18 @@ <h2>DESCRIPTION</h2>
If compiled without <a href="https://gdal.org/">OGR</a> present, the
functionality is limited to:
<ul>
<li>Reporting the projection information for the current location,
<li>Reporting the projection information for the current project
petrasovaa marked this conversation as resolved.
Show resolved Hide resolved
(previously called location),
either in conventional GRASS (-p flag) or PROJ (-j flag) format</li>
<li>Changing the datum, or reporting and modifying the datum transformation
parameters, for the current location</li>
parameters, for the current project</li>
</ul>

<p>When compiled with OGR, functionality is increased and allows output of
the projection information in the Well-Known Text (WKT) format popularised
petrasovaa marked this conversation as resolved.
Show resolved Hide resolved
by proprietary GIS. In addition, if one of the parameters <em>georef</em>,
<em>wkt</em>, <em>proj4</em> or <em>epsg</em> is specified, rather than the
projection information being read from the current location it is imported
projection information being read from the current project it is imported
petrasovaa marked this conversation as resolved.
Show resolved Hide resolved
from an external source as follows:

<dl>
Expand Down Expand Up @@ -72,9 +73,9 @@ <h2>DESCRIPTION</h2>

<p>In addition however, if the -c flag is specified, <em>g.proj</em> will
create new GRASS projection files (PROJ_INFO, PROJ_UNITS, WIND and
DEFAULT_WIND) based on the imported information. If the <em>location</em>
parameter is specified in addition to -c, then a new location will be created.
Otherwise the projection information files in the current location will be
DEFAULT_WIND) based on the imported information. If the <em>project</em>
parameter is specified in addition to -c, then a new project will be created.
Otherwise the projection information files in the current project will be
overwritten. The program will <strong>not</strong> warn before doing this.

<p>The final mode of operation of g.proj is to report on the datum
Expand All @@ -92,7 +93,7 @@ <h2>NOTES</h2>
<strong>-1:</strong> List available parameter sets in a GUI-parsable (but also
human-readable) format and exit.<br>
<strong>0 (default):</strong> Continue without specifying parameters - if
used when creating a location, other GRASS modules will use the "default"
used when creating a project, other GRASS modules will use the "default"
(likely non-optimum) parameters for this datum if necessary in the future.<br>
<strong>Any other number less than or equal to the number of parameter sets
available for this datum:</strong> Choose this parameter set and add it to the
Expand All @@ -101,7 +102,7 @@ <h2>NOTES</h2>
datum transformation parameters using one of the above two methods
<strong>even if</strong> a valid parameter set is already specified in the
input co-ordinate system. This can be useful to change the datum information
for an existing location.
for an existing project.

<p>Output is simply based on the input projection information. g.proj does
<strong>not</strong> attempt to verify that the co-ordinate system thus
Expand All @@ -118,22 +119,22 @@ <h2>EXAMPLES</h2>

<h3>Print information</h3>

Print the projection information for the current location:<br>
Print the projection information for the current project:<br>
petrasovaa marked this conversation as resolved.
Show resolved Hide resolved

<div class="code"><pre>
g.proj -p
</pre></div>

<p>
List the possible datum transformation parameters for the current location:<br>
List the possible datum transformation parameters for the current project:<br>

<div class="code"><pre>
g.proj -t datumtrans=-1
</pre></div>

<h3>Create projection (PRJ) file</h3>

Create a '.prj' file in ESRI format corresponding to the current location:<br>
Create a '.prj' file in ESRI format corresponding to the current project:<br>

<div class="code"><pre>
g.proj -wef > irish_grid.prj
Expand All @@ -155,24 +156,24 @@ <h3>Read projection from file</h3>
cat proj4.description | g.proj -w proj4=-
</pre></div>

<h3>Create new location</h3>
<h3>Create new project</h3>

<p>Create a new location with the co-ordinate system referred to by EPSG code
<p>Create a new project with the co-ordinate system referred to by EPSG code
petrasovaa marked this conversation as resolved.
Show resolved Hide resolved
4326 (Latitude-Longitude/WGS84), without explicitly specifying datum
transformation parameters:<br>

<div class="code"><pre>
g.proj -c epsg=4326 location=latlong
</pre></div>

<p>Create a new location with the co-ordinate system referred to by ESRI-EPSG code
<p>Create a new project with the co-ordinate system referred to by ESRI-EPSG code
petrasovaa marked this conversation as resolved.
Show resolved Hide resolved
900913 (<a href="http://spatialreference.org/ref/user/6/">Google Mercator Projection</a>)<br>

<div class="code"><pre>
g.proj -c epsg=900913 location=google
</pre></div>

<p>Create a new location with the co-ordinate system referred to by EPSG code
<p>Create a new project with the co-ordinate system referred to by EPSG code
petrasovaa marked this conversation as resolved.
Show resolved Hide resolved
29900 (Irish Grid), selecting datum transformation parameter set no. 2:<br>

<div class="code"><pre>
Expand All @@ -181,21 +182,21 @@ <h3>Create new location</h3>
g.proj -c epsg=29900 datumtrans=2 location=irish_grid
</pre></div>

<p>Create a new location with the same co-ordinate system as the current
location, but forcing a change to datum transformation parameter set no. 1:<br>
<p>Create a new project with the same co-ordinate system as the current
petrasovaa marked this conversation as resolved.
Show resolved Hide resolved
project, but forcing a change to datum transformation parameter set no. 1:<br>

<div class="code"><pre>
g.proj -c location=newloc -t datumtrans=1
</pre></div>

<p>Create a new location with the co-ordinate system from a WKT definition
<p>Create a new project with the co-ordinate system from a WKT definition
petrasovaa marked this conversation as resolved.
Show resolved Hide resolved
stored in a text file:<br>

<div class="code"><pre>
g.proj -c wkt=irish_grid.prj location=irish_grid
</pre></div>

<p>Create a new location from a PROJ description, explicitly
<p>Create a new project from a PROJ description, explicitly
specifying a datum and using the default datum transformation
parameters:<br>

Expand Down
Loading
Loading