[GRASS-SVN] r48277 - in grass/branches/releasebranch_6_4/raster3d:
base r3.cross.rast r3.gwflow r3.in.ascii r3.in.v5d
r3.out.ascii r3.out.v5d r3.out.vtk r3.stats r3.to.rast
svn_grass at osgeo.org
svn_grass at osgeo.org
Tue Sep 13 16:13:36 EDT 2011
Author: neteler
Date: 2011-09-13 13:13:36 -0700 (Tue, 13 Sep 2011)
New Revision: 48277
Modified:
grass/branches/releasebranch_6_4/raster3d/base/r3.info.html
grass/branches/releasebranch_6_4/raster3d/base/r3.mask.html
grass/branches/releasebranch_6_4/raster3d/base/r3.null.html
grass/branches/releasebranch_6_4/raster3d/base/r3.timestamp.html
grass/branches/releasebranch_6_4/raster3d/r3.cross.rast/description.html
grass/branches/releasebranch_6_4/raster3d/r3.gwflow/description.html
grass/branches/releasebranch_6_4/raster3d/r3.in.ascii/description.html
grass/branches/releasebranch_6_4/raster3d/r3.in.v5d/description.html
grass/branches/releasebranch_6_4/raster3d/r3.out.ascii/description.html
grass/branches/releasebranch_6_4/raster3d/r3.out.v5d/description.html
grass/branches/releasebranch_6_4/raster3d/r3.out.vtk/description.html
grass/branches/releasebranch_6_4/raster3d/r3.stats/description.html
grass/branches/releasebranch_6_4/raster3d/r3.to.rast/description.html
Log:
HTML prettified
Modified: grass/branches/releasebranch_6_4/raster3d/base/r3.info.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/base/r3.info.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/base/r3.info.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -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>
Modified: grass/branches/releasebranch_6_4/raster3d/base/r3.mask.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/base/r3.mask.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/base/r3.mask.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -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 G3D-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
Modified: grass/branches/releasebranch_6_4/raster3d/base/r3.null.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/base/r3.null.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/base/r3.null.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -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>
Modified: grass/branches/releasebranch_6_4/raster3d/base/r3.timestamp.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/base/r3.timestamp.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/base/r3.timestamp.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -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,11 +42,11 @@
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
-<p>
+<br>
day is 1-31<br>
month is jan,feb,...,dec<br>
year is 4 digit year<br>
@@ -58,16 +55,16 @@
mintue is 0-59<br>
second is 0-59.9999 (fractions of second allowed)<br>
timezone is +hhmm or -hhmm (eg, -0600)<br>
-<p>
+<br>
parts can be missing
-<p>
+<br>
1994 [bc]<br>
Jan 1994 [bc]<br>
15 jan 1000 [bc]<br>
15 jan 1994 [bc] 10 [+0000]<br>
15 jan 1994 [bc] 10:00 [+0100]<br>
15 jan 1994 [bc] 10:00:23.34 [-0500]<br>
-<p>
+<br>
</tt>
<b> Relative</b>
There are two types of relative datetime values, year-
@@ -94,13 +91,15 @@
<tt>
3 months 15 days<br>
3 years 10 days
-<p>
-<H2>BUGS</H2>
+</tt>
+
+<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>
Modified: grass/branches/releasebranch_6_4/raster3d/r3.cross.rast/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/r3.cross.rast/description.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/r3.cross.rast/description.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -23,19 +23,19 @@
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>
@@ -48,7 +48,7 @@
g.region res=150 res3=150 t=1000 b=0 tbres=100
# synthetic data, could be geological structures:
-r3.mapcalc "map3d=sin(row())+sin(col())+sin(depth()*depth())"
+r3.mapcalc "map3d = sin(row())+sin(col())+sin(depth()*depth())"
#create a cutplane map
r.mapcalc "cutplane = col()*10"
@@ -59,12 +59,14 @@
<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
+Sören Gebbert
<p><i>Last changed: $Date$</i>
Modified: grass/branches/releasebranch_6_4/raster3d/r3.gwflow/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/r3.gwflow/description.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/r3.gwflow/description.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -1,4 +1,5 @@
<h2>DESCRIPTION</h2>
+
This numerical module calculates transient, confined groundwater flow
in three dimensions based on volume maps and the current 3D region resolution.
All initial- and boundary-conditions must be provided as
@@ -12,14 +13,14 @@
<p>
The groundwater flow will always be calculated transient.
-If you want to calculate steady state, set the timestep
-to a large number (billions of seconds) or set the
-specific yield raster maps to zero.
+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
-finite volume discretization. The groundwater flow partial
+finite volume discretization. The groundwater flow partial
differential equation is of the following form:
<p>
@@ -41,39 +42,39 @@
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:
+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>
The groundwater flow equation can be solved with several numerical solvers.
-Aditionally a direct Gauss solver and LU solver are available. Those direct solvers
+Additionally a direct Gauss solver and a LU solver are available. Those direct solvers
only work with quadratic matrices, so be careful using them with large maps
-(maps of size 10.000 cells will need more than one gigabyte of RAM).
+(maps of size 10.000 cells will need more than one Gigabyte of RAM).
<h2>EXAMPLE</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
g.region res=25 res3=25 t=100 b=0 n=1000 s=0 w=0 e=1000 -p
#now create the input raster maps for a confined aquifer
-r3.mapcalc "phead=if(row() == 1 && depth() == 4, 50, 40)"
-r3.mapcalc "status=if(row() == 1 && depth() == 4, 2, 1)"
-r3.mapcalc "well=if(row() == 20 && col() == 20 , -0.00025, 0)"
-r3.mapcalc "hydcond=0.00025"
-r3.mapcalc "syield=0.0001"
-r.mapcalc "recharge=0.0"
+r3.mapcalc "phead = if(row() == 1 && depth() == 4, 50, 40)"
+r3.mapcalc "status = if(row() == 1 && depth() == 4, 2, 1)"
+r3.mapcalc "well = if(row() == 20 && col() == 20 , -0.00025, 0)"
+r3.mapcalc "hydcond = 0.00025"
+r3.mapcalc "syield = 0.0001"
+r.mapcalc "recharge = 0.0"
r3.gwflow -s solver=cg phead=phead status=status hc_x=hydcond hc_y=hydcond \
hc_z=hydcond q=well s=syield r=recharge output=gwresult dt=8640000 velocity=gwresult_velocity
@@ -82,14 +83,21 @@
r3.out.vtk -p in=gwresult,status vector=gwresult_velocity_x,gwresult_velocity_y,gwresult_velocity_z out=/tmp/gwdata3d.vtk
#now load the data into ParaView
+paraview --data=/tmp/gwdata3d.vtk
</pre></div>
<h2>SEE ALSO</h2>
-<em><a href="r.gwflow.html">r.gwflow</a></em><br>
-<em><a href="r3.out.vtk.html">r3.out.vtk</a></em><br>
+<em>
+<a href="r.gwflow.html">r.gwflow</a>,
+<a href="r3.out.vtk.html">r3.out.vtk</a>
+</em>
<h2>AUTHOR</h2>
-Soeren Gebbert
+Sören Gebbert
+<p>
+This work is based on the Diploma Thesis of Sören Gebbert available
+<a href="http://www.hydrogeologie.tu-berlin.de/fileadmin/fg66/_hydro/Diplomarbeiten/2007_Diplomarbeit_Sören_Gebbert.pdf">here</a>
+at Technical University Berlin, Germany.
<p><i>Last changed: $Date$</i>
Modified: grass/branches/releasebranch_6_4/raster3d/r3.in.ascii/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/r3.in.ascii/description.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/r3.in.ascii/description.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -3,9 +3,25 @@
<em>r3.in.ascii</em> allows a user to create a (binary) GRASS 3D raster map
layer from a 3D ASCII raster input file with (optional) TITLE.
+<p>
+Note that for compression the <em>none</em> option only specifies
+that neither LZW nor RLE is used for compression. It
+does not turn off the compression all together. 3D raster maps do
+not support non-compressed files.
+
+<p>
+The <em>tiledimension</em> parameter defines the dimension of the tiles
+used in the output file. The format is: XxYxZ
+
+<p>
+The <em>nv</em> parameter specifies which value to convert to NULL-value.
+If the specified value is <em>none</em>, no conversion is performed.
+Default is <em>none</em>.
+
<h2>NOTES</h2>
+
The format of the 3D ASCII file:
-<pre>
+<div class="code"><pre>
north: <em>floating point</em>
south: <em>floating point</em>
east: <em>floating point</em>
@@ -15,7 +31,7 @@
rows: <em>integer</em>
cols: <em>integer</em>
levels: <em>integer</em>
-</pre>
+</pre></div>
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
@@ -26,21 +42,6 @@
library at an early stage and will be turned off as soon as confidence has
built up.
-<p>
-Note that for compression the <em>none</em> option only specifies
-that neither LZW nor RLE is used for compression. It
-does not turn off the compression all together. 3D raster maps do
-not support non-compressed files.
-
-<p>
-The <em>tiledimension</em> parameter defines the dimension of the tiles
-used in the output file. The format is: XxYxZ
-
-<p>
-The <em>nv</em> parameter specifies which value to convert to NULL-value.
-If the specified value is <em>none</em>, no conversion is performed.
-Default is <em>none</em>.
-
<h2>EXAMPLES</h2>
4x3x2 sample. Note, that lower-left (SW) corner of the bottom level comes first.
@@ -92,6 +93,7 @@
Helena Mitasova, Bill Brown, Lubos Mitas, Jaro Hofierka
<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>,
Modified: grass/branches/releasebranch_6_4/raster3d/r3.in.v5d/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/r3.in.v5d/description.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/r3.in.v5d/description.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -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,8 +14,11 @@
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
Modified: grass/branches/releasebranch_6_4/raster3d/r3.out.ascii/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/r3.out.ascii/description.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/r3.out.ascii/description.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -5,9 +5,9 @@
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>).
<h2>NOTES</h2>
The default format for the ASCII file is equivalent to that required
@@ -16,8 +16,8 @@
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>
north: <i>floating point</i>
south: <i>floating point</i>
east: <i>floating point</i>
@@ -27,27 +27,30 @@
rows: <i>integer</i>
cols: <i>integer</i>
levels: <i>integer</i>
-</pre>
+</pre></div>
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,
-<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)
and so on.
-</pre>
+</pre></div>
<p>
-One level maps can be imported with <em>r.in.ascii</em> (Raster 2D) after removing
+One level maps can be imported with <em>r.in.ascii</em> (2D raster) after removing
the header lines "top", "bottom" and "levels".
<h2>SEE ALSO</h2>
-<em><a href="r3.in.ascii.html">r3.in.ascii</a></em><br>
-<em><a href="g.region.html">g.region</a></em><br>
+<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
Modified: grass/branches/releasebranch_6_4/raster3d/r3.out.v5d/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/r3.out.v5d/description.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/r3.out.v5d/description.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -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,9 +15,11 @@
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
Modified: grass/branches/releasebranch_6_4/raster3d/r3.out.vtk/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/r3.out.vtk/description.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/r3.out.vtk/description.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -8,6 +8,7 @@
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>
@@ -34,24 +35,23 @@
optional, so only the geometry can be exported.
<p>
-If you use <i>top</i> and <i>bottom</i> and the 2D and 3D region values 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 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 must be within 0 and 255. If not, the values are automatically set
+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.
<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.
+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.
<p>
If the <em>-c</em> flag is used and the data should be visualised together with
@@ -64,12 +64,12 @@
<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
+<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> <I>celldata</I> The cells are created with the same hight, width and depth
+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>
+visualize one value at a time.</li>
</ul>
<h2>EXAMPLE</h2>
@@ -79,10 +79,10 @@
<div class="code"><pre>
g.region -d
g.region res=150 res3=150 t=80 b=0 tbres=10
-r.mapcalc "bottom=1800. - elevation.10m"
+r.mapcalc "bottom = 1800. - elevation.10m"
# synthetic data, could be geological structures:
-r3.mapcalc "map3d=row()+col()+depth()"
+r3.mapcalc "map3d = row()+col()+depth()"
#export of volume to VTK:
r3.out.vtk -s input=map3d top=elevation.10m bottom=bottom output=/tmp/out.vtk
@@ -99,10 +99,10 @@
g.region n=4926970 s=4914857 w=591583 e=607793 res=50 res3=50 t=80 b=0 tbres=10
#create a bottom surface
-r.mapcalc "bottom=1800. - elevation.10m"
+r.mapcalc "bottom = 1800. - elevation.10m"
# synthetic data, could be geological structures:
-r3.mapcalc "map3d=row()+col()+depth()"
+r3.mapcalc "map3d = row()+col()+depth()"
#get some satellite images with r.in.onearth
r.in.onearth -l output=Sat tmband=Red
@@ -130,15 +130,15 @@
g.region n=4926970 s=4914857 w=591583 e=607793 res=50 res3=50 t=80 b=0 tbres=10
# create a bottom surface
-r.mapcalc "bottom=1800. - elevation.10m"
+r.mapcalc "bottom = 1800. - elevation.10m"
# synthetic data, could be geological structures:
-r3.mapcalc "map3d=row()+col()+depth()"
+r3.mapcalc "map3d = row()+col()+depth()"
# synthetic vector data, could be groundwater stream vectors
-r3.mapcalc "x_part =sin(row())"
-r3.mapcalc "y_part =cos(col())"
-r3.mapcalc "z_part =sin(depth())"
+r3.mapcalc "x_part = sin(row())"
+r3.mapcalc "y_part = cos(col())"
+r3.mapcalc "z_part = sin(depth())"
# export the stuff data to VTK:
@@ -156,7 +156,7 @@
<div class="code"><pre>
#reduce resolution:
g.region -dp3 res=1000 res3=1000
-r.mapcalc "bottom=100"
+r.mapcalc "bottom = 100"
#export of volume to VTK:
r3.out.vtk -s in=precip3d.500z50 top=dem500 bottom=bottom
@@ -170,11 +170,13 @@
<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ören Gebbert
<p><i>Last changed: $Date$</i>
Modified: grass/branches/releasebranch_6_4/raster3d/r3.stats/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/r3.stats/description.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/r3.stats/description.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -11,13 +11,14 @@
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 @@
Volume = 600000000.000
Percentage = 100.000
Cell count = 600
-
-
</pre></div>
<h2>SEE ALSO</h2>
@@ -99,8 +98,7 @@
<h2>AUTHOR</h2>
+Sören Gebbert
-Soeren Gebbert<br>
-
<p>
<i>Last changed: $Date$</i>
Modified: grass/branches/releasebranch_6_4/raster3d/r3.to.rast/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/r3.to.rast/description.html 2011-09-13 20:13:02 UTC (rev 48276)
+++ grass/branches/releasebranch_6_4/raster3d/r3.to.rast/description.html 2011-09-13 20:13:36 UTC (rev 48277)
@@ -15,7 +15,6 @@
</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 @@
<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ören Gebbert
<p><i>Last changed: $Date$</i>
More information about the grass-commit
mailing list