HTML prettified

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

raster3d/r3.cross.rast/r3.cross.rast.html

@@ -1,13 +1,13 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-This module creates a cross section 2D map from one RASTER3D raster volume
-map based on a 2D elevation map.  It checks if the value of the
-elevation map is located in the z-coordinate space of the 3D map.  If
+This module creates a cross section 2D map from one 3D raster volume
+map based on a 2D elevation map. It checks if the value of the
+elevation map is located in the z-coordinate space of the 3D map. If
 so, the 3D voxel value for this position is transferred to the related
 cross section output map cell, otherwise the NULL value is set.
 
 <center>
-<img src=r3.cross.rast.png border=0><BR>
+<img src=r3.cross.rast.png border=0><br>
 <table border=0 width=700>
 <tr><td><center>
 <i>How r3.cross.rast works</i>
@@ -15,36 +15,33 @@ cross section output map cell, otherwise the NULL value is set.
 </table>
 </center>
 
-
-<br>
-<br>
+<p>
 If the 2D and 3D region settings are different,
 the 2D resolution will be adjust to the 3D resolution.
 
-
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 To create a cut plane elevation map use <em>r.mapcalc</em>. Some examples:
 <ul>
- <li>To create a cut plane elevation map in x direction type
+<li>To create a cut plane elevation map in x direction type
  <br><i>r.mapcalc "cutplane = col()*x"</i>,<br> x be the value for
  the elevation. If the range of col() is 1 ... 10, the elevation map
  has the range 1 ... 10 if x == 1 and if x == 10 the range 10
  ... 100</li>
 
- <li>To create a cut plane elevation map in y direction type
+<li>To create a cut plane elevation map in y direction type
  <br><i>r.mapcalc "cutplane = row()*x"</i>,<br> x be the value for
  the elevation. If the range of col() is 1 ... 10, the elevation map
  has the range 1 ... 10 if x == 1 and if x == 10 the range 10
  ... 100</li>
 
- <li>The user can also make a cut in y and x direction with <em>r.mapcalc</em> by
+<li>The user can also make a cut in y and x direction with <em>r.mapcalc</em> by
      using <br><i>r.mapcalc "cutplane = (row()+col())*x"</i></li>
 </ul>
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
-<H3>Simple Spearfish example</H3>
+<h3>Simple Spearfish example</h3>
 
 <div class="code"><pre>
 g.region -d
@@ -60,15 +57,16 @@ r.mapcalc "cutplane = col()*10"
 r3.cross.rast input=map3d elevation=cutplane output=crosssection
 </pre></div>
 
+<h2>SEE ALSO</h2>
 
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="g.region.html">g.region</A></EM><br>
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM><br>
-<EM><A HREF="r3.mapcalc.html">r3.mapcalc</A></EM><br>
-<EM><A HREF="r3.to.rast.html">r3.to.rast</A></EM><br>
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="r.mapcalc.html">r.mapcalc</a>,
+<a href="r3.mapcalc.html">r3.mapcalc</a>,
+<a href="r3.to.rast.html">r3.to.rast</a>
+</em>
 
-<H2>AUTHOR</H2>
-Soeren Gebbert
+<h2>AUTHOR</h2>
+S&ouml;ren Gebbert
 
 <p><i>Last changed: $Date$</i>

raster3d/r3.gwflow/r3.gwflow.html

@@ -1,30 +1,31 @@
 <h2>DESCRIPTION</h2>
+
 This numerical module calculates implicit transient and steady state,
 confined groundwater flow in three dimensions based on volume maps
 and the current 3D region settings.
 All initial- and boundary-conditions must be provided as volume maps.
 The unit in the location must be meters.
-<br>
 <p>
-This module is sensitive to mask settings. All cells which are outside the mask
-are ignored and handled as no flow boundaries.
+This module is sensitive to mask settings. All cells which are outside
+the mask are ignored and handled as no flow boundaries.
 <p>
-The module calculates the piezometric head and optionally the water balance for each cell
-and the groundwater velocity field in 3 dimensions.
+The module calculates the piezometric head and optionally the water
+balance for each cell and the groundwater velocity field in 3 dimensions.
 The vector components can be visualized with ParaView if they are exported
 with <em>r3.out.vtk</em>.
 
 <p>
 The groundwater flow will always be calculated transient. 
-For steady state computation set the timestep
+For steady state computation the user should set the timestep
 to a large number (billions of seconds) or set the
 specific yield raster map to zero.
 
 <h2>NOTES</h2>
 
