[GRASS-SVN] r69747 - in grass/branches/releasebranch_7_2: temporal temporal/t.rast.neighbors temporal/t.rast.to.rast3 temporal/t.vect.observe.strds temporal/t.vect.what.strds vector/v.buffer vector/v.db.select
svn_grass at osgeo.org
svn_grass at osgeo.org
Thu Oct 27 14:24:04 PDT 2016
Author: neteler
Date: 2016-10-27 14:24:04 -0700 (Thu, 27 Oct 2016)
New Revision: 69747
Modified:
grass/branches/releasebranch_7_2/temporal/t.rast.neighbors/t.rast.neighbors.html
grass/branches/releasebranch_7_2/temporal/t.rast.to.rast3/t.rast.to.rast3.html
grass/branches/releasebranch_7_2/temporal/t.vect.observe.strds/t.vect.observe.strds.html
grass/branches/releasebranch_7_2/temporal/t.vect.what.strds/t.vect.what.strds.html
grass/branches/releasebranch_7_2/temporal/temporalintro.html
grass/branches/releasebranch_7_2/vector/v.buffer/v.buffer.html
grass/branches/releasebranch_7_2/vector/v.db.select/v.db.select.html
Log:
temporal manual: language improvements (contributed by veroandreo); minor vector manual improvements (trunk, r69746); temporalintro man sync to trunk
Modified: grass/branches/releasebranch_7_2/temporal/t.rast.neighbors/t.rast.neighbors.html
===================================================================
--- grass/branches/releasebranch_7_2/temporal/t.rast.neighbors/t.rast.neighbors.html 2016-10-27 21:20:55 UTC (rev 69746)
+++ grass/branches/releasebranch_7_2/temporal/t.rast.neighbors/t.rast.neighbors.html 2016-10-27 21:24:04 UTC (rev 69747)
@@ -7,19 +7,19 @@
and the aggregation method can be chosen.
<p>
The user must provide an input and an output space time raster dataset and
-the basename of the resulting raster maps. The resulting STRDS will have
+the basename of the resulting raster maps. The resulting STRDS will have
the same temporal resolution as the input dataset.
All maps will be processed using the current region settings.
<p>
The user can select a subset of the input space time raster dataset for
processing using a SQL WHERE statement. The number of CPU's to be used
for parallel processing can be specified with the <em>nprocs</em>
-option, to speedup the computation on multi-core system.
+option to speedup the computation on multi-core system.
<h2>EXAMPLE</h2>
-To smooth the maps contained into a space time dataset run:
+To smooth the maps contained in a space time dataset run:
<div class="code"><pre>
t.rast.neighbors input=tempmean_monthly output=smooth_tempmean_monthly \
@@ -76,8 +76,7 @@
+----------------------------------------------------------------------------+
-# now compare the values between original data and the smoothed one
-t.rast.list input=smooth_tempmean_monthly columns=name,start_time,min,max
+# now compare the values between the original and the smoothed dataset
t.rast.list input=smooth_tempmean_monthly columns=name,start_time,min,max
name|start_time|min|max
Modified: grass/branches/releasebranch_7_2/temporal/t.rast.to.rast3/t.rast.to.rast3.html
===================================================================
--- grass/branches/releasebranch_7_2/temporal/t.rast.to.rast3/t.rast.to.rast3.html 2016-10-27 21:20:55 UTC (rev 69746)
+++ grass/branches/releasebranch_7_2/temporal/t.rast.to.rast3/t.rast.to.rast3.html 2016-10-27 21:24:04 UTC (rev 69747)
@@ -27,6 +27,27 @@
based granularity as well. This may result in millions of space time
voxel cube layers!
+<h3>Management of open file limits</h3>
+The maximum number of raster maps that can be processed is given by the
+per-user limit of the operating system. For example, both the the hard and soft
+limit for users is typically 1024. The soft limit can be changed with e.g.
+ulimit -n 4096 (UNIX-based operating systems) but not higher than the
+hard limit. If the latter is too low, you can as superuser add an entry in
+
+<div class="code"><pre>
+/etc/security/limits.conf
+# <domain> <type> <item> <value>
+your_username hard nofile 4096
+</pre></div>
+
+This will raise the hard limit to 4096 files. Also have a look at the overall
+limit of the operating system
+<div class="code"><pre>
+cat /proc/sys/fs/file-max
+</pre></div>
+which, on modern Linux systems, is several 100,000 files.
+
+
<h2>EXAMPLE</h2>
To create a voxel map layer from a subset of the <em>tempmean_monthly</em>
space time dataset, run:
Modified: grass/branches/releasebranch_7_2/temporal/t.vect.observe.strds/t.vect.observe.strds.html
===================================================================
--- grass/branches/releasebranch_7_2/temporal/t.vect.observe.strds/t.vect.observe.strds.html 2016-10-27 21:20:55 UTC (rev 69746)
+++ grass/branches/releasebranch_7_2/temporal/t.vect.observe.strds/t.vect.observe.strds.html 2016-10-27 21:24:04 UTC (rev 69747)
@@ -11,11 +11,11 @@
start to end). A column name must be specified for each input space
time raster dataset.
<p>
-As results a new space time vector dataset is generated that contains
-a single (new) vector map that links to as many time stamped attribute
-tables as raster map layer are present in the input space time raster
-dataset. Hence, for each time step in the space time raster dataset a
-new attribute table is created. The GRASS GIS Temporal Framework allows
+The result is a new space time vector dataset that contains a single
+(new) vector map which links to as many time-stamped attribute tables
+as raster map layers are present in the input space time raster dataset.
+Hence, for each time step in the space time raster dataset a new
+attribute table is created. The GRASS GIS Temporal Framework allows
to time stamp attribute tables that can be linked to a single vector
map layer.
<p>
@@ -29,7 +29,7 @@
<h2>EXAMPLE</h2>
-The example show how to create a space time vector dataset and a vector
+The example shows how to create a space time vector dataset and a vector
layer starting from a point vector and a space time raster dataset:
<div class="code"><pre>
Modified: grass/branches/releasebranch_7_2/temporal/t.vect.what.strds/t.vect.what.strds.html
===================================================================
--- grass/branches/releasebranch_7_2/temporal/t.vect.what.strds/t.vect.what.strds.html 2016-10-27 21:20:55 UTC (rev 69746)
+++ grass/branches/releasebranch_7_2/temporal/t.vect.what.strds/t.vect.what.strds.html 2016-10-27 21:24:04 UTC (rev 69747)
@@ -1,14 +1,14 @@
<h2>DESCRIPTION</h2>
-The module <em>t.vect.what.strds</em> samples a space time raster dataset
-at spatio-temporal locations of a space time vector dataset.
+The module <em>t.vect.what.strds</em> samples a space time raster dataset
+(STRDS) at the spatio-temporal locations of a space time vector dataset (STVDS).
<h2>EXAMPLE</h2>
The example is based on the space time vector dataset "precip_stations at climate_2009_2012"
created in the <a href="t.vect.observe.strds.html">t.vect.observe.strds</a> example.
-In below example the command fills the new column "new_temp" with values
+In the example below, the module fills the new column "new_temp" with values
extracted from the "tempmean_monthly" space time raster dataset:
<div class="code"><pre>
Modified: grass/branches/releasebranch_7_2/temporal/temporalintro.html
===================================================================
--- grass/branches/releasebranch_7_2/temporal/temporalintro.html 2016-10-27 21:20:55 UTC (rev 69746)
+++ grass/branches/releasebranch_7_2/temporal/temporalintro.html 2016-10-27 21:24:04 UTC (rev 69747)
@@ -1,7 +1,7 @@
<!-- meta page description: Temporal data processing in GRASS GIS -->
<!-- meta page index: temporal -->
-The temporal enabled GRASS introduces three new datatypes that
+The temporal enabled GRASS introduces three new data types that
are designed to handle time series data:
<ul>
<li> <em>Space time raster datasets</em> (strds) are designed to manage
@@ -20,49 +20,84 @@
<h3>Temporal data management in general</h3>
-Space time datasets are stored in a temporal database. SQLite3 or
-PostgreSQL are supported as SQL database back end. Temporal databases
-stored in other mapsets can be used as long as they are in the
-user's current mapset search path (managed with <a href="g.mapsets.html">g.mapsets</a>).
+Space time datasets are stored in a temporal database. A core principle of the
+temporal framework is that temporal databases are mapset specific. A new temporal
+database is created when a temporal command is invoked in a mapset that does not
+contain any temporal databases yet. For example, when a mapset was recently created.
<p>
+<b>Therefore, as space-time datasets are mapset specific, they can only register
+raster, 3D raster or vector maps from the same mapset.</b>
+<p>
+By default, space-time datasets can not register maps from other mapsets. This is
+a security measure, since the registration of maps in a space-time dataset will
+always modify the metadata of the registered map. This is critical if:
+<ul>
+ <li>
+ The user has no write access to the maps from other mapsets he wants to register
+ </li>
+ <li>
+ If registered maps are removed from other mapsets, the temporal database will not be updated
+ and will contain ghost maps
+ </li>
+</ul>
+
+SQLite3 or PostgreSQL are supported as temporal database backends.
+Temporal databases stored in other mapsets can be accessed as long as those
+other mapsets are in the user's current mapset search path (managed with
+<a href="g.mapsets.html">g.mapsets</a>). Access to space-time datasets from
+other mapsets is read-only. They can not be modified or removed.
+<p>
Connection settings are performed with <a href="t.connect.html">t.connect</a>.
-As default a sqlite3 database will be created in the current mapset that
-stores all space time datasets and registered time series maps.
+As default, a SQLite3 database will be created in the current mapset that
+stores all space-time datasets and registered time series maps.
<p>
-New space time datasets are created in the temporal database with
+New space-time datasets are created in the temporal database with
<a href="t.create.html">t.create</a>. The name of the new dataset, the
type (strds, str3ds, stvds), the title and the description must be
-provided for creation. Optional the temporal type (absolute, relative)
-and semantic information can be provided.
+provided for creation. Optionally, the temporal type (absolute, relative)
+and the semantic information can be provided.
<p>
-The module <a href="t.remove.html">t.remove</a> will remove the space time datasets
-from the temporal database. Use <a href="t.support.html">t.support</a>
-to modify the metadata of space time datasets or to update the metadata
-that is derived from registered maps. This module also checks for removed
-and modified maps and updates the space time datasets accordingly.
-Rename a space time dataset with <a href="t.rename.html">t.rename</a>.
-<p>
-The module <a href="t.register.html">t.register</a> is designed to
+The module <a href="t.register.html">t.register</a> is designed to
register raster, 3D raster and vector maps in the temporal database and
-optionally in a space time dataset. It supports different input options. Maps
+in the space-time datasets. It supports different input options. Maps
to register can be provided as a comma separated string at the command line, or
-in an input file. The module supports the definition of time stamps
+in an input file. The module supports the definition of time stamps
(time instances or intervals) for each map in the input file.
With <a href="t.unregister.html">t.unregister</a> maps can be unregistered
-from space time datasets and the temporal database.
+from space-time datasets and from the temporal database.
<p>
-To print information about space time datasets or registered maps, the
+
+<b>Important</b><br>
+<i>Use only temporal commands like t.register to attach a time stamp to
+raster, 3D raster and vector maps. The commands r.timestamp, r3.timestamp and
+v.timestamp should not be used, since they do not register maps in
+the temporal database and modify only the metadata of the map in the
+spatial database. However, maps with timestamps attached with *.timestamp modules
+can be registered in space-time datasets using the existing timestamp.</i>
+
+<p>
+The module <a href="t.remove.html">t.remove</a> will remove the space-time datasets
+from the temporal database and optionally all registered maps. It will take care
+of multiple map registration, hence if maps are registered in several space-time
+datasets in the current mapset.
+Use <a href="t.support.html">t.support</a>
+to modify the metadata of space time datasets or to update the metadata
+that is derived from registered maps. This module also checks for removed
+and modified maps and updates the space-time datasets accordingly.
+Rename a space-time dataset with <a href="t.rename.html">t.rename</a>.
+<p>
+To print information about space-time datasets or registered maps, the
module <a href="t.info.html">t.info</a> can be used.
-<a href="t.list.html">t.list</a> will list all space time datasets and
+<a href="t.list.html">t.list</a> will list all space-time datasets and
registered maps in the temporal database.
<p>
-To compute and check the temporal topology of a space time datasets the
+To compute and check the temporal topology of space-time datasets the
module <a href="t.topology.html">t.topology</a> was designed. The module
-<a href="t.sample.html">t.sample</a> samples input space time dataset(s)
-with a sample space time dataset and print the result to standard output.
-Several different sample methods are supported that can be combined.
+<a href="t.sample.html">t.sample</a> samples input space-time dataset(s)
+with a sample space-time dataset and prints the result to standard output.
+Different sampling methods are supported and can be combined.
<p>
-List of general management modules:
+List of general management modules:
<ul>
<li><a href="t.connect.html">t.connect</a></li>
<li><a href="t.create.html">t.create</a></li>
@@ -77,7 +112,7 @@
<li><a href="t.topology.html">t.topology</a></li>
</ul>
-<h3>Modules to visualize space time datasets and temporal data</h3>
+<h3>Modules to visualize space-time datasets and temporal data</h3>
<ul>
<li><a href="g.gui.animation.html">g.gui.animation</a></li>
@@ -86,21 +121,21 @@
<li><a href="g.gui.tplot.html">g.gui.tplot</a></li>
</ul>
-<h3>Modules to process space time raster datasets</h3>
+<h3>Modules to process space-time raster datasets</h3>
The focus of the temporal GIS framework is the processing and analysis of
-raster time series. Hence the majority of the temporal modules are designed to process space time raster
-datasets. However, there are several modules to process space time 3D raster datasets
-and space time vector datasets.
+raster time series. Hence, the majority of the temporal modules are designed
+to process space-time raster datasets. However, there are several modules to
+process space-time 3D raster datasets and space-time vector datasets.
<h4>Querying and map calculation</h4>
-Registered maps of a space time raster datasets can be listed using
+Registered maps of a space-time raster dataset can be listed using
<a href="t.rast.list.html">t.rast.list</a>. This module supports several
-methods how the maps should be listed using SQL queries do determine how
-they are selected and sorted. Subsets of space time raster datasets can
+methods to list maps and uses SQL queries to determine how these maps
+are selected and sorted. Subsets of space-time raster datasets can
be extracted with <a href="t.rast.extract.html">t.rast.extract</a> that
-allows additionally to perform mapcalc operations on the selected raster
+allows to perform additional mapcalc operations on the selected raster
maps.
<ul>
@@ -111,21 +146,23 @@
<li><a href="t.rast.neighbors.html">t.rast.neighbors</a></li>
</ul>
-Additionally, there is <a href="v.what.strds.html">v.what.strds</a>.
+Moreover, there is <a href="v.what.strds.html">v.what.strds</a>, that uploads
+space-time raster dataset values at positions of vector points, to the
+attribute table of the vector map.
<h4>Aggregation and accumulation analysis</h4>
-The temporal framework support the aggregation of space time raster
+The temporal framework supports the aggregation of space-time raster
datasets. It provides three modules to perform aggregation using different
-approaches. To aggregate a space time raster map using a temporal
+approaches. To aggregate a space-time raster map using a temporal
granularity like 4 months, 7 days and so on use
<a href="t.rast.aggregate.html">t.rast.aggregate</a>. The module
<a href="t.rast.aggregate.ds.html">t.rast.aggregate.ds</a> allows the
-aggregation of raster map series using the intervals of the maps (raster,
-3D raster and vector) of a 2. space time dataset. A simple interface to
+aggregation of a raster map time series using the intervals of the maps (raster,
+3D raster and vector) of another space-time dataset. A simple interface to
<a href="r.series.html">r.series</a> is the module
<a href="t.rast.series.html">t.rast.series</a> that processes the whole
-input space time raster dataset or a subset of it.
+input space-time raster dataset or a subset of it.
<ul>
<li><a href="t.rast.aggregate.html">t.rast.aggregate</a></li>
@@ -137,14 +174,14 @@
<h4>Export/import conversion</h4>
-Space time raster datasets can be exported with <a href="t.rast.export.html">t.rast.export</a>
-as compressed tar archive. Such archives can be imported
-using <a href="t.rast.import.html">t.rast.import</a>,
+Space-time raster datasets can be exported with <a href="t.rast.export.html">t.rast.export</a>
+as a compressed tar archive. Such archives can then be imported
+using <a href="t.rast.import.html">t.rast.import</a>.
<p>
The module <a href="t.rast.to.rast3.html">t.rast.to.rast3</a> converts
-space time raster datasets into space time voxel cubes. All 3D raster modules
-can be used to process such voxel cubes. This conversion allows the export of space time raster datasets
-as netcdf files that include time as one dimension.
+space-time raster datasets into space-time voxel cubes. All 3D raster modules
+can be used to process such voxel cubes. This conversion allows the export of
+space-time raster datasets as netCDF files that include time as one dimension.
<ul>
<li><a href="t.rast.export.html">t.rast.export</a></li>
@@ -163,7 +200,7 @@
<h3>Modules to manage, process and analyze STR3DS and STVDS</h3>
-Several space time vector dataset modules were developed, to allow the handling
+Several space-time vector dataset modules were developed to allow the handling
of vector time series data.
<ul>
@@ -176,8 +213,8 @@
<li><a href="t.vect.db.select.html">t.vect.db.select</a></li>
</ul>
-The space time 3D raster dataset modules are doing exactly the same as their raster
-pendants but with 3D raster map layers:
+The space-time 3D raster dataset modules are doing exactly the same as their
+raster pendants, but with 3D raster map layers:
<ul>
<li><a href="t.rast3d.list.html">t.rast3d.list</a></li>
@@ -198,4 +235,3 @@
<li><a href="http://www.geostat-course.org/Topic_Gebbert">GEOSTAT 2012 TGRASS Course</a></li>
</ul>
-
Modified: grass/branches/releasebranch_7_2/vector/v.buffer/v.buffer.html
===================================================================
--- grass/branches/releasebranch_7_2/vector/v.buffer/v.buffer.html 2016-10-27 21:20:55 UTC (rev 69746)
+++ grass/branches/releasebranch_7_2/vector/v.buffer/v.buffer.html 2016-10-27 21:24:04 UTC (rev 69747)
@@ -125,6 +125,9 @@
<h3>Buffer inside input areas</h3>
+In this example, an internal buffer ("inward buffer" or "negative buffer")
+is generated using a negative <b>distance</b> value:
+
<div class="code"><pre>
v.buffer input=lakes output=lakes_buffer type=area distance=-50
</pre></div>
Modified: grass/branches/releasebranch_7_2/vector/v.db.select/v.db.select.html
===================================================================
--- grass/branches/releasebranch_7_2/vector/v.db.select/v.db.select.html 2016-10-27 21:20:55 UTC (rev 69746)
+++ grass/branches/releasebranch_7_2/vector/v.db.select/v.db.select.html 2016-10-27 21:24:04 UTC (rev 69747)
@@ -55,7 +55,7 @@
</pre></div>
-<h3>Select empty vector features (no data entries)</h3>
+<h3>Select not empty vector features (no data entries)</h3>
<div class="code"><pre>
v.db.select geonames_wake where="ALTERNATEN IS NOT NULL"
More information about the grass-commit
mailing list