cleanup

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

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

@@ -1,36 +1,8 @@
-<H2>DESCRIPTION</H2>
-Convert a 3D ASCII raster text file into a (binary) 3D raster map layer. 
+<h2>DESCRIPTION</h2>
 
-<H3>Parameters:</H3>
-<DL>
-<DT><B>type</B>
-<DD>Data type used in the output file
-<DD>Options: default, double, float
+<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.
 
-<DT><B>precision</B>
-<DD>Precision used in the output file
-<DD>Options: default, max, 0-52
-
-<DT><B>compression</B>
-<DD>Note that 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.  RASTER3D does
-not support non-compressed files.
-<DD>Options: default, rle, none
-
-<DT><B>tiledimension</B>
-<DD>The dimension of the tiles used in the output file.  The format is: XxYxZ
-
-<DT><B>nv</B>
-<DD>Specifies which value to convert to NULL-value.  If the specified value is 
-<em>none</em>, no conversion is performed.  Default is <em>*</em>.
-
-<DT><B>input</B>
-<DD>Path and name of ASCII file to be imported
-
-<DT><B>output</B>
-<DD>Name of the RASTER3D output map
-</DL>
 
 <center>
 <img src="g3d_volume_layout.png" border=0><BR>
@@ -41,8 +13,8 @@ not support non-compressed files.
 </table>
 </center>
 
-<H2>NOTES</H2>
-The format for the ascii file is:
+<h2>NOTES</h2>
+The format for the ASCII file is:
 <pre>
 version: <i>"grass7"</i>
 order:   <i>"nsbt" or "nstb" or "snbt" or "sntb"</i>
@@ -57,28 +29,32 @@ cols:    <i>integer</i>
 levels:  <i>integer</i>
 </pre>
 
-The version and order option are introduced in grass7 June 2011. The version option 
-is self explaining. The order option specifies the row and depth order of the data in the input file.
-The supported row/depth ordering is documented in the <A HREF="r3.out.ascii.html">r3.out.ascii</A> 
-manpage. The order of the data in the input file does not specifiy the data order in the 
-generated output raster3d map which is in any case <em>north -> south, west -> east, bottom -> top</em> ordering. 
-So dependent on the order information the data is automatically imported into the correct internal coordinate system.
+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
+and depth order of the data in the input file.
+The supported row/depth ordering is documented in the <em>r3.out.ascii</em>
+manual page. The order of the data in the input file does not specifiy the
+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>
-The version and order options are not mandatory. In case no version and order option is specified, 
-the default grass6 ascii format is assumed.
+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>
-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>.
+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>
+<h2>EXAMPLES</h2>
 
-4x3x2 sample. Note in case no specific ordering is specified in the input file the
-upper-left (NW) corner of the bottom level comes first. The according order option is: nsbt for
-north -> south, bottom -> top ordering. This is identical with <em>r.in.ascii</em>
-for single level data. So the y coordinate is 0 at the northern edge.
+4x3x2 sample. Note in case no specific ordering is specified in the input
+file the upper-left (NW) corner of the bottom level comes first. The according
+order option is: nsbt for north -> south, bottom -> top ordering. This is
+identical with <em>r.in.ascii</em> for single level data. So the y coordinate
+is 0 at the northern edge.
 
 <div class="code"><pre>
 north: 3.0
@@ -98,19 +74,20 @@ 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 <em>test.r3.out.ascii.sh</em> script located in 
-the r3.out.ascii directory.
+Note that unit tests for r3.in.ascii are implemented in the
+<em>test.r3.out.ascii.sh</em> script located in the
+<em>r3.out.ascii</em> directory.
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Roman Waupotitsch, Michael Shapiro, 
 Helena Mitasova, Bill Brown, Lubos Mitas, Jaro Hofierka, Soeren 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>,
-<A HREF="v.to.rast3.html">v.to.rast3</A>
-</EM>
+<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>,
+<a href="v.to.rast3.html">v.to.rast3</a>
+</em>
 
 <p>
 <i>Last changed: $Date$</i>