-The groundwater flow calculation is based on Darcy's law and a numerical implicit
-finite volume discretization. The discretization results in a symmetric and positive definit
-linear equation system in form of <i>Ax = b</i>, which must be solved. The groundwater flow partial
+The groundwater flow calculation is based on Darcy's law and a numerical
+implicit finite volume discretization. The discretization results in a
+symmetric and positive definit linear equation system in form of
+<i>Ax = b</i>, which must be solved. The groundwater flow partial
 differential equation is of the following form:
 
 <p>
@@ -46,35 +47,39 @@ In detail for 3 dimensions:
 </ul>
 
 <p>
-Two different boundary conditions are implemented, 
-the Dirichlet and Neumann conditions. By default the calculation area
-is surrounded by homogeneous Neumann boundary conditions.
-The calculation and boundary status of single cells can be set with the status map, 
-the following cell states are supportet:
+Two different boundary conditions are implemented, the Dirichlet and
+Neumann conditions. By default the calculation area is surrounded by
+homogeneous Neumann boundary conditions. The calculation and boundary
+status of single cells can be set with the status map, the following
+cell states are supported:
 
 <ul>
-<li>0 == inactive - the cell with status 0 will not be calulated, active cells will have a no flow boundary to an inactive cell</li>
-<li>1 == active - this cell is used for groundwater calculation, inner sources can be defined for those cells</li>
-<li>2 == Dirichlet - cells of this type will have a fixed piezometric head value which do not change over time </li>
+<li>0 == inactive - the cell with status 0 will not be calulated,
+ active cells will have a no flow boundary to an inactive cell</li>
+<li>1 == active - this cell is used for groundwater calculation,
+ inner sources can be defined for those cells</li>
+<li>2 == Dirichlet - cells of this type will have a fixed piezometric
+ head value which do not change over time </li>
 </ul>
 
 <p>
-Note that all required raster maps are read into main memory. Additionally the
-linear equation system will be allocated, so the memory consumption of this
-module rapidely grow with the size of the input maps.
+Note that all required raster maps are read into main memory. Additionally
+the linear equation system will be allocated, so the memory consumption of
+this module rapidely grow with the size of the input maps.
 
 <p>
-The resulting linear equation system <i>Ax = b</i> can be solved with several solvers.
-An iterative solvers with sparse and quadratic matrices support is implemented.
+The resulting linear equation system <i>Ax = b</i> can be solved with
+several solvers. An iterative solvers with sparse and quadratic matrices
+support is implemented.
 The conjugate gradients method with (pcg) and without (cg) precondition.
 Aditionally a direct Cholesky solver is available. This direct solver
-only work with normal quadratic matrices, so be careful using them with large maps
-(maps of size 10.000 cells will need more than one gigabyte of RAM).
-Always prefer a sparse matrix solver.
+only work with normal quadratic matrices, so be careful using them with
+large maps (maps of size 10.000 cells will need more than one Gigabyte
+of RAM). The user should always prefer to use a sparse matrix solver.
 
 <h2>EXAMPLE 1</h2>
-Use this small script to create a working groundwater flow area and
-data. Make sure you are not in a lat/lon projection.
+This small script creates a working groundwater flow area and
+data. It cannot be run in a lat/lon location.
 
 <div class="code"><pre>
 # set the region accordingly
@@ -98,7 +103,7 @@ r3.out.vtk -p in=gwresult,status,budget vector=vx,vy,vz out=/tmp/gwdata3d.vtk
 paraview --data=/tmp/gwdata3d.vtk
 </pre></div>
 
-<H2>EXAMPLE 2</H2>
+<h2>EXAMPLE 2</h2>
 This will create a nice 3D model with geological layer with different
 hydraulic conductivities. Make sure you are not in a lat/lon projection.
 
@@ -129,16 +134,17 @@ paraview --data=/tmp/gwdata3d.vtk
 
 <h2>SEE ALSO</h2>
 
-<em><a href="r.gwflow.html">r.gwflow</a></em><br>
-<em><a href="r.solute.transport.html">r.solute.transport</a></em><br>
-<em><a href="r3.out.vtk.html">r3.out.vtk</a></em>
+<em>
+<a href="r.gwflow.html">r.gwflow</a>,
+<a href="r.solute.transport.html">r.solute.transport</a>,
+<a href="r3.out.vtk.html">r3.out.vtk</a>
+</em>
 
 <h2>AUTHOR</h2>
 S&ouml;ren Gebbert
 <p>
-This work is based on the Diploma Thesis of S&ouml;ren Gebbert available 
-<a href="http://www.hydrogeologie.tu-berlin.de/fileadmin/fg66/_hydro/Diplomarbeiten/2007_Diplomarbeit_Soeren_Gebbert.pdf">here</a>
+This work is based on the Diploma Thesis of S&ouml;ren Gebbert available
+<a href="http://www.hydrogeologie.tu-berlin.de/fileadmin/fg66/_hydro/Diplomarbeiten/2007_Diplomarbeit_S&ouml;ren_Gebbert.pdf">here</a>
 at Technical University Berlin, Germany.
 
