[GRASS-SVN] r62842 - in grass/branches/releasebranch_7_0/temporal: . t.connect t.create t.info t.list t.merge t.rast.accdetect t.rast.accumulate t.rast.aggregate t.rast.aggregate.ds t.rast.colors t.rast.export t.rast.extract t.rast.import t.rast.list t.rast.mapcalc t.rast.neighbors t.rast.out.vtk t.rast.series t.rast.to.rast3 t.rast.univar t.rast3d.extract t.rast3d.list t.rast3d.mapcalc t.rast3d.univar t.register t.remove t.rename t.sample t.shift t.snap t.support t.topology t.unregister t.vect.db.select t.vect.export t.vect.extract t.vect.import t.vect.list t.vect.observe.strds t.vect.univar t.vect.what.strds
svn_grass at osgeo.org
svn_grass at osgeo.org
Thu Nov 20 13:33:36 PST 2014
Author: neteler
Date: 2014-11-20 13:33:36 -0800 (Thu, 20 Nov 2014)
New Revision: 62842
Modified:
grass/branches/releasebranch_7_0/temporal/t.connect/t.connect.html
grass/branches/releasebranch_7_0/temporal/t.create/t.create.html
grass/branches/releasebranch_7_0/temporal/t.info/t.info.html
grass/branches/releasebranch_7_0/temporal/t.list/t.list.html
grass/branches/releasebranch_7_0/temporal/t.merge/t.merge.html
grass/branches/releasebranch_7_0/temporal/t.rast.accdetect/t.rast.accdetect.html
grass/branches/releasebranch_7_0/temporal/t.rast.accumulate/t.rast.accumulate.html
grass/branches/releasebranch_7_0/temporal/t.rast.aggregate.ds/t.rast.aggregate.ds.html
grass/branches/releasebranch_7_0/temporal/t.rast.aggregate/t.rast.aggregate.html
grass/branches/releasebranch_7_0/temporal/t.rast.colors/t.rast.colors.html
grass/branches/releasebranch_7_0/temporal/t.rast.export/t.rast.export.html
grass/branches/releasebranch_7_0/temporal/t.rast.extract/t.rast.extract.html
grass/branches/releasebranch_7_0/temporal/t.rast.import/t.rast.import.html
grass/branches/releasebranch_7_0/temporal/t.rast.list/t.rast.list.html
grass/branches/releasebranch_7_0/temporal/t.rast.mapcalc/t.rast.mapcalc.html
grass/branches/releasebranch_7_0/temporal/t.rast.neighbors/t.rast.neighbors.html
grass/branches/releasebranch_7_0/temporal/t.rast.out.vtk/t.rast.out.vtk.html
grass/branches/releasebranch_7_0/temporal/t.rast.series/t.rast.series.html
grass/branches/releasebranch_7_0/temporal/t.rast.to.rast3/t.rast.to.rast3.html
grass/branches/releasebranch_7_0/temporal/t.rast.univar/t.rast.univar.html
grass/branches/releasebranch_7_0/temporal/t.rast3d.extract/t.rast3d.extract.html
grass/branches/releasebranch_7_0/temporal/t.rast3d.list/t.rast3d.list.html
grass/branches/releasebranch_7_0/temporal/t.rast3d.mapcalc/t.rast3d.mapcalc.html
grass/branches/releasebranch_7_0/temporal/t.rast3d.univar/t.rast3d.univar.html
grass/branches/releasebranch_7_0/temporal/t.register/t.register.html
grass/branches/releasebranch_7_0/temporal/t.remove/t.remove.html
grass/branches/releasebranch_7_0/temporal/t.rename/t.rename.html
grass/branches/releasebranch_7_0/temporal/t.sample/t.sample.html
grass/branches/releasebranch_7_0/temporal/t.shift/t.shift.html
grass/branches/releasebranch_7_0/temporal/t.snap/t.snap.html
grass/branches/releasebranch_7_0/temporal/t.support/t.support.html
grass/branches/releasebranch_7_0/temporal/t.topology/t.topology.html
grass/branches/releasebranch_7_0/temporal/t.unregister/t.unregister.html
grass/branches/releasebranch_7_0/temporal/t.vect.db.select/t.vect.db.select.html
grass/branches/releasebranch_7_0/temporal/t.vect.export/t.vect.export.html
grass/branches/releasebranch_7_0/temporal/t.vect.extract/t.vect.extract.html
grass/branches/releasebranch_7_0/temporal/t.vect.import/t.vect.import.html
grass/branches/releasebranch_7_0/temporal/t.vect.list/t.vect.list.html
grass/branches/releasebranch_7_0/temporal/t.vect.observe.strds/t.vect.observe.strds.html
grass/branches/releasebranch_7_0/temporal/t.vect.univar/t.vect.univar.html
grass/branches/releasebranch_7_0/temporal/t.vect.what.strds/t.vect.what.strds.html
grass/branches/releasebranch_7_0/temporal/temporalintro.html
Log:
temporal manual: selective sync to trunk
Modified: grass/branches/releasebranch_7_0/temporal/t.connect/t.connect.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.connect/t.connect.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.connect/t.connect.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -4,23 +4,29 @@
<h2>NOTES</h2>
-Values are stored in the mapset's <tt>VAR</tt> file;
-the connection is not tested for validity.
-<p>The <b>-d</b> flag will set the default TGIS connection parameters.
-A sqlite3 database "tgis/sqlite.db" will be created in the PERMANET directory
+Values are stored in the mapset's <tt>VAR</tt> file; the connection is
+not tested for validity. <p>The <b>-d</b> flag will set the default
+TGIS connection parameters.
+<!-- TODO: really always PERMANENT? - see http://trac.osgeo.org/grass/ticket/2258 -->
+A SQLite3 database "tgis/sqlite.db" will be created in the PERMANENT directory
of the current location. It will be located in the "tgis" sub-directory to not
interfere with the sqlite3 database used for vector attribute storage.
-<p>The <b>-p</b> flag will display the current TGIS connection parameters.
-<p>The <b>-pg</b> flag will display the current TGIS connection parameters using shell style.
-<p>The <b>-c</b> flag will silently check if the TGIS connection parameters have
-been set, and if not will set them to use GRASS's default values.
+<p>The <b>-p</b> flag will display the current TGIS connection parameters.
+<p>The <b>-pg</b> flag will display the current TGIS connection parameters
+using shell style.
+<p>The <b>-c</b> flag will silently check if the TGIS connection
+parameters have been set, and if not will set them to use GRASS's
+default values.
+
<h2>Note</h2>
-The default TGIS database of type sqlite3 is located in the PERMANENT mapset directory.
-Temporal GIS content from all created mapsets will be stored here. In case
-you have thousends of maps to register in the temporal database or you need concurrent read
-and write access in the TGIS database, consider to use a postgresql database instead.
+The default TGIS database of type sqlite3 is located in the PERMANENT
+mapset directory. Temporal GIS content from all created mapsets will be
+stored here. In case you have thousands of maps to register in the
+temporal database or you need concurrent read and write access in the
+TGIS database, consider to use a postgresql database instead.
+
<h3>SQLite</h3>
<div class="code"><pre>
@@ -28,10 +34,12 @@
t.connect -p
t.info -s
</pre></div>
-<p>The SQLite database is created automatically when used the first time.
+<p>
+The SQLite database is created automatically when used the first time.
+
<h3>PostgreSQL</h3>
-In case you use a postgresql database, you will need to specify the TGIS database connection
+In case you use a PostgreSQL database, you will need to specify the TGIS database connection
for each mapset.
<div class="code"><pre>
t.connect driver=pg database="dbname=grass_test user=soeren password=abcdefgh"
Modified: grass/branches/releasebranch_7_0/temporal/t.create/t.create.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.create/t.create.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.create/t.create.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -3,30 +3,29 @@
The purpose of this module is the creation of space time datasets of
type raster (STRDS), 3D raster (STR3DS) and vector (STVDS).
<p>
-Space time datasets represent spatio-temporal fields in the temporal GRASS framework.
-They are designed to collect any amount of time stamped maps with time intervals
-and time instances.
-The temporal type of a space time dataset
-can be absolute or relative and must be set on dataset creation besides the name and the description.
+Space time datasets represent spatio-temporal fields in the temporal
+GRASS framework. They are designed to collect any amount of time
+stamped maps with time intervals and time instances. The temporal type
+of a space time dataset can be absolute or relative and must be set on
+dataset creation besides the name and the description.
<p>
-Time stamped maps can registered in and unregistered from space time datasets.
-The spatio-temporal extent as well as the metadata of a space time dataset is derived from its registered maps.
-Hence the metadata is dependent from the dataset type (raster, 3D raster, vector).
-<p>
+Time stamped maps can registered in and unregistered from space time
+datasets. The spatio-temporal extent as well as the metadata of a space
+time dataset is derived from its registered maps. Hence the metadata is
+dependent from the dataset type (raster, 3D raster, vector).
-
<h2>EXAMPLE</h2>
-In this example we create 7 raster maps using r.mapcalc with random values
-that will be registered in a single space time
-raster dataset named <em>precipitation_daily</em> using a daily temporal granularity.
-The names of the raster maps are stored in a text
-file that is used for raster map registration.
-We use <em>t.create</em> for the space time raster dataset creation
-and <em>t.register</em> to register the raster maps
-in the space time raster dataset.
-At the end we report informations about the
-space time raster dataset to stdout using <em>t.info</em>.
+In this example we create 7 raster maps using r.mapcalc with random
+values that will be registered in a single space time raster dataset
+named <em>precipitation_daily</em> using a daily temporal granularity.
+The names of the raster maps are stored in a text file that is used for
+raster map registration. We use <em>t.create</em> for the space time
+raster dataset creation and <em>t.register</em> to register the raster
+maps in the space time raster dataset. At the end we report
+informations about the space time raster dataset to stdout using
+<em>t.info</em>.
+
<div class="code"><pre>
MAPS="map_1 map_2 map_3 map_4 map_5 map_6 map_7"
Modified: grass/branches/releasebranch_7_0/temporal/t.info/t.info.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.info/t.info.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.info/t.info.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,28 +1,31 @@
<h2>DESCRIPTION</h2>
-<em>t.info</em> reports informations about any dataset that is registered in the temporal database in
-human readable or shell script style. Datasets are raster, 3D raster and vector maps as well as their
-corresponding space time datasets (STRDS, STR3DS and STVDS). This module reports the informations that
-are stored in the temporal database. These are basic informations (id, name, mapset, creator,
-creation time, temporal type),
-the temporal and spatial extent and dataset type specific metadata.
-The user has to utilize <em>r.info, r3.info, v.info</em>
-to report detailed informations about raster, 3D raster and vector maps, since
-not all map specific informations and metadata are stored in the temporal database.
+<em>t.info</em> reports informations about any dataset that is
+registered in the temporal database in human readable or shell script
+style. Datasets are raster, 3D raster and vector maps as well as their
+corresponding space time datasets (STRDS, STR3DS and STVDS). This
+module reports the informations that are stored in the temporal
+database. These are basic informations (id, name, mapset, creator,
+creation time, temporal type), the temporal and spatial extent and
+dataset type specific metadata. The user has to utilize <em>r.info</em>,
+<em>r3.info</em>, <em>v.info</em> to report detailed informations about
+raster, 3D raster and vector maps, since not all map specific
+informations and metadata are stored in the temporal database.
<p>
-In addition, informations about the chosen temporal database backend can be reported.
+In addition, informations about the chosen temporal database backend
+can be reported.
<h2>EXAMPLE</h2>
-In this example we first report temporal database backend information using <em>t.info -s</em>.
-Then we create a single raster maps using <em>r.mapcalc</em> with random values
-that will be registered in a single space time
-raster dataset named <em>precipitation_daily</em> using a daily temporal granularity.
-We use <em>t.create</em> for the space time raster dataset creation
-and <em>t.register</em> to register the raster map
-in the space time raster dataset.
-At the end we report informations about the raster map and the
-space time raster dataset to stdout.
+In this example we first report temporal database backend information
+using <em>t.info -s</em>. Then we create a single raster maps using
+<em>r.mapcalc</em> with random values that will be registered in a
+single space time raster dataset named <em>precipitation_daily</em>
+using a daily temporal granularity. We use <em>t.create</em> for the
+space time raster dataset creation and <em>t.register</em> to register
+the raster map in the space time raster dataset. At the end we report
+informations about the raster map and the space time raster dataset to
+stdout.
<div class="code"><pre>
@@ -128,6 +131,7 @@
|
+----------------------------------------------------------------------------+
</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.list/t.list.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.list/t.list.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.list/t.list.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,20 +1,22 @@
<h2>DESCRIPTION</h2>
-<em>t.list</em> lists any dataset that is registered in the temporal database.
-Datasets are raster, 3D raster and vector maps as well as their
-corresponding space time datasets (STRDS, STR3DS and STVDS). The type of the dataset
-can be specified using the <em>type</em> option, default is STRDS. By default all datasets with
-relative and absolute time are listed. However, the user has the ability to specify
-a single temporal type with the <em>temporaltype</em> option.
-The user can define the columns that should
-be printed for each dataset and the order of the datasets. In addition a SQL WHERE statement can
-be specified to select a subset of the requested datasets.
+<em>t.list</em> lists any dataset that is registered in the temporal
+database. Datasets are raster, 3D raster and vector maps as well as
+their corresponding space time datasets (STRDS, STR3DS and STVDS). The
+type of the dataset can be specified using the <em>type</em> option,
+default is STRDS. By default all datasets with relative and absolute
+time are listed. However, the user has the ability to specify a single
+temporal type with the <em>temporaltype</em> option. The user can
+define the columns that should be printed for each dataset and the
+order of the datasets. In addition a SQL WHERE statement can be
+specified to select a subset of the requested datasets.
<h2>EXAMPLE</h2>
-In this example we will create 3 raster maps and register them first only in the
-temporal database an then in the newly created space time raster dataset.
-We use t.list to show what maps are already in the
+In this example we will create three raster maps and register them first
+only in the temporal database an then in the newly created space time
+raster dataset. We use <em>t.list</em> to show what maps are already
+in the temporal database:
<div class="code"><pre>
# Generate data
@@ -40,7 +42,6 @@
t.list strds
precipitation_daily at soeren
-
</pre></div>
<h2>SEE ALSO</h2>
Modified: grass/branches/releasebranch_7_0/temporal/t.merge/t.merge.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.merge/t.merge.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.merge/t.merge.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,20 +1,23 @@
<h2>DESCRIPTION</h2>
-This module is designed to register the maps of several input space time datasets in a single output dataset.
-The datasets to merge can be either space time raster, 3D raster or vector datasets and must
-have the same temporal type (absolute or relative).
+This module is designed to register the maps of several input space
+time datasets in a single output dataset. The datasets to merge can be
+either space time raster, 3D raster or vector datasets and must have
+the same temporal type (absolute or relative).
<p>
-Existing space time datasets located in the current mapset can be specified as output as well. The
-maps from the input space time datasets will be added to the output.
+Existing space time datasets located in the current mapset can be
+specified as output as well. The maps from the input space time
+datasets will be added to the output.
<p>
-Maps from the input space time datasets will be registered only once in the
-output space time dataset, hence the same maps can be registered in different input space time datasets.
+Maps from the input space time datasets will be registered only once in
+the output space time dataset, hence the same maps can be registered in
+different input space time datasets.
<h2>Examples</h2>
-In this example we will create two space time raster datasets and register
-two unique maps in each of it. Then we merge the two space time raster
-datasets together.
+In this example we will create two space time raster datasets and
+register two unique maps in each of it. Then we merge the two space
+time raster datasets together.
<div class="code"><pre>
r.mapcalc expr="map1 = rand(0, 10)" -s
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.accdetect/t.rast.accdetect.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.accdetect/t.rast.accdetect.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.accdetect/t.rast.accdetect.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,44 +1,64 @@
<h2>DESCRIPTION</h2>
-<b>t.rast.accdetect</b> is designed to detect accumulation pattern in temporally accumulated
-space time raster datasets created by <a href="t.rast.accumulate.html">t.rast.accumulate</a>.
+<b>t.rast.accdetect</b> is designed to detect accumulation pattern in
+temporally accumulated space time raster datasets created by
+<a href="t.rast.accumulate.html">t.rast.accumulate</a>.
This module expects a space time raster dataset as input that is the result
of a <a href="t.rast.accumulate.html">t.rast.accumulate</a> run.
<p>
-The <b>start</b> time and the <b>end</b> time of the pattern detection process must be set,
-eg. <b>start="2000-03-01" end="2011-01-01"</b>. The <b>start</b> and <b>end</b> time do not need to be the same
-as for the accumulation run that produced the input space time raster dataset.
-In addition a <b>cycle</b>, eg. "8 months", can be specified, that defines
-after which time interval the accumulation pattern detection process restarts. The <b>offset</b> option specifies the
-time between two cycles that should be skipped, eg. "4 months". Please make sure that the <b>cycle</b> and
-<b>offset</b> options are same as in the accumulation process that produces the input space time raster dataset, otherwise the accumulation pattern detection will produce wrong results.
+The <b>start</b> time and the <b>end</b> time of the pattern detection
+process must be set, eg. <b>start="2000-03-01" end="2011-01-01"</b>.
+The <b>start</b> and <b>end</b> time do not need to be the same as for
+the accumulation run that produced the input space time raster dataset.
+In addition a <b>cycle</b>, eg. "8 months", can be specified, that
+defines after which time interval the accumulation pattern detection
+process restarts. The <b>offset</b> option specifies the time between
+two cycles that should be skipped, eg. "4 months". Please make sure
+that the <b>cycle</b> and <b>offset</b> options are same as in the
+accumulation process that produces the input space time raster dataset,
+otherwise the accumulation pattern detection will produce wrong
+results.
<p>
The <b>minimum</b> and <b>maximum</b> values of the pattern detection
process can be set, either by using space time raster datasets or
by using fixed values for all raster cells and time steps.
<p>
-Using space time raster datasets allow to specify minimum and maximum values for each raster cell and each time step. For example,
-we want to detect the germination (minimum value) and harvesting (maximum value) dates for different crops in Germany using the growing-degree-day (GDD) method for several years. Different crops may grow in different raster cells and change with time because of crop rotation.
-Hence we need to specify different GDD germination/harvesting (minimum/maximum) values for different raster cells and different years.
+Using space time raster datasets allow to specify minimum and maximum
+values for each raster cell and each time step. For example, we want to
+detect the germination (minimum value) and harvesting (maximum value)
+dates for different crops in Germany using the growing-degree-day (GDD)
+method for several years. Different crops may grow in different raster
+cells and change with time because of crop rotation. Hence we need to
+specify different GDD germination/harvesting (minimum/maximum) values
+for different raster cells and different years.
<p>
-The raster maps that specifies the
-minimum and maximum values of the actual granule will be detected using the following temporal relations:
-equals, during, overlaps, overlapped and contains.
-First all maps with equal time stamps to the current granule of the input STRDS will be detected,
-the first minimum map and the first maximum map that were found are used as range definitions.
-If no equal maps are found then maps with a temporal during relation are detected,
-then maps that temporally overlap the actual granules, until
-maps are detected that have a temporal contain relation.
-If no maps are found or minimum/maximum STRDS are not set, then the <b>range</b> option is used, eg. <b>range=480,730</b>.
+The raster maps that specifies the minimum and maximum values of the
+actual granule will be detected using the following temporal relations:
+equals, during, overlaps, overlapped and contains. First all maps with
+equal time stamps to the current granule of the input STRDS will be
+detected, the first minimum map and the first maximum map that were
+found are used as range definitions. If no equal maps are found then
+maps with a temporal during relation are detected, then maps that
+temporally overlap the actual granules, until maps are detected that
+have a temporal contain relation. If no maps are found or
+minimum/maximum STRDS are not set, then the <b>range</b> option is
+used, eg. <b>range=480,730</b>.
<p>
The <b>base</b> name of of the generated maps must always be set.
<p>
-This module produces two output space time raster datasets. The <b>occurrence</b> output STRDS stores the time in days
-from the begin of a cycle for each raster cell and time step that has a value within the minimum and maximum definition.
-These values can be used to compute the duration of the recognized accumulation pattern. The <b>indicator</b> output STRDS
-uses three values, that can be set using the <b>staend</b> option, to mark raster cells with integer values that indicate the start, the intermediate state and the end of a accumulation pattern. As default specifies the value 1 the start, the value 2 the intermediate state and the value 3 the end of the accumulation pattern in a cycle.
+This module produces two output space time raster datasets. The
+<b>occurrence</b> output STRDS stores the time in days from the begin
+of a cycle for each raster cell and time step that has a value within
+the minimum and maximum definition. These values can be used to compute
+the duration of the recognized accumulation pattern. The
+<b>indicator</b> output STRDS uses three values, that can be set using
+the <b>staend</b> option, to mark raster cells with integer values that
+indicate the start, the intermediate state and the end of a
+accumulation pattern. As default specifies the value 1 the start, the
+value 2 the intermediate state and the value 3 the end of the
+accumulation pattern in a cycle.
<h2>EXAMPLE</h2>
@@ -46,14 +66,14 @@
<h2>SEE ALSO</h2>
-<b>
-<a href="t.rast.accumulate.html">t.rast.accumulate</a><br>
-<a href="t.rast.aggregate.html">t.rast.aggregate</a><br>
-<a href="t.rast.mapcalc.html">t.rast.mapcalc</a><br>
-<a href="t.info.html">t.info</a><br>
-<a href="r.series.accumulate.html">r.series.accumulate</a><br>
-<a href="g.region.html">g.region</a><br>
-</b>
+<em>
+<a href="t.rast.accumulate.html">t.rast.accumulate</a>,
+<a href="t.rast.aggregate.html">t.rast.aggregate</a>,
+<a href="t.rast.mapcalc.html">t.rast.mapcalc</a>,
+<a href="t.info.html">t.info</a>,
+<a href="r.series.accumulate.html">r.series.accumulate</a>,
+<a href="g.region.html">g.region</a>
+</em>
<h2>AUTHOR</h2>
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.accumulate/t.rast.accumulate.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.accumulate/t.rast.accumulate.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.accumulate/t.rast.accumulate.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,51 +1,65 @@
<h2>DESCRIPTION</h2>
-<b>t.rast.accumulate</b> is designed to perform temporal accumulations of space time raster datasets.
+<b>t.rast.accumulate</b> is designed to perform temporal accumulations
+of space time raster datasets.
-This module expects a space time raster dataset as input that will be sampled by a given <b>granularity</b>.
-All maps that have the start time during the actual granule will be accumulated with the predecessor
-granule accumulation result using the raster module <a href="r.series.accumulate.html">r.series.accumulate</a>.
-The default granularity is 1 day, but any temporal granularity can be set.
+This module expects a space time raster dataset as input that will be
+sampled by a given <b>granularity</b>. All maps that have the start
+time during the actual granule will be accumulated with the predecessor
+granule accumulation result using the raster module
+<a href="r.series.accumulate.html">r.series.accumulate</a>. The default
+granularity is 1 day, but any temporal granularity can be set.
+
<p>
-The <b>start</b> time and the <b>end</b> time of the accumulation process must be set,
-eg. <b>start="2000-03-01" end="2011-01-01"</b>.
-In addition a <b>cycle</b>, eg. <b>cycle="8 months"</b>, can be specified, that defines
-after which time interval the accumulation process restarts. The <b>offset</b> option specifies the
-time between two cycles that should be skipped, eg. <b>offset="4 months"</b>.
+The <b>start</b> time and the <b>end</b> time of the accumulation
+process must be set, eg. <b>start="2000-03-01" end="2011-01-01"</b>. In
+addition a <b>cycle</b>, eg. <b>cycle="8 months"</b>, can be specified,
+that defines after which time interval the accumulation process
+restarts. The <b>offset</b> option specifies the time between two
+cycles that should be skipped, eg. <b>offset="4 months"</b>.
+
<p>
The <b>lower</b> and <b>upper</b> <b>limits</b> of the accumulation
-process can be set, either by using space time raster datasets or
-by using fixed values for all raster cells and time steps. The raster maps that specifies the
-lower and upper limits of the actual granule will be detected using the following temporal relations:
-equals, during, overlaps, overlapped and contains.
-First all maps with equal time stamps to the current granule will be detected,
-the first lower map and the first upper map that were found are used as limit definitions.
-If no equal maps are found then maps with a temporal during relation are detected,
-then maps that temporally overlap the actual granules, until
-maps are detected that have a temporal contain relation.
-If no maps are found or lower/upper STRDS are not defined, then the <b>limits</b> option is used, eg. <b>limits=10,30</b>.
+process can be set, either by using space time raster datasets or by
+using fixed values for all raster cells and time steps. The raster
+maps that specifies the lower and upper limits of the actual granule
+will be detected using the following temporal relations: equals,
+during, overlaps, overlapped and contains. First all maps with equal
+time stamps to the current granule will be detected, the first lower
+map and the first upper map that were found are used as limit
+definitions. If no equal maps are found then maps with a temporal
+during relation are detected, then maps that temporally overlap the
+actual granules, until maps are detected that have a temporal contain
+relation. If no maps are found or lower/upper STRDS are not defined,
+then the <b>limits</b> option is used, eg. <b>limits=10,30</b>.
+
<p>
-The <b>upper</b> <b>limit</b> is only used in the Biologically Effective Degree Days calculation.
+The <b>upper</b> <b>limit</b> is only used in the Biologically
+Effective Degree Days calculation.
+
<p>
The options <b>shift</b>, <b>scale</b> and <b>method</b> are passed to
<a href="r.series.accumulate.html">r.series.accumulate</a>.
Please refer to the manual page of <a href="r.series.accumulate.html">r.series.accumulate</a>
for detailed option description.
+
<p>
-The <b>output</b> is a new space time raster dataset with the provided start time, end time and granularity
-containing the accumulated raster maps. The <b>base</b> name of of the generated maps must always be set.
-The <b>output</b> space time raster dataset can then be analyzed
-using <a href="t.rast.accdetect.html">t.rast.accdetect</a> to detect specific accumulation patterns.
+The <b>output</b> is a new space time raster dataset with the provided
+start time, end time and granularity containing the accumulated raster
+maps. The <b>base</b> name of of the generated maps must always be set.
+The <b>output</b> space time raster dataset can then be analyzed using
+<a href="t.rast.accdetect.html">t.rast.accdetect</a> to detect specific
+accumulation patterns.
<h2>EXAMPLE</h2>
-This is an example how to accumulate the daily mean temperature of Europe from 1990 to 2000 using
-the growing-degree-day method to detect grass hopper reproduction cycles that are critical
-to agriculture.
+This is an example how to accumulate the daily mean temperature of
+Europe from 1990 to 2000 using the growing-degree-day method to detect
+grass hopper reproduction cycles that are critical to agriculture.
<div class="code"><pre>
# Get the temperature data
-wget www-pool.math.tu-berlin.de/~soeren/grass/temperature_mean_1990_2000_daily_celsius.tar.gz
+wget http://www-pool.math.tu-berlin.de/~soeren/grass/temperature_mean_1990_2000_daily_celsius.tar.gz
# Create a temporary location directory
mkdir -p /tmp/grassdata/LL
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.aggregate/t.rast.aggregate.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.aggregate/t.rast.aggregate.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.aggregate/t.rast.aggregate.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,13 +1,13 @@
<h2>DESCRIPTION</h2>
-<em>t.rast.aggregate</em> temporally aggregates space time raster datasets
-by a specific temporal granularity.
-This module support <em>absolute</em> and <em>relative time</em>.
-The temporal granularity of absolute time can be
-<em>seconds, minutes, hours, days, weeks, months</em> or <em>years</em>.
-Mixing of granularities eg. "1 year, 3 months 5 days" is not supported.
-In case of relative time the temporal unit of the input space time raster
-dataset is used. The granularity must be specified with an integer value.
+<em>t.rast.aggregate</em> temporally aggregates space time raster
+datasets by a specific temporal granularity. This module support
+<em>absolute</em> and <em>relative time</em>. The temporal granularity
+of absolute time can be <em>seconds, minutes, hours, days, weeks,
+months</em> or <em>years</em>. Mixing of granularities eg. "1 year, 3
+months 5 days" is not supported. In case of relative time the temporal
+unit of the input space time raster dataset is used. The granularity
+must be specified with an integer value.
<p>
This module is sensitive to the current region and mask settings,
hence spatial extent and spatial resolution. In case the registered
@@ -17,12 +17,13 @@
<h2>NOTES</h2>
-The raster module <em>r.series</em> is used internally. Hence all aggregate
-methods of <em>r.series</em> are supported. See the
+The raster module <em>r.series</em> is used internally. Hence all
+aggregate methods of <em>r.series</em> are supported. See the
<a href="r.series.html">r.series</a> manual page for details.
<p>
-This module will shift the start date for each aggregation process depending on the
-provided temporal granularity. The following shifts will performed:
+This module will shift the start date for each aggregation process
+depending on the provided temporal granularity. The following shifts
+will performed:
<ul>
<li><em>granularity years</em>: will start at the first of January, hence 14-08-2012 00:01:30 will be shifted to 01-01-2012 00:00:00</li>
@@ -35,9 +36,10 @@
<h2>EXAMPLES</h2>
-In this example, we create 7 raster maps that will be registered in a single space time
-raster dataset named <em>precipitation_daily</em> using a daily temporal granularity.
-The names of the raster maps are stored in a text file that is used for raster map registration.
+In this example, we create 7 raster maps that will be registered in a
+single space time raster dataset named <em>precipitation_daily</em>
+using a daily temporal granularity. The names of the raster maps are
+stored in a text file that is used for raster map registration.
<p>
The space time raster dataset <em>precipitation_daily</em> with daily temporal granularity
will be aggregated to weekly precipitation resulting in the output space time raster dataset
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.aggregate.ds/t.rast.aggregate.ds.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.aggregate.ds/t.rast.aggregate.ds.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.aggregate.ds/t.rast.aggregate.ds.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,30 +1,33 @@
<h2>DESCRIPTION</h2>
-This module works like <a href="t.rast.aggregate.html">t.rast.aggregate</a> but instead
-of defining a fixed granularity for temporal aggregation the time intervals of
-all maps registered in a second space time dataset (can be STRDS, STR3DS or STVDS)
-are used to aggregate the maps of the input space time raster dataset.
+This module works like
+<a href="t.rast.aggregate.html">t.rast.aggregate</a> but instead of
+defining a fixed granularity for temporal aggregation the time
+intervals of all maps registered in a second space time dataset (can be
+STRDS, STR3DS or STVDS) are used to aggregate the maps of the input
+space time raster dataset.
<h2>EXAMPLE</h2>
-In this example we create 7 raster maps that will be registered in a single space time
-raster dataset named <em>precipitation_daily</em> using a daily temporal granularity.
-The names of the raster maps are stored in a text file that is used for raster map registration.
+In this example we create 7 raster maps that will be registered in a
+single space time raster dataset named <em>precipitation_daily</em>
+using a daily temporal granularity. The names of the raster maps are
+stored in a text file that is used for raster map registration.
<p>
-A space time vector dataset is created out of two vector maps with different
-temporal resolution. The maps are created using v.random.
-The first map has a granule of 3 days the second a granule of 4 days.
+A space time vector dataset is created out of two vector maps with
+different temporal resolution. The maps are created using v.random. The
+first map has a granule of 3 days the second a granule of 4 days.
<p>
-The space time raster dataset <em>precipitation_daily</em> with daily temporal granularity
-will be aggregated using the space time vector dataset
-resulting in the output space time raster dataset
-<em>precipitation_agg</em>. The aggregation method is set to <em>sum</em> to accumulate the precipitation values
-of all intervals in the space time vector dataset. The sampling option assures that only raster maps that are
-temporally during the time intervals of the space time vector dataset are
-considered for computation:
+The space time raster dataset <em>precipitation_daily</em> with daily
+temporal granularity will be aggregated using the space time vector
+dataset resulting in the output space time raster dataset
+<em>precipitation_agg</em>. The aggregation method is set to
+<em>sum</em> to accumulate the precipitation values of all intervals in
+the space time vector dataset. The sampling option assures that only
+raster maps that are temporally during the time intervals of the space
+time vector dataset are considered for computation:
<div class="code"><pre>
-
MAPS="map_1 map_2 map_3 map_4 map_5 map_6 map_7"
for map in ${MAPS} ; do
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.colors/t.rast.colors.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.colors/t.rast.colors.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.colors/t.rast.colors.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -15,13 +15,13 @@
<h2>EXAMPLE</h2>
-In this example we create 6 raster maps that will be registered in a single space time
-raster dataset named <em>precip_abs</em> using a monthly temporal granularity.
-Then we set an equilized grey color table using <em>t.rast.colors</em> and print the
-color table of the first map to stdout representing the data range of the space time raster dataset.
+In this example we create 6 raster maps that will be registered in a
+single space time raster dataset named <em>precip_abs</em> using a
+monthly temporal granularity. Then we set an equilized grey color table
+using <em>t.rast.colors</em> and print the color table of the first map
+to stdout representing the data range of the space time raster dataset.
<div class="code"><pre>
-
g.region s=0 n=80 w=0 e=120 b=0 t=50 res=10 res3=10 -p3
r.mapcalc --o expr="prec_1 = 100"
@@ -56,7 +56,6 @@
600 234:234:234
nv 255:255:255
default 255:255:255
-
</pre></div>
<h2>SEE ALSO</h2>
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.export/t.rast.export.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.export/t.rast.export.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.export/t.rast.export.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,30 +1,35 @@
<h2>DESCRIPTION</h2>
-This module exports a space time raster dataset as a tar archive. The archive contains the
-raster maps either as geotiff files or as GRASS binary files exported using r.out.bin.
-The map specific color tables are exported as well in case of geotiff files.
-In addition several meta data files are created in the archive that describe the
-temporal layout. All time stamps are stored in the file "list.txt", for each map one row.
-The name of the map, the start time and the end time are written. In case of a time instance,
-the start time is equal to the end time. The "init.txt" files stores the temporal
-type, the number of maps, the chosen export format and some other metadata. The "proj.txt"
-files stores the projection information as proj4 string of the
-location the space time raster dataset was exported from.
-The file "readme.txt" describes the file format. The output of r.info is stored in "metadata.txt".
+This module exports a space time raster dataset as a tar archive. The
+archive contains the raster maps either as geotiff files or as GRASS
+binary files exported using r.out.bin. The map specific color tables
+are exported as well in case of geotiff files. In addition several meta
+data files are created in the archive that describe the temporal
+layout. All time stamps are stored in the file "list.txt", for each map
+one row. The name of the map, the start time and the end time are
+written. In case of a time instance, the start time is equal to the end
+time. The "init.txt" files stores the temporal type, the number of
+maps, the chosen export format and some other metadata. The "proj.txt"
+files stores the projection information as proj4 string of the location
+the space time raster dataset was exported from. The file "readme.txt"
+describes the file format. The output of r.info is stored in
+"metadata.txt".
<p>
-The tar archive can be compressed using the <b>compress</b> option. Gzip and bzip2 are
-available. A <b>where</b> option can be specified, to export only a subset of the space time dataset.
-Archives exported with <b>t.rast.export</b> can be importet with <b>t.rast.import</b>.
+The tar archive can be compressed using the <b>compress</b> option.
+Gzip and bzip2 are available. A <b>where</b> option can be specified,
+to export only a subset of the space time dataset. Archives exported
+with <b>t.rast.export</b> can be importet with <b>t.rast.import</b>.
<h2>EXAMPLE</h2>
-In this example we create 7 raster maps that will be registered in a single space time
-raster dataset named <em>precipitation_daily</em> using a daily temporal granularity.
-The names of the raster maps are stored in a text file that is used for raster map registration.
-We export the created space time raster dataset and will have a look at some files that are created:
+In this example we create 7 raster maps that will be registered in a
+single space time raster dataset named <em>precipitation_daily</em>
+using a daily temporal granularity. The names of the raster maps are
+stored in a text file that is used for raster map registration. We
+export the created space time raster dataset and will have a look at
+some files that are created:
<div class="code"><pre>
-
MAPS="map_1 map_2 map_3 map_4 map_5 map_6 map_7"
for map in ${MAPS} ; do
@@ -106,9 +111,8 @@
time stamps in ISO-Format. Field separator is |
metadata.txt -- The output of t.info
readme.txt -- This file
+</pre></div>
-</div>
-
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.extract/t.rast.extract.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.extract/t.rast.extract.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.extract/t.rast.extract.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,16 +1,18 @@
<h2>DESCRIPTION</h2>
-The purpose of <b>t.rast.extract</b> is to extract a subset of a space time
-raster dataset and to store that subset in a different space time raster dataset.
-The <b>where</b> condition is used to select the subset. In addition a r.mapcalc
-sub-expression can be specified that performs operations on all maps of the selected subset.
-In this expression the name of the input space time raster dataset can be used
-as simple map name. Other STRDS than the input STRDS can not be specified, but
-any raster map. In case a r.mapcalc sub-expression is defined, the base name
-of the resulting raster maps must be specified. The r.mapcalc expression can be
-used to select maps as well, since by default resulting empty maps are not registered
-in the output space time raster dataset and removed after processing. The number of
-parallel grass processes can be specified to speed up the processing.
+The purpose of <b>t.rast.extract</b> is to extract a subset of a space
+time raster dataset and to store that subset in a different space time
+raster dataset. The <b>where</b> condition is used to select the
+subset. In addition a r.mapcalc sub-expression can be specified that
+performs operations on all maps of the selected subset. In this
+expression the name of the input space time raster dataset can be used
+as simple map name. Other STRDS than the input STRDS can not be
+specified, but any raster map. In case a r.mapcalc sub-expression is
+defined, the base name of the resulting raster maps must be specified.
+The r.mapcalc expression can be used to select maps as well, since by
+default resulting empty maps are not registered in the output space
+time raster dataset and removed after processing. The number of
+parallel GRASS GIS processes can be specified to speed up the processing.
<p>
If no r.mapcalc expression is defined, the selected maps are simply registered in
the new created output space time raster dataset to avoid data duplication.
@@ -29,16 +31,16 @@
<h2>EXAMPLE</h2>
-In this example we create 8 raster maps that will be registered in a single space time
-raster dataset named <em>precipitation_yearly</em> using a yearly temporal granularity.
-The names of the raster maps are stored in a text file that is used for raster map registration.
+In this example we create 8 raster maps that will be registered in a
+single space time raster dataset named <em>precipitation_yearly</em>
+using a yearly temporal granularity. The names of the raster maps are
+stored in a text file that is used for raster map registration.
<p>
Then we extract all maps that are later 2005 and store the selected maps in
the space time raster dataset <em>precipitation_yearly_later_2005</em>.
<p>
<div class="code"><pre>
-
MAPS="map_1 map_2 map_3 map_4 map_5 map_6 map_7 map_8"
for map in ${MAPS} ; do
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.import/t.rast.import.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.import/t.rast.import.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.import/t.rast.import.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -8,13 +8,13 @@
<h2>EXAMPLE</h2>
-In this example we create 7 raster maps that will be registered in a single space time
-raster dataset named <em>precipitation_daily</em> using a daily temporal granularity.
-The names of the raster maps are stored in a text file that is used for raster map registration.
-We export the created space time raster dataset and will import it again.
+In this example we create 7 raster maps that will be registered in a
+single space time raster dataset named <em>precipitation_daily</em>
+using a daily temporal granularity. The names of the raster maps are
+stored in a text file that is used for raster map registration. We
+export the created space time raster dataset and will import it again.
<div class="code"><pre>
-
MAPS="map_1 map_2 map_3 map_4 map_5 map_6 map_7"
for map in ${MAPS} ; do
@@ -54,8 +54,7 @@
new_map_5 soeren 2012-09-07 00:00:00 2012-09-08 00:00:00
new_map_6 soeren 2012-09-08 00:00:00 2012-09-09 00:00:00
new_map_7 soeren 2012-09-09 00:00:00 2012-09-10 00:00:00
-</pre>
-</div>
+</pre></div>
<h2>SEE ALSO</h2>
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.list/t.rast.list.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.list/t.rast.list.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.list/t.rast.list.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,25 +1,33 @@
<h2>DESCRIPTION</h2>
-List time stamped raster map layers that are registered in a space time raster dataset. This module provides
-several options to list map layers and their metadata. Listing of map layer can be ordered by metadata,
-metadata columns can be specified and SQL where conditions can be provided to select a map layer subset
-of the input space time raster dataset. Most of the raster map specific metadat is available for column selection,
-sorting and SQL where statements.
+List time stamped raster map layers that are registered in a space time
+raster dataset. This module provides several options to list map layers
+and their metadata. Listing of map layer can be ordered by metadata,
+metadata columns can be specified and SQL where conditions can be
+provided to select a map layer subset of the input space time raster
+dataset. Most of the raster map specific metadat is available for
+column selection, sorting and SQL where statements.
-Using the <b>method</b> option allows the specification of different methods to list map layers.
-Method <i>col</i> is the deafult option and sensitive to the <b>column</b>,<b>order</b>
-and <b>where</b> options. It will simply print user specified metadata columns of one map layer per line.
-The <i>comma</i> method will list the map layer as comma separated list that can be used as input
-for spatial modules.
-To print interval length in days and distance from the begin use method <i>delta</i>. Method
-<i>deltagap</i> will additionally print temporal gaps between map layer. The <i>gran</i>
-method allows the listing of map layer sampled by a user defined <b>granule</b>. As default the granularity
-of the space time raster dataset is used for sampling.
+Using the <b>method</b> option allows the specification of different
+methods to list map layers. Method <i>col</i> is the deafult option and
+sensitive to the <b>column</b>,<b>order</b> and <b>where</b> options.
+It will simply print user specified metadata columns of one map layer
+per line. The <i>comma</i> method will list the map layer as comma
+separated list that can be used as input for spatial modules.
+<p>
+To print interval length in days and distance from the begin use method
+<i>delta</i>. Method <i>deltagap</i> will additionally print temporal
+gaps between map layer. The <i>gran</i> method allows the listing of
+map layer sampled by a user defined <b>granule</b>. As default the
+granularity of the space time raster dataset is used for sampling.
-For user defined column separator can be specified with the <b>separator</b> option.
+For user defined column separator can be specified with the <b>separator</b>
+option.
<h2>EXAMPLE</h2>
+
This example shows several options that are available for map layers listing.
+
<div class="code"><pre>
g.region s=0 n=80 w=0 e=120 b=0 t=50 res=10 res3=10 -p3
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.mapcalc/t.rast.mapcalc.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.mapcalc/t.rast.mapcalc.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.mapcalc/t.rast.mapcalc.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,23 +1,28 @@
<h2>DESCRIPTION</h2>
-The purpose of <em>t.rast.mapcalc</em> is to perform spatio-temporal <em>mapcalc</em> expressions
-on maps of temporally sampled space time raster datasets (STRDS). Spatial and temporal
-operators and internal variables are available in the expression string. The description of the spatial
-operators, functions and internal variables is available in the <a href="r.mapcalc.html">r.mapcalc</a> manual page.
-The temporal functions are described in detail below.
+The purpose of <em>t.rast.mapcalc</em> is to perform spatio-temporal
+<em>mapcalc</em> expressions on maps of temporally sampled space time
+raster datasets (STRDS). Spatial and temporal operators and internal
+variables are available in the expression string. The description of
+the spatial operators, functions and internal variables is available in
+the <a href="r.mapcalc.html">r.mapcalc</a> manual page. The temporal
+functions are described in detail below.
<p>
-This module expects several parameter. All space time raster datasets that are referenced in
-the <em>mapcalc expression</em> must be listed in the <em>input</em> option. The <em>first</em> space time raster
-dataset that is listed as input will be used to temporally sample all other
-space time raster datasets. The temporal sampling method can be chosen using
-the <em>method</em> option. The order of the STRDS's in the mapcalc expression can be different
-to the order of the STRDS's in the input option. The resulting space time raster dataset
-must be specified in the <em>output</em> option together with the <em>base</em> name
-of generated raster maps that are registered in the resulting STRDS. Empty maps
-resulting from map-calculation are not registered by default. This behavior can be changed
-with the <em>-n</em> flag. The flag <em>-s</em> can be used to assure that only spatial related
-maps in the STRDS's are processed. Spatial related means that temporally related maps overlap
-in their spatial extent.
+This module expects several parameter. All space time raster datasets
+that are referenced in the <em>mapcalc expression</em> must be listed
+in the <em>input</em> option. The <em>first</em> space time raster
+dataset that is listed as input will be used to temporally sample all
+other space time raster datasets. The temporal sampling method can be
+chosen using the <em>method</em> option. The order of the STRDS's in
+the mapcalc expression can be different to the order of the STRDS's in
+the input option. The resulting space time raster dataset must be
+specified in the <em>output</em> option together with the <em>base</em>
+name of generated raster maps that are registered in the resulting
+STRDS. Empty maps resulting from map-calculation are not registered by
+default. This behavior can be changed with the <em>-n</em> flag. The
+flag <em>-s</em> can be used to assure that only spatial related maps
+in the STRDS's are processed. Spatial related means that temporally
+related maps overlap in their spatial extent.
<p>
The module <em>t.rast.mapcalc</em> supports parallel processing. The option
<em>nprocs</em> specifies the number of processes that can be started in parallel.
@@ -74,13 +79,15 @@
<h2>NOTE</h2>
-We will discuss the internal work of <em>t.rast.mapcalc</em> with an example.
-Imagine we have two STRDS as input, each with monthly granularity. The first one
-<em>A</em> has 6 raster maps (a3 ... a8) with a temporal range from March to August. The second
-STRDS <em>B</em> has 12 raster maps (b1 ... b12) ranging from January to December.
-The value of the raster maps is the number of the month from their interval start time.
-Dataset <em>A</em> will be used to sample dataset <em>B</em> to create a dataset <em>C</em>.
-We want to add all maps with equal time stamps if the month of the start time is May or June,
+We will discuss the internal work of <em>t.rast.mapcalc</em> with an
+example. Imagine we have two STRDS as input, each with monthly
+granularity. The first one <em>A</em> has 6 raster maps (a3 ... a8)
+with a temporal range from March to August. The second STRDS <em>B</em>
+has 12 raster maps (b1 ... b12) ranging from January to December. The
+value of the raster maps is the number of the month from their interval
+start time. Dataset <em>A</em> will be used to sample dataset
+<em>B</em> to create a dataset <em>C</em>. We want to add all maps with
+equal time stamps if the month of the start time is May or June,
otherwise we multiply the maps. The command will look as follows:
<p>
<div class="code"><pre>
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.neighbors/t.rast.neighbors.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.neighbors/t.rast.neighbors.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.neighbors/t.rast.neighbors.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,31 +1,35 @@
<h2>DESCRIPTION</h2>
-<em>t.rast.neighbors</em> performs <a href="r.neighbors.html">r.neighbors</a> computations
-on the maps of a space time raster dataset (STRDS). This module supports a subset of options
-that are available in <a href="r.neighbors.html">r.neighbors</a>.
-The size of the neighborhood and the aggregation method can be chosen.
+<em>t.rast.neighbors</em> performs <a href="r.neighbors.html">r.neighbors</a>
+computations on the maps of a space time raster dataset (STRDS). This
+module supports a subset of options that are available in
+<a href="r.neighbors.html">r.neighbors</a>. The size of the neighborhood
+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 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 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 multicore system.
+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 multicore system.
-
<h2>EXAMPLE</h2>
-In this example we create 7 raster maps that will be registered in a single space time
-raster dataset named <em>precipitation_daily</em> using a daily temporal granularity.
-The names of the raster maps are stored in a text file that is used for raster map registration.
+In this example we create 7 raster maps that will be registered in a
+single space time raster dataset named <em>precipitation_daily</em>
+using a daily temporal granularity. The names of the raster maps are
+stored in a text file that is used for raster map registration.
<p>
-A neighborhood average smoothing with a window size of 5 cells will be performed on
-the space time raster dataset <em>precipitation_daily</em> resulting in the output space time raster dataset
-<em>precipitation_daily_smooth</em>. The base name of the new generated raster maps is <em>prec_smooth</em>.
-The temporal resolution of the resulting STRDS is identical to the input STRDS.
+A neighborhood average smoothing with a window size of 5 cells will be
+performed on the space time raster dataset <em>precipitation_daily</em>
+resulting in the output space time raster dataset
+<em>precipitation_daily_smooth</em>. The base name of the new generated
+raster maps is <em>prec_smooth</em>. The temporal resolution of the
+resulting STRDS is identical to the input STRDS.
<div class="code"><pre>
@@ -155,7 +159,6 @@
prec_smooth_5 2012-08-24 00:00:00 163.966667 293.3
prec_smooth_6 2012-08-25 00:00:00 204.98 324.611111
prec_smooth_7 2012-08-26 00:00:00 154.25 340.366667
-
</pre></div>
<h2>SEE ALSO</h2>
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.out.vtk/t.rast.out.vtk.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.out.vtk/t.rast.out.vtk.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.out.vtk/t.rast.out.vtk.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,6 +2,14 @@
TBD.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.series/t.rast.series.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.series/t.rast.series.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.series/t.rast.series.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,7 +2,6 @@
TBD.
-
<h2>EXAMPLE</h2>
Example for monthly aggregation:
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.to.rast3/t.rast.to.rast3.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.to.rast3/t.rast.to.rast3.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.to.rast3/t.rast.to.rast3.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,6 +2,14 @@
TBD.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.rast.univar/t.rast.univar.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast.univar/t.rast.univar.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast.univar/t.rast.univar.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -11,7 +11,6 @@
median value, third quartile and percentile 90.
<div class="code"><pre>
-
MAPS="map_1 map_2 map_3 map_4 map_5 map_6 map_7"
maxn=10
Modified: grass/branches/releasebranch_7_0/temporal/t.rast3d.extract/t.rast3d.extract.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast3d.extract/t.rast3d.extract.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast3d.extract/t.rast3d.extract.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,6 +2,14 @@
TBD.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.rast3d.list/t.rast3d.list.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast3d.list/t.rast3d.list.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast3d.list/t.rast3d.list.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,8 +1,18 @@
<h2>DESCRIPTION</h2>
-This module provides the same functionality as <a href="t.rast.list.html">t.rast.list</a>,
-the only difference is the 3d raster map layer metadata. Please refer to the manpage of <a href="t.rast.list.html">t.rast.list</a>.
+This module provides the same functionality as
+<a href="t.rast.list.html">t.rast.list</a>, the only difference is the
+3D raster map layer metadata. Please refer to the manual page of
+<a href="t.rast.list.html">t.rast.list</a>.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.rast3d.mapcalc/t.rast3d.mapcalc.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast3d.mapcalc/t.rast3d.mapcalc.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast3d.mapcalc/t.rast3d.mapcalc.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,6 +2,14 @@
TBD.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.rast3d.univar/t.rast3d.univar.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rast3d.univar/t.rast3d.univar.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rast3d.univar/t.rast3d.univar.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,7 +1,9 @@
<h2>DESCRIPTION</h2>
-This module provides the same functionality as <a href="t.rast.univar.html">t.rast.list</a>,
-the only difference is the vector map layer metadata. Please refer to the manpage of <a href="t.rast.univar.html">t.rast.list</a>.
+This module provides the same functionality as
+<a href="t.rast.univar.html">t.rast.list</a>, the only difference is the
+vector map layer metadata. Please refer to the manpage of
+<a href="t.rast.univar.html">t.rast.list</a>.
<h2>SEE ALSO</h2>
Modified: grass/branches/releasebranch_7_0/temporal/t.register/t.register.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.register/t.register.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.register/t.register.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,37 +1,41 @@
<h2>DESCRIPTION</h2>
-The module <em>t.register</em> is designed to register raster, 3D raster and
-vector maps in the temporal database and in specific space time datasets.
-This module must be used to assign time stamps to raster, 3D raster and vector maps.
-The existing timestamp modules <a href="r.timestamp.html">r.timestamp</a>,
-<a href="r3.timestamp.html">r3.timestamp</a> and <a href="v.timestamp.html">v.timestamp</a>
-do not register the maps in the temporal database of GRASS. However, timestamps that have been
-created with these modules can be read and used by <em>t.register</em>. This works only for
-maps that are not already registered in the temporal database.
+The module <em>t.register</em> is designed to register raster, 3D
+raster and vector maps in the temporal database and in specific space
+time datasets. This module must be used to assign time stamps to
+raster, 3D raster and vector maps. The existing timestamp modules
+<a href="r.timestamp.html">r.timestamp</a>,
+<a href="r3.timestamp.html">r3.timestamp</a> and
+<a href="v.timestamp.html">v.timestamp</a> do not register the maps in the
+temporal database of GRASS. However, timestamps that have been created
+with these modules can be read and used by <em>t.register</em>. This
+works only for maps that are not already registered in the temporal
+database.
<p>
-This module supports absolute and relative time. Maps can be registered by command line argument
-(a list of comma separated map names) or using an input file.
-The start time, the end time and a temporal increment can be provided by command line
-or in the input file.
-End time and increment are mutual exclusive.
-The user can register single maps or a list of maps at once. Maps can be registered in several
-space time datasets using the same timestamp.
+This module supports absolute and relative time. Maps can be registered
+by command line argument (a list of comma separated map names) or using
+an input file. The start time, the end time and a temporal increment
+can be provided by command line or in the input file. End time and
+increment are mutual exclusive. The user can register single maps or a
+list of maps at once. Maps can be registered in several space time
+datasets using the same timestamp.
<p>
-Start time and end time with absolute time must be provided using the format <b>yyyy-mm-dd HH:MM:SS +HHMM</b>.
-It is supported to specify only the date <b>yyyy-mm-dd</b>.
-In case of relative time the temporal unit (years, months, days, hours, minutes or seconds) must be provided.
+Start time and end time with absolute time must be provided using the
+format <b>yyyy-mm-dd HH:MM:SS +HHMM</b>. It is supported to specify
+only the date <b>yyyy-mm-dd</b>. In case of relative time the temporal
+unit (years, months, days, hours, minutes or seconds) must be provided.
The relative start time, end time and the increment are integers.
<h2>Note</h2>
-The timestamps of registred maps will be stored in the temporal
-database and in the metadata of the grass maps in the spatial database. This assures
-that timestamps can always be accessed with <em>(r|r3|v).timestamp</em> and the temporal
-modules. Timestamps should only be modified with <em>t.register</em> because
-the <em>(r|r3|v).timestamp</em> modules have no access to the temporal database.
-<p>
+The timestamps of registered maps will be stored in the temporal
+database and in the metadata of the grass maps in the spatial database.
+This assures that timestamps can always be accessed with
+<em>(r|r3|v).timestamp</em> and the temporal modules. Timestamps should
+only be modified with <em>t.register</em> because the
+<em>(r|r3|v).timestamp</em> modules have no access to the temporal
+database.
-
<h2>INPUT FILE FORMAT</h2>
Specification of map names:
@@ -75,12 +79,12 @@
<h2>EXAMPLE</h2>
-In this example we create 6 raster maps that will be registered in a single space time
-raster dataset named <em>precip_abs</em> using a monthly temporal granularity.
-The -i flag generates interval time. The generated timestamps will be
-inspected using <em>r.timestamp</em> and t.rast.list.
-We will register an additional map with
-a timetsamp that was set with <em>r.timestamp</em>.
+In this example we create 6 raster maps that will be registered in a
+single space time raster dataset named <em>precip_abs</em> using a
+monthly temporal granularity. The -i flag generates interval time. The
+generated timestamps will be inspected using <em>r.timestamp</em> and
+t.rast.list. We will register an additional map with a timetsamp that
+was set with <em>r.timestamp</em>.
<div class="code"><pre>
r.mapcalc expr="prec_1 = 100"
@@ -127,7 +131,6 @@
prec_5 test2 2001-05-01 00:00:00 2001-06-01 00:00:00
prec_6 test2 2001-06-01 00:00:00 2001-07-01 00:00:00
prec_7 test2 2001-07-01 00:00:00 2001-08-01 00:00:00
-
</pre></div>
Modified: grass/branches/releasebranch_7_0/temporal/t.remove/t.remove.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.remove/t.remove.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.remove/t.remove.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,12 +1,54 @@
<h2>DESCRIPTION</h2>
-TBD.
+The module <em>t.remove</em> removes space time datasets (strds, str3ds,
+stvds) from the temporal database. In other words, it deletes the relevant
+database entries and not the maps.
+<p>
+Optionally, also the raster, 3D raster and vector maps of the space time
+datasets can be removed using the <b>-r</b> (recursive) and <b>-f</b>
+(force) flags. Recursive removal works only if both flags are checked
+(use <b>-rf</b>).
+<h2>EXAMPLE</h2>
+
+In this example we create a space time raster dataset (strds) named
+<b>precip_months_sum</b> using a subset of the monthly precipitation
+raster maps from the North Carolina climate sample data set. In order to
+be able to show case recursive removal without deleting original sample
+data, new data is generated by means of computing yearly precipitation sums.
+Finally, all newly produced data (strds and raster maps) is removed again.
+
+<div class="code"><pre>
+#Create new and empty strds
+t.create output=precip_months_sum semantictype=mean \
+ title="Monthly sum of precipitation" \
+ description="Monthly sum of precipitation for the \
+ North Carolina sample data location"
+
+#Register maps from sample dataset (selecting a subset with g.list)
+t.register -i type=rast input=precip_months_sum \
+ maps=$(g.list type=rast pattern=201*_precip separator=comma) \
+ start="2010-01-01" increment="1 months"
+
+#Create some new data by aggregating with 1 years granularity
+t.rast.aggregate input=precip_months_sum \
+ output=precip_years_sum basename=precip_years_sum granularity="1 \
+ years" method=sum
+
+#Remove all newly produced data:
+# a) the aggregated strds with 1 years granularity together with its raster maps
+t.remove -rf type=strds input=precip_years_sum
+
+# b) the strds with 1 months granularity, but not the original sample data
+t.remove type=strds input=precip_months_sum
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
<a href="t.create.html">t.create</a>,
-<a href="t.info.html">t.info</a>
+<a href="t.info.html">t.info</a>,
+<a href="t.register.html">t.register</a>
</em>
<h2>AUTHOR</h2>
Modified: grass/branches/releasebranch_7_0/temporal/t.rename/t.rename.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.rename/t.rename.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.rename/t.rename.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -3,6 +3,14 @@
This module renames space time datasets of different types (strds, stvds, str3ds)
and updates the space time dataset register entries of the registered maps.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.sample/t.sample.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.sample/t.sample.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.sample/t.sample.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,6 +2,14 @@
TBD.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.shift/t.shift.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.shift/t.shift.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.shift/t.shift.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -168,7 +168,6 @@
prec_4 soeren 2012-01-04 12:00:00 2012-01-05 12:00:00
prec_5 soeren 2012-01-05 12:00:00 2012-01-06 12:00:00
prec_6 soeren 2012-01-06 12:00:00 2012-01-07 12:00:00
-
</pre></div>
<h2>SEE ALSO</h2>
Modified: grass/branches/releasebranch_7_0/temporal/t.snap/t.snap.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.snap/t.snap.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.snap/t.snap.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,14 +1,17 @@
<h2>DESCRIPTION</h2>
-<em>t.snap</em> is designed to convert time instances of maps into time intervals or to
-create valid temporal topologies for space time datasets. Raster, 3D raster and vector space time datasets are supported
-with absolute and relative time.
+<em>t.snap</em> is designed to convert time instances of maps into time
+intervals or to create valid temporal topologies for space time
+datasets. Raster, 3D raster and vector space time datasets are
+supported with absolute and relative time.
<p>
-This module "snaps" the end time of each registered map of a space time dataset to the start time
-of the map that is the temporal nearest neighbour in the future. Maps with equal time stamps
-are not modified and must be removed or modified to create a valid temporal topology.
-In case the last map in the space time dataset is a time instance, the granularity of the space time
-dataset will be used to create the time interval.
+This module "snaps" the end time of each registered map of a space time
+dataset to the start time of the map that is the temporal nearest
+neighbour in the future. Maps with equal time stamps are not modified
+and must be removed or modified to create a valid temporal topology. In
+case the last map in the space time dataset is a time instance, the
+granularity of the space time dataset will be used to create the time
+interval.
<h2>EXAMPLE</h2>
@@ -157,7 +160,6 @@
prec_4 soeren 2012-01-04 00:00:00 2012-01-05 00:00:00
prec_5 soeren 2012-01-05 00:00:00 2012-01-06 00:00:00
prec_6 soeren 2012-01-06 00:00:00 2012-01-07 00:00:00
-
</pre></div>
<h2>SEE ALSO</h2>
Modified: grass/branches/releasebranch_7_0/temporal/t.support/t.support.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.support/t.support.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.support/t.support.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,6 +2,14 @@
TBD.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.topology/t.topology.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.topology/t.topology.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.topology/t.topology.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,6 +2,14 @@
TBD.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.unregister/t.unregister.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.unregister/t.unregister.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.unregister/t.unregister.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,7 +1,63 @@
<h2>DESCRIPTION</h2>
-TBD.
+This module is designed to unregister raster, 3d raster and vector map
+layers from space time datasets and the temporal database.
+<p>
+Map layer that should be unregistered from the temporal database can be
+specified as a list of comma separated map names or using a text file,
+that contains one map layer name per line. By default the map type that
+should be unregistered is set to raster. The option<em>type</em> must
+be used to specify 3d raster or vector map layer types.
+
+<h2>INPUT FILE FORMAT</h2>
+
+Specification of map names:
+<div class="code"><pre>
+a1
+a2
+a3
+a4
+a5
+a6
+</pre></div>
+
+<h3>NOTE</h3>
+In case the <em>input</em> option is used to specify a space time dataset
+the maps are only unregistered from the space time dataset, but not from the
+temporal database. The reason is that maps can be registered in
+multiple space time datasets and there is a need to
+unregister them from a specific STDS without affecting other STDS.
+
+<h2>EXAMPLE</h2>
+
+In this example we create 2 raster map layers that will be registered
+in a space time raster dataset named <em>A</em> using a
+monthly temporal granularity. We use t.unregister to unregister a map
+layer from the space time dataset and from the temporal database.
+
+<div class="code"><pre>
+r.mapcalc expr="a1 = 100"
+r.mapcalc expr="a2 = 200"
+
+t.create type=strds temporaltype=absolute \
+ output=A title="Example" \
+ descr="Example"
+
+t.register -i type=rast input=A \
+ maps=a1,a2 \
+ start="2001-01-01" increment="1 month"
+
+# We unregister raster maps a1 and a2 from a space time dataset,
+# the raster maps are still present in the temporal database
+t.unregister type=rast input=A maps=a1,a2
+
+# We unregister raster map a1 and a2 from the temporal database, hence
+# the time stamps are removed
+t.unregister type=rast maps=a1,a2
+</pre></div>
+
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.vect.db.select/t.vect.db.select.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.vect.db.select/t.vect.db.select.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.vect.db.select/t.vect.db.select.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,6 +2,14 @@
TBD.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.vect.export/t.vect.export.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.vect.export/t.vect.export.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.vect.export/t.vect.export.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -21,6 +21,7 @@
with <em><a href="t.vect.import.html">t.vect.import</a></em>.
<h2>EXAMPLE</h2>
+
In this example 5 vector maps are created and
registered in a single space time vector dataset named <em>random_locations</em>.
Each vector map represents random locations
Modified: grass/branches/releasebranch_7_0/temporal/t.vect.extract/t.vect.extract.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.vect.extract/t.vect.extract.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.vect.extract/t.vect.extract.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,6 +2,14 @@
TBD.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.vect.import/t.vect.import.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.vect.import/t.vect.import.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.vect.import/t.vect.import.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -7,6 +7,7 @@
<h2>EXAMPLE</h2>
+
In this example 5 vector maps are created and registered in a single space time
vector dataset named <em>random_locations</em>. Each vector map represents
random locations within the boundary of the state taken at 1 month intervals.
@@ -43,8 +44,7 @@
new_map_3 at user1|new_map_3|None|user1|2012-03-01 00:00:00|2012-04-01 00:00:00
new_map_4 at user1|new_map_4|None|user1|2012-04-01 00:00:00|2012-05-01 00:00:00
new_map_5 at user1|new_map_5|None|user1|2012-05-01 00:00:00|2012-06-01 00:00:00
-</pre>
-</div>
+</pre></div>
<h2>SEE ALSO</h2>
Modified: grass/branches/releasebranch_7_0/temporal/t.vect.list/t.vect.list.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.vect.list/t.vect.list.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.vect.list/t.vect.list.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,8 +1,18 @@
<h2>DESCRIPTION</h2>
-This module provides the same functionality as <a href="t.rast.list.html">t.rast.list</a>,
-the only difference is the vector map layer metadata. Please refer to the manpage of <a href="t.rast.list.html">t.rast.list</a>.
+This module provides the same functionality as
+<a href="t.rast.list.html">t.rast.list</a>, the only difference is the
+vector map layer metadata. Please refer to the manual page of
+<a href="t.rast.list.html">t.rast.list</a>.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.vect.observe.strds/t.vect.observe.strds.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.vect.observe.strds/t.vect.observe.strds.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.vect.observe.strds/t.vect.observe.strds.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,6 +2,14 @@
TBD.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.vect.univar/t.vect.univar.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.vect.univar/t.vect.univar.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.vect.univar/t.vect.univar.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,6 +2,14 @@
TBD.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
Modified: grass/branches/releasebranch_7_0/temporal/t.vect.what.strds/t.vect.what.strds.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/t.vect.what.strds/t.vect.what.strds.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/t.vect.what.strds/t.vect.what.strds.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -2,9 +2,22 @@
TBD.
+<h2>EXAMPLE</h2>
+
+The example is based on the XXX sample dataset:
+
+<div class="code"><pre>
+TBD
+</pre></div>
+
<h2>SEE ALSO</h2>
<em>
+<a href="r.univar.html">r.univar</a>,
+<a href="v.univar.html">v.univar</a>,
+<a href="v.what.rast.html">v.what.rast</a>,
+<a href="v.what.rast3.html">v.what.rast3</a>,
+<a href="v.what.vect.html">v.what.vect</a>,
<a href="t.create.html">t.create</a>,
<a href="t.info.html">t.info</a>
</em>
Modified: grass/branches/releasebranch_7_0/temporal/temporalintro.html
===================================================================
--- grass/branches/releasebranch_7_0/temporal/temporalintro.html 2014-11-20 21:29:59 UTC (rev 62841)
+++ grass/branches/releasebranch_7_0/temporal/temporalintro.html 2014-11-20 21:33:36 UTC (rev 62842)
@@ -1,5 +1,6 @@
<!-- meta page description: Temporal data processing in GRASS GIS -->
<!-- meta page index: temporal -->
+<h3>The temporal GIS framework in general</h3>
The temporal GIS framework in GRASS introduces three new datatypes that
are designed to handle time series data:
@@ -37,7 +38,7 @@
Space time datasets are stored in a temporal database. SQLite3 or
PostgreSQL are supported as SQL database back end.
Connection settings are performed with <a href="t.connect.html">t.connect</a>.
-<!-- todo: really always PERMANENT? -> Yes thats the default that can be modified -->
+<!-- TODO: really always PERMANENT? - see http://trac.osgeo.org/grass/ticket/2258 -->
As default a sqlite3 database will be created in the PERMANENT mapset that
stores all space time datasets and registered time series maps from all
mapsets in the location.
More information about the grass-commit
mailing list