temporal manual: minor updates

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

temporal/t.connect/t.connect.html

@@ -6,12 +6,15 @@
 
 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 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. 
+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.
@@ -20,7 +23,7 @@ default values.
 
 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 
+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.
 
@@ -36,10 +39,8 @@ t.info -s
 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 for each mapset.
-
+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"
 t.connect -p

temporal/t.info/t.info.html

@@ -28,6 +28,7 @@ informations about the raster map and the space time raster dataset to
 stdout.
 
 <div class="code"><pre>
+
 t.info -s
  +------------------- Temporal DBMI backend information ----------------------+
  | DBMI Python interface:...... sqlite3

temporal/t.list/t.list.html

@@ -13,9 +13,10 @@ 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 
+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 t.list to show what maps are already in the 
+raster dataset. We use <em>t.list</em> to show what maps are already
+in the temporal database:
 
 <div class="code"><pre>
 # Generate data
@@ -41,7 +42,6 @@ t.register type=rast input=precipitation_daily maps=map1,map2,map3
 
 t.list strds
  precipitation_daily@soeren
-
 </pre></div>
 
 <h2>SEE ALSO</h2>

temporal/t.merge/t.merge.html

@@ -196,6 +196,7 @@ t.info precipitation_daily_3
  |     output="precipitation_daily_3"
  | 
  +----------------------------------------------------------------------------+
+
 </pre></div>
 
 <h2>SEE ALSO</h2>

temporal/t.rast.accumulate/t.rast.accumulate.html

@@ -65,7 +65,7 @@ wget http://www-pool.math.tu-berlin.de/~soeren/grass/temperature_mean_1990_2000_
 mkdir -p /tmp/grassdata/LL
 
 # Start GRASS and create a new location with PERMANENT mapset
-grass70  -c EPSG:4326 /tmp/grassdata/LL/PERMANENT
+grass71  -c EPSG:4326 /tmp/grassdata/LL/PERMANENT
 
 # Import the temperature data
 t.rast.import in=temperature_mean_1990_2000_daily_celsius.tar.gz \

temporal/t.rast.export/t.rast.export.html

@@ -30,7 +30,6 @@ 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

temporal/t.register/t.register.html

@@ -28,7 +28,7 @@ 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 
+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 

temporal/t.remove/t.remove.html

@@ -47,6 +47,7 @@ t.remove type=strds input=precip_months_sum
 
 <em>
 <a href="t.create.html">t.create</a>,
+<a href="t.info.html">t.info</a>,
 <a href="t.register.html">t.register</a>
 </em>
 

temporal/t.vect.list/t.vect.list.html

@@ -3,7 +3,7 @@
 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>.
+<a href="t.rast.list.html">t.rast.list</a>.
 
 <h2>EXAMPLE</h2>
 

temporal/t.vect.what.strds/t.vect.what.strds.html

@@ -17,13 +17,7 @@ TBD
 <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> 
-</em>
-
-
-<h2>SEE ALSO</h2>
-
-<em>
+<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>

temporal/temporalintro.html

@@ -38,7 +38,7 @@ List of general management modules:
 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? -> see http://trac.osgeo.org/grass/ticket/2258 -->
+<!-- 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.