-
 <p><i>Last changed: $Date$</i>

raster3d/r3.in.ascii/r3.in.ascii.html

@@ -29,8 +29,8 @@ Default is <em>none</em>.
 
 <h2>NOTES</h2>
 
-The format for the ASCII file is:
-<pre>
+The format of the 3D ASCII file:
+<div class="code"><pre>
 version: <i>"grass7"</i>
 order:   <i>"nsbt" or "nstb" or "snbt" or "sntb"</i>
 north:   <i>floating point</i>
@@ -42,7 +42,7 @@ bottom:  <i>floating point</i>
 rows:    <i>integer</i>
 cols:    <i>integer</i>
 levels:  <i>integer</i>
-</pre>
+</pre></div>
 
 The version and order option have been introduced in GRASS 7 in June 2011.
 The version option is self explaining. The order option specifies the row
@@ -53,15 +53,14 @@ data order in the generated output 3D raster map which is in any case
 <em>north -> south, west -> east, bottom -> top</em> order.
 So dependent on the order information the data is automatically imported
 into the correct internal coordinate system.
-<P>
+<p>
 The version and order options are not mandatory. In case no version and
 order option is specified, the default GRASS 6 ASCII format is assumed.
-<P>
+<p>
 This header is followed by the cell values in <em>floating point</em> format 
 organized in rows with constant <em>col</em> and <em>level</em> coordinate.
 The rows are organized by constant <em>level</em> coordinate. Individual cell
 values are separated by <em>space</em> or <em>CR</em>.
-<p>
 
 <h2>EXAMPLES</h2>
 
@@ -89,15 +88,16 @@ x1,y2,z2  x2,y2,z2  x3,y2,z2  x4,y2,z2
 x1,y3,z2  x2,y3,z2  x3,y3,z2  x4,y3,z2
 </pre></div>
 
-Note that unit tests for r3.in.ascii are implemented in the
+Note that unit tests for <em>r3.in.ascii</em> are implemented in the
 <em>test.r3.out.ascii.sh</em> script located in the
 <em>r3.out.ascii</em> directory.
 
 <h2>AUTHORS</h2>
 Roman Waupotitsch, Michael Shapiro, 
-Helena Mitasova, Bill Brown, Lubos Mitas, Jaro Hofierka, Soeren Gebbert
+Helena Mitasova, Bill Brown, Lubos Mitas, Jaro Hofierka, S&ouml;ren Gebbert
 
 <h2>SEE ALSO</h2>
+
 <em>
 <a href="r.in.ascii.html">r.in.ascii</a>,
 <a href="r3.out.ascii.html">r3.out.ascii</a>,

raster3d/r3.in.v5d/r3.in.v5d.html

@@ -1,8 +1,8 @@
 <h2>DESCRIPTION</h2>
 
-<em>r3.in.v5d</em> imports 3-dimensional files (i.e. the V5D file with one variable
-and one time step). Otherwise, only first variable and timestep from 4/5D
-V5D file will be imported.
+<em>r3.in.v5d</em> imports 3-dimensional files (i.e. the V5D file with
+one variable and one time step). Otherwise, only first variable and
+timestep from 4/5D V5D file will be imported.
 
 <p>
 <a href="http://www.ssec.wisc.edu/~billh/vis5d.html">Vis5D</a> is a system
@@ -14,7 +14,10 @@ for wind trajectory tracing, a way to make text anotations for publications,
 support for interactive data analysis, etc.
 
 <h2>SEE ALSO</h2>
-<em><a href="r3.out.v5d.html">r3.out.v5d</a></em>
+
+<em>
+<a href="r3.out.v5d.html">r3.out.v5d</a>
+</em>
 
 <h2>AUTHOR</h2>
 Jaro Hofierka, GeoModel s.r.o., Slovakia

raster3d/r3.info/r3.info.html

@@ -1,13 +1,16 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>r3.info</EM> reports metadata and range of 3D voxel maps.
+<em>r3.info</em> reports metadata and range of 3D voxel maps.
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="r.info.html">r.info</A></EM><br>
+<em>
+<a href="r.info.html">r.info</a>
+</em>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Roman Waupotitsch, Michael Shapiro, 
 Helena Mitasova, Bill Brown, Lubos Mitas,
 Jaro Hofierka
+
 <p><i>Last changed: $Date$</i>

raster3d/r3.mask/r3.mask.html

