temporal manual: explain absolute and relative time; HTML cosmetics

git-svn-id: https://svn.osgeo.org/grass/grass/trunk@66174 15284696-431f-4ddb-bdfa-cd5b030d7da7

temporal/t.connect/t.connect.html

@@ -11,7 +11,7 @@ using shell style.
 parameters have been set, and if not will set them to use GRASS's
 default values.
 
-<h2>NOTE</h2>
+<h2>NOTES</h2>
 
 Setting the connection with t.connect will not test the connection for validity.
 Hence a database connection will not be established.

temporal/t.list/t.list.html

@@ -11,7 +11,7 @@ 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>NOTE</h2>
+<h2>NOTES</h2>
 
 The SQL where and sort expression will be applied for each temporal
 database that was found in accessible mapsets. Hence sorting works only

temporal/t.rast.aggregate.ds/t.rast.aggregate.ds.html

@@ -7,7 +7,7 @@ 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>NOTE</h2>
+<h2>NOTES</h2>
 The sampling method must be specified from the sampler dataset point of view.
 It defines the temporal relations hips between intervals of the sampling 
 dataset and the input space time raster dataset.

temporal/t.rast.extract/t.rast.extract.html

@@ -19,7 +19,7 @@ If no <em>r.mapcalc</em> expression is defined, the selected maps are
 simply registered in the new created output space time raster dataset
 to avoid data duplication.
 
-<h2>Note</h2>
+<h2>NOTES</h2>
 
 The <em>r.mapcalc</em> sub-expression should not contain the left side
 <tt>"map ="</tt> of a full <em>r.mapcalc</em> expression, only the right

temporal/t.rast.gapfill/t.rast.gapfill.html

@@ -6,7 +6,7 @@ space time raster dataset automatically. The predecessor and successor maps
 of the gaps will be identified and used to linear interpolate the raster
 map between them.
 
-<h2>Note</h2>
+<h2>NOTES</h2>
 This module uses <a href="r.series.interp.html">r.series.interp</a> to
 perform the interpolation for each gap independently. Hence several
 interpolation processes can be run in parallel.

temporal/t.rast.import/t.rast.import.html

@@ -3,7 +3,7 @@
 <em>t.rast.import</em> imports a space time raster dataset archive that
 was exported with <a href="t.rast.export.html">t.rast.export</a>.
 
-<h2>NOTE</h2>
+<h2>NOTES</h2>
 
 Optionally a base map name can be provided to avoid that existing
 raster maps are overwritten by the map names that are used in the STRDS

temporal/t.rast.mapcalc/t.rast.mapcalc.html

@@ -77,7 +77,7 @@ Supported internal variables for absolute time of the current sample interval or
 The <em>end_*</em> functions are represented by the null() internal variables
 in case of time instances.
 
-<h2>NOTE</h2>
+<h2>NOTES</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

temporal/t.rast.to.rast3/t.rast.to.rast3.html

@@ -15,7 +15,7 @@ Gaps between raster map layer in the STRDS will
 be represented by NULL values in the voxel map layer.
 
 
-<h2>NOTE</h2>
+<h2>NOTES</h2>
 
 The reference time for all space time voxel cubes is
 1900-01-0100:00:00. This allows the alignment space time voxel cubes

temporal/t.register/t.register.html

@@ -12,10 +12,15 @@ 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
+This module supports absolute and relative time. The absolute temporal type
+refers to a fixed date while the relative temporal type refers to data
+without fixed time stamps (e.g., sequential maps used to calculate
+multi-decadal averages).
+
+<p>
+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.
@@ -26,7 +31,7 @@ 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>
+<h2>NOTES</h2>
 
 The timestamps of registered maps will be stored in the temporal
 database and in the metadata of the grass maps in the spatial database.
@@ -48,7 +53,8 @@ prec_5
 prec_6
 </pre></div>
 
-Specification of map names and the absolute start time (date) of the time instances:
+Specification of map names and the absolute start time (date) of the
+time instances:
 <div class="code"><pre>
 prec_1|2001-01-01
 prec_2|2001-02-01
@@ -67,7 +73,8 @@ terra_lst_day20020116|2002-01-16 10:30
 terra_lst_day20020117|2002-01-17 10:30
 </pre></div>
 
-Specification of the map name and the absolute time interval with start and end time:
+Specification of the map name and the absolute time interval with start
+and end time:
 <div class="code"><pre>
 prec_1|2001-01-01|2001-04-01
 prec_2|2001-04-01|2001-07-01
@@ -91,7 +98,12 @@ t.register -i type=raster input=precipitation_monthly \
 
 <h3>Synthetic maps</h3>
 
-In this example we create 6 raster maps that will be registered in a single space time raster dataset named precip_abs using a monthly temporal granularity. The -i flag generates interval time. The generated timestamps will be inspected using r.timestamp and t.rast.list. We will register an additional map with a timetsamp that was set with r.timestamp.
+In this example we create 6 raster maps that will be registered in a
+single space time raster dataset named precip_abs using a monthly
+temporal granularity. The <b>-i</b> flag generates interval time. The
+generated timestamps will be inspected using <em>r.timestamp</em> and
+<em>t.rast.list</em>. We will register an additional map with a timestamp
+that was set with <em>r.timestamp</em>.
 
 <div class="code"><pre>
 r.mapcalc expr="prec_1 = 100"

temporal/t.rename/t.rename.html

@@ -3,7 +3,7 @@
 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>NOTE</h2>
+<h2>NOTES</h2>
 
 Renaming of space time datasets works only for SQLite based temporal databases.
 

temporal/t.sample/t.sample.html

@@ -12,7 +12,7 @@ time datasets using temporal topology. The flag <em>-s</em> enables a
 spatio-temporal topology, so that only spatio-temporal related map 
 layers of space time datasets are considered in the analysis.
 
-<h2>NOTE</h2>
+<h2>NOTES</h2>
 
 The temporal relation <em>start</em> means that the start time of an 
 input map layer is temporally located in an interval of a sample map 

temporal/t.shift/t.shift.html

@@ -11,7 +11,7 @@ month(s), week(s), day(s), hour(s), minute(s) or second(s).
 The granularity in case of relative time is an integer. The temporal 
 unit is the unit of the space time dataset and can not be modified.
 
-<h2>Note</h2>
+<h2>NOTES</h2>
 Be careful when shifting space time datasets with absolute time. The 
 temporal granularity may change if you shift a space time dataset with 
 a unit that is different from the space time dataset granularity. Be