@@ -1,26 +1,19 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-File <EM>map</EM> is used as reference file.
+File <em>map</em> is used as reference file.
 Cells in the mask are marked as "mask out" if the corresponding cell in
-<EM>map</EM> contains a value in the range specified with <EM>maskvalues</EM>.
-<P>
+<em>map</em> contains a value in the range specified with <em>maskvalues</em>.
+<p>
 Before a new 3D-mask can be created the exisitng mask has to be removed
-with <EM>g.remove</EM>.
+with <em>g.remove</em>.
 
-<H3>Parameters:</H3>
-<DL>
-<DT><B>maskvalues</B>
-<DD>Values specified to be masked out
+<h2>SEE ALSO</h2>
 
-<DT><B>grid3d</B>
-<DD>Name of RASTER3D-map that is used as the mask reference
-</DL>
+<em>
+<a href="g.remove.html">g.remove</a>
+</em>
 
-<H2>SEE ALSO</H2>
-
-<EM><A HREF="g.remove.html">g.remove</A></EM>
-
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Roman Waupotitsch, Michael Shapiro, 
 Helena Mitasova, Bill Brown, Lubos Mitas,
 Jaro Hofierka

raster3d/r3.null/r3.null.html

@@ -1,13 +1,16 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
+Modifies the NULL values of a 3D raster map.
 
-Modifies the NULL values of <EM>map</EM>.
+<h2>SEE ALSO</h2>
 
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.null.html">r.null</A></EM><br>
+<em>
+<a href="r.null.html">r.null</a>
+</em>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Roman Waupotitsch, Michael Shapiro, 
 Helena Mitasova, Bill Brown, Lubos Mitas,
 Jaro Hofierka
+
 <p><i>Last changed: $Date$</i>

raster3d/r3.out.ascii/r3.out.ascii.html

@@ -5,9 +5,9 @@ a valid 3D raster map in the current mapset search path. The <em>output</em>
 parameter is the name of an ASCII file which will be written in the 
 current working directory.
 <p>
-If <em>output</em> is not specified then standard output (stdout) is used. The
-<em>-h</em> flag may be used to suppress header information. The module is
-sensitive to region settings (set with <em>g.region</em>).
+If <em>output</em> is not specified then standard output (stdout) is used.
+The <em>-h</em> flag may be used to suppress header information. The
+module is sensitive to region settings (set with <em>g.region</em>).
 <p>
 The <em>-c</em> flag will create GRASS 6 <em>r3.in.ascii</em> compatible
 output.
@@ -19,8 +19,8 @@ by <em>r3.in.ascii</em>. In particular, files output by
 3D raster maps with <em>r3.in.ascii</em>.
 
 <p>
-The format for the ASCII file is:
-<pre>
+The format of the ASCII file is:
+<div class="code"><pre>
 version: <i>"grass7"</i>
 order:   <i>"nsbt" or "nstb" or "snbt" or "sntb"</i>
 north:   <i>floating point</i>
@@ -32,33 +32,34 @@ bottom:  <i>floating point</i>
 rows:    <i>integer</i>
 cols:    <i>integer</i>
 levels:  <i>integer</i>
-</pre>
+</pre></div>
 
 The <b>version</b> and <b>order</b> options have been introduced in GRASS 7 in June 2011.
 The <b>order</b> option describes the order of rows and depths in the output. 
 It is possible to create output of different row order using the <em>-r</em> flag 
 and output of different depths order using the  <em>-d</em> flag. The default order is:
-<pre>
-west -> east for columns
-north -> south for rows
-bottom -> top for depths
-</pre>
+<p>
+<div class="code"><pre>
+west -&gt; east for columns
+north -&gt; south for rows
+bottom -&gt; top for depths
+</pre></div>
 
-This order is compatible with the r.in.ascii row -> column ordering. The column 
+This order is compatible with the <em>r.in.ascii</em> row -&gt; column ordering. The column 
 order can not be changed but the row and depth order. Supported orders are:
 
 <ul>
-    <li><b>nsbt</b>:   north -> south and bottom -> top ordering which is the default (no flags)</li>
-    <li><b>snbt</b>:   south -> north and bottom -> top ordering using <em>-r</em> flag</li>
-    <li><b>nstb</b>:   north -> south and top -> bottom ordering using <em>-d</em> flag</li>
-    <li><b>sntb</b>:   south -> north and top -> bottom ordering using <em>-rd</em> flag</li>
+<li><b>nsbt</b>: north -&gt; south and bottom -&gt; top ordering which is the default (no flags)</li>
+<li><b>snbt</b>: south -&gt; north and bottom -&gt; top ordering using <em>-r</em> flag</li>
+<li><b>nstb</b>: north -&gt; south and top -&gt; bottom ordering using <em>-d</em> flag</li>
+<li><b>sntb</b>: south -&gt; north and top -&gt; bottom ordering using <em>-rd</em> flag</li>
 </ul>
 
 The header is followed by cell values in <em>floating point</em> format.
 Cell values are output as a series of horizontal slices in row-major
-order. That is in case of the default north -> south and bottom -> top (nsbt) ordering:
+order. That is in case of the default north -&gt; south and bottom -&gt; top (nsbt) ordering:
 
-<pre>
+<div class="code"><pre>
   (x, y, z)       (x + 1, y, z)     ...     (x + cols, y, z)
 (x, y + 1, z)   (x + 1, y + 1, z)   ...   (x + cols, y + 1, z)
       .                 .                           .
@@ -75,20 +76,24 @@ order. That is in case of the default north -> south and bottom -> top (nsbt) or
 (x, y + rows, z + 1)   (x + 1, y + rows, z + 1) ... (x + cols, y + rows, z + 1)
 
 and so on.
-</pre>
+</pre></div>
 
 The data starts with the upper left corner (NW) at the bottom of the data set.
 
-<P>
-One level maps can be imported with <em>r.in.ascii</em> (2D raster) using the default <b>nsbt</b> order
-and removing the header lines "version", "order", "top", "bottom" and "levels".
+<p>
+One level maps can be imported with <em>r.in.ascii</em> (2D raster) using
+the default <b>nsbt</b> order and removing the header lines "version",
+"order", "top", "bottom" and "levels".
 
 <h2>SEE ALSO</h2>
-<em><a href="r3.in.ascii.html">r3.in.ascii</a></em>,
-<em><a href="g.region.html">g.region</a></em>
 
-<H2>AUTHORS</H2>
+<em>
+<a href="r3.in.ascii.html">r3.in.ascii</a>,
+<a href="g.region.html">g.region</a>
+</em>
+
+<h2>AUTHORS</h2>
 Roman Waupotitsch, Michael Shapiro, 
-Helena Mitasova, Bill Brown, Lubos Mitas, Jaro Hofierka, Soeren Gebbert
+Helena Mitasova, Bill Brown, Lubos Mitas, Jaro Hofierka, S&ouml;ren Gebbert
 
 <p><i>Last changed: $Date$</i>

raster3d/r3.out.v5d/r3.out.v5d.html

@@ -1,8 +1,9 @@
 <h2>DESCRIPTION</h2>
 
 Exports 3D raster maps to V5D format. The <em>map</em> parameter is a valid 
-3D raster map in the current mapset search path. The <em>output</em> parameter is the name 
-of a V5D file which will be written in the current working directory. 
+3D raster map in the current mapset search path. The <em>output</em>
+parameter is the name  of a V5D file which will be written in the current
+working directory. 
 
 <p>
 <a href="http://www.ssec.wisc.edu/~billh/vis5d.html">Vis5D</a> is a system
@@ -14,10 +15,13 @@ for wind trajectory tracing, a way to make text anotations for publications,
 support for interactive data analysis, etc.
 
 <h2>SEE ALSO</h2>
-<i><a href="r3.in.v5d.html">r3.in.v5d</a>,
+
+<em>
+<a href="r3.in.v5d.html">r3.in.v5d</a>,
 <a href="r3.out.vtk.html">r3.out.vtk</a>
-</i>
+</em>
 
 <h2>AUTHOR</h2>
 Jaro Hofierka, GeoModel s.r.o., Slovakia
+
 <p><i>Last changed: $Date$</i>

raster3d/r3.out.vtk/r3.out.vtk.html

@@ -1,76 +1,80 @@
-<H2>DESCRIPTION</H2>
-
-Outputs <I>3D raster</I> maps into <I>VTK-ASCII</I> format.  <I>Maps</I> are
-valid 3D raster maps in the current mapset.  <I>output</I> is the name of
-a VTK-ASCII file which will be written in the current working directory.
-If <I>output</I> is not specified then <B>stdout</B> is used.  
-The module is sensitive to region settings (set with <em>g.region</em>).
-
-<H2>NOTES</H2>
-This filter generates <I>structured points</I>  with <I>celldata</I> 
-(default) or <I>pointdata</I>. If top and bottom surfaces are requested
-a <I>unstructured grid</I> with <I>celldata</I>  or a <I>structured grid</I>
-with <I>pointdata</I> is generated.
+<h2>DESCRIPTION</h2>
+
+The module <em>r3.out.vtk</em> outputs 3D raster maps into VTK-ASCII format.
+Maps are valid 3D raster maps in the current mapset search path. The
+<em>output</em> parameter is the name of a VTK-ASCII file which will be
+written in the current working directory. If <em>output</em> is not
+specified then standard output (stdout) is used. The module is sensitive
+to region settings (set with <em>g.region</em>).
+
+<h2>NOTES</h2>
+
+This module generates <i>structured points</i> with <i>celldata</i> 
+(default) or <i>pointdata</i>. If top and bottom surfaces are requested
+an <i>unstructured grid</i> with <i>celldata</i> or a <i>structured grid</i>
+with <i>pointdata</i> is generated.
 This data is put in a simple VTK-ASCII file. Neither XML nor 
-binary output are supported. It is possible to choose more then one RASTER3D map
-to be written in the VTK-ASCII file. Each <I>celldata</I> is named as the
-3D raster map it represents. You can visualize this file with the 
-<EM><A HREF="http://www.vtk.org">VTK Toolkit</A></EM>, 
-<EM><A HREF="http://www.paraview.org">Paraview</A></EM> and 
-<EM><A HREF="http://mayavi.sourceforge.net">MayaVi</A></EM> which are based on VTK.
-If you have a 3D raster map with partly no data, use the threshold filter in paraview to 
-visualize the valid data. Just filter all data which is greater/lesser than the 
-chosen null value in the VTK-ASCII file.
-
-<BR><BR>
-The top and bottom region settings are expected in meters. 
-If a Latitude-Longitude (LL) coordinates are used, the elevation value for each voxel
-will be converted into degree.
-<BR><BR>
-The <I>input</I>, <I>rgbmaps</I> and <I>vectormaps</I> are optional, 
-so only the geometry can be exported.
-<BR><BR>
-If you use <I>top</I> and <I>bottom</I> and the 2D and 3D region settings are different,
-the 2D resolution will be adjust to the 3D resolution. The elevation maps are expected
-in meters. If LL coordinates are used, the elevation will automatically converted into degree.
-If the surface and bottom maps are in a different unit than meters, use the scale parameter
-to convert them into meters.
-<BR><BR>
+binary output are supported. It is possible to choose more then one 3D raster
+map
+to be written in the VTK-ASCII file. Each <i>celldata</i> is named as the
+3D raster map it represents. The user can visualize this file with the 
+<em><a href="http://www.vtk.org">VTK Toolkit</a></em>, 
+<em><a href="http://www.paraview.org">ParaView</a></em> and 
+<em><a href="http://mayavi.sourceforge.net">MayaVi</a></em> which are based on
+VTK. In case of 3D raster map with partially no data, the threshold filter in
+ParaView can be used to visualize the valid data. Just filter all data which is
+greater/lesser than the chosen null value in the VTK-ASCII file.
+
+<p>
+The top and bottom region values are expected in meters. 
+If a Latitude-Longitude (LL) coordinates are used, the elevation value for each
+voxel will be converted into degrees.
+
+<p>
+The <em>input</em>, <em>rgbmaps</em> and <em>vectormaps</em> parameters are
+optional, so only the geometry can be exported.
+
+<p>
+If the user defines <em>top</em> and <em>bottom</em> and the 2D and 3D region
+values differ, the 2D resolution will be adjusted to the 3D resolution. The
+elevation maps are expected in meters. If Lat/Long coordinates are used, the
+elevation will automatically converted into degree.
+If the surface and bottom maps are in a different unit than meters, use the
+scale parameter to convert them into meters.
+
+<p>
 The RGB voxel data can be created from 2D raster maps (Landsat TM images) 
-with <EM><A HREF="r.to.rast3.html">r.to.rast3</A></EM>. The values of the RGB maps
+with <em><a href="r.to.rast3.html">r.to.rast3</a></em>. The values of the RGB maps
 must be within 0 and 255. If not, the values are automatically set
 to 0 and warnings will be printed to stderr.
-<BR><BR>
+
+<p>
 The vector data is created from three 3D raster maps. Each map represents a vector component.
 So x, y and z components are required in this order. This data can be visualized with Glyph3d or 
 StreamTracer filters within Paraview.
-<br>
-<br>
-If the <em>-c</em> flag is used and the data should be visualised together with other
-data exported via <em>*.out.vtk</em> modules, be sure the <em>-c</em> flag was also
-set in these modules. But this will only work with data from the SAME location (the
-reference point for the coordinates transformation is based on the center point of
-the default region).
 
-<H3>Difference between point- and celldata</H3>
+<p>
+If the <em>-c</em> flag is used and the data should be visualised together with
+other data exported via <em>*.out.vtk</em> modules, be sure the <em>-c</em> flag
+was also set in these modules. But this will only work with data from the SAME
+location (the reference point for the coordinates transformation is based on the
+center point of the default region).
+
+<h3>Difference between point- and celldata</h3>
 
 <em>r3.out.vtk</em> can export 3D raster maps with different representations.
 <ul>
-   <li>
-      <I>pointdata</I> -- the cells/values are represented by the center of the cell. 
-      Instead of cells, points are created. Each point can hold different values, 
-      but the user can only visualize one value at a time. 
-   </li>
-   <li>
-       <I>celldata</I>  
-       The cells are created with the same hight, width and depth as in GRASS. Each cell 
-       can hold different values, but the user can only visualize one value at a time. 
-   </li>
+<li> <em>pointdata</em> -- the cells/values are represented by the center of the
+cell. Instead of cells, points are created. Each point can hold different
+values, but the user can only visualize one value at a time.</li>
+<li> <em>celldata</em> The cells are created with the same hight, width and depth
+as in GRASS. Each cell can hold different values, but the user can only
+visualize one value at a time.</li>
 </ul>
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
-<H3>Simple Spearfish example</H3>
+<h3>Simple Spearfish example</h3>
 
 <div class="code"><pre>
 g.region -d
@@ -166,11 +170,13 @@ paraview --data=/tmp/slovakia3d.vtk
 
 <h2>SEE ALSO</h2>
 
-<em><A HREF="r.out.vtk.html">r.out.vtk</a></em>,
-<em><A HREF="r3.out.ascii.html">r3.out.ascii</a></em>,
-<em><A HREF="g.region.html">g.region</a></em>
+<em>
+<a href="r.out.vtk.html">r.out.vtk</a>,
+<a href="r3.out.ascii.html">r3.out.ascii</a>,
+<a href="g.region.html">g.region</a>
+</em>
 
 <h2>AUTHOR</h2>
-Soeren Gebbert
+S&ouml;ren Gebbert
 
 <p><i>Last changed: $Date$</i>

raster3d/r3.retile/r3.retile.html

@@ -1,16 +1,19 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-Writes a copy of an existing RASTER3D map with a user defined 
+Writes a copy of an existing 3D raster map with a user defined 
 number of tiles in x, y and z direction. 
-The precision and the type of the original RASTER3D map are used for the new retiled RASTER3D map. 
+The precision and the type of the original 3D raster map are used for
+the new retiled 3D raster map. 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM><A HREF="r3.info.html">r3.cross.rast</A></EM><br>
-<EM><A HREF="r3.out.ascii.html">r3.out.ascii</A></EM><br>
-<EM><A HREF="g.region.html">g.region</A></EM><br>
+<em>
+<a href="r3.info.html">r3.cross.rast</a>,
+<em><a href="r3.out.ascii.html">r3.out.ascii</a>,
+<em><a href="g.region.html">g.region</a>
+</em>
 
-<H2>AUTHOR</H2>
-Soeren Gebbert
+<h2>AUTHOR</h2>
+S&ouml;ren Gebbert
 
 <p><i>Last changed: $Date: 2010-09-24 14:05:56 +0200 (Fr, 24. Sep 2010) $</i>

raster3d/r3.stats/r3.stats.html

@@ -11,13 +11,14 @@ If the flag <em>-e</em> is set, the number of subranges will be ignored.
 
 As with most GRASS 3D raster map modules, <em>r3.stats</em> operates on the cell
 array defined by the current 3D region settings, not the original extent and
-resolution of the input map. See <em><a href="g.region.html">g.region</a></em>.
+resolution of the input map. See <em>g.region</em>.
 <p>
 The region setting will not effect the memory consumption of this module.
 The number of subranges in case of value range calculation or the number of 
 equal value groups effect the memory consumption and the calculation time.
-The user can expect a huge time consumption to calculate the equal value groups (flag <em>-e</em>)
-if large region settings occur for maps which have many equal value groups (> 100000).
+The user can expect a huge time consumption to calculate the equal value
+groups (flag <em>-e</em>) if large region settings occur for maps which
+have many equal value groups (> 100000).
 
 <h2>EXAMPLES</h2>
 <h3>Lausanne FOSS4G 2006 3D demo dataset example</h3>
@@ -83,8 +84,6 @@ Sum of all cells:
         Volume = 600000000.000
         Percentage = 100.000
         Cell count = 600
-
-
 </pre></div>
 
 <h2>SEE ALSO</h2>
@@ -99,8 +98,7 @@ Sum of all cells:
 
 
 <h2>AUTHOR</h2>
-
-Soeren Gebbert<br>
+S&ouml;ren Gebbert
 
 <p>
 <i>Last changed: $Date$</i>

raster3d/r3.timestamp/r3.timestamp.html

@@ -1,40 +1,37 @@
-<H2>DESCRIPTION</H2>
-
+<h2>DESCRIPTION</h2>
 
 This command has 2 modes of operation. If no date argument
-     is supplied, then the current timestamp for the grid3d map
-     is printed. If a date argument is specified, then the
-     timestamp for the grid3d map is set to the specified
-     date(s).  See EXAMPLES below.
-
-
+is supplied, then the current timestamp for the 3D raster map
+is printed. If a date argument is specified, then the
+timestamp for the 3D raster map is set to the specified
+date(s). See EXAMPLES below.
 
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
 
- <b>r3.timestamp map=soils</b><br>
-	  Prints the timestamp for the "soils" grid3d map. If
+<b>r3.timestamp map=soils</b><br>
+	  Prints the timestamp for the "soils" 3D raster map. If
 	  there is no timestamp for soils, nothing is printed. If
 	  there is a timestamp, one or two lines are printed,
 	  depending on if the timestamp for the map consists of a
 	  single date or two dates (ie start and end dates).
 <p>
-<b>     r3.timestamp map=soils date='15 sep 1987'</b><br>
+<b>r3.timestamp map=soils date='15 sep 1987'</b><br>
 	  Sets the timestamp for "soils" to the single date<br>
 	  "15 sep 1987"
 <p>
-<b>     r3.timestamp map=soils date='15 sep 1987/20 feb 1988'</b><br>
+<b>r3.timestamp map=soils date='15 sep 1987/20 feb 1988'</b><br>
 	  Sets the timestamp for "soils" to have the start date<br>
 	  "15 sep 1987" and the end date "20 feb 1988"
 <p>
-<b>     r3.timestamp map=soils date='18 feb 2005 10:30:00/20 jul 2007 20:30:00'</b><br>
+<b>r3.timestamp map=soils date='18 feb 2005 10:30:00/20 jul 2007 20:30:00'</b><br>
 	  Sets the timestamp for "soils" to have the start date<br>
 	  "18 aug 2005 10:30:00" and the end date "20 jul 2007 20:30:00"
 <p>
 
-<b>     r3.timestamp map=soils date=none</b><br>
-	  Removes the timestamp for the "soils" grid3d map
+<b>r3.timestamp map=soils date=none</b><br>
+	  Removes the timestamp for the "soils" 3D raster map
 
-<H2>TIMESTAMP FORMAT</H2>
+<h2>TIMESTAMP FORMAT</h2>
      The timestamp values must use the format as described in the
      GRASS datetime library.  The source tree for this library
      should have a description of the format. For convience, the
@@ -45,7 +42,7 @@ This command has 2 modes of operation. If no date argument
      Relative values specify a span of time. Some examples will
      help clarify:
 <p>
-   <b>  Absolute</b><p>
+<b>Absolute</b><p>
 	  The general format for absolute values is
 <p><tt>
 	     day month year [bc] hour:minute:seconds timezone
@@ -95,12 +92,14 @@ This command has 2 modes of operation. If no date argument
 	     3 months 15 days<br>
 	     3 years 10 days
 </tt>
-<H2>BUGS</H2>
+
+<h2>BUGS</h2>
 Spaces in the timestamp value are required.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Michael Pelizzari<br>
 Lockheed Martin Space Systems<br>
 based on r.timestamp by Michael Shapiro, <br>
-U.S.Army Construction Engineering Research Laboratory
+U.S. Army Construction Engineering Research Laboratory
+
 <p><i>Last changed: $Date$</i>

raster3d/r3.to.rast/r3.to.rast.html

@@ -15,7 +15,6 @@ The user can force <em>r3.to.rast</em> to use the 2D resolution of the input
 </table>
 </center>
 
-
 <h2>NOTES</h2>
 Every slice of the 3D raster map is copied to one 2D raster map. The maps
 are named like <b>output</b><em>_slicenumber</em>. Slices are counted from bottom
@@ -25,12 +24,14 @@ The number of slices is equal to the number of depths.
 
 <h2>SEE ALSO</h2>
 
-<em><a href="r3.cross.rast.html">r3.cross.rast</a></em><br>
-<em><a href="r3.out.vtk.html">r3.out.vtk</a></em><br>
-<em><a href="r3.out.ascii.html">r3.out.ascii</a></em><br>
-<em><a href="g.region.html">g.region</a></em><br>
+<em>
+<a href="r3.cross.rast.html">r3.cross.rast</a>,
+<a href="r3.out.vtk.html">r3.out.vtk</a>,
+<a href="r3.out.ascii.html">r3.out.ascii</a>,
+<a href="g.region.html">g.region</a>
+</em>
 
 <h2>AUTHOR</h2>
-Soeren Gebbert
+S&ouml;ren Gebbert
 
 <p><i>Last changed: $Date$</i>