[GRASS-SVN] r31374 - in grass/trunk/raster: r.average r.basins.fill
r.bilinear r.bitpattern r.buffer r.carve r.cats r.circle
r.coin r.colors r.compress r.contour r.cost r.covar r.cross
r.describe r.digit r.drain r.grow2 r.gwflow r.in.bin
r.in.gridatb r.in.mat r.in.poly r.in.xyz r.info r.kappa r.li
r.los r.median r.mfilter r.mfilter.fp r.mode r.null r.out.arc
r.out.ascii r.out.bin r.out.gdal r.out.gridatb r.out.mat
r.out.mpeg r.out.png r.out.pov r.out.ppm r.out.ppm3
r.out.tiff r.out.vrml r.out.vtk r.patch r.profile r.proj
r.proj.seg r.quant r.quantile r.random r.random.cells
r.random.surface r.reclass r.recode r.region r.report
r.resamp.interp r.resamp.rst r.resamp.stats r.resample
r.rescale r.rescale.eq r.series r.statistics r.stats r.sum
r.sun r.sunmask r.support.stats r.surf.area r.surf.contour
r.surf.fractal r.surf.gauss r.surf.idw r.surf.idw2
r.surf.random r.terraflow r.texture r.thin r.timestamp
r.to.rast3 r.to.rast3elev r.to.vect r.topidx r.topmodel
r.transect r.volume r.walk r.water.outlet r.what r.what.color
svn_grass at osgeo.org
svn_grass at osgeo.org
Fri May 16 14:37:23 EDT 2008
Author: epatton
Date: 2008-05-16 14:37:23 -0400 (Fri, 16 May 2008)
New Revision: 31374
Modified:
grass/trunk/raster/r.average/description.html
grass/trunk/raster/r.basins.fill/description.html
grass/trunk/raster/r.bilinear/description.html
grass/trunk/raster/r.bitpattern/description.html
grass/trunk/raster/r.buffer/description.html
grass/trunk/raster/r.carve/description.html
grass/trunk/raster/r.cats/description.html
grass/trunk/raster/r.circle/description.html
grass/trunk/raster/r.coin/description.html
grass/trunk/raster/r.colors/description.html
grass/trunk/raster/r.compress/description.html
grass/trunk/raster/r.contour/description.html
grass/trunk/raster/r.cost/description.html
grass/trunk/raster/r.covar/description.html
grass/trunk/raster/r.cross/description.html
grass/trunk/raster/r.describe/description.html
grass/trunk/raster/r.digit/description.html
grass/trunk/raster/r.drain/description.html
grass/trunk/raster/r.grow2/description.html
grass/trunk/raster/r.gwflow/description.html
grass/trunk/raster/r.in.bin/description.html
grass/trunk/raster/r.in.gridatb/description.html
grass/trunk/raster/r.in.mat/description.html
grass/trunk/raster/r.in.poly/description.html
grass/trunk/raster/r.in.xyz/description.html
grass/trunk/raster/r.info/description.html
grass/trunk/raster/r.kappa/description.html
grass/trunk/raster/r.li/description.html
grass/trunk/raster/r.los/description.html
grass/trunk/raster/r.median/description.html
grass/trunk/raster/r.mfilter.fp/description.html
grass/trunk/raster/r.mfilter/description.html
grass/trunk/raster/r.mode/description.html
grass/trunk/raster/r.null/description.html
grass/trunk/raster/r.out.arc/description.html
grass/trunk/raster/r.out.ascii/description.html
grass/trunk/raster/r.out.bin/description.html
grass/trunk/raster/r.out.gdal/description.html
grass/trunk/raster/r.out.gridatb/description.html
grass/trunk/raster/r.out.mat/description.html
grass/trunk/raster/r.out.mpeg/description.html
grass/trunk/raster/r.out.png/description.html
grass/trunk/raster/r.out.pov/description.html
grass/trunk/raster/r.out.ppm/description.html
grass/trunk/raster/r.out.ppm3/description.html
grass/trunk/raster/r.out.tiff/description.html
grass/trunk/raster/r.out.vrml/description.html
grass/trunk/raster/r.out.vtk/description.html
grass/trunk/raster/r.patch/description.html
grass/trunk/raster/r.profile/description.html
grass/trunk/raster/r.proj.seg/description.html
grass/trunk/raster/r.proj/description.html
grass/trunk/raster/r.quant/description.html
grass/trunk/raster/r.quantile/description.html
grass/trunk/raster/r.random.cells/description.html
grass/trunk/raster/r.random.surface/description.html
grass/trunk/raster/r.random/description.html
grass/trunk/raster/r.reclass/description.html
grass/trunk/raster/r.recode/description.html
grass/trunk/raster/r.region/description.html
grass/trunk/raster/r.report/description.html
grass/trunk/raster/r.resamp.interp/description.html
grass/trunk/raster/r.resamp.rst/description.html
grass/trunk/raster/r.resamp.stats/description.html
grass/trunk/raster/r.resample/description.html
grass/trunk/raster/r.rescale.eq/description.html
grass/trunk/raster/r.rescale/description.html
grass/trunk/raster/r.series/description.html
grass/trunk/raster/r.statistics/description.html
grass/trunk/raster/r.stats/description.html
grass/trunk/raster/r.sum/description.html
grass/trunk/raster/r.sun/description.html
grass/trunk/raster/r.sunmask/description.html
grass/trunk/raster/r.support.stats/description.html
grass/trunk/raster/r.surf.area/description.html
grass/trunk/raster/r.surf.contour/description.html
grass/trunk/raster/r.surf.fractal/description.html
grass/trunk/raster/r.surf.gauss/description.html
grass/trunk/raster/r.surf.idw/description.html
grass/trunk/raster/r.surf.idw2/description.html
grass/trunk/raster/r.surf.random/description.html
grass/trunk/raster/r.terraflow/description.html
grass/trunk/raster/r.texture/description.html
grass/trunk/raster/r.thin/description.html
grass/trunk/raster/r.timestamp/description.html
grass/trunk/raster/r.to.rast3/description.html
grass/trunk/raster/r.to.rast3elev/description.html
grass/trunk/raster/r.to.vect/description.html
grass/trunk/raster/r.topidx/description.html
grass/trunk/raster/r.topmodel/description.html
grass/trunk/raster/r.transect/description.html
grass/trunk/raster/r.volume/description.html
grass/trunk/raster/r.walk/description.html
grass/trunk/raster/r.water.outlet/description.html
grass/trunk/raster/r.what.color/description.html
grass/trunk/raster/r.what/description.html
Log:
Raster manpage HTML tags uniformily lowercased
Modified: grass/trunk/raster/r.average/description.html
===================================================================
--- grass/trunk/raster/r.average/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.average/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,66 +1,66 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.average</EM> calculates the average value of data
-contained in a <EM>cover</EM> raster map layer for areas
+<em>r.average</em> calculates the average value of data
+contained in a <em>cover</em> raster map layer for areas
assigned the same category value in the user-specified
-<EM>base</EM> raster map layer. These averaged values are
+<em>base</em> raster map layer. These averaged values are
stored in the category labels file associated with a new
-<EM>output</EM> map layer.
+<em>output</em> map layer.
The values to be averaged are taken from a user-specified
-<EM>cover</EM> map. The <EM>category values</EM> for the
-<EM>cover</EM> map will be averaged, unless the <B>-c</B>
-flag is set. If the <B>-c</B> flag is set, the values that
-appear in the <EM>category labels</EM> file for the
-<EM>cover</EM> map will be averaged instead (see example
+<em>cover</em> map. The <em>category values</em> for the
+<em>cover</em> map will be averaged, unless the <b>-c</b>
+flag is set. If the <b>-c</b> flag is set, the values that
+appear in the <em>category labels</em> file for the
+<em>cover</em> map will be averaged instead (see example
below).
-<P>
+<p>
-The <EM>output</EM> map is actually a <EM>reclass</EM> of the <EM>base</EM>
-map (see <EM> <A HREF="r.reclass.html">r.reclass</A></EM>), and will have
-exactly the same <EM>category values</EM> as the <EM>base</EM> map. The
-averaged values computed by <EM>r.average</EM> are stored in the
-<EM>output</EM> map's <EM>category labels</EM> file.
+The <em>output</em> map is actually a <em>reclass</em> of the <em>base</em>
+map (see <em> <a href="r.reclass.html">r.reclass</a></em>), and will have
+exactly the same <em>category values</em> as the <em>base</em> map. The
+averaged values computed by <em>r.average</em> are stored in the
+<em>output</em> map's <em>category labels</em> file.
-The <B>base=</B> map is an existing raster map layer in the user's current
+The <b>base=</b> map is an existing raster map layer in the user's current
mapset search path. For each group of cells assigned the same category
-value in the <EM>base</EM> map, the values assigned these cells in the
-<EM>cover</EM> map will be averaged.
+value in the <em>base</em> map, the values assigned these cells in the
+<em>cover</em> map will be averaged.
-The <EM>cover</EM> map is an existing raster map layer containing the values
+The <em>cover</em> map is an existing raster map layer containing the values
(in the form of cell category values or cell category labels) to be averaged
-within each category of the <EM>base</EM> map.
+within each category of the <em>base</em> map.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-The <B>-c</B> option requires that the category label for
-each category in the <EM>cover</EM> map be a valid number,
+The <b>-c</b> option requires that the category label for
+each category in the <em>cover</em> map be a valid number,
integer, or decimal. To be exact, if the first item in the
label is numeric, then that value is used. Otherwise, zero
is used. The following table covers all possible cases:
-<P>
-<PRE>
+<p>
+<pre>
category value
label used by -c
______________________
.12 .12
.80 KF .8
no data 0
-</PRE>
-<P>
+</pre>
+<p>
(This flag is very similar to the @ operator in
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
and the user is encouraged to read the manual entry for
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>
to see how it works there.)
-<P>
+<p>
-The user should use the results of <EM>r.average</EM> with
+The user should use the results of <em>r.average</em> with
care. Since this utility assigns a value to each cell
which is based on global information (i.e., information at
spatial locations other than just the location of the cell
@@ -68,19 +68,19 @@
geographic region and mask settings are the same as they
were at the time that the result map was created.
-<P>
+<p>
Results are affected by the current region settings and mask.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
Assume that
-<EM>farms</EM>
+<em>farms</em>
is a map with 7 farms (i.e., 7 categories), and that
-<EM>soils.Kfactor</EM>
+<em>soils.Kfactor</em>
is a map of soil K factor values with the following category file:
-<PRE>
+<pre>
cat cat
value label
0 no soil data
@@ -93,22 +93,22 @@
7 .32
8 .37
9 .43
-</PRE>
+</pre>
Then
-<P>
-<DL>
-<DD>
-<B>r.average -c base=</B><EM>farms</EM>
-<B>cover=</B><EM>soils.Kfactor</EM> <B>output=</B><EM>K.by.farm</EM>
-</DL>
+<p>
+<dl>
+<dd>
+<b>r.average -c base=</b><em>farms</em>
+<b>cover=</b><em>soils.Kfactor</em> <b>output=</b><em>K.by.farm</em>
+</dl>
will compute the average soil K factor for each farm, and store the result
-in the output map <EM>K.by.farm</EM>, which will be a reclass of
-<EM>farms</EM> with category labels as follows (example only):
+in the output map <em>K.by.farm</em>, which will be a reclass of
+<em>farms</em> with category labels as follows (example only):
-<PRE>
+<pre>
cat cat
value label
1 .1023
@@ -118,25 +118,25 @@
5 .003
6 .28
7 .2345
-</PRE>
+</pre>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="r.category.html">r.category</A></EM>,
-<EM><A HREF="r.clump.html">r.clump</A></EM>,
-<EM><A HREF="r.describe.html">r.describe</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.mfilter.html">r.mfilter</A></EM>,
-<EM><A HREF="r.mode.html">r.mode</A></EM>,
-<EM><A HREF="r.neighbors.html">r.neighbors</A></EM>,
-<EM><A HREF="r.reclass.html">r.reclass</A></EM>,
-<EM><A HREF="r.statistics.html">r.statistics</A></EM>,
-<EM><A HREF="r.stats.html">r.stats</A></EM>
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.category.html">r.category</a></em>,
+<em><a href="r.clump.html">r.clump</a></em>,
+<em><a href="r.describe.html">r.describe</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.mfilter.html">r.mfilter</a></em>,
+<em><a href="r.mode.html">r.mode</a></em>,
+<em><a href="r.neighbors.html">r.neighbors</a></em>,
+<em><a href="r.reclass.html">r.reclass</a></em>,
+<em><a href="r.statistics.html">r.statistics</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro,
U.S. Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.basins.fill/description.html
===================================================================
--- grass/trunk/raster/r.basins.fill/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.basins.fill/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.basins.fill</EM>
+<em>r.basins.fill</em>
generates a raster map layer depicting subbasins, based
on input raster map layers for the coded stream network
(where each channel segment has been "coded" with a unique category value)
@@ -10,11 +10,11 @@
the ridge which defines the perimeter of the watershed.
The coded stream network can be generated
as part of the
-<EM><A HREF="r.watershed.html">r.watershed</A></EM> program,
+<em><a href="r.watershed.html">r.watershed</a></em> program,
but the map layer of ridges will need to be created by hand
-(for example, through digitizing done in <EM><A HREF="v.digit.html">v.digit</A></EM>).
+(for example, through digitizing done in <em><a href="v.digit.html">v.digit</a></em>).
-<P>
+<p>
The resulting output raster map layer will
code the subbasins with category values matching
@@ -24,32 +24,32 @@
If the resulting map layer from this program appears to
have holes within a subbasin, the program should be
rerun with a higher number of passes.
-<BR><BR>
+<br><br>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
The current geographic region setting is ignored.
Instead, the geographic region for the entire input stream's
map layer is used.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-See Appendix A of the <B>GRASS</B> <a
+See Appendix A of the <b>GRASS</b> <a
href="http://grass.itc.it/gdp/raster/r.watershed.ps">Tutorial:
r.watershed</a> for further details on the combined use of
-<EM>r.basins.fill</EM> and <EM><A HREF="r.watershed.html">r.watershed</A></EM>.
+<em>r.basins.fill</em> and <em><a href="r.watershed.html">r.watershed</a></em>.
-<P>
-<EM><A HREF="r.watershed.html">r.watershed</A></EM>,
-<EM><A HREF="v.digit.html">v.digit</A></EM>
+<p>
+<em><a href="r.watershed.html">r.watershed</a></em>,
+<em><a href="v.digit.html">v.digit</a></em>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
Dale White,
Dept. of Geography,
Pennsylvania State University
-<BR>
+<br>
Larry Band, Dept. of Geography, University of Toronto, Canada
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.bilinear/description.html
===================================================================
--- grass/trunk/raster/r.bilinear/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.bilinear/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,13 +1,13 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<H3>
+<h3>
This module is deprecated and scheduled for demolition.
-<BR>
+<br>
Please use "<em><a href="r.resamp.interp.html">r.resamp.interp</a></em>"
-instead.</H3>
+instead.</h3>
-<EM>r.bilinear</EM> fills a grid cell (raster) matrix with interpolated values
+<em>r.bilinear</em> fills a grid cell (raster) matrix with interpolated values
generated from a set of input layer data points. It uses the bilinear
interpolation method, a simple algorithm usually applied only to
completely defined raster areas (input data void of null data values).
@@ -18,7 +18,7 @@
discontinuously across lines intersecting the cell centers of the input raster.
-<P>
+<p>
If there is a current working mask, it applies to the output
raster map. Only those cells falling within the mask will be
@@ -30,9 +30,9 @@
set to null.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-The <B>north</B> and <B>south</B> parameters have been included to allow
+The <b>north</b> and <b>south</b> parameters have been included to allow
for specific input values to be assigned to the north and/or south poles for
longitude-latitude grids. These data, if included, are used to interpolate
values for cells that are north or south of a line intersecting the cell
@@ -46,7 +46,7 @@
only if the input raster has an east edge identical to its west edge.
-<P>
+<p>
For longitude-latitude databases, the interpolation algorithm is based on
degree fractions, not on the absolute distances between cell centers. Any
@@ -54,27 +54,27 @@
interpolation method.
-<P>
+<p>
-</B><EM>r.bilinear</EM> may be used in some instances as an alternative to the
-nearest neighbor approach inherent to <EM>r.resample</EM>. Note, however, that
+</b><em>r.bilinear</em> may be used in some instances as an alternative to the
+nearest neighbor approach inherent to <em>r.resample</em>. Note, however, that
the extent of non-null data area of the output raster must be less than that
of the input raster. The only exception to this occurs in the case where the
-<B>north</B> and <B>south</B> parameters are utilized for longitude-latitude
+<b>north</b> and <b>south</b> parameters are utilized for longitude-latitude
rasters.
-<P>
+<p>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><a href="r.surf.idw.html">r.surf.idw</a></EM>,
-<EM><a href="r.surf.idw2.html">r.surf.idw2</a></EM>,
-<EM><a href="g.region.html">g.region</a></EM>,
-<EM><a href="r.resample.html">r.resample</a></EM>,
-<EM><a href="r.resamp.interp.html">r.resamp.interp</a></EM>,
-<EM><a href="r.resamp.stats.html">r.resamp.stats</a></EM>
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.resample.html">r.resample</a></em>,
+<em><a href="r.resamp.interp.html">r.resamp.interp</a></em>,
+<em><a href="r.resamp.stats.html">r.resamp.stats</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Greg Koerper <br>
ManTech Environmental Technology, Inc.<br>
Modified: grass/trunk/raster/r.bitpattern/description.html
===================================================================
--- grass/trunk/raster/r.bitpattern/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.bitpattern/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.bitpattern</EM> performs bit pattern comparisons.
+<em>r.bitpattern</em> performs bit pattern comparisons.
The module can be used to pixelwise verify a satellite image
for low quality pixels if a Quality Control Bit Index map is
provided (e.g. as for MODIS sensor maps).
@@ -21,7 +21,7 @@
can be used to exclude low quality pixel in the input satellite
image using <em>r.mapcalc</em> (OR and NOT operators).
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
<ol>
<li>define position:
@@ -39,13 +39,13 @@
</pre>
</ol>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="r.mapcalc.html">r.mapcalc</A>
-</EM>
+<em>
+<a href="r.mapcalc.html">r.mapcalc</a>
+</em>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
Radim Blazek, Markus Neteler
Modified: grass/trunk/raster/r.buffer/description.html
===================================================================
--- grass/trunk/raster/r.buffer/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.buffer/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.buffer</EM> creates a new raster map layer showing
+<em>r.buffer</em> creates a new raster map layer showing
buffer (a.k.a. "distance" or "proximity") zones around all
cells that contain non-NULL category values in an existing
raster map layer. The distances of buffer zones from cells
@@ -27,20 +27,20 @@
Category 3: Buffer Zone 2 around roads
Category 4: Buffer Zone 3 around roads
</pre></div>
-<BR>
+<br>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
The user has the option of identifying up to 250 continuous zones.
The zones are identified by specifying the upper limit of each desired zone
-(<EM>r.buffer</EM> assumes that <tt>0</tt> is the starting point).
+(<em>r.buffer</em> assumes that <tt>0</tt> is the starting point).
("Continuous" is used in the sense that each category
zone's lower value is the previous zone's upper value. The
first buffer zone always has distance <tt>0</tt> as its lower
-bound.) Buffer distances can be specified using one of five units with the <EM>
-units</EM> parameter: <EM>meters, kilometers, feet, miles</EM>, and <EM>nautmiles</EM>
+bound.) Buffer distances can be specified using one of five units with the <em>
+units</em> parameter: <em>meters, kilometers, feet, miles</em>, and <em>nautmiles</em>
(nautical miles).
-<P>
+<p>
<!-- ??? is this the real method used or some ancient option ??? -->
Distances from cells containing the user-specified category values
@@ -51,40 +51,40 @@
containing the category values of interest, but works
slowly when there are numerous cells containing the
category values of interest spread throughout the area.
-<P>
+<p>
-<EM>r.buffer</EM> measures distances from center of cell to
+<em>r.buffer</em> measures distances from center of cell to
center of cell using Euclidean distance measure for
planimetric locations (like UTM) and using ellipsoidal
geodesic distance measure for latitude/longitude locations.
-<P>
+<p>
-<EM>r.buffer</EM> calculates distance zones from all cells having non-NULL
-category values in the <EM>input</EM> map. If the user wishes to calculate
-distances from only selected <EM>input</EM> map layer
+<em>r.buffer</em> calculates distance zones from all cells having non-NULL
+category values in the <em>input</em> map. If the user wishes to calculate
+distances from only selected <em>input</em> map layer
category values, the user should run (for example)
-<EM><A HREF="r.reclass.html">r.reclass</A></EM> prior to
-<EM>r.buffer</EM>, to reclass all categories from which distance zones
+<em><a href="r.reclass.html">r.reclass</a></em> prior to
+<em>r.buffer</em>, to reclass all categories from which distance zones
are not desired to be calculated into category NULL.
-<P>
+<p>
-The <B>-z</B> flag can be used to ignore raster values of zero instead of NULL
+The <b>-z</b> flag can be used to ignore raster values of zero instead of NULL
values in the input raster map.
-<P>
+<p>
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
In the following example, the buffer zones would be (in the default units
of meters): 0-100, 101-200, 201-300, 301-400 and 401-500.
-<BR>
+<br>
<div class="code"><pre>
-<B>r.buffer input=</B>roads <B>output=</B>roads.buf <B>distances=</B>100,200,300,400,500
+<b>r.buffer input=</b>roads <b>output=</b>roads.buf <b>distances=</b>100,200,300,400,500
</pre></div>
Result:
<div class="code"><pre>
-<B>r.category input=</B>roads.buf
+<b>r.category input=</b>roads.buf
1 distances calculated from these locations
2 0-100 meters
@@ -94,22 +94,22 @@
6 400-500 meters
</pre></div>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="g.region.html">g.region</A><br>
-<A HREF="r.cost.html">r.cost</A><br>
-<A HREF="r.mapcalc.html">r.mapcalc</A><br>
-<A HREF="r.reclass.html">r.reclass</A><br>
-<A HREF="v.buffer.html">v.buffer</A>
-</EM>
+<em>
+<a href="g.region.html">g.region</a><br>
+<a href="r.cost.html">r.cost</a><br>
+<a href="r.mapcalc.html">r.mapcalc</a><br>
+<a href="r.reclass.html">r.reclass</a><br>
+<a href="v.buffer.html">v.buffer</a>
+</em>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
Michael Shapiro, U.S. Army Construction Engineering
Research Laboratory
-<BR>
+<br>
James Westervelt, U.S. Army Construction Engineering
Research Laboratory
Modified: grass/trunk/raster/r.carve/description.html
===================================================================
--- grass/trunk/raster/r.carve/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.carve/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<em>r.carve</em> accepts vector stream data as input, transforms them to
raster, and subtracts a defaultdepth+additionaldepth from a DEM. If
@@ -10,38 +10,38 @@
can then be combined with contours to interpolate a new DEM with
better representation of valleys.
-<H2>NOTE</H2>
+<h2>NOTE</h2>
<em>r.carve</em> does not create a depressionless DEM because many
depressions are in flat areas and not in the streams.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
<div class="code"><pre>
g.region rast=elevation.10m -p
r.carve rast=elevation.10m vect=streams out=carve_dem width=20 depth=5
</pre></div>
-<H2>BUGS</H2>
+<h2>BUGS</h2>
<!-- Is this still the case as of Jan 11, 2008? - EP -->
The module does not operate yet in latitude-longitude locations. It
has not been thoroughly tested, so not all options may work properly -
but this was the intention.
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
<a href="http://skagit.meas.ncsu.edu/~helena/gmslab/reports/cerl99/rep99.html">Terrain
modeling and Soil Erosion Simulations for Fort Hood and Fort Polk test
areas</a>, by Helena Mitasova, Lubos Mitas, William M. Brown, Douglas
M. Johnston, GMSL (Report for CERL 1999)
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.flow.html">r.flow</A></EM>,
-<EM><A HREF="r.fill.dir.html">r.fill.dir</A></EM>,
-<EM><A HREF="r.watershed.html">r.watershed</A></EM>
+<h2>SEE ALSO</h2>
+<em><a href="r.flow.html">r.flow</a></em>,
+<em><a href="r.fill.dir.html">r.fill.dir</a></em>,
+<em><a href="r.watershed.html">r.watershed</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Bill Brown (GMSL)<br>
GRASS 6 update: Brad Douglas
Modified: grass/trunk/raster/r.cats/description.html
===================================================================
--- grass/trunk/raster/r.cats/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.cats/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,43 +1,43 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.category</EM> prints the category values and labels for the raster map
-layer specified by <B>map=</B><EM>name</EM> to standard output.
+<em>r.category</em> prints the category values and labels for the raster map
+layer specified by <b>map=</b><em>name</em> to standard output.
-<P>
+<p>
The user can specify all needed parameters on the command line, and run the
program non-interactively. If the user does not specify any categories
-(e.g., using the optional <B>cats=</B><EM>range</EM>[,<EM>range</EM>,...]
+(e.g., using the optional <b>cats=</b><em>range</em>[,<em>range</em>,...]
argument), then all the category values and labels for the named raster map
-layer that occur in the map are printed. The entire <EM>map</EM> is read
-using <EM><A HREF="r.describe.html">r.describe</A></EM>, to determine which
-categories occur in the <EM>map</EM>. If a listing of categories is
+layer that occur in the map are printed. The entire <em>map</em> is read
+using <em><a href="r.describe.html">r.describe</a></em>, to determine which
+categories occur in the <em>map</em>. If a listing of categories is
specified, then the labels for those categories only are printed. The
-<EM>cats</EM> may be specified as single category values, or as ranges of
+<em>cats</em> may be specified as single category values, or as ranges of
values. The user may also (optionally) specify that a field separator other
than a space or tab be used to separate the category value from its
corresponding category label in the output, by using the
-<B>fs=</B><EM>character</EM>|<EM>space</EM>|<EM>tab</EM> option (see example
+<b>fs=</b><em>character</em>|<em>space</em>|<em>tab</em> option (see example
below). If no field separator is specified by the user, a tab is used to
separate these fields in the output, by default.
-<P>
+<p>
The output is sent to standard output in the form of one category per line,
with the category value first on the line, then an ASCII TAB character (or
-whatever single character or space is specified using the <B>fs</B>
+whatever single character or space is specified using the <b>fs</b>
parameter), then the label for the category.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
Any ASCII TAB characters which may be in the label are replaced by spaces.
-<P>
-The output from <EM>r.category</EM> can be redirected into a file, or piped into
+<p>
+The output from <em>r.category</em> can be redirected into a file, or piped into
another program.
-<H3>Input from a file</H3>
+<h3>Input from a file</h3>
The <b>rules</b> option allows the user to assign category labels from values
found in a file. The label can refer to a single category, range of
@@ -51,7 +51,7 @@
If the filename is given as "-", the category labels are read from <tt>stdin</tt>
-<H3>Default and dynamic category labels</H3>
+<h3>Default and dynamic category labels</h3>
Default and dynamic category labels can be created for categories that
are not explicitly labeled.
@@ -70,33 +70,33 @@
or
15:30 label description
</pre>
-<P>
+<p>
In the format line
<ul>
<li>$1 refers to the value num*5.0+1000 (ie, using the first 2 coefficients)
<li>$2 refers to the value num*5.0+1005 (ie, using the last 2 coefficients)
</ul>
$1.2 will print $1 with 2 decimal places.
-<P>
+<p>
Also, the form $?xxx$yyy$ translates into yyy if the category is 1, xxx
otherwise. The $yyy$ is optional. Thus
-<P>
+<p>
$1 meter$?s
<p>
-will become: 1 meter (for category 1)<BR>
+will become: 1 meter (for category 1)<br>
2 meters (for category 2), etc.
-<P>
+<p>
format='Elevation: $1.2 to $2.2 feet' ## Format Statement
coefficients="5.0,1000,5.0,1005" ## Coefficients
-<P>
+<p>
The format and coefficients above would be used to generate the
following statement in creation of the format appropriate category
string for category "num":
-<P>
+<p>
sprintf(buff,"Elevation: %.2f to %.2f feet", num*5.0+1000, num*5.0*1005)
-<P>
+<p>
Note: while both the format and coefficent lines must be present
a blank line for the format string will effectively suppress
automatic label generation.
@@ -107,71 +107,71 @@
know that i-th rule maps fp range to i, thus we know for sure
that cats.labels[i] corresponds to i-th quant rule
-->
-<P>
+<p>
To use a "<tt>$</tt>" in the label without triggering the plural test,
put "<tt>$$</tt>" in the format string.
-<P>
+<p>
Use 'single quotes' when using a "<tt>$</tt>" on the command line to
avoid unwanted shell substitution.
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
-<P>
-<DL>
-<DT><div class="code"><pre>
+<p>
+<dl>
+<dt><div class="code"><pre>
r.category map=soils
</pre></div>
-<DD>
+<dd>
prints the values and labels associated with all of the categories in the
-<EM>soils</EM> raster map layer;
+<em>soils</em> raster map layer;
-<DT><div class="code"><pre>
+<dt><div class="code"><pre>
r.category map=soils cats=10,12,15-20
</pre></div>
-<DD>
-prints only the category values and labels for <EM>soils</EM> map layer
+<dd>
+prints only the category values and labels for <em>soils</em> map layer
categories <tt>10, 12</tt>, and <tt>15</tt> through <tt>20</tt>; and
-<DT><div class="code"><pre>
+<dt><div class="code"><pre>
r.category map=soils cats=10,20 fs=':'
</pre></div>
-<DD>
-prints the values and labels for <EM>soils</EM> map layer categories
+<dd>
+prints the values and labels for <em>soils</em> map layer categories
<tt>10</tt> and <tt>20</tt>, but uses "<tt>:</tt>" (instead of a tab)
as the character separating the category values from the category
values in the output.
-</DL>
+</dl>
-<DL>
-<DT>Example output:
-<DD>
-<P>
+<dl>
+<dt>Example output:
+<dd>
+<p>
<div class="code"><pre>
10:Dumps, mine, Cc
20:Kyle clay, KaA
</pre></div>
-</DL>
+</dl>
-<H2>TODO</H2>
+<h2>TODO</h2>
-Respect the <B>fs=</B> field separator setting for input rules.
+Respect the <b>fs=</b> field separator setting for input rules.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
UNIX Manual entries for <i>awk</i> and <i>sort</i>
-<P>
-<EM><A HREF="r.coin.html">r.coin</A></EM>,
-<EM><A HREF="r.describe.html">r.describe</A></EM>,
-<EM><A HREF="d.what.rast.html">d.what.rast</A></EM>,
-<EM><A HREF="r.support.html">r.support</A></EM>
+<p>
+<em><a href="r.coin.html">r.coin</a></em>,
+<em><a href="r.describe.html">r.describe</a></em>,
+<em><a href="d.what.rast.html">d.what.rast</a></em>,
+<em><a href="r.support.html">r.support</a></em>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
-Michael Shapiro, U.S. Army Construction Engineering Research Laboratory<BR>
+Michael Shapiro, U.S. Army Construction Engineering Research Laboratory<br>
Hamish Bowman, University of Otago, New Zealand (label creation options)
<p>
Modified: grass/trunk/raster/r.circle/description.html
===================================================================
--- grass/trunk/raster/r.circle/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.circle/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,54 +1,54 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-This module creates an output raster map centered on the <EM>x,y</EM> values specified
-with the <EM>coordinate</EM> parameter, out to the edge of the current region.
-The output cell values increase linearly from the specified center. The <EM>min</EM>
-and <EM>max</EM> parameters control the inner and outer output raster map radii, respectively.
+This module creates an output raster map centered on the <em>x,y</em> values specified
+with the <em>coordinate</em> parameter, out to the edge of the current region.
+The output cell values increase linearly from the specified center. The <em>min</em>
+and <em>max</em> parameters control the inner and outer output raster map radii, respectively.
<p>
-The <EM>mult</EM> parameter can be used to multiply the output raster cells by a common factor.
+The <em>mult</em> parameter can be used to multiply the output raster cells by a common factor.
Note that this parameter does not affect the output raster position or size; only the z-values
are changed with this parameter.
-<P>
+<p>
Binary-output raster maps (solid circles of one value) can be created
-with the <B>-b</B> flag. Raster maps so created can be used to create
-binary filters for use in <EM>i.ifft</EM> (inverse Fourier transformations;
-apply filter with <EM>r.mask</EM>).
+with the <b>-b</b> flag. Raster maps so created can be used to create
+binary filters for use in <em>i.ifft</em> (inverse Fourier transformations;
+apply filter with <em>r.mask</em>).
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
Generate a raster circle at current map center with a radius of 300m and outwardly
increasing raster values:
-<PRE>
+<pre>
EASTCENTER=`g.region -c | awk ' /center easting:/ { print $3 }'`
NORTHCENTER=`g.region -c | awk ' /center northing:/ { print $3 }'`
r.circle output=circle coordinate=${EASTCENTER},${NORTHCENTER} max=300
-</PRE>
+</pre>
Generate a binary raster ring around current map center with an inner radius
of 500m and an outer radius of 1000m:
-<PRE>
+<pre>
EASTCENTER=`g.region -c | awk ' /center easting:/ { print $3 }'`
NORTHCENTER=`g.region -c | awk ' /center northing:/ { print $3 }'`
r.circle -b output=circle coordinate=${EASTCENTER},${NORTHCENTER} min=500 max=1000
-</PRE>
+</pre>
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="g.region.html">g.region</A>,
-<A HREF="g.remove.html">g.remove</A>,
-<A HREF="g.rename.html">g.rename</A>,
-<A HREF="i.fft.html">i.fft</A>,
-<A HREF="i.ifft.html">i.ifft</A>,
-<A HREF="r.mask">r.mask</A>
-</EM>
+<h2>SEE ALSO</h2>
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="g.remove.html">g.remove</a>,
+<a href="g.rename.html">g.rename</a>,
+<a href="i.fft.html">i.fft</a>,
+<a href="i.ifft.html">i.ifft</a>,
+<a href="r.mask">r.mask</a>
+</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Bill Brown, U.S. Army Construction Engineering Research Laboratory<br>
Additional flag/min/max parameter by Markus Neteler, University of Hannover
Modified: grass/trunk/raster/r.coin/description.html
===================================================================
--- grass/trunk/raster/r.coin/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.coin/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,13 +1,13 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.coin</EM> tabulates the mutual occurrence of two
+<em>r.coin</em> tabulates the mutual occurrence of two
raster map layers' categories with respect to one another.
This analysis program respects the current geographic
region and mask settings.
-<P>
+<p>
-<EM>r.coin</EM>
+<em>r.coin</em>
tabulates the coincidence of category values among the two
map layers and prepares the basic table from which the
report is to be created. This tabulation is followed by an
@@ -15,24 +15,24 @@
the table is extremely long, the user may decide that
viewing it is not so important after all, and may cancel
the request at this point. Assuming the user continues,
-<EM>r.coin</EM> then allows the user to choose one of eight
+<em>r.coin</em> then allows the user to choose one of eight
units of measure in which the report results can be given.
These units are:
-<P>
+<p>
-<DL>
-<DT><EM>c</EM> <DD>cells
-<DT><EM>p</EM> <DD>percent cover of region
-<DT><EM>x</EM> <DD>percent of <map name> category (column)
-<DT><EM>y</EM> <DD>percent of <map name> category (row)
-<DT><EM>a</EM> <DD>acres
-<DT><EM>h</EM> <DD>hectares
-<DT><EM>k</EM> <DD>square kilometers
-<DT><EM>m</EM> <DD>square miles
-</DL>
+<dl>
+<dt><em>c</em> <dd>cells
+<dt><em>p</em> <dd>percent cover of region
+<dt><em>x</em> <dd>percent of <map name> category (column)
+<dt><em>y</em> <dd>percent of <map name> category (row)
+<dt><em>a</em> <dd>acres
+<dt><em>h</em> <dd>hectares
+<dt><em>k</em> <dd>square kilometers
+<dt><em>m</em> <dd>square miles
+</dl>
-<P>
+<p>
Note that three of these options give results as percentage
values: "p" is based on the grand total number of cells;
@@ -48,40 +48,40 @@
is given the option to rerun the coincidence tabulation
using a different unit of measurement.
-<P>
+<p>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-It is <B>not</B> a good idea to run <EM>r.coin</EM> on a
+It is <b>not</b> a good idea to run <em>r.coin</em> on a
map layer which has a monstrous number of categories (e.g.,
-unreclassed elevation). Because <EM>r.coin</EM> reports
+unreclassed elevation). Because <em>r.coin</em> reports
information for each and every category, it is better to
-reclassify those categories (using <EM>r.reclass</EM>)
+reclassify those categories (using <em>r.reclass</em>)
into a more manageable number prior to running
-<EM>r.coin</EM> on the reclassed raster map layer.
+<em>r.coin</em> on the reclassed raster map layer.
-<P>
+<p>
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
Below is a sample of tabular output produced by
-<EM>r.coin</EM>. Here, map output is stated in units of
+<em>r.coin</em>. Here, map output is stated in units of
square miles. The report tabulates the coincidence of the
-Spearfish sample database's <EM>owner</EM> and
-<EM>road</EM> raster map layers' categories. The
-<EM>owner</EM> categories in this case refer to whether the
+Spearfish sample database's <em>owner</em> and
+<em>road</em> raster map layers' categories. The
+<em>owner</em> categories in this case refer to whether the
land is in private hands (category 1) or is owned by the
-U.S. Forest Service (category 2). The <EM>roads</EM> map
+U.S. Forest Service (category 2). The <em>roads</em> map
layer categories refer to various types of roads (with the
exception of category value "0", which indicates "no data";
i.e., map locations at which no roads exist).
-<EM>r.coin</EM> does not report category labels. The user
+<em>r.coin</em> does not report category labels. The user
should run
-<EM><A HREF="r.report.html">r.report</A></EM> or
-<EM><A HREF="r.category.html">r.category</A></EM>
+<em><a href="r.report.html">r.report</a></em> or
+<em><a href="r.category.html">r.category</a></em>
to obtain this information.
-<P>
+<p>
The body of the report is arranged in panels. The map layer
with the most categories is arranged along the vertical
@@ -96,29 +96,29 @@
the non-zero category rows. A cross total (Table Row Total)
of all columns for each row appears in a separate panel.
-<P>
+<p>
Note how the following information may be obtained from the sample report.
-<P>
+<p>
In the Spearfish data base, in area not owned by the Forest Service, there
are 50.63 square miles of land not used for roads. Roads make up 9.27 square
miles of land in this area.
-<P>
+<p>
Of the total 102.70 square miles in Spearfish, 42.80
square miles is owned by the Forest Service.
-<BR>
+<br>
In total, there are 14.58 square miles of roads.
-<P>
+<p>
There are more category 2 roads outside Forest Service land
(2.92 mi. sq.)
than there are inside Forest land boundaries (0.72 mi. sq.).
-<P>
+<p>
Following is a sample report.
-<PRE>
+<pre>
+------------------------------------------------------------+
| COINCIDENCE TABULATION REPORT |
|------------------------------------------------------------|
@@ -170,33 +170,33 @@
|--------------------------------|
|w/o 0 | 14.58 | 14.58 |
+--------------------------------+
-</PRE>
+</pre>
-<P>
+<p>
-<EM>r.coin</EM> calculates the coincidence of two raster
-map layers. Although <EM>r.coin</EM> allows the user to
+<em>r.coin</em> calculates the coincidence of two raster
+map layers. Although <em>r.coin</em> allows the user to
rerun the report using different units, it is not possible
to simply rerun the report with different map layers. In
order to choose new map layers, it is necessary to rerun
-<EM>r.coin.</EM>
+<em>r.coin.</em>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="g.region.html">g.region</A>,
-<!-- not ported to GRASS 6 <A HREF="m.ipf.html">m.ipf</A>, -->
-<A HREF="r.category.html">r.category</A>,
-<A HREF="r.describe.html">r.describe</A>,
-<A HREF="r.reclass.html">r.reclass</A>,
-<A HREF="r.report.html">r.report</A>,
-<A HREF="r.stats.html">r.stats</A>
-</EM>
+<em>
+<a href="g.region.html">g.region</a>,
+<!-- not ported to GRASS 6 <a href="m.ipf.html">m.ipf</a>, -->
+<a href="r.category.html">r.category</a>,
+<a href="r.describe.html">r.describe</a>,
+<a href="r.reclass.html">r.reclass</a>,
+<a href="r.report.html">r.report</a>,
+<a href="r.stats.html">r.stats</a>
+</em>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
Michael O'Shea,
-<BR>
+<br>
Michael Shapiro, <br>
U.S. Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.colors/description.html
===================================================================
--- grass/trunk/raster/r.colors/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.colors/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -275,7 +275,7 @@
cat rules.file | r.colors map=threecats color=rules
</pre></div>
-<P><BR>
+<p><br>
To create a natural looking LUT for true map layer <i>elevation</i>, use the
following rules specification file. It will assign light green shades to the
lower elevations (first 20% of the LUT), and then darker greens (next 15%, and
Modified: grass/trunk/raster/r.compress/description.html
===================================================================
--- grass/trunk/raster/r.compress/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.compress/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,9 +1,9 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-The GRASS program <EM>r.compress</EM> can be used to compress and decompress
+The GRASS program <em>r.compress</em> can be used to compress and decompress
raster map layers.
-<P>
+<p>
During compression, this program reformats raster maps
using a run-length-encoding (RLE) algorithm. Raster map
@@ -20,34 +20,34 @@
and regular (uncompressed) file formats. This allows the use
of whichever raster data format consumes less space.
-<P>
+<p>
As an example, the Spearfish data base raster map layer
-<EM>owner</EM> was originally a size of 26600 bytes. After
+<em>owner</em> was originally a size of 26600 bytes. After
it was compressed, the raster map became only 1249 bytes
(25351 bytes smaller).
-<P>
+<p>
Raster files may be decompressed to return them to their
-original format, using the <B>-u</B> flag of
-<EM>r.compress</EM>. If <EM>r.compress</EM> is asked to
+original format, using the <b>-u</b> flag of
+<em>r.compress</em>. If <em>r.compress</em> is asked to
compress a raster map which is already compressed (or to
decompress an already decompressed raster map), it simply informs
the user the map is already (de)compressed and exits.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-<EM>r.compress</EM> can be run either non-interactively or
+<em>r.compress</em> can be run either non-interactively or
interactively. In non-interactive use, the user must
specify the name(s) of the raster map layer(s) to be
compressed (or decompressed) on the command line, using the
-form <B>map=</B><EM>name</EM>[,<EM>name</EM>,...] (where
-each <EM>name</EM> is the name of a raster map layer to be
+form <b>map=</b><em>name</em>[,<em>name</em>,...] (where
+each <em>name</em> is the name of a raster map layer to be
compressed or decompressed). The default behavior is to
compress the named map(s).
-<H3>FORMATS</H3>
+<h3>FORMATS</h3>
Conceptually, a raster data file consists of rows of cells,
with each row containing the same number of cells. A cell
@@ -58,12 +58,12 @@
bytes, and category values in the range above 65535 require
3 (or more) bytes per cell.
-<P>
+<p>
-The <B>decompressed</B> raster map format matches the
+The <b>decompressed</b> raster map format matches the
conceptual format. For example, a raster map with 1 byte
cells that is 100 rows with 200 cells per row, consists of
-20,000 bytes. Running the UNIX command <EM>ls -l</EM> on
+20,000 bytes. Running the UNIX command <em>ls -l</em> on
this file will show a size of 20,000. If the cells were 2
byte cells, the file would require 40,000 bytes. The map
layer category values start with the upper left corner cell
@@ -72,12 +72,12 @@
first cell of the second row of category values (moving
from left to right). There are no end-of-row markers or
other syncing codes in the raster map. A cell header file
-(<EM>cellhd</EM>) is used to define how this string of bytes
+(<em>cellhd</em>) is used to define how this string of bytes
is broken up into rows of category values.
-<P>
+<p>
-The <B>compressed</B> format is not so simple, but is quite
+The <b>compressed</b> format is not so simple, but is quite
elegant in its design. It not only requires less disk space
to store the raster data, but often can result in faster
execution of graphic and analysis programs since there is
@@ -87,19 +87,19 @@
automatically used when new raster map layers are
created).
-<H4>PRE-3.0 FORMAT:</H4>
+<h4>PRE-3.0 FORMAT:</h4>
First 3 bytes (chars) - These are a special code that identifies
the raster data as compressed.
-<P>
+<p>
Address array (long) - array (size of the number of rows +
1) of addresses pointing to the internal start of each row.
Because each row may be a different size, this array is
necessary to provide a mapping of the data.
-<P>
+<p>
Row by row, beginning at the northern edge of the data, a
series of byte groups describes the data. The number of
@@ -108,16 +108,16 @@
255) of the number of cells that contain the category
values given by the remaining bytes of the group.
-<H4>POST-3.0 FORMAT:</H4>
+<h4>POST-3.0 FORMAT:</h4>
The 3 byte code is not used.
Instead, a field in the cell header is used to indicate compressed format.
-<P>
+<p>
The address array is the same.
-<P>
+<p>
The RLE format is the same as the pre-3.0 RLE, except that
each row of data is preceded by a single byte containing
@@ -125,7 +125,7 @@
run-length-encoding the row would not require less space
than non-run-length-encoding, then the row is not encoded.
-<P>
+<p>
These improvements give better compression than the pre-3.0
format in 99% of the raster data layers. The kinds of
@@ -135,11 +135,11 @@
only be larger by the size of the address array and the
single byte preceding each row.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.support.html">r.support</A></EM>
+<em><a href="r.support.html">r.support</a></em>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
James Westervelt,<br>
Michael Shapiro,<br>
Modified: grass/trunk/raster/r.contour/description.html
===================================================================
--- grass/trunk/raster/r.contour/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.contour/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -4,7 +4,7 @@
Contours can be produced using a comma-separated list of values in <b>levels</b>, or at some regular increment using the <b>step</b> parameter, using <b>minlevel</b> and <b>maxlevel</b> as minimum and maximum contour values, respectively. If no <b>minlevel</b> or <b>maxlevel</b> is specified, the minimum and maximum cell values in the <b>input</b> raster map will be used.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
<em>r.contour</em> will either step through incremental contours or produce
contours from a list of levels, not both. If both a list of levels and
a step are specified, the list will be produced and the step will be ignored.
Modified: grass/trunk/raster/r.cost/description.html
===================================================================
--- grass/trunk/raster/r.cost/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.cost/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,69 +1,69 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<P><EM>r.cost</EM> determines the cumulative cost of moving to each
-cell on a <EM>cost surface</EM> (the <B>input</B> raster map) from
+<p><em>r.cost</em> determines the cumulative cost of moving to each
+cell on a <em>cost surface</em> (the <b>input</b> raster map) from
other user-specified cell(s) whose locations are specified by their
geographic coordinate(s). Each cell in the original cost surface map
will contain a category value which represents the cost of traversing
-that cell. <EM>r.cost</EM> will produce an <B>output</B> raster map in
+that cell. <em>r.cost</em> will produce an <b>output</b> raster map in
which each cell contains the lowest total cost of traversing the
space between each cell and the user-specified points. (Diagonal
costs are multiplied by a factor that depends on the dimensions of
the cell.) This program uses the current geographic region settings.
-The <B>output</B> map will be of the same data format as the <B>input</B>
-map, integer or floating point.</P>
+The <b>output</b> map will be of the same data format as the <b>input</b>
+map, integer or floating point.</p>
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
-The <B>input</B> <EM>name</EM> is the name of a raster map whose category values
-represent the surface cost. The <B>output</B> <EM>name</EM> is the name of the
+The <b>input</b> <em>name</em> is the name of a raster map whose category values
+represent the surface cost. The <b>output</b> <em>name</em> is the name of the
resultant raster map of cumulative cost.
-<P>
-<EM>r.cost</EM> can be run with three different methods of identifying the
+<p>
+<em>r.cost</em> can be run with three different methods of identifying the
starting point(s). One or more points (geographic coordinate pairs) can be
-provided as specified <B>coordinate</B>s on the command line, from a vector
+provided as specified <b>coordinate</b>s on the command line, from a vector
points file, or from a raster map.
All non-NULL cells are considered to be starting points.
-Each <EM>x,y</EM> <B>coordinate</B> pair gives the geographic location of a
+Each <em>x,y</em> <b>coordinate</b> pair gives the geographic location of a
point from which the transportation cost should be figured. As many points as
desired can be entered by the user. These starting points can also be read
-from a vector points file through the <B>start_sites</B> option or from a
-raster map through the <B>start_rast</B> option.
-<P>
+from a vector points file through the <b>start_sites</b> option or from a
+raster map through the <b>start_rast</b> option.
+<p>
<em>r.cost</em> will stop cumulating costs when either <b>max_cost</b> is reached,
-or one of the stop points given with <B>stop_coordinates</B> is reached.
+or one of the stop points given with <b>stop_coordinates</b> is reached.
Alternatively, the stop points can be read from a vector points file with the
-<B>stop_sites</B> option. During execution, once the cumulative cost to all
+<b>stop_sites</b> option. During execution, once the cumulative cost to all
stopping points has been determined, processing stops.
Both sites read from a vector points file and those given on the command line
will be processed.
-<P>
+<p>
The null cells in the <b>input</b> map can be assigned a (positive floating
point) cost with the <b>null_cost</b> option.
<br>
-When input map null cells are given a cost with the <B>null_cost</B>
+When input map null cells are given a cost with the <b>null_cost</b>
option, the corresponding cells in the output map are no longer null
cells. By using the <b>-n</b> flag, the null cells of the input map are
-retained as null cells in the output map.</P>
+retained as null cells in the output map.</p>
-<P>
+<p>
As <em>r.cost</em> can run for a very long time, it can be useful to
use the <b>-v</b> verbose flag to track progress.
-<P>
+<p>
The Knight's move (<b>-k</b> flag) may be used to improve the accuracy of
the output. In the diagram below, the center location (<tt>O</tt>) represents a
grid cell from which cumulative distances are calculated. Those
neighbors marked with an <tt>X</tt> are always considered for cumulative cost
-updates. With the <B>-k</B> option, the neighbors marked with a <tt>K</tt> are
+updates. With the <b>-k</b> option, the neighbors marked with a <tt>K</tt> are
also considered.
-</P>
+</p>
<div class="code"><pre>
. . . . . . . . . . . . . . .
. . . K . . K . . .
@@ -77,10 +77,10 @@
. . . K . . K . . .
. . . . . . . . . . . . . . .
</pre></div>
-<BR>
+<br>
Knight's move example:
<center>
-<img src=rcost_knightsmove.png border=1><BR>
+<img src=rcost_knightsmove.png border=1><br>
<table border=0 width=590>
<tr><td><center>
<i>Flat cost surface without (left pane) and with the knight's move (right pane).
@@ -91,37 +91,37 @@
</center>
-<H2>NULL CELLS</H2>
+<h2>NULL CELLS</h2>
-<P>By default null cells in the input raster map are excluded from
+<p>By default null cells in the input raster map are excluded from
the algorithm, and thus retained in the output map.
-<P>
-If one wants <B>r.cost</B> to transparently cross any region of null cells,
-the <B>null_cost</B>=<tt>0.0</tt> option should be used. Then null cells just
+<p>
+If one wants <b>r.cost</b> to transparently cross any region of null cells,
+the <b>null_cost</b>=<tt>0.0</tt> option should be used. Then null cells just
propagate the adjacent costs. These cells can be retained as null cells in the
-output map by using the <B>-n</B> flag.
+output map by using the <b>-n</b> flag.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-<P>Sometimes, when the differences among integer cell category values in the
-<EM>r.cost</EM> cumulative cost surface output are small, this
-cumulative cost output cannot accurately be used as input to <EM><A HREF="r.drain.html">r.drain</A></EM>
-(<EM><A HREF="r.drain.html">r.drain</A></EM> will output bad
+<p>Sometimes, when the differences among integer cell category values in the
+<em>r.cost</em> cumulative cost surface output are small, this
+cumulative cost output cannot accurately be used as input to <em><a href="r.drain.html">r.drain</a></em>
+(<em><a href="r.drain.html">r.drain</a></em> will output bad
results). This problem can be circumvented by making the differences
between cell category values in the cumulative cost output bigger. It
-is recommended that, if the output from <EM>r.cost</EM> is to be used
-as input to <EM><A HREF="r.drain.html">r.drain</A></EM>, the user
-multiply the input cost surface map to <EM>r.cost</EM> by the value
-of the map's cell resolution, before running <EM>r.cost</EM>. This
-can be done using <EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>. The map
-resolution can be found using <EM><A HREF="g.region.html">g.region</A></EM>.
+is recommended that, if the output from <em>r.cost</em> is to be used
+as input to <em><a href="r.drain.html">r.drain</a></em>, the user
+multiply the input cost surface map to <em>r.cost</em> by the value
+of the map's cell resolution, before running <em>r.cost</em>. This
+can be done using <em><a href="r.mapcalc.html">r.mapcalc</a></em>. The map
+resolution can be found using <em><a href="g.region.html">g.region</a></em>.
This problem doesn't arise with floating point maps.
-<H4>Algorithm notes</H4>
+<h4>Algorithm notes</h4>
The fundamental approach to calculating minimum travel cost is as
-follows:<P> The user generates a raster map indicating the cost of
+follows:<p> The user generates a raster map indicating the cost of
traversing each cell in the north-south and east-west directions.
This map, along with a set of starting points are submitted to
<em>r.cost</em>. The starting points are put into a list cells from which
@@ -132,13 +132,13 @@
of selecting the lowest cumulative cost cell, computing costs to the
neighbors, putting the neighbors on the list and removing the
originating cell from the list continues until the list is empty.
-<P>
+<p>
The most time consuming aspect of this algorithm is the management of
the list of cells for which cumulative costs have been at least
initially computed. <em>r.cost</em> uses a binary tree with an linked list
at each node in the tree for efficiently holding cells with identical
cumulative costs.
-<P>
+<p>
<em>r.cost</em>, like most all GRASS raster programs, is also made to be run on
maps larger that can fit in available computer memory. As the
algorithm works through the dynamic list of cells it can move almost
@@ -147,14 +147,14 @@
and from disk) as needed. This provides a virtual memory approach
optimally designed for 2-D raster maps.
The amount of map to hold in memory at one time can be controlled with the
-<B>percent_memory</B> option. For large maps this value will have to be set
+<b>percent_memory</b> option. For large maps this value will have to be set
to a lower value.
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
-<P>Consider the following example:
-</P>
+<p>Consider the following example:
+</p>
<div class="code"><pre>
Input:
COST SURFACE
@@ -167,7 +167,7 @@
. . . . . . . . . . . . . . .
. 8 . 7 . 8 . 8 . 8 . 8 . 5 .
. . . . . . . . . . _____ . .
- . 8 . 8 . 1 . 1 . 5 | <B>3</B> | 9 .
+ . 8 . 8 . 1 . 1 . 5 | <b>3</b> | 9 .
. . . . . . . . . . |___| . .
. 8 . 1 . 1 . 2 . 5 . 3 . 9 .
. . . . . . . . . . . . . . .
@@ -175,41 +175,41 @@
Output (using -k): Output (not using -k):
CUMULATIVE COST SURFACE CUMULATIVE COST SURFACE
- . . . . . . . . . . . . . . . . . . . <B>* * * * *</B> . . . . . .
- . 21. 21. 20. 19. 17. 15. 14. . 22. 21<B>* 21* 20*</B> 17. 15. 14.
- . . . . . . . . . . . . . . . . . . . <B>* * * * *</B> . . . . . .
- . 20. 19. 22. 19. 15. 12. 11. . 20. 19. 22<B>* 20*</B> 15. 12. 11.
- . . . . . . . . . . . . . . . . . . . . . <B>* * * * *</B> . . . .
- . 22. 18. 17. 17. 12. 11. 9. . 22. 18. 17<B>* 18* 13*</B> 11. 9.
- . . . . . . . . . . . . . . . . . . . . . <B>* * * * *</B> . . . .
+ . . . . . . . . . . . . . . . . . . . <b>* * * * *</b> . . . . . .
+ . 21. 21. 20. 19. 17. 15. 14. . 22. 21<b>* 21* 20*</b> 17. 15. 14.
+ . . . . . . . . . . . . . . . . . . . <b>* * * * *</b> . . . . . .
+ . 20. 19. 22. 19. 15. 12. 11. . 20. 19. 22<b>* 20*</b> 15. 12. 11.
+ . . . . . . . . . . . . . . . . . . . . . <b>* * * * *</b> . . . .
+ . 22. 18. 17. 17. 12. 11. 9. . 22. 18. 17<b>* 18* 13*</b> 11. 9.
+ . . . . . . . . . . . . . . . . . . . . . <b>* * * * *</b> . . . .
. 21. 14. 13. 12. 8. 6. 6. . 21. 14. 13. 12. 8. 6. 6.
. . . . . . . . . . _____. . . . . . . . . . . . . . . . .
- . 16. 13. 8. 7. 4 | <B>0</B> | 6. . 16. 13. 8. 7 . 4. 0. 6.
+ . 16. 13. 8. 7. 4 | <b>0</b> | 6. . 16. 13. 8. 7 . 4. 0. 6.
. . . . . . . . . . |___|. . . . . . . . . . . . . . . . .
. 14. 9. 8. 9. 6. 3. 8. . 14. 9. 8. 9 . 6. 3. 8.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
</pre></div>
-<P>
+<p>
<!-- ??? are "starting" and "ending" swapped in the following text ??? -->
-The user-provided ending location in the above example is the boxed <B>3</B>
+The user-provided ending location in the above example is the boxed <b>3</b>
in the above input map. The costs in the output map represent the total
cost of moving from each box ("cell") to one or more (here,
only one) starting location(s). Cells surrounded by asterisks are
those that are different between operations using and not using the
-Knight's move (<B>-k</B>) option.
+Knight's move (<b>-k</b>) option.
-<H4>Output analysis</H4>
+<h4>Output analysis</h4>
The output map can be viewed, for example, as an elevation model in which
-the starting location(s) is/are the lowest point(s). Outputs from <EM>r.cost</EM>
-can be used as inputs to <EM><A HREF="r.drain.html">r.drain</A></EM>, in order
+the starting location(s) is/are the lowest point(s). Outputs from <em>r.cost</em>
+can be used as inputs to <em><a href="r.drain.html">r.drain</a></em>, in order
to trace the least-cost path given by this model between any given cell
-and the <EM>r.cost</EM> starting location(s). The two programs, when
+and the <em>r.cost</em> starting location(s). The two programs, when
used together, generate least-cost paths or corridors between any two
map locations (cells).
-<H4>Shortest distance surfaces</H4>
+<h4>Shortest distance surfaces</h4>
The <em>r.cost</em> module allows for computing the shortest distance
of each pixel from raster lines, such as determining the shortest distances
of households to the nearby road. For this cost surfaces with cost value 1 are
@@ -229,32 +229,32 @@
</pre></div>
-<H2>BUGS</H2>
+<h2>BUGS</h2>
The percentage done calculation reported in verbose mode is often not linear
and ends well before 100%. This does not affect output.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.drain.html">r.drain</A></EM>,
-<EM><A HREF="r.walk.html">r.walk</A></EM>,
-<EM><A HREF="r.in.ascii.html">r.in.ascii</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.out.ascii.html">r.out.ascii</A></EM>
+<em><a href="r.drain.html">r.drain</a></em>,
+<em><a href="r.walk.html">r.walk</a></em>,
+<em><a href="r.in.ascii.html">r.in.ascii</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.out.ascii.html">r.out.ascii</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
-Antony Awaida,<BR>
-Intelligent Engineering<BR>
-Systems Laboratory,<BR>
-M.I.T.<BR>
-<BR>
-James Westervelt,<BR>
+Antony Awaida,<br>
+Intelligent Engineering<br>
+Systems Laboratory,<br>
+M.I.T.<br>
+<br>
+James Westervelt,<br>
U.S.Army Construction Engineering Research Laboratory
-<P>Updated for Grass 5<BR>
+<p>Updated for Grass 5<br>
Pierre de Mouveaux (pmx at audiovu.com)
-</P>
+</p>
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.covar/description.html
===================================================================
--- grass/trunk/raster/r.covar/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.covar/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,17 +1,17 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.covar</EM> outputs a covariance/correlation matrix for user-specified
+<em>r.covar</em> outputs a covariance/correlation matrix for user-specified
raster map layer(s). The output can be printed, or saved by redirecting
output into a file.
-<P>
+<p>
The output is an N x N symmetric covariance (correlation) matrix,
where N is the number of raster map layers specified on the command line.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
This module can be used as the first step of a principle components
transformation.
@@ -19,77 +19,77 @@
eigen values and eigen vectors. An NxN covariance matrix would result in
N real eigen values and N eigen vectors (each composed of N real numbers).
-<P>
+<p>
-The module <EM><A HREF="m.eigensystem.html">m.eigensystem</A></EM> in
+The module <em><a href="m.eigensystem.html">m.eigensystem</a></em> in
src.contrib can be compiled and used to generate the eigen values and
vectors.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
For example,
-<DL>
-<DD>
-<B>r.covar</B> map=</B><EM>layer.1</EM>,<EM>layer.2</EM>,<EM>layer.3</EM>
-</DL>
+<dl>
+<dd>
+<b>r.covar</b> map=</b><em>layer.1</em>,<em>layer.2</em>,<em>layer.3</em>
+</dl>
would produce a 3x3 matrix (values are example only):
-<PRE>
+<pre>
1.000000 0.914922 0.889581
0.914922 1.000000 0.939452
0.889581 0.939452 1.000000
-</PRE>
+</pre>
In the above example, the eigen values and corresponding eigen vectors
for the covariance matrix are:
-<PRE>
+<pre>
component eigen value eigen vector
1 1159.745202 < 0.691002 0.720528 0.480511 >
2 5.970541 < 0.711939 -0.635820 -0.070394 >
3 146.503197 < 0.226584 0.347470 -0.846873 >
-</PRE>
+</pre>
The component corresponding to each vector can be produced using
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>
as follows:
-<DL>
-<DD>
-<B>r.mapcalc</B> 'pc.1 = 0.691002*layer.1 + 0.720528*layer.2 + 0.480511*layer.3'
-<BR>
-<B>r.mapcalc</B> 'pc.2 = 0.711939*layer.1 - 0.635820*layer.2 - 0.070394*layer.3'
-<BR>
-<B>r.mapcalc</B> 'pc.3 = 0.226584*layer.1 + 0.347470*layer.2 - 0.846873*layer.3'
-</DL>
+<dl>
+<dd>
+<b>r.mapcalc</b> 'pc.1 = 0.691002*layer.1 + 0.720528*layer.2 + 0.480511*layer.3'
+<br>
+<b>r.mapcalc</b> 'pc.2 = 0.711939*layer.1 - 0.635820*layer.2 - 0.070394*layer.3'
+<br>
+<b>r.mapcalc</b> 'pc.3 = 0.226584*layer.1 + 0.347470*layer.2 - 0.846873*layer.3'
+</dl>
Note that based on the relative sizes of the eigen values,
-<EM>pc.1</EM>
+<em>pc.1</em>
will contain about 88% of the variance in the data set,
-<EM>pc.2</EM>
+<em>pc.2</em>
will contain about 1% of the variance in the data set, and
-<EM>pc.3</EM>
+<em>pc.3</em>
will contain about 11% of the variance in the data set.
Also, note that the range of values produced in
-<EM>pc.1</EM>, <EM>pc.2</EM>, and <EM>pc.3</EM> will
+<em>pc.1</em>, <em>pc.2</em>, and <em>pc.3</em> will
not (in general) be the same as those for
-<EM>layer.1</EM>, <EM>layer.2</EM>, and <EM>layer.3</EM>.
+<em>layer.1</em>, <em>layer.2</em>, and <em>layer.3</em>.
It may be necessary to rescale
-<EM>pc.1</EM>, <EM>pc.2</EM> and <EM>pc.3</EM> to
+<em>pc.1</em>, <em>pc.2</em> and <em>pc.3</em> to
the desired range (e.g. 0-255).
-This can be done with <EM><A HREF="r.rescale.html">r.rescale</A></EM>.
+This can be done with <em><a href="r.rescale.html">r.rescale</a></em>.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="i.pca.html">i.pca</A></EM>,
-<EM><A HREF="m.eigensystem.html">m.eigensystem</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.rescale.html">r.rescale</A></EM>
+<em><a href="i.pca.html">i.pca</a></em>,
+<em><a href="m.eigensystem.html">m.eigensystem</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.rescale.html">r.rescale</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.cross/description.html
===================================================================
--- grass/trunk/raster/r.cross/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.cross/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,45 +1,45 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.cross</EM> creates an <EM>output</EM> raster map layer representing
+<em>r.cross</em> creates an <em>output</em> raster map layer representing
all unique combinations of category values in the raster input layers
-(input=</B><EM>name,name,name</EM>, ...). At least two, but not more than
-ten, <EM>input</EM> map layers must be specified. The user must also
-specify a name to be assigned to the <EM>output</EM> raster map layer
-created by <EM>r.cross</EM>.
+(input=</b><em>name,name,name</em>, ...). At least two, but not more than
+ten, <em>input</em> map layers must be specified. The user must also
+specify a name to be assigned to the <em>output</em> raster map layer
+created by <em>r.cross</em>.
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
The program will be run non-interactively if the user specifies
-the names of between 2-10 raster map layers be used as <EM>input</EM>,
-and the name of a raster map layer to hold program <EM>output</EM>.
+the names of between 2-10 raster map layers be used as <em>input</em>,
+and the name of a raster map layer to hold program <em>output</em>.
-<P>
+<p>
-With the <B>-z</B> flag zero data values are not crossed.
+With the <b>-z</b> flag zero data values are not crossed.
This means that if a zero category value occurs in any input data layer,
the combination is assigned to category zero in the resulting map layer,
even if other data layers contain non-zero data.
-In the example given above, use of the <B>-z</B> option
+In the example given above, use of the <b>-z</b> option
would cause 3 categories to be generated instead of 5.
-<P>
+<p>
-If the <B>-z</B> flag is not specified, then map layer combinations
+If the <b>-z</b> flag is not specified, then map layer combinations
in which not all category values are zero will be assigned
a unique category value in the resulting map layer.
-<P>
+<p>
-Category values in the new <EM>output</EM> map layer will be the
-cross-product of the category values from these existing <EM>input</EM> map
+Category values in the new <em>output</em> map layer will be the
+cross-product of the category values from these existing <em>input</em> map
layers.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
For example, suppose that, using two raster map layers,
the following combinations occur:
-<PRE>
+<pre>
map1 map2
___________
0 1
@@ -47,12 +47,12 @@
1 1
1 2
2 4
-</PRE>
+</pre>
-<EM>r.cross</EM> would produce a new raster map layer with 5 categories:
+<em>r.cross</em> would produce a new raster map layer with 5 categories:
-<PRE>
+<pre>
map1 map2 output
____________________
0 1 1
@@ -60,23 +60,23 @@
1 1 3
1 2 4
2 4 5
-</PRE>
+</pre>
Note: The actual category value assigned to a particular combination
-in the <EM>result</EM> map layer is
+in the <em>result</em> map layer is
dependent on the order in which the combinations occur in the input map
layer data and can be considered essentially random.
The example given here is illustrative only.
-<H2>SUPPORT FILES</H2>
+<h2>SUPPORT FILES</h2>
-The category file created for the <EM>output</EM> raster map
+The category file created for the <em>output</em> raster map
layer describes the
combinations of input map layer category values which generated
each category.
In the above example, the category labels would be:
-<PRE>
+<pre>
category category
value label
______________________________
@@ -85,23 +85,23 @@
3 layer1(1) layer2(1)
4 layer1(1) layer2(2)
5 layer1(2) layer2(4)
-</PRE>
+</pre>
-A random color table is also generated for the <EM>output</EM> map layer.
+A random color table is also generated for the <em>output</em> map layer.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-When run non-interactively, <EM>r.cross</EM> will not protect existing
-files in the user's mapset. If the user specifies an <EM>output</EM>
+When run non-interactively, <em>r.cross</em> will not protect existing
+files in the user's mapset. If the user specifies an <em>output</em>
file name that already exists in his mapset, the existing file will
-be overwritten by the new <EM>r.cross</EM> output.
+be overwritten by the new <em>r.cross</em> output.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.covar.html">r.covar</A></EM>,
-<EM><A HREF="r.stats.html">r.stats</A></EM>
+<em><a href="r.covar.html">r.covar</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.describe/description.html
===================================================================
--- grass/trunk/raster/r.describe/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.describe/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,29 +1,29 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM><B>r.describe</B></EM> prints a terse listing of category values found in
+<em><b>r.describe</b></em> prints a terse listing of category values found in
a user-specified raster map layer.
-<P>
+<p>
-<EM><B>r.describe</B></EM> ignores the current geographic region and mask, and
+<em><b>r.describe</b></em> ignores the current geographic region and mask, and
reads the full extent of the input raster map. This functionality is useful if the
-user intends to <EM>reclassify</EM> or <EM>rescale</EM> the data,
-since these functions (<EM><A HREF="r.reclass.html">r.reclass</A></EM> and
-<EM><A HREF="r.rescale.html">r.rescale</A></EM>)
-also ignore the current <EM>geographic region</EM>
-and <EM>mask</EM>.
+user intends to <em>reclassify</em> or <em>rescale</em> the data,
+since these functions (<em><a href="r.reclass.html">r.reclass</a></em> and
+<em><a href="r.rescale.html">r.rescale</a></em>)
+also ignore the current <em>geographic region</em>
+and <em>mask</em>.
<p>
-The <EM><B>nv</B></EM> parameter sets the string to be used to represent <tt>NULL</tt>
+The <em><b>nv</b></em> parameter sets the string to be used to represent <tt>NULL</tt>
values in the module output; the default is '*'.
<p>
-The <EM><B>nsteps</B></EM> parameter sets the number of quantisation steps to divide into
+The <em><b>nsteps</b></em> parameter sets the number of quantisation steps to divide into
the input raster map.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-<H3>FLAGS</H3>
+<h3>FLAGS</h3>
If the user selects the <b>-r</b> flag, a range of category values found in
the raster map layer will be printed. The range is divided into three groups:
@@ -34,45 +34,45 @@
<p>
-The <B>-d</B> flag can be used to force <em>r.describe</em> to respect the current region
+The <b>-d</b> flag can be used to force <em>r.describe</em> to respect the current region
extents when repoting raster map categories. The default behavior is to read the full
extent of the input raster map.
<p>
-If the <B>-1</B> flag is specified, the output appears with one category value/range per line.
+If the <b>-1</b> flag is specified, the output appears with one category value/range per line.
<p>
-The <B>-n</B> flag suppresses the reporting of <tt>NULL</tt> values.
+The <b>-n</b> flag suppresses the reporting of <tt>NULL</tt> values.
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
The following examples are from the Spearfish60 sample Location:
<p>
# Print the full list of raster map categories:
-<div class="code"><PRE>
+<div class="code"><pre>
r.describe landcover.30m
* 11 21-23 31 32 41-43 51 71 81-83 85 91 92
-</PRE></div>
+</pre></div>
<p>
# Print the raster range only:
-<div class="code"><PRE>
+<div class="code"><pre>
r.describe -r landcover.30m
11 thru 92
*
-</PRE></div>
+</pre></div>
# Print raster map category range, suppressing nulls:
-<div class="code"><PRE>
+<div class="code"><pre>
r.describe -n landcover.30m
11 21-23 31 32 41-43 51 71 81-83 85 91 92
-</PRE></div>
+</pre></div>
<p>
# Print raster map categories, one category per line:
-<div class="code"><PRE>
+<div class="code"><pre>
r.describe -1 geology
*
@@ -85,23 +85,23 @@
7
8
9
-</PRE></div>
+</pre></div>
<p>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="g.region.html">g.region</A>,
-<A HREF="r.mask.html">r.mask</A>,
-<A HREF="r.reclass.html">r.reclass</A>,
-<A HREF="r.report.html">r.report</A>,
-<A HREF="r.rescale.html">r.rescale</A>,
-<A HREF="r.stats.html">r.stats</A>,
-<A HREF="r.univar.html">r.univar</A>
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="r.mask.html">r.mask</a>,
+<a href="r.reclass.html">r.reclass</a>,
+<a href="r.report.html">r.report</a>,
+<a href="r.rescale.html">r.rescale</a>,
+<a href="r.stats.html">r.stats</a>,
+<a href="r.univar.html">r.univar</a>
-</EM>
+</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.digit/description.html
===================================================================
--- grass/trunk/raster/r.digit/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.digit/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-The GRASS tool <EM>r.digit</EM> provides the user with a
+The GRASS tool <em>r.digit</em> provides the user with a
way to draw lines, areas, and circles on a monitor screen,
and to save these features in a raster map. Lines, areas,
and circles are to be drawn using a pointing device
@@ -9,7 +9,7 @@
the category number associated with the line, area, or
circle subsequently drawn by the user. Lines, areas, and
circles are defined by the series of points marked by the
-user inside the map window. <EM>r.digit</EM> will close
+user inside the map window. <em>r.digit</em> will close
areas when the user has not. By drawing a series of such
features, the user can repair maps, identify areas of
interest, or simply draw graphics for advertisement. When
@@ -17,20 +17,20 @@
instructions is generated. It is available for use as a
mask, in analyses, and for display.
-<P>
+<p>
The <b>bgcmd</b> option is intended to be used with display (d.*) commands.
If several display commands are to be used to render the background
they should be separated with the semi-colon ';' character.
When run from the command line, these display commands will generally
need to be "quoted" as they will contain spaces (see examples).
-<P>
+<p>
Digitizing is done in a "polygon" method. Each area is
circumscribed completely. Two or more overlapping areas and/or lines
might define a single part of a map. Each part of the map,
however, is assigned only the LAST area or line which
covered it.
-<H3>THE PROCESS:</H3>
+<h3>THE PROCESS:</h3>
<h4>Start a monitor and display a raster to help setup and zoom to area of interest</h4>
<div class="code"><pre>
@@ -43,34 +43,34 @@
r.digit out=name_of_new_raster_map bgcmd="d.rast map=name_of_raster"
</pre></div>
-<OL>
+<ol>
-<LI>Choose to define an area or line, exit, or quit.
+<li>Choose to define an area or line, exit, or quit.
If you choose to finish (<tt>exit</tt>) a new map is then created.
If you quit, the session exits with nothing created.
-<LI>If you choose to make an area or line you must identify
+<li>If you choose to make an area or line you must identify
the category number for that area or line.
-<LI>Using the mouse trace the line or circumscribe the area;
+<li>Using the mouse trace the line or circumscribe the area;
or, finish (go to Step 1).
-</OL>
+</ol>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="v.digit.html">v.digit</A></EM>,
-<EM><A HREF="d.graph.html">d.graph</A></EM>,
-<EM><A HREF="d.linegraph.html">d.linegraph</A></EM>,
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="r.in.poly.html">r.in.poly</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.to.vect.html">r.to.vect</A></EM>,
-<EM><A HREF="v.in.ascii.html">v.in.ascii</A></EM>
+<em><a href="v.digit.html">v.digit</a></em>,
+<em><a href="d.graph.html">d.graph</a></em>,
+<em><a href="d.linegraph.html">d.linegraph</a></em>,
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.in.poly.html">r.in.poly</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.to.vect.html">r.to.vect</a></em>,
+<em><a href="v.in.ascii.html">v.in.ascii</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro, U.S.Army Construction Engineering
Research Laboratory
Modified: grass/trunk/raster/r.drain/description.html
===================================================================
--- grass/trunk/raster/r.drain/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.drain/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,62 +1,62 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.drain</EM> traces a flow through a least-cost path in an elevation
+<em>r.drain</em> traces a flow through a least-cost path in an elevation
model. The <b>input</b> elevation surface (a raster map layer) might
be a cumulative cost map generated by the
-<EM><A HREF="r.cost.html">r.cost</A></EM> program.
+<em><a href="r.cost.html">r.cost</a></em> program.
The <b>output</b> result (also a raster map layer) will show one or more
least-cost paths between each user-provided location(s) and the minima
-(low category values) in the <B>input</B> map. By default, the <B>output</B>
+(low category values) in the <b>input</b> map. By default, the <b>output</b>
will be an integer CELL map with <tt>1</tt> along the least cost path,
and null cells elsewhere.
-<P>
-With the <B>-c</B> (<EM>copy</EM>) flag, the input map cell values are
-copied verbatim along the path. With the <B>-a</B> (<EM>accumulate</EM>)
+<p>
+With the <b>-c</b> (<em>copy</em>) flag, the input map cell values are
+copied verbatim along the path. With the <b>-a</b> (<em>accumulate</em>)
flag, the accumulated cell value from the starting point up to the current
-cell is written on output. With either the <B>-c</B> or the <B>-a</B> flags, the
-<B>output</B> map is created with the same cell type as the <B>input</B> map (integer,
+cell is written on output. With either the <b>-c</b> or the <b>-a</b> flags, the
+<b>output</b> map is created with the same cell type as the <b>input</b> map (integer,
float or double).
-With the <B>-n</B> (<EM>number</EM>) flag, the cells are numbered consecutively from the
+With the <b>-n</b> (<em>number</em>) flag, the cells are numbered consecutively from the
starting point to the final point.
-The <B>-c</B>, <B>-a</B>, and <B>-n</B> flags are mutually incompatible.
+The <b>-c</b>, <b>-a</b>, and <b>-n</b> flags are mutually incompatible.
-<P>
+<p>
The path is calculated by choosing the steeper "slope" between adjacent
cells. The slope calculation accurately acounts for the variable scale in
lat-lon projections.
-<P>
-The <B>coordinate</B> parameter consists of map E and N grid coordinates of
+<p>
+The <b>coordinate</b> parameter consists of map E and N grid coordinates of
a starting point. Each x,y pair is the easting and northing (respectively) of
a starting point from which a least-cost corridor will be developed.
-The <B>vector_points</B> parameter can take multiple vector maps containing
+The <b>vector_points</b> parameter can take multiple vector maps containing
additional starting points.
Up to 1024 starting points can be input from a combination of the
-<B>coordinate</B> and <B>vector_points</B> parameters.
+<b>coordinate</b> and <b>vector_points</b> parameters.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-<EM>r.drain</EM> currently finds only the lowest point
+<em>r.drain</em> currently finds only the lowest point
(the cell having the smallest category value) in the
input file that can be reached through directly adjacent cells
that are less than or equal in value to the cell reached immediately
prior to it; therefore, it will not necessarily reach the lowest point
-in the input file. It currently finds <EM>pits</EM> in the data, rather
+in the input file. It currently finds <em>pits</em> in the data, rather
than the lowest point in the entire input map. The <em>r.fill.dir</em>,
<em>r.terraflow</em>, and <em>r.basins.fill</em> modules can be used to
fill in subbasins prior to processing with <em>r.drain</em>.
-<P>
+<p>
-<EM>r.drain</EM> will not give sane results at the region boundary. On outer rows
+<em>r.drain</em> will not give sane results at the region boundary. On outer rows
and columns bordering the edge of the region, the flow direction is always directly out
of the map. In this case, the user could try adjusting the region extents slightly with
-<EM>g.region</EM> to allow additional outlet paths for <EM>r.drain</EM>.
+<em>g.region</em> to allow additional outlet paths for <em>r.drain</em>.
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
Consider the following example:
@@ -78,16 +78,16 @@
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
</pre></div>
-<P>
+<p>
The user-provided starting location in the above example is
-the boxed <B>19</B> in the left-hand map. The path in the output
+the boxed <b>19</b> in the left-hand map. The path in the output
shows the least-cost corridor for moving from the starting
box to the lowest (smallest) possible point. This is the path a raindrop
would take in this landscape.
-<P>
+<p>
-With the <B>-c</B> <EM>(copy)</EM> flag, you get the following result:
+With the <b>-c</b> <em>(copy)</em> flag, you get the following result:
<div class="code"><pre>
Input: Output:
@@ -106,12 +106,12 @@
. 17. 9 . 8 . 7 . 8 . 6 .12 . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-Note that the last <EM>0</EM> will not be put in the null values map.
+Note that the last <em>0</em> will not be put in the null values map.
</pre></div>
-<P>
+<p>
-With the <B>-a</B> <EM>(accumulate)</EM> flag, you get the following result:
+With the <b>-a</b> <em>(accumulate)</em> flag, you get the following result:
<div class="code"><pre>
Input: Output:
@@ -131,9 +131,9 @@
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
</pre></div>
-<P>
+<p>
-With the <B>-n</B> <EM>(number)</EM> flag, you get the following result:
+With the <b>-n</b> <em>(number)</em> flag, you get the following result:
<div class="code"><pre>
Input: Output:
@@ -153,40 +153,40 @@
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
</pre></div>
-<P>
+<p>
-<H2>BUGS</H2>
+<h2>BUGS</h2>
-<P>
+<p>
Sometimes, when the differences among integer cell category values in the
-<EM><A HREF="r.cost.html">r.cost</a></EM> cumulative cost surface output are
+<em><a href="r.cost.html">r.cost</a></em> cumulative cost surface output are
small, this cumulative cost output cannot accurately be used as input to
-<EM>r.drain</EM> (<EM>t.drain</EM> will output bad results).
+<em>r.drain</em> (<em>t.drain</em> will output bad results).
This problem can be circumvented by making the differences
between cell category values in the cumulative cost output bigger. It
-is recommended that if the output from <EM>r.cost</EM> is to be used
-as input to <EM>r.drain</EM>, the user multiply the <EM>r.cost</EM>
+is recommended that if the output from <em>r.cost</em> is to be used
+as input to <em>r.drain</em>, the user multiply the <em>r.cost</em>
input cost surface map by the value of the map's cell resolution,
-before running <EM>r.cost</EM>. This can be done using
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>. The map resolution can be
-found using <EM><A HREF="g.region.html">g.region</A></EM>.
+before running <em>r.cost</em>. This can be done using
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>. The map resolution can be
+found using <em><a href="g.region.html">g.region</a></em>.
This problem doesn't arise with floating point maps.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="r.cost.html">r.cost</A></EM>,
-<EM><A HREF="r.fill.dir.html">r.fill.dir</A></EM>,
-<EM><A HREF="r.basins.fill.html">r.basins.fill</A></EM>,
-<EM><A HREF="r.terraflow.html">r.terraflow</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.walk.html">r.walk</A></EM>
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.cost.html">r.cost</a></em>,
+<em><a href="r.fill.dir.html">r.fill.dir</a></em>,
+<em><a href="r.basins.fill.html">r.basins.fill</a></em>,
+<em><a href="r.terraflow.html">r.terraflow</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.walk.html">r.walk</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Completely rewritten by Roger S. Miller, 2001
-<P>
+<p>
July 2004 at WebValley 2004, error checking and vector points added by
Matteo Franchi (Liceo Leonardo Da Vinci, Trento) and
Roberto Flor (ITC-irst, Trento, Italy)
Modified: grass/trunk/raster/r.grow2/description.html
===================================================================
--- grass/trunk/raster/r.grow2/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.grow2/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,23 +1,23 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.grow</EM> adds cells around the perimeters of all areas
+<em>r.grow</em> adds cells around the perimeters of all areas
in a user-specified raster map layer and stores the output in
a new raster map layer. The user can use it to grow by one or
more than one cell, or like <em>r.buffer</em>, but with the
option of preserving the original cells (similar to combining
<em>r.buffer</em> and <em>r.patch</em>).
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.buffer.html">r.buffer</A></EM>,
-<EM><A HREF="r.patch.html">r.patch</A></EM>
+<em><a href="r.buffer.html">r.buffer</a></em>,
+<em><a href="r.patch.html">r.patch</a></em>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
Marjorie Larson,
U.S. Army Construction Engineering Research Laboratory
-<P>
+<p>
Glynn Clements
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.gwflow/description.html
===================================================================
--- grass/trunk/raster/r.gwflow/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.gwflow/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
This numerical program calculates transient, confined and
unconfined groundwater flow in two dimensions based on
raster maps and the current region resolution.
@@ -7,7 +7,7 @@
<p>
<center>
-<img src=r_gwflow_concept.png border=0><BR>
+<img src=r_gwflow_concept.png border=0><br>
<table border=0 width=700>
<tr><td><center>
<i>Workflow of r.gwflow</i>
@@ -28,7 +28,7 @@
specific yield/ effective porosity raster maps to zero.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
The groundwater flow calculation is based on Darcy's law and a
finite volume discretization. The solved groundwater flow partial
@@ -69,7 +69,7 @@
(maps of size 10.000 cells will need more than one gigabyte of RAM).
Always prefer a sparse matrix solver.
-<H2>EXAMPLE</H2>
+<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.
@@ -109,12 +109,12 @@
paraview --data=/tmp/gwdata_unconf2d.vtk &
</pre></div>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r3.gwflow.html">r3.gwflow</A></EM><br>
-<EM><A HREF="r.out.vtk.html">r.out.vtk</A></EM><br>
+<em><a href="r3.gwflow.html">r3.gwflow</a></em><br>
+<em><a href="r.out.vtk.html">r.out.vtk</a></em><br>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Soeren Gebbert
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.in.bin/description.html
===================================================================
--- grass/trunk/raster/r.in.bin/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.in.bin/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,16 +1,16 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.in.bin</EM> allows a user to create a (binary) GRASS raster map layer
+<em>r.in.bin</em> allows a user to create a (binary) GRASS raster map layer
from a variety of binary raster data formats.
-<P>
-The <B> -s</B> flag is used for importing two's-complement signed data.
-<P>
-The <B> -h</B> flag is used to read region information from a Generic
+<p>
+The <b> -s</b> flag is used for importing two's-complement signed data.
+<p>
+The <b> -h</b> flag is used to read region information from a Generic
Mapping Tools (GMT) type binary header. It is compatible with GMT binary
grid types 1 and 2.
-<P>
+<p>
The north, south, east, and west field values entered
are the coordinates of the edges of the geographic region.
The rows and cols field values entered describe the dimensions
@@ -20,92 +20,92 @@
If the bytes field is entered incorrectly an error will be generated
suggesting a closer bytes value.
-<P>
-<EM>r.in.bin</EM> can be used to import numerous binary arrays including:
+<p>
+<em>r.in.bin</em> can be used to import numerous binary arrays including:
ETOPO30, ETOPO-5, ETOPO-2, Globe DEM, BIL, AVHRR and GMT binary arrays (ID 1 & 2)
-<P>
+<p>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-If optional parameters are not supplied, <B>r.in.bin</B> attempts
+If optional parameters are not supplied, <b>r.in.bin</b> attempts
to calculate them. For example if the rows and columns parameters are
-not entered, <B>r.in.bin</B> automatically calculates them by subtracting
+not entered, <b>r.in.bin</b> automatically calculates them by subtracting
south from north and west from east. This will only produce correct
results if the raster resolution equals 1. Also, if the north, south,
-east, and west parameters are not entered, <B>r.in.bin</B> assigns
+east, and west parameters are not entered, <b>r.in.bin</b> assigns
them from the rows and columns parameters. In the above AVHRR example,
the raster would be assigned a north=128, south=0, east=128, west=0.
-<P>
+<p>
The geographic coordinates north, south, east, and west
describe the outer edges of the geographic region. They
run along the edges of the cells at the edge of the
-geographic region and <EM>not</EM> through the center of the cells
+geographic region and <em>not</em> through the center of the cells
at the edges.
-<P>
+<p>
Eastern limit of geographic region (in projected coordinates must be east
of the west parameter value, but in geographical coordinates will wrap
-around the globe; user errors can be detected by comparing the <EM>ewres</EM> and
-<EM>nsres</EM> values of the imported map layer carefully).
+around the globe; user errors can be detected by comparing the <em>ewres</em> and
+<em>nsres</em> values of the imported map layer carefully).
<br>
Western limit of geographic region (in projected coordinates must be west
of the east parameter value, but in geographical coordinates will wrap
-around the globe; user errors can be detected by comparing the <EM>ewres</EM> and
-<EM>nsres</EM> values of the imported map layer carefully).
-<P>
-Notes on (non)signed data:<P>
+around the globe; user errors can be detected by comparing the <em>ewres</em> and
+<em>nsres</em> values of the imported map layer carefully).
+<p>
+Notes on (non)signed data:<p>
If you use the -s flag the highest bit is the sign bit. If this is 1 the
data is negative, and the data interval is half of the unsigned (not
exactly).
-<P>
-This flag is only used if <B>bytes=</B> 1. If <B>bytes=</B> is greater
+<p>
+This flag is only used if <b>bytes=</b> 1. If <b>bytes=</b> is greater
than 1 the flag is ignored.
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
<h3>GTOPO30 DEM</h3>
-The following is a sample call of <EM>r.in.bin</EM> to import
+The following is a sample call of <em>r.in.bin</em> to import
<a href=http://edcdaac.usgs.gov/gtopo30/gtopo30.asp>GTOPO30 DEM</a>
data:
-<P>
+<p>
<div class="code"><pre>
r.in.bin -sb input=E020N90.DEM output=gtopo30 bytes=2 north=90 south=40
east=60 west=20 r=6000 c=4800
</pre></div>
-<P>
+<p>
(you can add "anull=-9999" if you want sea level to have a NULL value)
<h3>GMT</h3>
-The following is a sample call of <EM>r.in.bin</EM> to import a GMT
+The following is a sample call of <em>r.in.bin</em> to import a GMT
type 1 (float) binary array:
-<P>
+<p>
<div class="code"><pre>
r.in.bin -hf input=sample.grd output=sample.grass
</pre></div>
-<P>
+<p>
(-b could be used to swap bytes if required)
<h3>AVHRR</h3>
-The following is a sample call of <EM>r.in.bin</EM> to import an AVHRR image:
-<P>
+The following is a sample call of <em>r.in.bin</em> to import an AVHRR image:
+<p>
<div class="code"><pre>
r.in.bin in=p07_b6.dat out=avhrr c=128 r=128
</pre></div>
<h3>ETOPO2</h3>
-The following is a sample call of <EM>r.in.bin</EM> to import
+The following is a sample call of <em>r.in.bin</em> to import
<a href=http://www.ngdc.noaa.gov/mgg/image/2minrelief.html>ETOPO2 DEM</a> data (here full data set):
-<P>
+<p>
<div class="code"><pre>
r.in.bin ETOPO2.dos.bin out=ETOPO2min r=5400 c=10800 n=90 s=-90 w=-180 e=180 bytes=2
r.colors ETOPO2min rules=terrain
</pre></div>
<h3>TOPEX/SRTM30 PLUS</h3>
-The following is a sample call of <EM>r.in.bin</EM> to import
+The following is a sample call of <em>r.in.bin</em> to import
<a href="http://topex.ucsd.edu/WWW_html/srtm30_plus.html">SRTM30 PLUS</a> data:
-<P>
+<p>
<div class="code"><pre>
r.in.bin -sb input=e020n40.Bathmetry.srtm output=e020n40_topex \
bytes=2 north=40 south=-10 east=60 west=20 r=6000 c=4800
@@ -113,22 +113,22 @@
</pre></div>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="r.out.bin.html">r.out.bin</A>,
-<A HREF="r.in.ascii.html">r.in.ascii</A>,
-<A HREF="r.out.ascii.html">r.out.ascii</A>,
-<A HREF="r.in.arc.html">r.in.arc</A>,
-<A HREF="r.out.arc.html">r.out.arc</A>,
-<A HREF="r.in.gdal.html">r.in.gdal</A>,
-<A HREF="r.out.gdal.html">r.out.gdal</A>,
-<A HREF="r.in.srtm.html">r.in.srtm</A>
-</EM>
+<em>
+<a href="r.out.bin.html">r.out.bin</a>,
+<a href="r.in.ascii.html">r.in.ascii</a>,
+<a href="r.out.ascii.html">r.out.ascii</a>,
+<a href="r.in.arc.html">r.in.arc</a>,
+<a href="r.out.arc.html">r.out.arc</a>,
+<a href="r.in.gdal.html">r.in.gdal</a>,
+<a href="r.out.gdal.html">r.out.gdal</a>,
+<a href="r.in.srtm.html">r.in.srtm</a>
+</em>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
-Jacques Bouchard, France (bouchard at onera.fr)<BR>
-Bob Covill, Canada (bcovill at tekmap.ns.ca)<BR>
+Jacques Bouchard, France (bouchard at onera.fr)<br>
+Bob Covill, Canada (bcovill at tekmap.ns.ca)<br>
Man page: Zsolt Felker (felker at c160.pki.matav.hu)
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.in.gridatb/description.html
===================================================================
--- grass/trunk/raster/r.in.gridatb/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.in.gridatb/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,15 +1,15 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.in.gridatb</EM> imports GRIDATB.FOR map file (TOPMODEL) into GRASS
+<em>r.in.gridatb</em> imports GRIDATB.FOR map file (TOPMODEL) into GRASS
raster map.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.topmodel.html">r.topmodel</A>,</EM>
-<EM><A HREF="r.out.gridatb.html">r.out.gridatb</A></EM>
+<em><a href="r.topmodel.html">r.topmodel</a>,</em>
+<em><a href="r.out.gridatb.html">r.out.gridatb</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Huidae Cho based on code from Keith Beven
Modified: grass/trunk/raster/r.in.mat/description.html
===================================================================
--- grass/trunk/raster/r.in.mat/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.in.mat/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,11 +1,11 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.in.mat</EM> will import a GRASS raster map from a Version 4 MAT-File
+<em>r.in.mat</em> will import a GRASS raster map from a Version 4 MAT-File
which was created with Matlab or Octave.
Attributes such as map title and bounds will also be imported if they exist.
-<BR>
-<BR>
-Specifically, the following array variables will be read:<BR>
+<br>
+<br>
+Specifically, the following array variables will be read:<br>
<ul>
<li><b> map_data</b>
<li><b> map_name</b>
@@ -16,33 +16,33 @@
<li><b> map_western_edge</b>
</ul>
-Any other variables in the MAT-file will be simply skipped over.<BR>
-<BR>
+Any other variables in the MAT-file will be simply skipped over.<br>
+<br>
The '<b>map_name</b>' variable is optional, if it exists, and is valid, the
new map will be thus named. If it doesn't exist or a name is specified with
the <b>output=</b> option, the raster map's name will be set to
"<tt>MatFile</tt>" or the name specified respectively.
(maximum 64 characters; normal GRASS naming rules apply)
-<BR>
-<BR>
+<br>
+<br>
The '<b>map_title</b>' variable is optional, the map's title is set if it
exists.
-<BR>
-<BR>
+<br>
+<br>
The '<b>map_northern_edge</b>' and like variables are mandatory unless the
user is importing to a "XY" non-georeferenced location
(e.g. imagery data). Latitude and longitude values should be in decimal form.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-<EM>r.in.mat</EM> imports a Version 4 MAT-File. These files can be
+<em>r.in.mat</em> imports a Version 4 MAT-File. These files can be
successfully created with more modern versions of Matlab and Octave
-(see "EXAMPLES" below).<BR><BR>
+(see "EXAMPLES" below).<br><br>
Everything should be Endian safe, so the file to be imported can be simply
copied between different system architectures without binary translation
-(caveat: see "TODO" below).<BR><BR>
+(caveat: see "TODO" below).<br><br>
As there is no IEEE value for <tt>NaN</tt> in integer arrays, GRASS's null
value may be used to represent it within these maps. Usually Matlab will save
@@ -55,12 +55,12 @@
</pre></div>
<tt>NaN</tt> values in either floating point or double-precision floating point
-matrices should translate into null values as expected.<BR><BR>
+matrices should translate into null values as expected.<br><br>
-<EM>r.in.mat</EM> must load the entire map array into memory before writing,
+<em>r.in.mat</em> must load the entire map array into memory before writing,
therefore it might have problems with <i>huge</i> arrays.
-(a 3000x4000 DCELL map uses about 100mb RAM)<BR><BR>
+(a 3000x4000 DCELL map uses about 100mb RAM)<br><br>
GRASS defines its map bounds at the outer-edge of the bounding cells, not at
the coordinates of their centroids. Thus, the following Matlab commands may
@@ -73,15 +73,15 @@
ew_res = x_range/cols
</pre></div>
-<BR>
+<br>
Remember Matlab arrays are referenced as <tt>(row,column)</tt>,
i.e. <tt>(y,x)</tt>.
-<BR><BR>
-In addition, <EM>r.in.mat</EM> and <EM>r.out.mat</EM> make for a nice
+<br><br>
+In addition, <em>r.in.mat</em> and <em>r.out.mat</em> make for a nice
binary container format for transferring georeferenced maps around,
even if you don't use Matlab or Octave.
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
In Matlab, save with:
<div class="code"><pre>
@@ -93,44 +93,44 @@
save -mat4-binary filename.mat map_*
</pre></div>
-<BR>
+<br>
-<H2>TODO</H2>
+<h2>TODO</h2>
Robust support for mixed-Endian importation.
<i>(This is a work in progress, please help by reporting any failures to the
<a href="http://grass.itc.it/bugtracking/bugreport.html">
GRASS bug tracking system</a>)</i>
-<BR>
+<br>
Add support for importing map history, category information, color map, etc.
if they exist.
-<BR>
+<br>
Option to import a version 5 MAT-File, with map and support information
stored in a single structured array.
-<H2>BUGS</H2>
+<h2>BUGS</h2>
If you encounter any problems, please contact the GRASS Development Team.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
<i>
<a href="r.out.mat.html">r.out.mat</a>,
<a href="r.in.ascii.html">r.in.ascii</a>,
<a href="r.in.bin.html">r.in.bin</a>,
<a href="r.mapcalc.html">r.mapcalc</a>,
-<a href="r.null.html">r.null</a>.<P>
+<a href="r.null.html">r.null</a>.<p>
The <a href="http://www.octave.org">Octave</a> project
</i>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
-Hamish Bowman<BR> <i>
-Department of Marine Science<BR>
-University of Otago<BR>
-New Zealand</i><BR>
+Hamish Bowman<br> <i>
+Department of Marine Science<br>
+University of Otago<br>
+New Zealand</i><br>
-<BR>
+<br>
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.in.poly/description.html
===================================================================
--- grass/trunk/raster/r.in.poly/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.in.poly/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,42 +1,42 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.in.poly</EM> allows the creation of GRASS binary
+<em>r.in.poly</em> allows the creation of GRASS binary
raster maps from ASCII files in the current directory
containing polygon, linear, and point features.
-<P>
-The <B>input</B> file is an ASCII text file containing the
+<p>
+The <b>input</b> file is an ASCII text file containing the
polygon, linear, and point feature definitions.
The format of this file is described in the
-<A HREF="#format.html"><B>INPUT FORMAT</B></A> section below.
+<a href="#format.html"><b>INPUT FORMAT</b></a> section below.
-<P>
+<p>
The number of raster <b>rows</b> to hold in memory is per default 4096.
This parameter allows users with less memory (or more) on their
-system to control how much memory <EM>r.in.poly</EM> uses.
+system to control how much memory <em>r.in.poly</em> uses.
Usually the default value is fine.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-<P>
+<p>
The data will be imported using the current region settings to set the
new raster map's bounds and resolution. Any features falling outside
the current region will be cropped. The region settings are contolled
with the <em>g.region</em> module.
-<P>
+<p>
The format is a simplified version of the standard GRASS vector ASCII
-format used by <EM>v.in.ascii</EM>.
+format used by <em>v.in.ascii</em>.
-<P>
+<p>
Polygons are filled, i.e. they define an area.
-<A NAME="format.html"></A>
-<H2>INPUT FORMAT</H2>
+<A NAME="format.html"></a>
+<h2>INPUT FORMAT</h2>
-The input format for the <B>input</B> file consists of
+The input format for the <b>input</b> file consists of
sections describing either polygonal areas, linear features, or
point features. The basic format is:
@@ -70,15 +70,15 @@
The coordinates of the vertices of the polygon, or the coordinates defining
the linear or point feature follow and must have a space in the first
-column and at least one space between the <EM>easting</EM> and the
-<EM>northing.</EM> To give meaning to the features, the
+column and at least one space between the <em>easting</em> and the
+<em>northing.</em> To give meaning to the features, the
"<tt>=</tt>" indicates that the feature currently being
-processed has category value <EM>cat#</EM> (which must be
-an integer) and a <EM>label</EM> (which may be more than
+processed has category value <em>cat#</em> (which must be
+an integer) and a <em>label</em> (which may be more than
one word, or which may be omitted).
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
An area described by four points:
@@ -91,24 +91,24 @@
= 42 stadium
</pre></div>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<A HREF="r.digit.html">r.digit</A> for
+<a href="r.digit.html">r.digit</a> for
interactive on-screen polygon/line digitizing for raster maps
-<P>
-<A HREF="r.colors.html">r.colors</A>
+<p>
+<a href="r.colors.html">r.colors</a>
for creates color tables for raster maps
-<P>
+<p>
-<A HREF="d.rast.edit.html">d.rast.edit</A>,
-<A HREF="g.region.html">g.region</A>,
-<A HREF="r.in.xyz.html">r.in.xyz</A>,
-<A HREF="r.patch.html">r.patch</A>,
-<A HREF="v.in.ascii.html">v.in.ascii</A>,
-<A HREF="v.digit.html">v.digit</A>
+<a href="d.rast.edit.html">d.rast.edit</a>,
+<a href="g.region.html">g.region</a>,
+<a href="r.in.xyz.html">r.in.xyz</a>,
+<a href="r.patch.html">r.patch</a>,
+<a href="v.in.ascii.html">v.in.ascii</a>,
+<a href="v.digit.html">v.digit</a>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro, U.S.Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.in.xyz/description.html
===================================================================
--- grass/trunk/raster/r.in.xyz/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.in.xyz/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,14 +1,14 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-The <EM>r.in.xyz</EM> module will load and bin ungridded x,y,z ASCII data
+The <em>r.in.xyz</em> module will load and bin ungridded x,y,z ASCII data
into a new raster map. The user may choose from a variety of statistical
methods in creating the new raster.
-<P>
-<EM>r.in.xyz</EM> is designed for processing massive point cloud datasets,
+<p>
+<em>r.in.xyz</em> is designed for processing massive point cloud datasets,
for example raw LIDAR or sidescan sonar swath data. It has been tested with
datasets as large as 1.5 billion points.
-<P>
-Available statistics for populating the raster are:<BR>
+<p>
+Available statistics for populating the raster are:<br>
<ul>
<table>
<tr><td><em>n</em></td> <td>number of points in cell</td></tr>
@@ -25,20 +25,20 @@
<td>p<sup><i>th</i></sup> percentile of points in cell</td></tr>
<tr><td><em>skewness</em></td> <td>skewness of points in cell</td></tr>
<tr><td><em>trimmean</em></td> <td>trimmed mean of points in cell</td></tr>
-</table><BR>
+</table><br>
<li><em>Variance</em> and derivatives use the biased estimator (n). [subject to change]
<li><em>Coefficient of variance</em> is given in percentage and defined as
<tt>(stddev/mean)*100</tt>.
</ul>
-<BR>
+<br>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
<h4>Memory use</h4>
-While the <B>input</B> file can be arbitrarily large, <EM>r.in.xyz</EM>
+While the <b>input</b> file can be arbitrarily large, <em>r.in.xyz</em>
will use a large amount of system memory for large raster regions (10000x10000).
If the module refuses to start complaining that there isn't enough memory,
use the <b>percent</b> parameter to run the module in several passes.
@@ -50,7 +50,7 @@
The aggregate functions <em>median, percentile, skewness</em> and
<em>trimmed mean</em> will also use more memory.
-<P>
+<p>
The default map <b>type</b>=<tt>FCELL</tt> is intended as compromise between
preserving data precision and limiting system resource consumption.
If reading data from a <tt>stdin</tt> stream, the program can only run using
@@ -77,7 +77,7 @@
# Lat/Lon location:
# points_per_sq_m = n_points / (ns_extent * ew_extent*cos(lat) * (1852*60)^2)
</pre></div>
-<P>
+<p>
If you only intend to interpolate the data with <em>r.to.vect</em> and
<em>v.surf.rst</em>, then there is little point to setting the region
resolution so fine that you only catch one data point per cell -- you might
@@ -90,32 +90,32 @@
points falling <em>exactly</em> on the southern region bound.
(to capture those adjust the region with "<tt>g.region s=s-0.000001</tt>";
see <em>g.region</em>)
-<P>
+<p>
Blank lines and comment lines starting with the hash symbol (<tt>#</tt>)
will be skipped.
-<P>
+<p>
The <b>zrange</b> parameter may be used for filtering the input data by
vertical extent. Example uses might include preparing multiple raster
sections to be combined into a 3D raster array with <em>r.to.rast3</em>, or
for filtering outliers on relatively flat terrain.
-<P>
+<p>
In varied terrain the user may find that <em>min</em> maps make for a good
noise filter as most LIDAR noise is from premature hits. The <em>min</em> map
may also be useful to find the underlying topography in a forested or urban
environment if the cells are over sampled.
-<P>
-The user can use a combination of <EM>r.in.xyz</EM> <B>output</b> maps to create
+<p>
+The user can use a combination of <em>r.in.xyz</em> <b>output</b> maps to create
custom filters. e.g. use <em>r.mapcalc</em> to create a <tt>mean-(2*stddev)</tt>
map. [In this example the user may want to include a lower bound filter in
<em>r.mapcalc</em> to remove highly variable points (small <em>n</em>) or run
-<EM>r.neighbors</EM> to smooth the stddev map before further use.]
+<em>r.neighbors</em> to smooth the stddev map before further use.]
<h4>Reprojection</h4>
If the raster map is to be reprojected, it may be more appropriate to reproject
the input points with <em>m.proj</em> or <em>cs2cs</em> before running
-<EM>r.in.xyz</EM>.
+<em>r.in.xyz</em>.
<h4>Interpolation into a DEM</h4>
@@ -129,16 +129,16 @@
Run <em>r.univar</em> on your raster map to check the number of non-NULL cells
and adjust bounds and/or resolution as needed before proceeding.
-<P>
+<p>
Typical commands to create a DEM using a regularized spline fit:
<div class="code"><pre>
r.univar lidar_min
r.to.vect -z feature=point in=lidar_min out=lidar_min_pt
v.surf.rst layer=0 in=lidar_min_pt elev=lidar_min.rst
</pre></div>
-<BR>
+<br>
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
Import the <a href="http://mpa.itc.it/grasstutor/data_menu2nd.phtml">Jockey's
Ridge, NC, LIDAR dataset</a>, and process into a clean DEM:
@@ -168,31 +168,31 @@
r.mapcalc "lidar_min.rst_scaled = lidar_min.rst / (1852*60)"
r.colors lidar_min.rst_scaled rule=bcyr -n -e
</pre></div>
-<BR>
+<br>
-<H2>TODO</H2>
+<h2>TODO</h2>
<ul>
-<li> Support for multiple map output from a single run.<BR>
+<li> Support for multiple map output from a single run.<br>
<tt>method=string[,string,...] output=name[,name,...]</tt>
</ul>
-<H2>BUGS</H2>
+<h2>BUGS</h2>
<ul>
<li> <em>n</em> map sum can be ever-so-slightly more than `<tt>wc -l</tt>`
with e.g. <tt>percent=10</tt> or less.
- <BR>Cause unknown.
+ <br>Cause unknown.
<li> <em>n</em> map <tt>percent=100</tt> and <tt>percent=xx</tt> maps
differ slightly (point will fall above/below the segmentation line)
- <BR>Investigate with "<tt>r.mapcalc diff=bin_n.100 - bin_n.33</tt>" etc.
- <BR>Cause unknown.
+ <br>Investigate with "<tt>r.mapcalc diff=bin_n.100 - bin_n.33</tt>" etc.
+ <br>Cause unknown.
<li> "<tt>nan</tt>" can leak into <em>coeff_var</em> maps.
- <BR>Cause unknown. Possible work-around: "<tt>r.null setnull=nan</tt>"
+ <br>Cause unknown. Possible work-around: "<tt>r.null setnull=nan</tt>"
<!-- HB: "possible" when someone fixes r.null to allow it ;) -->
<!-- Another method: r.mapcalc 'No_nan = if(map == map, map, null() )' -->
</ul>
@@ -200,36 +200,36 @@
If you encounter any problems (or solutions!) please contact the GRASS
Development Team.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
<i>
-<a href="g.region.html">g.region</a><BR>
-<a href="m.proj.html">m.proj</a><BR>
-<a href="r.fillnulls.html">r.fillnulls</a><BR>
-<a href="r.in.ascii.html">r.in.ascii</a><BR>
-<a href="r.mapcalc.html">r.mapcalc</a><BR>
-<a href="r.neighbors.html">r.neighbors</a><BR>
-<a href="r.out.xyz.html">r.out.xyz</a><BR>
-<a href="r.to.rast3.html">r.to.rast3</a><BR>
-<a href="r.to.vect.html">r.to.vect</a><BR>
-<a href="r.univar.html">r.univar</a><BR>
-<a href="r.univar.sh.html">r.univar.sh</a><BR>
-<a href="v.in.ascii.html">v.in.ascii</a><BR>
-<a href="v.out.ascii.html">v.out.ascii</a><BR>
+<a href="g.region.html">g.region</a><br>
+<a href="m.proj.html">m.proj</a><br>
+<a href="r.fillnulls.html">r.fillnulls</a><br>
+<a href="r.in.ascii.html">r.in.ascii</a><br>
+<a href="r.mapcalc.html">r.mapcalc</a><br>
+<a href="r.neighbors.html">r.neighbors</a><br>
+<a href="r.out.xyz.html">r.out.xyz</a><br>
+<a href="r.to.rast3.html">r.to.rast3</a><br>
+<a href="r.to.vect.html">r.to.vect</a><br>
+<a href="r.univar.html">r.univar</a><br>
+<a href="r.univar.sh.html">r.univar.sh</a><br>
+<a href="v.in.ascii.html">v.in.ascii</a><br>
+<a href="v.out.ascii.html">v.out.ascii</a><br>
<a href="v.surf.rst.html">v.surf.rst</a>
</i>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
-Hamish Bowman<BR> <i>
-Department of Marine Science<BR>
-University of Otago<BR>
-New Zealand</i><BR>
-<BR>
+Hamish Bowman<br> <i>
+Department of Marine Science<br>
+University of Otago<br>
+New Zealand</i><br>
+<br>
Extended by Volker Wichmann to support the aggregate functions
<i>median, percentile, skewness</i> and <i>trimmed mean</i>.
-<BR>
+<br>
<p>
<i>Last changed: $Date$</i></p>
Modified: grass/trunk/raster/r.info/description.html
===================================================================
--- grass/trunk/raster/r.info/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.info/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.info</EM> reports some basic information about a
+<em>r.info</em> reports some basic information about a
user-specified raster map layer. This map layer must exist
in the user's current mapset search path. Information
about the map's boundaries, resolution, projection, data
@@ -9,36 +9,36 @@
the timestamp and
history are put into a table and written to standard
output. The types of information listed can also be found
-in the <EM>cats</EM>, <EM>cellhd</EM>, and <EM>hist</EM>
+in the <em>cats</em>, <em>cellhd</em>, and <em>hist</em>
directories under the mapset in which the named map is
stored.
-<P>
+<p>
The user can save the tabular output to a file
by using the UNIX redirection mechanism (>); for example, the user
-might save a report on the <EM>soils</EM> map layer in a file called
-<EM>soil.rpt</EM> by typing:
-<DL>
-<DD>
-<B>r.info map=</B><EM>soils</EM> > <EM>soil.rpt</EM>
-</DL>
+might save a report on the <em>soils</em> map layer in a file called
+<em>soil.rpt</em> by typing:
+<dl>
+<dd>
+<b>r.info map=</b><em>soils</em> > <em>soil.rpt</em>
+</dl>
-<P>
-<H2>ACCURACY</H2>
+<p>
+<h2>ACCURACY</h2>
On large maps, the total number of cells in the map may not be displayed
with an accurate number. This is only cosmetic.
-<P>
+<p>
Some standards (ISO-C90) and compilers do not support the 'long long' type
as a 64-bit type. In the case that GRASS was built with such a compiler,
-an accuracy message may be displayed in the output of <EM>r.info</EM>
+an accuracy message may be displayed in the output of <em>r.info</em>
after Total Cells:.
-<P>
+<p>
-Below is the report produced by <EM>r.info</EM> for the raster map
-<EM>slope</EM> in the Spearfish sample data base.
+Below is the report produced by <em>r.info</em> for the raster map
+<em>slope</em> in the Spearfish sample data base.
-<PRE>
+<pre>
+----------------------------------------------------------------------------+
| Layer: slope Date: Mon Nov 5 10:55:57 2001 |
| Mapset: PERMANENT Login of Creator: neteler |
@@ -71,22 +71,22 @@
| min_slp_allowed = 0.000000 |
| |
+----------------------------------------------------------------------------+
-</PRE>
+</pre>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.mapsets.html">g.mapsets</A>,</EM>
-<EM><A HREF="r.coin.html">r.coin</A>,</EM>
-<EM><A HREF="r.describe.html">r.describe</A>,</EM>
-<EM><A HREF="r.report.html">r.report</A>,</EM>
-<EM><A HREF="r.stats.html">r.stats</A>,</EM>
-<EM><A HREF="r.support.html">r.support</A>,</EM>
-<EM><A HREF="r.univar.html">r.univar</A>,</EM>
-<EM><A HREF="r.what.html">r.what</A></EM>
+<em><a href="g.mapsets.html">g.mapsets</a>,</em>
+<em><a href="r.coin.html">r.coin</a>,</em>
+<em><a href="r.describe.html">r.describe</a>,</em>
+<em><a href="r.report.html">r.report</a>,</em>
+<em><a href="r.stats.html">r.stats</a>,</em>
+<em><a href="r.support.html">r.support</a>,</em>
+<em><a href="r.univar.html">r.univar</a>,</em>
+<em><a href="r.what.html">r.what</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael O'Shea,
-<A HREF="http://www.cecer.army.mil/">U.S. Army Construction Engineering Research Laboratory</A>
+<a href="http://www.cecer.army.mil/">U.S. Army Construction Engineering Research Laboratory</a>
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.kappa/description.html
===================================================================
--- grass/trunk/raster/r.kappa/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.kappa/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,28 +1,28 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.kappa</EM> tabulates the error matrix of classification result by
+<em>r.kappa</em> tabulates the error matrix of classification result by
crossing classified map layer with respect to reference map layer. Both
-overall <EM>kappa</EM> (accompanied by its <EM>variance</EM>) and
-conditional <EM>kappa</EM> values are calculated. This analysis program
+overall <em>kappa</em> (accompanied by its <em>variance</em>) and
+conditional <em>kappa</em> values are calculated. This analysis program
respects the current geographic region and mask settings.
-<P>
-<EM>r.kappa</EM> calculates the error matrix of the
+<p>
+<em>r.kappa</em> calculates the error matrix of the
two map layers and prepares the table from which the report
-is to be created. <EM>kappa</EM> values for overall and
+is to be created. <em>kappa</em> values for overall and
each classes are computed along with their variances. Also
percent of commission and ommission error, total correct
classified result by pixel counts, total area in pixel
counts and percentage of overall correctly classified
pixels are tabulated.
-<P>
+<p>
The report will be write to an output file which is in
plain text format and named by user at prompt of running
the program.
-<P>
+<p>
The body of the report is arranged in panels. The
classified result map layer categories is arranged along
the vertical axis of the table, while the reference map
@@ -36,30 +36,30 @@
representing the sum of all the rows in that column.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
It is recommended to reclassify categories of classified
result map layer into a more manageable number before
-running <EM>r.kappa</EM> on the classified raster map
-layer. Because <EM>r.kappa</EM> calculates and then reports
+running <em>r.kappa</em> on the classified raster map
+layer. Because <em>r.kappa</em> calculates and then reports
information for each and every category.
-<P>
+<p>
-<EM>NA</EM>'s in output file mean non-applicable in case
-<EM>MASK</EM> exists.
+<em>NA</em>'s in output file mean non-applicable in case
+<em>MASK</em> exists.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<!--<EM><A HREF="m.ipf.html">m.ipf</A></EM>,-->
-<EM><A HREF="r.category.html">r.category</A></EM>,
-<EM><A HREF="r.mask.html">r.mask</A></EM>,
-<EM><A HREF="r.reclass.html">r.reclass</A></EM>,
-<EM><A HREF="r.report.html">r.report</A></EM>,
-<EM><A HREF="r.stats.html">r.stats</A></EM>
+<em><a href="g.region.html">g.region</a></em>,
+<!--<em><a href="m.ipf.html">m.ipf</a></em>,-->
+<em><a href="r.category.html">r.category</a></em>,
+<em><a href="r.mask.html">r.mask</a></em>,
+<em><a href="r.reclass.html">r.reclass</a></em>,
+<em><a href="r.report.html">r.report</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Tao Wen, University of Illinois at Urbana-Champaign, Illinois
Modified: grass/trunk/raster/r.li/description.html
===================================================================
--- grass/trunk/raster/r.li/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.li/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -15,7 +15,7 @@
<h2>KEYWORDS</h2>
raster, landscape structure analysis, overview, landscape metrics, landscape pattern, landscape analysis
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
The <em>r.li</em> suite is a toolset for multiscale analysis of landscape structure.
It aims at replacing the <em>r.le</em> suite of modules through a client-server,
@@ -53,14 +53,14 @@
index using on the areas selected on configuration file.
</ol>
-<H2>NOTE</H2>
+<h2>NOTE</h2>
Also the <em>r.li.daemon</em> has a main function and it can be run, but it is only a
template for development of new indices.
<!-- mhh ??: -->
The function itself has no meaning, it can be used only for debug.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
To calculate a patch density index on a whole 'geology' raster map in the
Spearfish region, using a 5x5 moving window, follow this procedure:
@@ -115,7 +115,7 @@
configuration file on a 200x200 raster map, then the sample area is
10x10.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
<b>Core modules</b>:
<ul>
@@ -160,27 +160,27 @@
<li> <a href="r.li.simpson.html">r.li.simpson</a>: Calculates Simpson's diversity index on a raster map</li>
</ul>
-<H2>ADDING NEW INDICES</H2>
+<h2>ADDING NEW INDICES</h2>
New indices can be defined and implemented by any C programmer, without having to
deal with all basic functions (IO etc.). The computing architecture and the functions
are clearly separated, thus allowing an easy expandability. Every index is defined
separately, placed in a directory along with its Makefile for compiling it and a file
description.html which describes the index including a simple example of use.
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
analysis program for quantifying landscape structure. USDA For. Serv.
Gen. Tech. Rep. PNW-351 (<a href="http://www.fs.fed.us/pnw/pubs/gtr_351.pdf">PDF</a>).
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
<a href="mailto:porta at cli.di.unipi.it">Claudio Porta</a> and
<a href="mailto:spano at cli.di.unipi.it">Lucio Davide Spano</a>, students of Computer Science
University of Pisa (Italy). <br>
Commission from Faunalia Pontedera (PI)<br>
<p><i>Last changed: $Date$</i>
-<HR>
-<P><a href="index.html">Main index</a> - <a href="raster.html">raster index</a> - <a href="full_index.html">Full index</a>
+<hr>
+<p><a href="index.html">Main index</a> - <a href="raster.html">raster index</a> - <a href="full_index.html">Full index</a>
</body>
</html>
Modified: grass/trunk/raster/r.los/description.html
===================================================================
--- grass/trunk/raster/r.los/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.los/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.los</EM> generates a raster output map in which the cells that are
+<em>r.los</em> generates a raster output map in which the cells that are
visible from a user-specified observer position are marked with the
vertical angle (in degrees) required to see those cells (viewshed).
A value of 0 is directly below the specified viewing position,
@@ -9,58 +9,58 @@
The angle to the cell containing the viewing position is undefined
and set to 180.
-<P>
-To run <EM>r.los</EM>, the user must specify at least
-an <B>input</B> map name, <B>output</B> map name, and the geographic
-<B>coordinate</B>s of the user's viewing location;
+<p>
+To run <em>r.los</em>, the user must specify at least
+an <b>input</b> map name, <b>output</b> map name, and the geographic
+<b>coordinate</b>s of the user's viewing location;
any remaining parameters whose values are unspecified
will be set to their default values (see below).
-<P>
-The <B>patt_map</B> is the name of a binary (1/0) raster map layer in which
+<p>
+The <b>patt_map</b> is the name of a binary (1/0) raster map layer in which
cells within the areas of interest are assigned the category value '1', and
all other cells are assigned the category value '0' or NULL. If this parameter is
omitted, the analysis will be performed for the whole area within a certain
distance of the viewing point inside the geographic region boundaries.
-<BR>
-Default: assign all cells that are within the <B>max_dist</B> and within
+<br>
+Default: assign all cells that are within the <b>max_dist</b> and within
the user's current geographic region boundaries a value of 1.
-<P>
-The <B>obs_elev</B> parameter defines the height of the observer (in
+<p>
+The <b>obs_elev</b> parameter defines the height of the observer (in
meters) above the viewing point's elevation.
-<P>
+<p>
-The <B>max_dist</B> parameter is the maximum distance (in meters) from the
+The <b>max_dist</b> parameter is the maximum distance (in meters) from the
viewing point inside of which the line of sight analysis will be performed.
The cells outside this distance range are assigned a NULL value.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
For accurate results, the program must be run with the resolution of the
geographic region set equal to the resolution of the data
-(see <EM><A HREF="g.region.html">g.region</A></EM>).
+(see <em><a href="g.region.html">g.region</a></em>).
-<P>
+<p>
The time to complete the calculation increases dramatically with the region size.
Try to keep the columns and rows under 1000.
-<P>
+<p>
It is advisable to use a 'pattern layer' which identifies
the areas of interest in which the line of sight analysis
is required. Such a measure will reduce the time taken by
the program to run.
-<P>
+<p>
The curvature of the Earth is not taken into account for these calculations.
However, for interest's sake, a handy calculation for distance to the true horizon
is approximated by <i>d = sqrt(13*h)</i> where <i>h</i> is the height of the observer
in meters (above sea level) and <i>d</i> is the distance to the horizon in km.
-This may be useful for setting the <B>max_dist</B> value.
+This may be useful for setting the <b>max_dist</b> value.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
Spearfish example - calculation of viewshed from 50m tower
on top of a mountain:
@@ -72,22 +72,22 @@
echo "symbol extra/target 25 598869 4916642 red" | d.graph -m
</pre></div>
-<H2>TODO</H2>
+<h2>TODO</h2>
Rewrite using ideas from <em>r.cva</em> and a method which scales better
-to large regions.<BR>A suggested method is detailed in:<BR>
-Izraelevitz, David (USACE).<BR>
-'A Fast Algorithm for Approximate Viewshed Computation'<BR>
+to large regions.<br>A suggested method is detailed in:<br>
+Izraelevitz, David (USACE).<br>
+'A Fast Algorithm for Approximate Viewshed Computation'<br>
<i>Photogrammetric Engineering & Remote Sensing</i>, July 2003
<!-- http://article.gmane.org/gmane.comp.gis.grass.devel/1781
Post by Paul Kelly 2003-08-13 to grass-dev,
"Re: [bug #2061] (grass) r.los needs FP update" -->
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A></EM>
+<em><a href="g.region.html">g.region</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Kewan Q. Khawaja, Intelligent Engineering Systems Laboratory, M.I.T.
Modified: grass/trunk/raster/r.median/description.html
===================================================================
--- grass/trunk/raster/r.median/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.median/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,29 +1,29 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.median</EM> calculates the median category of data
-contained in a <B>cover</B> raster map layer for areas
+<em>r.median</em> calculates the median category of data
+contained in a <b>cover</b> raster map layer for areas
assigned the same category value in the user-specified
-<B>base</B> raster map layer. These median values are
-stored in the new <B>output</B> map layer.
+<b>base</b> raster map layer. These median values are
+stored in the new <b>output</b> map layer.
-<P>
-The <B>output</B> map is actually a <EM>reclass</EM> of the <B>base</B> map.
+<p>
+The <b>output</b> map is actually a <em>reclass</em> of the <b>base</b> map.
-The <B>base</B> map is an existing raster map layer in the user's current
+The <b>base</b> map is an existing raster map layer in the user's current
mapset search path. For each group of cells assigned the
-same category value in the <B>base</B> map, the median of
-the values assigned these cells in the <B>cover</B> map
+same category value in the <b>base</b> map, the median of
+the values assigned these cells in the <b>cover</b> map
will be computed.
-<P>
-The <B>cover</B> map is an existing raster map layer containing the values
-to be used to compute the median within each category of the <B>base</B> map.
+<p>
+The <b>cover</b> map is an existing raster map layer containing the values
+to be used to compute the median within each category of the <b>base</b> map.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-The user should use the results of <EM>r.median</EM> with
+The user should use the results of <em>r.median</em> with
care. Since this utility assigns a value to each cell
which is based on global information (i.e., information at
spatial locations other than just the location of the cell
@@ -31,10 +31,10 @@
geographic region and mask settings are the same as they
were at the time that the result map was created.
-<P>
+<p>
Results are affected by the current region settings and mask.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
Median K-factor (erosion) for Spearfish fields:
@@ -44,23 +44,23 @@
r.univar K.by.farm.median
</pre></div>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="r.average.html">r.average</A></EM>,
-<EM><A HREF="r.category.html">r.category</A></EM>,
-<EM><A HREF="r.clump.html">r.clump</A></EM>,
-<EM><A HREF="r.describe.html">r.describe</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.mfilter.html">r.mfilter</A></EM>,
-<EM><A HREF="r.mode.html">r.mode</A></EM>,
-<EM><A HREF="r.neighbors.html">r.neighbors</A></EM>,
-<EM><A HREF="r.reclass.html">r.reclass</A></EM>,
-<EM><A HREF="r.statistics.html">r.statistics</A></EM>,
-<EM><A HREF="r.stats.html">r.stats</A></EM>,
-<EM><A HREF="r.univar.html">r.univar</A></EM>
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.average.html">r.average</a></em>,
+<em><a href="r.category.html">r.category</a></em>,
+<em><a href="r.clump.html">r.clump</a></em>,
+<em><a href="r.describe.html">r.describe</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.mfilter.html">r.mfilter</a></em>,
+<em><a href="r.mode.html">r.mode</a></em>,
+<em><a href="r.neighbors.html">r.neighbors</a></em>,
+<em><a href="r.reclass.html">r.reclass</a></em>,
+<em><a href="r.statistics.html">r.statistics</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>,
+<em><a href="r.univar.html">r.univar</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro,
U.S.Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.mfilter/description.html
===================================================================
--- grass/trunk/raster/r.mfilter/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.mfilter/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,35 +1,35 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.mfilter</EM> filters the raster <EM>input</EM> to produce the
-raster <EM>output</EM> according to the matrix <EM>filter</EM> designed
-by the user (see <EM>FILTERS</EM> below).
-The filter is applied <EM>repeat</EM> times (default <EM>value</EM> is 1).
-The <EM>output</EM> raster map layer can be given a <EM>TITLE</EM> if desired.
+<em>r.mfilter</em> filters the raster <em>input</em> to produce the
+raster <em>output</em> according to the matrix <em>filter</em> designed
+by the user (see <em>FILTERS</em> below).
+The filter is applied <em>repeat</em> times (default <em>value</em> is 1).
+The <em>output</em> raster map layer can be given a <em>TITLE</em> if desired.
(This TITLE should be put in quotes if it contains more than one word.)
-With <B>-z</B> flag the filter is applied only to zero category values in
+With <b>-z</b> flag the filter is applied only to zero category values in
the input raster map layer. The non-zero category values are not changed.
Note that if there is more than one filter step, this rule is applied to the
intermediate raster map layer -- only zero category values which result from
the first filter will be changed. In most cases this will NOT be the
desired result. Hence -z should be used only with single step filters.
-<P>
+<p>
-The <B>filter</B> parameter defines the name of an existing, user-created
+The <b>filter</b> parameter defines the name of an existing, user-created
UNIX ASCII file whose contents is a matrix defining the way in which the
-<EM>input</EM> file will be filtered. The format of this file is described
+<em>input</em> file will be filtered. The format of this file is described
below, under FILTERS.
-<P>
+<p>
-The <B>repeat</B> parameter defines the number of times the <EM>filter</EM>
-is to be applied to the <EM>input</EM> data.
+The <b>repeat</b> parameter defines the number of times the <em>filter</em>
+is to be applied to the <em>input</em> data.
-<H2>FILTERS</H2>
+<h2>FILTERS</h2>
-The <EM>filter</EM> file is a normal UNIX ASCII file designed by the user.
+The <em>filter</em> file is a normal UNIX ASCII file designed by the user.
It has the following format:
-<PRE>
+<pre>
TITLE TITLE
MATRIX n
.
@@ -37,37 +37,37 @@
.
DIVISOR d
TYPE S/P
-</PRE>
+</pre>
-<DT>TITLE
+<dt>TITLE
-<DD>A one-line TITLE for the filter.
+<dd>A one-line TITLE for the filter.
If a TITLE was not specified on the command line, it can be specified here.
This TITLE would be used to construct a TITLE for the resulting raster map
layer. It should be a one-line description of the filter.
-<DT>MATRIX
+<dt>MATRIX
-<DD>The matrix (n x n) follows on the next n lines. <EM>n</EM> must be
+<dd>The matrix (n x n) follows on the next n lines. <em>n</em> must be
an odd integer greater than or equal to 3.
The matrix itself consists of n rows of n integers.
The integers must be separated from each other by at least 1 blank.
-<DT>DIVISOR
+<dt>DIVISOR
-<DD>The filter divisor is <EM>d</EM>. If not specified, the default is 1.
+<dd>The filter divisor is <em>d</em>. If not specified, the default is 1.
If the divisor is zero (0), then the divisor is dependent on the
category values in the neighborhood
(see HOW THE FILTER WORKS below).
-<DT>TYPE
+<dt>TYPE
-<DD>The filter type. <EM>S</EM> means sequential, while <EM>P</EM> mean parallel.
+<dd>The filter type. <em>S</em> means sequential, while <em>P</em> mean parallel.
If not specified, the default is S.
-<P>
+<p>
Sequential filtering happens in place. As the filter is applied to the
raster map layer, the category values that were changed in neighboring
@@ -75,23 +75,23 @@
cell being filtered.
-<P>
+<p>
Parallel filtering happens in such a way that the original raster
map layer category values are used to produce the new category value.
-<P>
+<p>
More than one filter may be specified in the filter file.
The additional filter(s) are described just like the first.
For example, the following describes two filters:
-</P>
+</p>
-</DD>
+</dd>
-<H2>EXAMPLE FILTER FILE</H2>
+<h2>EXAMPLE FILTER FILE</h2>
-<PRE>
+<pre>
TITLE 3x3 average, non-zero data only, followed by 5x5 average
MATRIX 3
1 1 1
@@ -108,9 +108,9 @@
1 1 1 1 1
DIVISOR 25
TYPE P
-</PRE>
+</pre>
-<H2>HOW THE FILTER WORKS</H2>
+<h2>HOW THE FILTER WORKS</h2>
The filter process produces a new category value for each cell
in the input raster map layer by multiplying the category values of the
@@ -123,7 +123,7 @@
values where the corresponding input cell is non-zero.)
-<P>
+<p>
If more than one filter step is specified, either because the
repeat value was greater than one or because the filter file
@@ -134,20 +134,20 @@
produce another intermediate result; and so on, until the
final filter is applied. Then the output cell is written.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
If the resolution of the geographic region does not agree with the
resolution of the raster map layer, unintended resampling of the original
data may occur. The user should be sure that the geographic region
is set properly.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="r.clump.html">r.clump</A></EM>,
-<EM><A HREF="r.neighbors.html">r.neighbors</A></EM>
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.clump.html">r.clump</a></em>,
+<em><a href="r.neighbors.html">r.neighbors</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro,
U.S.Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.mfilter.fp/description.html
===================================================================
--- grass/trunk/raster/r.mfilter.fp/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.mfilter.fp/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,35 +1,35 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.mfilter.fp</EM> filters the raster <EM>input</EM> to produce the
-raster <EM>output</EM> according to the matrix <EM>filter</EM> designed
-by the user (see <EM>FILTERS</EM> below).
-The filter is applied <EM>repeat</EM> times (default <EM>value</EM> is 1).
-The <EM>output</EM> raster map layer can be given a <EM>TITLE</EM> if desired.
+<em>r.mfilter.fp</em> filters the raster <em>input</em> to produce the
+raster <em>output</em> according to the matrix <em>filter</em> designed
+by the user (see <em>FILTERS</em> below).
+The filter is applied <em>repeat</em> times (default <em>value</em> is 1).
+The <em>output</em> raster map layer can be given a <em>TITLE</em> if desired.
(This TITLE should be put in quotes if it contains more than one word.)
-With <B>-z</B> flag the filter is applied only to null values in
+With <b>-z</b> flag the filter is applied only to null values in
the input raster map layer. The non-null category values are not changed.
Note that if there is more than one filter step, this rule is applied to the
intermediate raster map layer -- only null category values which result from
the first filter will be changed. In most cases this will NOT be the
desired result. Hence -z should be used only with single step filters.
-<P>
+<p>
-The <B>filter</B> parameter defines the name of an existing, user-created
+The <b>filter</b> parameter defines the name of an existing, user-created
UNIX ASCII file whose contents is a matrix defining the way in which the
-<EM>input</EM> file will be filtered. The format of this file is described
+<em>input</em> file will be filtered. The format of this file is described
below, under FILTERS.
-<P>
+<p>
-The <B>repeat</B> parameter defines the number of times the <EM>filter</EM>
-is to be applied to the <EM>input</EM> data.
+The <b>repeat</b> parameter defines the number of times the <em>filter</em>
+is to be applied to the <em>input</em> data.
-<H2>FILTERS</H2>
+<h2>FILTERS</h2>
-The <EM>filter</EM> file is a normal UNIX ASCII file designed by the user.
+The <em>filter</em> file is a normal UNIX ASCII file designed by the user.
It has the following format:
-<PRE>
+<pre>
TITLE TITLE
MATRIX n
.
@@ -37,37 +37,37 @@
.
DIVISOR d
TYPE S/P
-</PRE>
+</pre>
-<DT>TITLE
+<dt>TITLE
-<DD>A one-line TITLE for the filter.
+<dd>A one-line TITLE for the filter.
If a TITLE was not specified on the command line, it can be specified here.
This TITLE would be used to construct a TITLE for the resulting raster map
layer. It should be a one-line description of the filter.
-<DT>MATRIX
+<dt>MATRIX
-<DD>The matrix (n x n) follows on the next n lines. <EM>n</EM> must be
+<dd>The matrix (n x n) follows on the next n lines. <em>n</em> must be
an odd integer greater than or equal to 3.
The matrix itself consists of n rows of n values.
The values must be separated from each other by at least 1 blank.
-<DT>DIVISOR
+<dt>DIVISOR
-<DD>The filter divisor is <EM>d</EM>. If not specified, the default is 1.
+<dd>The filter divisor is <em>d</em>. If not specified, the default is 1.
If the divisor is zero (0), then the divisor is dependent on the
category values in the neighborhood
(see HOW THE FILTER WORKS below).
-<DT>TYPE
+<dt>TYPE
-<DD>The filter type. <EM>S</EM> means sequential, while <EM>P</EM> mean parallel.
+<dd>The filter type. <em>S</em> means sequential, while <em>P</em> mean parallel.
If not specified, the default is S.
-<P>
+<p>
Sequential filtering happens in place. As the filter is applied to the
raster map layer, the category values that were changed in neighboring
@@ -75,23 +75,23 @@
cell being filtered.
-<P>
+<p>
Parallel filtering happens in such a way that the original raster
map layer category values are used to produce the new category value.
-<P>
+<p>
More than one filter may be specified in the filter file.
The additional filter(s) are described just like the first.
For example, the following describes two filters:
-</P>
+</p>
-</DD>
+</dd>
-<H2>EXAMPLE FILTER FILE</H2>
+<h2>EXAMPLE FILTER FILE</h2>
-<PRE>
+<pre>
TITLE 3x3 average, non-null data only, followed by 5x5 average
MATRIX 3
1 1 1
@@ -108,9 +108,9 @@
1 1 1 1 1
DIVISOR 25
TYPE P
-</PRE>
+</pre>
-<H2>HOW THE FILTER WORKS</H2>
+<h2>HOW THE FILTER WORKS</h2>
The filter process produces a new category value for each cell
in the input raster map layer by multiplying the category values of the
@@ -122,7 +122,7 @@
values where the corresponding input cell is non-null.)
-<P>
+<p>
If more than one filter step is specified, either because the
repeat value was greater than one or because the filter file
@@ -133,21 +133,21 @@
produce another intermediate result; and so on, until the
final filter is applied. Then the output cell is written.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
If the resolution of the geographic region does not agree with the
resolution of the raster map layer, unintended resampling of the original
data may occur. The user should be sure that the geographic region
is set properly.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="r.clump.html">r.clump</A></EM>,
-<EM><A HREF="r.neighbors.html">r.neighbors</A></EM>
-<EM><A HREF="r.mfilter.html">r.mfilter</A></EM>
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.clump.html">r.clump</a></em>,
+<em><a href="r.neighbors.html">r.neighbors</a></em>
+<em><a href="r.mfilter.html">r.mfilter</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Glynn Clements.
Based upon r.mfilter, by Michael Shapiro,
Modified: grass/trunk/raster/r.mode/description.html
===================================================================
--- grass/trunk/raster/r.mode/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.mode/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,38 +1,38 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.mode</EM> calculates the most frequently occurring value (i. e., mode)
-of data contained in a <EM>cover</EM> raster map layer for areas assigned
-the same category value in the user-specified <EM>base</EM> raster map
-layer. These modes are stored in the new <EM>output</EM> map layer.
+<em>r.mode</em> calculates the most frequently occurring value (i. e., mode)
+of data contained in a <em>cover</em> raster map layer for areas assigned
+the same category value in the user-specified <em>base</em> raster map
+layer. These modes are stored in the new <em>output</em> map layer.
-<P>
-The <EM>output</EM> map is actually a <EM>reclass</EM> of the <EM>base</EM>
+<p>
+The <em>output</em> map is actually a <em>reclass</em> of the <em>base</em>
map.
-<P>
-The <B>base</B> parameter defines an existing raster map layer in the user's
+<p>
+The <b>base</b> parameter defines an existing raster map layer in the user's
current mapset search path. For each group of cells assigned the same
-category value in the <EM>base</EM> map, the mode of the values assigned
-these cells in the <EM>cover</EM> map will be computed.
+category value in the <em>base</em> map, the mode of the values assigned
+these cells in the <em>cover</em> map will be computed.
-<P>
-The <B>cover</B> parameter defines an existing raster map layer containing
+<p>
+The <b>cover</b> parameter defines an existing raster map layer containing
the values to be used to compute the mode within each category of the
-<EM>base</EM> map.
+<em>base</em> map.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-The user should use the results of <EM>r.mode</EM> with care.
+The user should use the results of <em>r.mode</em> with care.
Since this utility assigns a value to each
cell which is based on global information (i.e., information at spatial
locations other than just the location of the cell itself), the resultant
map layer is only valid if the geographic region and mask settings are
the same as they were at the time that the result map was created.
-<P>
+<p>
Results are affected by the current region settings and mask.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
Mode of K-factor (erosion) for Spearfish fields:
@@ -42,7 +42,7 @@
r.univar K.by.farm.mode
</pre></div>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
<em><a href="g.region.html">g.region</a></em>,
<em><a href="r.average.html">r.average</a></em>,
@@ -55,11 +55,11 @@
<em><a href="r.neighbors.html">r.neighbors</a></em>,
<em><a href="r.reclass.html">r.reclass</a></em>,
<em><a href="r.stats.html">r.stats</a></em>,
-<em><A HREF="r.statistics.html">r.statistics</a></em>,
-<em><A HREF="r.univar.html">r.univar</a></em>
+<em><a href="r.statistics.html">r.statistics</a></em>,
+<em><a href="r.univar.html">r.univar</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro,
U.S.Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.null/description.html
===================================================================
--- grass/trunk/raster/r.null/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.null/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,11 +1,11 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-The function of <EM>r.null</EM> is to explicitly create the NULL-value
+The function of <em>r.null</em> is to explicitly create the NULL-value
bitmap file. The intended usage is to fix "old" maps that don't have a
NULL-value bitmap file (i.e. to indicate if zero is valid value or is to be
converted to NULL). The module does not work with reclassified maps.
-<P>
+<p>
The design is flexible. Ranges of values can be set to NULL and/or the NULL
value can be eliminated and replace with a specified value.
@@ -15,7 +15,7 @@
be set to NULL. A range is either a single value (e.g., 5.3), or a pair of
values (e.g., 4.76-34.56). Existing NULL-values are left NULL, unless the
null argument is requested.
-<P>
+<p>
The <b>null</b> parameter eliminates the NULL value and replaces it with
value. This argument is applied only to existing NULL values, and not to the
@@ -33,7 +33,7 @@
</pre></div>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
Note that value is restricted to integer if the map is an integer map.
<p>
@@ -50,13 +50,13 @@
</pre></div>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.support.html">r.support</A></EM>
+<em><a href="r.support.html">r.support</a></em>
and
-<EM><A HREF="r.quant.html">r.quant</A></EM>
+<em><a href="r.quant.html">r.quant</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
U.S.Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.out.arc/description.html
===================================================================
--- grass/trunk/raster/r.out.arc/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.arc/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,55 +1,55 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.out.arc</EM> converts a user-specified raster map layer
-(<B>input=</B><EM>name</EM>) into an ESRI ARC-GRID ascii file
-(<B>output=</B><EM>name</EM>) suitable for export to other computer systems.
-The dp=<EM>value</EM> option (where <EM>value</EM> is a number of the user's
+<em>r.out.arc</em> converts a user-specified raster map layer
+(<b>input=</b><em>name</em>) into an ESRI ARC-GRID ascii file
+(<b>output=</b><em>name</em>) suitable for export to other computer systems.
+The dp=<em>value</em> option (where <em>value</em> is a number of the user's
choice) can be used to request that numbers after decimal points are
limited. However, to use this, the user should know the maximum number of
digits that will occur in the output file. The user can find the maximum
-number of digits occurring in the output file by running <EM>r.out.arc</EM>
-without the <B>dp=</B><EM>value</EM> option.
+number of digits occurring in the output file by running <em>r.out.arc</em>
+without the <b>dp=</b><em>value</em> option.
-<P>
+<p>
-The GRASS program <EM><A HREF="r.in.arc.html">r.in.arc</A></EM> can be used
+The GRASS program <em><a href="r.in.arc.html">r.in.arc</a></em> can be used
to perform the reverse function, converting an ESRI ARC-GRID ascii file in
suitable format to GRASS raster map format. The order of cell values in
file is from lower left to upper right (reverse to GRASS).
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-The output from <EM>r.out.arc</EM> may also be placed into a file
+The output from <em>r.out.arc</em> may also be placed into a file
by using the UNIX redirection mechanism; e.g.:
<div class="code"><pre>
r.out.arc input=soils output=- > out.grd
</pre></div>
-The output file <EM>out.grd</EM> can then be copied
+The output file <em>out.grd</em> can then be copied
onto a CDROM or floppy disk for export purposes.
-<P><BR>
-An Arc ASCII grid can be loaded into ArcGIS 8.3 though ArcToolbox.<BR>
+<p><br>
+An Arc ASCII grid can be loaded into ArcGIS 8.3 though ArcToolbox.<br>
Use the "Import to Raster" -> "ASCII to Grid" tool to create a binary grid
which can be selected using ArcCatalog. The spatial analyst extension may
need to be installed and activated within Arc.
-<P>
-In ArcGIS 9.0 the import tool can be found at:<BR>
+<p>
+In ArcGIS 9.0 the import tool can be found at:<br>
ArcMap -> Toolbox -> Conversion Tools -> To Raster -> ASCII to Raster
-<P>
-A GeoTIFF created with <EM><A HREF="r.out.gdal.html">r.out.gdal</A></EM> is
+<p>
+A GeoTIFF created with <em><a href="r.out.gdal.html">r.out.gdal</a></em> is
sometimes a better solution for transferring raster maps to other GIS software.
-<P>
-<H2>SEE ALSO</H2>
+<p>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.in.arc.html">r.in.arc</A></EM><BR>
-<EM><A HREF="r.out.gdal.html">r.out.gdal</A></EM><BR>
+<em><a href="r.in.arc.html">r.in.arc</a></em><br>
+<em><a href="r.out.gdal.html">r.out.gdal</a></em><br>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Markus Neteler, University of Hannover, Germany, <br>
based on r.out.ascii written by <br>
Modified: grass/trunk/raster/r.out.ascii/description.html
===================================================================
--- grass/trunk/raster/r.out.ascii/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.ascii/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,23 +1,23 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.out.ascii</EM> converts a user-specified raster map layer
-(<B>input=</B><EM>name</EM>) into an ASCII grid in a text file
-(<B>output=</B><EM>name</EM>) suitable for export to
+<em>r.out.ascii</em> converts a user-specified raster map layer
+(<b>input=</b><em>name</em>) into an ASCII grid in a text file
+(<b>output=</b><em>name</em>) suitable for export to
other computer systems.
-<P>
+<p>
-The GRASS program <EM><A HREF="r.in.ascii.html">r.in.ascii</A></EM> can be
+The GRASS program <em><a href="r.in.ascii.html">r.in.ascii</a></em> can be
used to perform the reverse function, converting an ASCII file in suitable
format to GRASS raster map format.
-<P>
-<!--With <B>-s</B> flag SURFER .grd ASCII GRID instead of GRASS ASCII GRID is
+<p>
+<!--With <b>-s</b> flag SURFER .grd ASCII GRID instead of GRASS ASCII GRID is
written (with reverted row order, different header).
-<P>
-With <B>-m</B> flag MODFLOW (USGS) free-format array instead of GRASS ASCII
+<p>
+With <b>-m</b> flag MODFLOW (USGS) free-format array instead of GRASS ASCII
GRID is written.-->
-<P>
+<p>
To write a SURFER .grd ASCII GRID file (with reverted row order and different
header) use the <em>-s</em> flag:
@@ -28,9 +28,9 @@
NULL data are coded to "1.70141e+038" for SURFER ASCII GRID files (ignoring
the <em>null=</em> parameter).
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-The output from <EM>r.out.ascii</EM> may be placed into a file by using the
+The output from <em>r.out.ascii</em> may be placed into a file by using the
UNIX redirection mechanism; e.g.:
<div class="code"><pre>
@@ -39,21 +39,21 @@
The output file out.file can then be printed or copied onto a CDROM
or floppy disk for export purposes.
-<P>
+<p>
To export the raster values as x,y,z values of cell centers (one per line)
-use the <em><A HREF="r.out.xyz.html">r.out.xyz</A></em> module.
+use the <em><a href="r.out.xyz.html">r.out.xyz</a></em> module.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="r.in.ascii.html">r.in.ascii</A>,
-<A HREF="r.in.arc.html">r.in.arc</A>,
-<A HREF="r.out.bin.html">r.out.bin</A>,
-<A HREF="r.out.gdal.html">r.out.gdal</A>,
-<A HREF="r.out.xyz.html">r.out.xyz</A>
-</EM>
+<em>
+<a href="r.in.ascii.html">r.in.ascii</a>,
+<a href="r.in.arc.html">r.in.arc</a>,
+<a href="r.out.bin.html">r.out.bin</a>,
+<a href="r.out.gdal.html">r.out.gdal</a>,
+<a href="r.out.xyz.html">r.out.xyz</a>
+</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro,
U.S. Army Construction Engineering Research Laboratory
<p>
Modified: grass/trunk/raster/r.out.bin/description.html
===================================================================
--- grass/trunk/raster/r.out.bin/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.bin/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,12 +1,12 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-The <EM>r.out.bin</EM> program exports a GRASS raster map to a binary array
+The <em>r.out.bin</em> program exports a GRASS raster map to a binary array
file. Optionally, output can be sent to standard output (stdout) for direct
input (pipe) into other applications. Data is exported according to the
original GRASS raster type (e.g. float). If the "-i" flag is specified, an
integer array is output. The region parameters are printed to stderr.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
With the -h flag, data can be directly used by
<a href=http://gmt.soest.hawaii.edu/>GMT</a> as Grid Format 1 (float) or
@@ -17,7 +17,7 @@
grdinfo new.grd=1 (if float)
</pre></div>
-<P>
+<p>
Exported data can be piped directly into the GMT program xyz2grd.
<div class="code"><pre>
r.out.bin input=grass.raster output=- | xyz2grd -R.... -ZTLf -
@@ -26,18 +26,18 @@
The example uses the GMT program xyz2grd with the -ZTLf flag indicating that
a float array was output.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.in.bin.html">r.in.bin</A>,
-<A HREF="r.in.ascii.html">r.in.ascii</A>
-<A HREF="r.out.ascii.html">r.out.ascii</A>
-<A HREF="r.in.arc.html">r.in.arc</A>,
-<A HREF="r.out.arc.html">r.out.arc</A></EM>
+<em><a href="r.in.bin.html">r.in.bin</a>,
+<a href="r.in.ascii.html">r.in.ascii</a>
+<a href="r.out.ascii.html">r.out.ascii</a>
+<a href="r.in.arc.html">r.in.arc</a>,
+<a href="r.out.arc.html">r.out.arc</a></em>
-<H2>AUTHOR</H2>
-This program is derived from <EM><A HREF="r.out.ascii.html">r.out.ascii</A></EM>
-with a few modifications. <BR>
-Author: <A HREF=mailto:bcovill at tekmap.ns.ca>Bob Covill</A>
+<h2>AUTHOR</h2>
+This program is derived from <em><a href="r.out.ascii.html">r.out.ascii</a></em>
+with a few modifications. <br>
+Author: <a href=mailto:bcovill at tekmap.ns.ca>Bob Covill</a>
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.out.gdal/description.html
===================================================================
--- grass/trunk/raster/r.out.gdal/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.gdal/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,22 +1,22 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.out.gdal</EM> allows a user to export a GRASS raster map layer
+<em>r.out.gdal</em> allows a user to export a GRASS raster map layer
into any GDAL supported raster map format.
For possible <em>metaopt</em> parameters see the 'supported formats' pages
of GDAL.
The <em>createopt</em> may be used to create TFW or World files ("TFW=YES",
"WORLDFILE=ON").
-<P>
-<EM>r.out.gdal</EM> also supports the export of multiband rasters through
-a group (created e.g. with <EM>i.group</EM>), when the group's name is entered
+<p>
+<em>r.out.gdal</em> also supports the export of multiband rasters through
+a group (created e.g. with <em>i.group</em>), when the group's name is entered
as input.
-<H2>SUPPORTED RASTER FORMATS</H2>
+<h2>SUPPORTED RASTER FORMATS</h2>
The set of <a href="http://www.gdal.org/formats_list.html">supported
-raster formats</a> written by <EM>r.out.gdal</EM> depends on the
-local GDAL installation. Available may be (incomplete list):<P>
+raster formats</a> written by <em>r.out.gdal</em> depends on the
+local GDAL installation. Available may be (incomplete list):<p>
<pre>
AAIGrid: Arc/Info ASCII Grid
@@ -44,12 +44,12 @@
XPM: X11 PixMap Format
</pre>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
When writing out GeoTIFF format for users of ESRI software or ImageMagick,
the band interleaving should be switched to pixel interleaving using
<em>createopt="INTERLEAVE=PIXEL"</em>.
-<P>
+<p>
To specify multiple options use a comma separated list
(<em>createopt="TFW=YES,COMPRESS=DEFLATE"</em>).
<p>
@@ -67,7 +67,7 @@
<em><a href="http://en.wikipedia.org/wiki/C_syntax#Typical_boundaries_of_primitive_integral_types">Typical boundaries of primitive integral types</a></em>
for details.
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
<h4>Export the integer raster roads map to GeoTIFF format:</h4>
<div class="code"><pre>
@@ -96,7 +96,7 @@
</pre></div>
-<H2>GDAL RELATED ERROR MESSAGES</H2>
+<h2>GDAL RELATED ERROR MESSAGES</h2>
<ul>
<li> "ERROR 6: SetColorInterpretation() not supported for this dataset.": This <i>may</i>
@@ -109,30 +109,30 @@
</ul>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
The <a href="http://www.gdal.org/formats_list.html">GDAL supported formats</a>
page.
-<BR>
-<EM>
-<A HREF="r.out.ascii.html">r.out.ascii</A>,
-<A HREF="r.out.arc.html">r.out.arc</A>,
-<A HREF="r.out.bin.html">r.out.bin</A>,
-<A HREF="r.out.mat.html">r.out.mat</A>,
-<A HREF="r.out.png.html">r.out.png</A>,
-<A HREF="r.out.ppm.html">r.out.ppm</A>,
-<A HREF="r.out.tiff.html">r.out.tiff</A>
-<BR>
-<A HREF="r.out.gdal.sh.html">r.out.gdal.sh</A></EM>
+<br>
+<em>
+<a href="r.out.ascii.html">r.out.ascii</a>,
+<a href="r.out.arc.html">r.out.arc</a>,
+<a href="r.out.bin.html">r.out.bin</a>,
+<a href="r.out.mat.html">r.out.mat</a>,
+<a href="r.out.png.html">r.out.png</a>,
+<a href="r.out.ppm.html">r.out.ppm</a>,
+<a href="r.out.tiff.html">r.out.tiff</a>
+<br>
+<a href="r.out.gdal.sh.html">r.out.gdal.sh</a></em>
(old shell script version using <tt>gdal_translate</tt>)
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
GDAL Pages: <a href="http://www.gdal.org">http://www.gdal.org</a>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Vytautas Vebra (oliver4grass at gmail.com)
Modified: grass/trunk/raster/r.out.gridatb/description.html
===================================================================
--- grass/trunk/raster/r.out.gridatb/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.gridatb/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,15 +1,15 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.out.gridatb</EM> exports a GRASS raster map to GRIDATB.FOR map file
+<em>r.out.gridatb</em> exports a GRASS raster map to GRIDATB.FOR map file
(TOPMODEL)
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.topmodel.html">r.topmodel</A>,</EM>
-<EM><A HREF="r.in.gridatb.html">r.in.gridatb</A></EM>
+<em><a href="r.topmodel.html">r.topmodel</a>,</em>
+<em><a href="r.in.gridatb.html">r.in.gridatb</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Huidae Cho based on code from Keith Beven
Modified: grass/trunk/raster/r.out.mat/description.html
===================================================================
--- grass/trunk/raster/r.out.mat/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.mat/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,11 +1,11 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.out.mat</EM> will export a GRASS raster map to a MAT-File which can
+<em>r.out.mat</em> will export a GRASS raster map to a MAT-File which can
be loaded into Matlab or Octave for plotting or further analysis.
Attributes such as map title and bounds will also be exported into
-additional array variables.<BR>
-<BR>
-Specifically, the following array variables are created:<BR>
+additional array variables.<br>
+<br>
+Specifically, the following array variables are created:<br>
<ul>
<li><b> map_data</b>
<li><b> map_name</b>
@@ -16,20 +16,20 @@
<li><b> map_western_edge</b>
</ul>
-<BR>
-In addition, <EM>r.out.mat</EM> makes for a nice binary container format
+<br>
+In addition, <em>r.out.mat</em> makes for a nice binary container format
for transferring georeferenced maps around, even if you don't use Matlab
or Octave.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-<EM>r.out.mat</EM> exports a Version 4 MAT-File. These files should
+<em>r.out.mat</em> exports a Version 4 MAT-File. These files should
successfully load into more modern versions of Matlab and Octave
-without any problems.<BR><BR>
+without any problems.<br><br>
Everything should be Endian safe, so the resultant file can be simply
copied between different system architectures without binary translation.
-<BR><BR>
+<br><br>
As there is no IEEE value for <tt>NaN</tt> for integer maps, GRASS's null
value is used to represent it within these maps. You'll have to do something
@@ -38,12 +38,12 @@
Null values in maps containing either floating point or double-precision
floating point data should translate into <tt>NaN</tt> values as expected.
-<BR><BR>
+<br><br>
-<EM>r.out.mat</EM> must load the entire map into memory before writing,
+<em>r.out.mat</em> must load the entire map into memory before writing,
therefore it might have problems with <i>huge</i> maps.
-(a 3000x4000 DCELL map uses about 100mb RAM)<BR><BR>
+(a 3000x4000 DCELL map uses about 100mb RAM)<br><br>
GRASS defines its map bounds at the outer-edge of the bounding cells, not at
the coordinates of their centroids. Thus, the following Matlab commands may
@@ -55,9 +55,9 @@
ns_res = y_range/rows
ew_res = x_range/cols
</pre></div>
-<BR>
+<br>
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
In Matlab, plot with either:
<div class="code"><pre>
@@ -69,31 +69,31 @@
contourf(map_data, 24), axis ij, axis equal, axis tight, colorbar
</pre></div>
-<BR>
+<br>
-<H2>TODO</H2>
+<h2>TODO</h2>
Add support for exporting map history, category information, color map, etc.
-<BR>
+<br>
Option to export as a version 5 MAT-File, with map and support information
stored in a single structured array.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
<i>
-<a href="r.in.mat.html">r.in.mat</a><BR>
-<a href="r.out.ascii.html">r.out.ascii</a>, <a href="r.out.bin.html">r.out.bin</a><BR>
-<a href="r.null.html">r.null</a><BR>
+<a href="r.in.mat.html">r.in.mat</a><br>
+<a href="r.out.ascii.html">r.out.ascii</a>, <a href="r.out.bin.html">r.out.bin</a><br>
+<a href="r.null.html">r.null</a><br>
The <a href="http://www.octave.org">Octave</a> project
</i>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
-Hamish Bowman<BR> <i>
-Department of Marine Science<BR>
-University of Otago<BR>
-New Zealand</i><BR>
+Hamish Bowman<br> <i>
+Department of Marine Science<br>
+University of Otago<br>
+New Zealand</i><br>
-<BR>
+<br>
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.out.mpeg/description.html
===================================================================
--- grass/trunk/raster/r.out.mpeg/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.mpeg/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.out.mpeg</EM> is a tool for combining a series of GRASS raster maps
+<em>r.out.mpeg</em> is a tool for combining a series of GRASS raster maps
into a single MPEG-1 (Motion Pictures Expert Group) format file. MPEG-1 is
a "lossy" video compression format, so the quality of each resulting frame
of the animation will be much diminished from the original raster image.
@@ -8,7 +8,7 @@
viewing program.
MPEG-2 and MPEG-4 provide much better quality animations.
-<P>
+<p>
The user may define up to four "views", or sub-windows, to animate
simultaneously. e.g., View 1 could be rainfall, View 2 flooded areas, View
3 damage to bridges or levees, View 4 other economic damage, all animated as
@@ -18,7 +18,7 @@
tmp space could also limit the number of frames you are able to convert.
<!-- flag to keep these to feed into another more modern encoder? -->
-<P>
+<p>
The environment variable GMPEG_SIZE is checked for a value to use as the
dimension, in pixels, of the longest dimension of the animation image. If
GMPEG_SIZE is not set, the animation size defaults to the rows & columns
@@ -29,7 +29,7 @@
compressed data "on-the-fly", therefore smaller dimensioned animations will
provide higher frame rates and smoother animations.
-<P>
+<p>
UNIX - style wild cards may be used with the command line version in place
of a raster map name, but wild cards must be quoted.
@@ -38,26 +38,26 @@
r.out.mpeg view1="rain[1-9]","rain1[0-2]" view2="temp*"
</pre></div>
-<P>
+<p>
If the number of files differs for each view, the view with the fewest files
will determine the number of frames in the animation.
-<P>
-With <B>-c</B> flag the module converts "on the fly", uses less disk space
-by using <EM>r.out.ppm</EM> with stdout option to convert frames as needed
+<p>
+With <b>-c</b> flag the module converts "on the fly", uses less disk space
+by using <em>r.out.ppm</em> with stdout option to convert frames as needed
instead of converting all frames to ppm before encoding. Only use when
encoding a single view. Use of this option also overrides any size
-defaults, using the <B>CURRENTLY DEFINED GRASS REGION for the output size</B>.
+defaults, using the <b>CURRENTLY DEFINED GRASS REGION for the output size</b>.
So be careful to set region to a reasonable size prior to encoding.
-<P>
-A quality value of <EM>qual=1</EM> will yield higher quality images, but
+<p>
+A quality value of <em>qual=1</em> will yield higher quality images, but
with less compression (larger MPEG file size). Compression ratios will vary
depending on the number of frames in the animation, but an MPEG produced
-using <EM>qual=5</EM> will usually be about 60% the size of the MPEG
-produced using <EM>qual=1</EM>.
+using <em>qual=5</em> will usually be about 60% the size of the MPEG
+produced using <em>qual=1</em>.
-<H2>BUGS</H2>
+<h2>BUGS</h2>
MPEG images must be 16-pixel aligned for successful compression, so if the
rows & columns of the calculated image size (scaled, with borders added)
are not evenly divisible by 16, a few rows/columns will be cut off the
@@ -65,21 +65,21 @@
recognize image MOTION, so abrupt changes from one frame to another will
cause a "noisy" encoding.
-<H2>NOTES</H2>
-This program requires the program <EM>mpeg_encode</EM> (aka <EM>ppmtompeg</EM>):
-<P>
-MPEG-1 Video Software Encoder<BR>
+<h2>NOTES</h2>
+This program requires the program <em>mpeg_encode</em> (aka <em>ppmtompeg</em>):
+<p>
+MPEG-1 Video Software Encoder<br>
(Version 1.3; March 14, 1994)
-<P>
+<p>
Lawrence A. Rowe, Kevin Gong, Ketan Patel, and Dan Wallach Computer Science
-Division-EECS, <DD>Univ. of Calif. at Berkeley</DD>
-<P>
+Division-EECS, <dd>Univ. of Calif. at Berkeley</dd>
+<p>
Available from Berkeley:
<a href="http://bmrc.berkeley.edu/frame/research/mpeg/mpeg_encode.html">http://bmrc.berkeley.edu/frame/research/mpeg/mpeg_encode.html</a>
-<BR>or as part of the netpbm package (<em>ppmtompeg</em>):
+<br>or as part of the netpbm package (<em>ppmtompeg</em>):
<a href="http://netpbm.sourceforge.net">http://netpbm.sourceforge.net</a>
-<P>
+<p>
Playback may be done with many viewers; <em>mpeg_encode</em>'s official companion
is <em>mpeg_play</em> available from Berkeley at
<a href="ftp://mm-ftp.cs.berkeley.edu/pub/multimedia/mpeg/play/">ftp://mm-ftp.cs.berkeley.edu/pub/multimedia/mpeg/play/</a>
@@ -87,17 +87,17 @@
<a href="http://packages.debian.org/ucbmpeg-play">http://packages.debian.org/ucbmpeg-play</a>
(includes maintained source code).
-<P>
-Use of the <EM>-c</EM> flag requires the <EM>r.out.ppm</EM> GRASS module
-with the <EM>stdout</EM> option.
+<p>
+Use of the <em>-c</em> flag requires the <em>r.out.ppm</em> GRASS module
+with the <em>stdout</em> option.
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.out.ppm.html">r.out.ppm</A></EM>
+<h2>SEE ALSO</h2>
+<em><a href="r.out.ppm.html">r.out.ppm</a></em>
<br>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Bill Brown,
U.S. Army Construction Engineering Research Laboratories
Modified: grass/trunk/raster/r.out.png/description.html
===================================================================
--- grass/trunk/raster/r.out.png/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.png/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,15 +1,15 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.out.png</EM> exports a GRASS raster map as non-georeferenced PNG image
+<em>r.out.png</em> exports a GRASS raster map as non-georeferenced PNG image
format
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.out.tiff.html">r.out.tiff</A>,</EM>
-<EM><A HREF="r.out.ascii.html">r.out.ascii</A></EM>
+<em><a href="r.out.tiff.html">r.out.tiff</a>,</em>
+<em><a href="r.out.ascii.html">r.out.ascii</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Alex Shevlakov
Modified: grass/trunk/raster/r.out.pov/description.html
===================================================================
--- grass/trunk/raster/r.out.pov/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.pov/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
r.out.pov converts a user-specified raster map layer (map==name) into a
height-field file for POVray (tga==name). The hftype==value option (where
@@ -13,10 +13,10 @@
value is assigned as follows: RED = high byte, GREEN = low byte, BLUE =
empty.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
An example Povray script file may look like this:
-<P>
+<p>
<div class="code"><pre>
#include "shapes.inc"
#include "colors.inc"
@@ -56,9 +56,9 @@
scale < 14500, Scale*6553.6, 13000 >
translate <18300, 0, 1100>
}
-</PRE></div>
+</pre></div>
-<H2>AUTHOR</H2>
-Klaus D. Meyer, GEUM.tec GbR, eMail: <I>GEUM.tec at geum.de</I>
+<h2>AUTHOR</h2>
+Klaus D. Meyer, GEUM.tec GbR, eMail: <i>GEUM.tec at geum.de</i>
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.out.ppm/description.html
===================================================================
--- grass/trunk/raster/r.out.ppm/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.ppm/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<em>r.out.ppm</em> converts a GRASS raster map into a PPM image
at the pixel resolution of the CURRENTLY DEFINED REGION.
@@ -13,7 +13,7 @@
before running <em>r.out.ppm</em>.<p>
By default the PPM file created is 24-bit color, rawbits storage.
-You can use the <B>-G</B> flag to force <em>r.out.ppm</em> to
+You can use the <b>-G</b> flag to force <em>r.out.ppm</em> to
output an 8-bit greyscale instead.
The greyscale conversion uses the NTSC conversion:<p>
@@ -26,17 +26,17 @@
<tt>ns_res</tt> differ, the aspect ratio of the resulting image will be off.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
A few ppm file comments are written: the name of the GRASS
raster map, resolution, etc. Although these are perfectly legal,
I've found one PD image utility that chokes on them, so if you need
-a commentless PPM file, use '<TT>out=- > outfile.ppm</TT>'. (When sending
+a commentless PPM file, use '<tt>out=- > outfile.ppm</tt>'. (When sending
output to stdout, no comments are written.)
-<H2>HINTS</H2>
+<h2>HINTS</h2>
You can create a PNG image with NULL values represented by a transparent
-background by using the <a href="pngdriver.html">PNG driver</A> with
+background by using the <a href="pngdriver.html">PNG driver</a> with
<a href="variables.html">GRASS_TRANSPARENT</a> set to TRUE.
Alternatively, you can use the <em>pnmtopng</em> program from
<a href="http://netpbm.sourceforge.net">netpbm</a> to do this:
@@ -46,15 +46,15 @@
pnmtopng -transparent white raster.ppm > raster.png
</pre></div>
-<H2>SEE ALSO</H2>
-<EM><A HREF="d.out.png.html">d.out.png</A></EM><BR>
-<EM><A HREF="r.out.ascii.html">r.out.ascii</A></EM><BR>
-<EM><A HREF="r.out.mpeg.html">r.out.mpeg</A></EM><BR>
-<EM><A HREF="r.out.png.html">r.out.png</A></EM><BR>
-<EM><A HREF="r.out.ppm3.html">r.out.ppm3</A></EM><BR>
-<EM><A HREF="r.out.tiff.html">r.out.tiff</A></EM>
+<h2>SEE ALSO</h2>
+<em><a href="d.out.png.html">d.out.png</a></em><br>
+<em><a href="r.out.ascii.html">r.out.ascii</a></em><br>
+<em><a href="r.out.mpeg.html">r.out.mpeg</a></em><br>
+<em><a href="r.out.png.html">r.out.png</a></em><br>
+<em><a href="r.out.ppm3.html">r.out.ppm3</a></em><br>
+<em><a href="r.out.tiff.html">r.out.tiff</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Bill Brown, UIUC
Modified: grass/trunk/raster/r.out.ppm3/description.html
===================================================================
--- grass/trunk/raster/r.out.ppm3/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.ppm3/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,36 +1,36 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<B>r.out.ppm3</B> converts 3 GRASS raster layers (R,G,B) to a PPM
+<b>r.out.ppm3</b> converts 3 GRASS raster layers (R,G,B) to a PPM
image file, using the current region.
-<P>
+<p>
This program converts a GRASS raster map to a PPM image file
using the the current region settings.
-<P>
+<p>
To get the full area and resolutin of the raster map, run:
<div class="code"><pre>
g.region rast=[mapname]
-</PRE></div>
+</pre></div>
-<P>before running <em>r.out.ppm3</em>.</P>
+<p>before running <em>r.out.ppm3</em>.</p>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
One pixel is written for each cell value, so if ew_res and ns_res
differ, the aspect ratio of the resulting image will be off.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.out.ppm.html">r.out.ppm</A>,</EM>
-<EM><A HREF="r.in.gdal.html">r.in.gdal</A>,</EM>
-<EM><A HREF="d.rgb.html">d.rgb</A></EM>
+<em><a href="r.out.ppm.html">r.out.ppm</a>,</em>
+<em><a href="r.in.gdal.html">r.in.gdal</a>,</em>
+<em><a href="d.rgb.html">d.rgb</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Glynn Clements <glynn.clements at virgin.net><br>
-Based upon <EM>r.out.ppm</EM> and <EM>d.rgb</EM>.
+Based upon <em>r.out.ppm</em> and <em>d.rgb</em>.
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.out.tiff/description.html
===================================================================
--- grass/trunk/raster/r.out.tiff/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.tiff/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,10 +1,10 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<p>This program converts a GRASS raster map to a TIFF raster map. Output may
be 8 or 24 bit (TrueColor). Optionally, a TIFF World file compatible with
ESRI's and other's products may be output.</p>
-<P>
+<p>
The program prompts the user for the name of a GRASS raster map, an output
TIFF file, whether an 8 or 24 bit format is desired, and whether or not to
create a TIFF world file. Currently only uncompressed, packpit, or deflate
@@ -22,24 +22,24 @@
programs that can utilize tiles, it can help speed up some drawing
operations.</p>
-<P>
+<p>
The user may adjust region and resolution before export using
<a href="g.region.html">g.region</a>.</p>
-<P>
+<p>
A better choice to export GRASS raster data might be
-<A HREF="r.out.gdal.html">r.out.gdal</A>.
+<a href="r.out.gdal.html">r.out.gdal</a>.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A>,</EM>
-<EM><A HREF="r.in.gdal.html">r.in.gdal</A>,</EM>
-<EM><A HREF="r.out.gdal.html">r.out.gdal</A></EM>
+<em><a href="g.region.html">g.region</a>,</em>
+<em><a href="r.in.gdal.html">r.in.gdal</a>,</em>
+<em><a href="r.out.gdal.html">r.out.gdal</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro,
U.S. Army Construction Engineering Research Laboratory
-<P>
+<p>
GRASS 5.0 team
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.out.vrml/description.html
===================================================================
--- grass/trunk/raster/r.out.vrml/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.vrml/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,8 +1,8 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
This module exports a GRASS raster map to the Virtual Reality Modeling
Language (VRML) format for 3D visualization.
-<P>
+<p>
This version only outputs raster maps in VRML 1.0 format.
The newer VRML 2.0 format will be more efficient for geographic
applications, as it introduces an "ElevationGrid" node so that
@@ -14,7 +14,7 @@
<em>output</em> parameter, it will be added.
-<H2>WARNING</H2>
+<h2>WARNING</h2>
VRML is not well suited for large geometrys which can result from even
a small geographic region. Most viewers seem to bog down with more
than 12,000 polygons, depending on your hardware & specific
@@ -25,14 +25,14 @@
size.<p>
-<H2>NOTE</H2>
+<h2>NOTE</h2>
This is a preliminary release of "<em>r.out.vrml</em>".
For further information about VRML and available viewers for various platforms, see:<p>
<a href="http://www.w3.org/MarkUp/VRML/">VRML Virtual Reality Modeling Language</a>
-<H2>BUGS:</H2>
+<h2>BUGS:</h2>
Currently the region is transformed to a unit size, so real geographic
location is lost. Side effects when working in a lat-lon location are
that besides general distortion due to projection, a very small
@@ -40,14 +40,14 @@
vertical units expected to be the same as map units.
-<H2>TODO</H2>
+<h2>TODO</h2>
Update to the more modern <a href="http://www.geovrml.org">GeoVRML format</a>,
or probably better the next generation
<a href="http://www.web3d.org">X3D format</a>.
See also the <a href="http://www.xj3d.org">Xj3D project</a>.
-<P>
+<p>
Future plans for this module are to allow draping of sites objects and
vector maps and using the new sites format available in floating
point GRASS to embed WWW links into site objects. It will also be
@@ -62,7 +62,7 @@
performance.
</ul>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Bill Brown, US Army Construction Engineering Research Laboratory
<p>
Modified: grass/trunk/raster/r.out.vtk/description.html
===================================================================
--- grass/trunk/raster/r.out.vtk/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.out.vtk/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,9 +1,9 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-Outputs <I>Raster</I> maps in <I>VTK-ASCII</I> format. <I>Map's</I> are
-valid Raster map's in the current mapset. <I>output</I> is the name of
+Outputs <i>Raster</i> maps in <i>VTK-ASCII</i> format. <i>Map's</i> are
+valid Raster map's in the current mapset. <i>output</i> is the name of
an 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.
+If <i>output</i> is not specified then <b>stdout</b> is used.
The module is sensitive to region settings (set with g.region).
<br>
<br>
@@ -27,28 +27,28 @@
<br>
The vector input requires three raster maps: x, y, z -- defining the vector coordinates - in this order.
More than one vector dataset (3 maps) is not supported.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
This filter generates:
<ul>
-<li><I>structured points</I> with <I>celldata</I> or <I>pointdata</I> if no elevationfile is given</li>
+<li><i>structured points</i> with <i>celldata</i> or <i>pointdata</i> if no elevationfile is given</li>
-<li><I>structured grid</I> (not recommendet) with <I>pointdata</I> if an elevationfile is given</li>
-<li><I>polydataset</I> with <I>pointdata</I> if an elevationfile is given (default)</li>
+<li><i>structured grid</i> (not recommendet) with <i>pointdata</i> if an elevationfile is given</li>
+<li><i>polydataset</i> with <i>pointdata</i> if an elevationfile is given (default)</li>
</ul>
and puts this in a simple VTK-ASCII file. Nor XML or
binary output are supported. It is possible to choose more then one raster map
to be written to the VTK-ASCII file. Each cell-/pointdata is named like the 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.
+<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 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
choosen null value in the VTK-ASCII file.
<br>
If elevation map is choosen, a polygonal grid is created with <i>quads</i>,
but the user can choose also <i>triangle strips</i> or <i>vertices</i>.
-These dataformats a documented at <EM><A HREF="http://www.vtk.org">VTK Toolkit</A></EM>.
+These dataformats a documented at <em><a href="http://www.vtk.org">VTK Toolkit</a></em>.
<br>
<br>
If the "-c" flag is used and the data should be visualised together with other data exported via *.out.vtk
@@ -60,24 +60,24 @@
-<H3>Difference between point- and celldata</H3>
+<h3>Difference between point- and celldata</h3>
r.out.vtk can export raster cells with different representations.
<ul>
<li>
- <I>pointdata</I> -- the cells/values are represented by the center of the cell.
+ <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. These points can
be connected in different ways.
</li>
<li>
- <I>celldata</I> -- is only provided if no elevation map is given.
+ <i>celldata</i> -- is only provided if no elevation map is given.
The cells are created with the same hight and width 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>
#set a nice region
@@ -91,7 +91,7 @@
paraview --data=/tmp/out.vtk
</pre></div>
-<H3>Spearfish example with RGB data</H3>
+<h3>Spearfish example with RGB data</h3>
<div class="code"><pre>
#set the region
@@ -112,13 +112,13 @@
</pre></div>
<br>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r3.out.vtk.html">r3.out.vtk</A></EM><br>
-<EM><A HREF="r.out.ascii.html">r.out.ascii</A></EM><br>
-<EM><A HREF="g.region.html">g.region</A></EM><br>
+<em><a href="r3.out.vtk.html">r3.out.vtk</a></em><br>
+<em><a href="r.out.ascii.html">r.out.ascii</a></em><br>
+<em><a href="g.region.html">g.region</a></em><br>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
Soeren Gebbert
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.patch/description.html
===================================================================
--- grass/trunk/raster/r.patch/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.patch/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-The GRASS program <EM>r.patch</EM> allows the user to build a new
+The GRASS program <em>r.patch</em> allows the user to build a new
raster map the size and resolution of the current region by assigning
known data values from input raster maps to the cells in this region.
This is done by filling in "no data" cells, those that do not yet
@@ -14,75 +14,75 @@
digital elevation data), or for updating an older map layer with more recent
data. The current geographic region definition and mask settings are
respected.
-<P>
-The first <EM>name</EM> listed in the string
-<B>input=</B><EM>name</EM>,<EM>name</EM>,<EM>name</EM>, ... is the name of
+<p>
+The first <em>name</em> listed in the string
+<b>input=</b><em>name</em>,<em>name</em>,<em>name</em>, ... is the name of
the first map whose data values will be used to fill in "no data" cells
-in the current region. The second through 200 (max) input <EM>name</EM>
+in the current region. The second through 200 (max) input <em>name</em>
maps will be used, in order, to supply data values for for the remaining
"no data" cells.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
-Below, the raster map layer on the far left is <B>patched</B>
-with the middle (<EM>patching</EM>) raster map layer,
-to produce the <EM>composite</EM> raster map layer on the right.
+Below, the raster map layer on the far left is <b>patched</b>
+with the middle (<em>patching</em>) raster map layer,
+to produce the <em>composite</em> raster map layer on the right.
-<PRE>
+<pre>
1 1 1 0 2 2 0 0 0 0 1 1 0 0 0 0 1 1 1 1 2 2 0 0
1 1 0 2 2 2 0 0 0 0 1 1 0 0 0 0 1 1 1 2 2 2 0 0
3 3 3 3 2 2 0 0 0 0 0 0 0 0 0 0 3 3 3 3 2 2 0 0
3 3 3 3 0 0 0 0 4 4 4 4 4 4 4 4 3 3 3 3 4 4 4 4
3 3 3 0 0 0 0 0 4 4 4 4 4 4 4 4 3 3 3 4 4 4 4 4
0 0 0 0 0 0 0 0 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
-</PRE>
+</pre>
-Switching the <EM>patched</EM> and the <EM>patching</EM> raster map layers
+Switching the <em>patched</em> and the <em>patching</em> raster map layers
produces the following results:
-<PRE>
+<pre>
0 0 1 1 0 0 0 0 1 1 1 0 2 2 0 0 1 1 1 1 2 2 0 0
0 0 1 1 0 0 0 0 1 1 0 2 2 2 0 0 1 1 1 1 2 2 0 0
0 0 0 0 0 0 0 0 3 3 3 3 2 2 0 0 3 3 3 3 2 2 0 0
4 4 4 4 4 4 4 4 3 3 3 3 0 0 0 0 4 4 4 4 4 4 4 4
4 4 4 4 4 4 4 4 3 3 3 0 0 0 0 0 4 4 4 4 4 4 4 4
4 4 4 4 4 4 4 4 0 0 0 0 0 0 0 0 4 4 4 4 4 4 4 4
-</PRE>
+</pre>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
Frequently, this program is used to patch together adjacent map layers which
have been digitized separately. The program
-<EM><A HREF="v.mkgrid.html">v.mkgrid</A></EM> can be used to make adjacent
+<em><a href="v.mkgrid.html">v.mkgrid</a></em> can be used to make adjacent
maps align neatly.
-<P>
+<p>
The user should check the current geographic region settings before running
-<EM>r.patch</EM>, to ensure that the region boundaries encompass all
+<em>r.patch</em>, to ensure that the region boundaries encompass all
of the data desired to be included in the composite map and to ensure that the
region resolution is the resolution of the desired data. To set the
-geographic region settings to one or several raster maps, the <EM>g.region</EM>
+geographic region settings to one or several raster maps, the <em>g.region</em>
program can be used:
<div class="code"><pre>
g.region rast=map1[,map2[,...]]
</pre></div>
-<P>
+<p>
-Use of <EM>r.patch</EM> is generally followed by use of the GRASS programs
-<EM><A HREF="g.remove.html">g.remove</A></EM> and
-<EM><A HREF="g.rename.html">g.rename</A></EM>;
-<EM>g.remove</EM> is used to remove the original (un-patched) raster map
-layers, while <EM>g.rename</EM> is used to then assign to the newly-created
+Use of <em>r.patch</em> is generally followed by use of the GRASS programs
+<em><a href="g.remove.html">g.remove</a></em> and
+<em><a href="g.rename.html">g.rename</a></em>;
+<em>g.remove</em> is used to remove the original (un-patched) raster map
+layers, while <em>g.rename</em> is used to then assign to the newly-created
composite (patched) raster map layer the name of the original raster map
layer.
-<P>
-<EM>r.patch</EM> creates support files for the patched, composite output map.
+<p>
+<em>r.patch</em> creates support files for the patched, composite output map.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
Create a list of maps matching a pattern, extend the region to include them
all, and patch them together to create a mosaic. Overlapping maps will be
@@ -93,19 +93,19 @@
g.region rast=$MAPS
r.patch in=$MAPS out=mosaic
</pre></div>
-<BR>
+<br>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="g.remove.html">g.remove</A></EM>,
-<EM><A HREF="g.rename.html">g.rename</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.support.html">r.support</A></EM>,
-<EM><A HREF="v.mkgrid.html">v.mkgrid</A></EM>
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="g.remove.html">g.remove</a></em>,
+<em><a href="g.rename.html">g.rename</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.support.html">r.support</a></em>,
+<em><a href="v.mkgrid.html">v.mkgrid</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro,
U.S. Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.profile/description.html
===================================================================
--- grass/trunk/raster/r.profile/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.profile/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
This program outputs two or four column (with <b>-g</b>) data to stdout or
an ASCII file. The default two column output consists of cumulative profile
@@ -9,99 +9,99 @@
<b>-i</b> flag. The profile resolution, or distance between profile
points, is obtained from the current region resolution, or can be manually
set with the <b>res</b> argument.
-<P>
-The <B>-i</B> flag allows the user for selecting the profile from the GRASS
+<p>
+The <b>-i</b> flag allows the user for selecting the profile from the GRASS
monitor by clicking the left mouse button along the profile; clicking the
right mouse button ends the profile.
-<P>
-The <B>profile</B> parameter can be set to comma separated geographic
+<p>
+The <b>profile</b> parameter can be set to comma separated geographic
coordinates for profile line endpoints. The interactive flag (<b>-i</b>)
overrides this option. Alternatively the coordinate pairs can be piped
from stdin, one comma separated pair per line.
-<P>
-The <B>res</B> parameter sets the distance between each profile point
+<p>
+The <b>res</b> parameter sets the distance between each profile point
(resolution). The resolution must be provided in GRASS database units (i.e.
decimal degrees for Lat Long databases and meters for UTM). By default
-<EM>r.profile</EM> uses the resolution of the current GRASS region.
-<P>
-The <B>null</B> parameter can optionally be set to change the character
+<em>r.profile</em> uses the resolution of the current GRASS region.
+<p>
+The <b>null</b> parameter can optionally be set to change the character
string representing null values.
-<H2>OUTPUT FORMAT</H2>
+<h2>OUTPUT FORMAT</h2>
-The multi column output from <EM>r.profile</EM> is intended for easy use in
+The multi column output from <em>r.profile</em> is intended for easy use in
other programs. The output can be piped (|) directly into other programs or
-saved to a file for later use. Output with geographic coordinates (<EM>-g</EM>)
-is compatible with <EM><a href="v.in.ascii.html">v.in.ascii</a></EM> and can
+saved to a file for later use. Output with geographic coordinates (<em>-g</em>)
+is compatible with <em><a href="v.in.ascii.html">v.in.ascii</a></em> and can
be piped direcly into this program.
-<div class="code"><PRE>
+<div class="code"><pre>
r.profile -ig input=elev.rast | v.in.ascii output=elev.profile fs=space
-</PRE></div>
+</pre></div>
The 2 column output is compatible with most plotting programs.
-<P>
+<p>
The optional RGB output provides the associated GRASS colour value for
each profile point.
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
-<B>Example 1</B><BR>
+<b>Example 1</b><br>
Extract a profile with coordinates provided on the command line:
-<div class="code"><PRE>
+<div class="code"><pre>
r.profile input=elev.rast output=profile.pts profile=562517,7779433,562984,7779533,563875,7779800
-</PRE></div>
+</pre></div>
This will extract a profile along the track defined by the three coordinate
pairs.
-<P><BR>
+<p><br>
-<B>Example 2</B><BR>
+<b>Example 2</b><br>
Extract a profile by interactively selecting the profile route from the GRASS
monitor:
-<div class="code"><PRE>
+<div class="code"><pre>
r.profile -i input=elev.rast output=profile.pts
-</PRE></div>
+</pre></div>
Use the left mouse button to select the profile route in the GRASS monitor. Use the
right mouse button to end the profile.
-<P><BR>
+<p><br>
-<B>Example 3</B><BR>
+<b>Example 3</b><br>
Extract a profile with coordinates provided from standard input or an external file:
<p>
-First create a points file with <EM><a href="d.where.html">d.where</a></EM>
+First create a points file with <em><a href="d.where.html">d.where</a></em>
-<div class="code"><PRE>
+<div class="code"><pre>
d.where > saved.points
-</PRE></div>
+</pre></div>
Then pipe the points file into r.profile
-<div class="code"><PRE>
+<div class="code"><pre>
cat saved.points | r.profile input=elev.rast output=profile.pts
-</PRE></div>
+</pre></div>
The advantage of this method is that the same profile points can be piped into
different GRASS rasters by changing the input parameter.
<p>
With this method the coordinates must be given as space or tab seperated easting
and northing. Labels after these values are ignored.
-<P>
+<p>
Another example using d.where:
-<div class="code"><PRE>
+<div class="code"><pre>
d.where | r.profile elevation.dem
-</PRE></div>
+</pre></div>
-<P><BR>
+<p><br>
-<B>Example 4</B><BR>
+<b>Example 4</b><br>
Pipe coordinates into r.profile
-<div class="code"><PRE>
+<div class="code"><pre>
r.profile elevation.dem res=1000 << EOF
591243,4926344
592509,4922156
@@ -112,10 +112,10 @@
606468,4917190
607766,4915664
EOF
-</PRE></div>
+</pre></div>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
The profile resolution is measured exactly from the supplied end or
"turning" point along the profile. The end of a profile segment will be an
@@ -130,17 +130,17 @@
This filters out the everything except the numbers.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="v.in.ascii.html">v.in.ascii</A></EM>,
-<EM><A HREF="d.where.html">d.where</A></EM>,
-<EM><A HREF="d.profile.html">d.profile</A></EM>,
-<EM><A HREF="r.what.html">r.what</A></EM>,
-<EM><A HREF="r.transect.html">r.transect</A></EM>,
+<em><a href="v.in.ascii.html">v.in.ascii</a></em>,
+<em><a href="d.where.html">d.where</a></em>,
+<em><a href="d.profile.html">d.profile</a></em>,
+<em><a href="r.what.html">r.what</a></em>,
+<em><a href="r.transect.html">r.transect</a></em>,
<em><a href="gm_profile.html">gis.m: PROFILE TOOL</a></em>
-<H2>AUTHOR</H2>
-<A HREF=mailto:bcovill at tekmap.ns.ca>Bob Covill</A>
+<h2>AUTHOR</h2>
+<a href=mailto:bcovill at tekmap.ns.ca>Bob Covill</a>
<p>
<i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.proj/description.html
===================================================================
--- grass/trunk/raster/r.proj/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.proj/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,15 +1,15 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.proj</EM> projects a raster map in a specified mapset of a
+<em>r.proj</em> projects a raster map in a specified mapset of a
specified location from the projection of the input location to a raster map
in the current location. The projection information is taken from the
current PROJ_INFO files, as set with <i><a href="g.setproj.html">g.setproj</a>
</i> and viewed with <i><a href="g.proj.html">g.proj</a></i>.
-<H4>Introduction</H4>
+<h4>Introduction</h4>
-<H5>Map projections</H5>
+<h5>Map projections</h5>
Map projections are a method of representing information from a
curved surface (usually a spheroid) in two dimensions, typically to allow
@@ -17,7 +17,7 @@
projections, with common ones divided into a number of classes, including
cylindrical and pseudo-cylindrical, conic and pseudo-conic, and azimuthal
methods, each of which may be conformal, equal-area, or neither.
-<P>
+<p>
The particular projection chosen depends on the purpose of the project,
and the size, shape and location of the area of interest. For example,
normal cylindrical projections are good for maps which are of greater extent
@@ -29,7 +29,7 @@
relationships, and better preserve arc-length, while equal-area projections
are more appropriate for statistical studies and work in which the amount of
material is important.
-<P>
+<p>
Projections are defined by precise mathematical relations, so the method
of projecting coordinates from a geographic reference frame
(latitude-longitude) into a projected cartesian reference frame (eg metres)
@@ -39,7 +39,7 @@
description of over 100 useful projections. This also includes a
programmers library of the projection methods to support other software
development.
-<P>
+<p>
Thus, converting a vector map - in which objects are located
with arbitrary spatial precision - from one projection into another is
usually accomplished by a simple two-step process: first the location of
@@ -47,7 +47,7 @@
projection into latitude-longitude, and then through a forward projection
into the target. (Of course the procedure will be one-step if either the
source or target is in geographic coordinates.)
-<P>
+<p>
Converting a raster map, or image, between different projections,
however, involves additional considerations.
A raster may be considered to represent a sampling of a
@@ -58,37 +58,37 @@
of points at intermediate locations relative to the source grid are
estimated.
-<H5>Projecting vector maps within the GRASS GIS</H5>
+<h5>Projecting vector maps within the GRASS GIS</h5>
<!-- move this into v.proj.html !! -->
GIS data capture, import and transfer often requires a projection
step, since the source or client will frequently be in a different
projection to the working projection.
-<P>
+<p>
In some cases it is convenient to do the conversion outside the package,
-prior to import or after export, using software such as <I>PROJ.4</I>'s
+prior to import or after export, using software such as <i>PROJ.4</i>'s
<i><a href="http://proj.maptools.org/">cs2cs</a></i> [1]. This is an easy
method for converting an ASCII file containing a list of coordinate points,
-since there is no topology to be preserved and <I>cs2cs</I> can be used to
+since there is no topology to be preserved and <i>cs2cs</i> can be used to
process simple lists using a one-line command.
-<P>
-The format of files containg vector maps with <B>lines</B> and <B>arcs</B> is
+<p>
+The format of files containg vector maps with <b>lines</b> and <b>arcs</b> is
generally more complex, as parts of the data stored in the files will describe
topology, and not just coordinates. In GRASS GIS the
-<I><A HREF="v.proj.html">v.proj</a></I> module is provided to reproject
+<i><a href="v.proj.html">v.proj</a></i> module is provided to reproject
vector maps, transferring topology and attributes as well as node coordinates.
This program uses the projection definition and parameters which are stored in
the PROJ_INFO and PROJ_UNITS files in the PERMANENT mapset directory for every
GRASS location.
-<BR><BR>
+<br><br>
-<H4>Design of r.proj</H4>
+<h4>Design of r.proj</h4>
As discussed briefly above, the fundamental step in re-projecting a
raster is resampling the source grid at locations corresponding to the
intersections of a grid in the target projection. The basic procedure for
accomplishing this, therefore, is as follows:
<p>
-<EM>r.proj</EM> converts a map to a new geographic projection. It reads a
+<em>r.proj</em> converts a map to a new geographic projection. It reads a
map from a different location, projects it and write it out to the current
location.
<br>
@@ -112,10 +112,10 @@
format as the input map. If any of the both interpolations is used, the
output map is written as floating point.
-<P>
+<p>
Note that, following normal GRASS conventions, the coverage and
resolution of the resulting grid is set by the current region settings,
-which may be adjusted using <I>g.region</I>. The target raster will be
+which may be adjusted using <i>g.region</i>. The target raster will be
relatively unbiased for all cases if its grid has a similar resolution to
the source, so that the resampling/interpolation step is only a local
operation. If the resolution is changed significantly, then the behaviour
@@ -124,26 +124,26 @@
numerical data. Note that three methods for the local interpolation step
are provided.
-<P>
-<EM>r.proj</EM> supports general datum transformations, making use of the
-<EM>PROJ.4</EM> co-ordinate system translation library.
-</P>
+<p>
+<em>r.proj</em> supports general datum transformations, making use of the
+<em>PROJ.4</em> co-ordinate system translation library.
+</p>
<h2>NOTES</h2>
To avoid excessive time consumption when reprojecting a map the region and
resolution of the target location should be set appropriately beforehand.
A simple way to do this is to generate a vector "box" map of the region in
-the source location using <em><A HREF="v.in.region.html">v.in.region</a></em>.
+the source location using <em><a href="v.in.region.html">v.in.region</a></em>.
This "box" map is then reprojected into the target location with
-<em><A HREF="v.proj.html">v.proj</a></em>.
+<em><a href="v.proj.html">v.proj</a></em>.
Next the region in the target location is set to the extent of the new vector
-map with <em><A HREF="g.region.html">g.region</a></em> along with the desired
+map with <em><a href="g.region.html">g.region</a></em> along with the desired
raster resolution (<em>g.region -m</em> can be used in Latitude/Longitude
locations to measure the geodetic length of a pixel).
<em>r.proj</em> is then run for the raster map the user wants to reproject.
In this case a little preparation goes a long way.
-<P>
+<p>
When reprojecting whole-world maps the user should disable map-trimming with
the <em>-n</em> flag. Trimming is not useful here because the module has the
whole map in memory anyway. Besides that, world "edges" are hard (or
@@ -158,10 +158,10 @@
<p>
Richards, John A. (1993), Remote Sensing Digital Image Analysis,
Springer-Verlag, Berlin, 2nd edition.
-<P>
+<p>
<a href=http://proj.maptools.org/>PROJ.4</a>: Projection/datum support library.
-<P>
-<B>Further reading</B>
+<p>
+<b>Further reading</b>
<ul>
<li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
<li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ.4)
@@ -169,29 +169,29 @@
<li> <a href="http://crs.bkg.bund.de/crs-eu/">Information and Service System for European Coordinate Reference Systems - CRS</a>
</ul>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="g.region.html">g.region</A>,
-<A HREF="g.proj.html">g.proj</A>,
-<A HREF="g.setproj.html">g.setproj</A>,
-<A HREF="i.rectify.html">i.rectify</A>,
-<A HREF="r.support.html">r.support</A>,
-<A HREF="r.stats.html">r.stats</A>,
-<A HREF="v.proj.html">v.proj</A>,
-<A HREF="v.in.region.html">v.in.region</A>
-</EM>
-<P>
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="g.proj.html">g.proj</a>,
+<a href="g.setproj.html">g.setproj</a>,
+<a href="i.rectify.html">i.rectify</a>,
+<a href="r.support.html">r.support</a>,
+<a href="r.stats.html">r.stats</a>,
+<a href="v.proj.html">v.proj</a>,
+<a href="v.in.region.html">v.in.region</a>
+</em>
+<p>
The 'gdalwarp' and 'gdal_translate' utilities are available from the
-<A HREF="http://www.gdal.org">GDAL</A> project.
+<a href="http://www.gdal.org">GDAL</a> project.
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
Martin Schroeder, University of Heidelberg, Germany<p>
Man page text from S.J.D. Cox, AGCRC, CSIRO Exploration & Mining, Nedlands, WA
<p>
Updated by <a href="mailto:morten at ngb.se">Morten Hulden</a>
-<P>
+<p>
Datum tranformation support and cleanup by Paul Kelly
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.proj.seg/description.html
===================================================================
--- grass/trunk/raster/r.proj.seg/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.proj.seg/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,15 +1,15 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.proj</EM> projects a raster map in a specified mapset of a
+<em>r.proj</em> projects a raster map in a specified mapset of a
specified location from the projection of the input location to a raster map
in the current location. The projection information is taken from the
current PROJ_INFO files, as set with <i><a href="g.setproj.html">g.setproj</a>
</i> and viewed with <i><a href="g.proj.html">g.proj</a></i>.
-<H4>Introduction</H4>
+<h4>Introduction</h4>
-<H5>Map projections</H5>
+<h5>Map projections</h5>
Map projections are a method of representing information from a
curved surface (usually a spheroid) in two dimensions, typically to allow
@@ -17,7 +17,7 @@
projections, with common ones divided into a number of classes, including
cylindrical and pseudo-cylindrical, conic and pseudo-conic, and azimuthal
methods, each of which may be conformal, equal-area, or neither.
-<P>
+<p>
The particular projection chosen depends on the purpose of the project,
and the size, shape and location of the area of interest. For example,
normal cylindrical projections are good for maps which are of greater extent
@@ -29,7 +29,7 @@
relationships, and better preserve arc-length, while equal-area projections
are more appropriate for statistical studies and work in which the amount of
material is important.
-<P>
+<p>
Projections are defined by precise mathematical relations, so the method
of projecting coordinates from a geographic reference frame
(latitude-longitude) into a projected cartesian reference frame (eg metres)
@@ -39,7 +39,7 @@
description of over 100 useful projections. This also includes a
programmers library of the projection methods to support other software
development.
-<P>
+<p>
Thus, converting a vector map - in which objects are located
with arbitrary spatial precision - from one projection into another is
usually accomplished by a simple two-step process: first the location of
@@ -47,7 +47,7 @@
projection into latitude-longitude, and then through a forward projection
into the target. (Of course the procedure will be one-step if either the
source or target is in geographic coordinates.)
-<P>
+<p>
Converting a raster map, or image, between different projections,
however, involves additional considerations.
A raster may be considered to represent a sampling of a
@@ -58,37 +58,37 @@
of points at intermediate locations relative to the source grid are
estimated.
-<H5>Projecting vector maps within the GRASS GIS</H5>
+<h5>Projecting vector maps within the GRASS GIS</h5>
<!-- move this into v.proj.html !! -->
GIS data capture, import and transfer often requires a projection
step, since the source or client will frequently be in a different
projection to the working projection.
-<P>
+<p>
In some cases it is convenient to do the conversion outside the package,
-prior to import or after export, using software such as <I>PROJ.4</I>'s
+prior to import or after export, using software such as <i>PROJ.4</i>'s
<i><a href="http://proj.maptools.org/">cs2cs</a></i> [1]. This is an easy
method for converting an ASCII file containing a list of coordinate points,
-since there is no topology to be preserved and <I>cs2cs</I> can be used to
+since there is no topology to be preserved and <i>cs2cs</i> can be used to
process simple lists using a one-line command.
-<P>
-The format of files containing vector maps with <B>lines</B> and <B>arcs</B> is
+<p>
+The format of files containing vector maps with <b>lines</b> and <b>arcs</b> is
generally more complex, as parts of the data stored in the files will describe
topology, and not just coordinates. In GRASS GIS the
-<I><A HREF="v.proj.html">v.proj</a></I> module is provided to reproject
+<i><a href="v.proj.html">v.proj</a></i> module is provided to reproject
vector maps, transferring topology and attributes as well as node coordinates.
This program uses the projection definition and parameters which are stored in
the PROJ_INFO and PROJ_UNITS files in the PERMANENT mapset directory for every
GRASS location.
-<BR><BR>
+<br><br>
-<H4>Design of r.proj</H4>
+<h4>Design of r.proj</h4>
As discussed briefly above, the fundamental step in re-projecting a
raster is resampling the source grid at locations corresponding to the
intersections of a grid in the target projection. The basic procedure for
accomplishing this, therefore, is as follows:
<p>
-<EM>r.proj</EM> converts a map to a new geographic projection. It reads a
+<em>r.proj</em> converts a map to a new geographic projection. It reads a
map from a different location, projects it and write it out to the current
location.
<br>
@@ -112,10 +112,10 @@
format as the input map. If any of the both interpolations is used, the
output map is written as floating point.
-<P>
+<p>
Note that, following normal GRASS conventions, the coverage and
resolution of the resulting grid is set by the current region settings,
-which may be adjusted using <I>g.region</I>. The target raster will be
+which may be adjusted using <i>g.region</i>. The target raster will be
relatively unbiased for all cases if its grid has a similar resolution to
the source, so that the resampling/interpolation step is only a local
operation. If the resolution is changed significantly, then the behaviour
@@ -124,26 +124,26 @@
numerical data. Note that three methods for the local interpolation step
are provided.
-<P>
-<EM>r.proj</EM> supports general datum transformations, making use of the
-<EM>PROJ.4</EM> co-ordinate system translation library.
-</P>
+<p>
+<em>r.proj</em> supports general datum transformations, making use of the
+<em>PROJ.4</em> co-ordinate system translation library.
+</p>
<h2>NOTES</h2>
To avoid excessive time consumption when reprojecting a map the region and
resolution of the target location should be set appropriately beforehand.
A simple way to do this is to generate a vector "box" map of the region in
-the source location using <em><A HREF="v.in.region.html">v.in.region</a></em>.
+the source location using <em><a href="v.in.region.html">v.in.region</a></em>.
This "box" map is then reprojected into the target location with
-<em><A HREF="v.proj.html">v.proj</a></em>.
+<em><a href="v.proj.html">v.proj</a></em>.
Next the region in the target location is set to the extent of the new vector
-map with <em><A HREF="g.region.html">g.region</a></em> along with the desired
+map with <em><a href="g.region.html">g.region</a></em> along with the desired
raster resolution (<em>g.region -m</em> can be used in Latitude/Longitude
locations to measure the geodetic length of a pixel).
<em>r.proj</em> is then run for the raster map the user wants to reproject.
In this case a little preparation goes a long way.
-<P>
+<p>
When reprojecting whole-world maps the user should disable map-trimming with
the <em>-n</em> flag. Trimming is not useful here because the module has the
whole map in memory anyway. Besides that, world "edges" are hard (or
@@ -158,10 +158,10 @@
<p>
Richards, John A. (1993), Remote Sensing Digital Image Analysis,
Springer-Verlag, Berlin, 2nd edition.
-<P>
+<p>
<a href=http://proj.maptools.org/>PROJ.4</a>: Projection/datum support library.
-<P>
-<B>Further reading</B>
+<p>
+<b>Further reading</b>
<ul>
<li> <a href="http://www.asprs.org/resources/grids/">ASPRS Grids and Datum</a>
<li> <a href="http://www.remotesensing.org/geotiff/proj_list/">Projections Transform List</a> (PROJ.4)
@@ -169,29 +169,29 @@
<li> <a href="http://crs.bkg.bund.de/crs-eu/">Information and Service System for European Coordinate Reference Systems - CRS</a>
</ul>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="g.region.html">g.region</A>,
-<A HREF="g.proj.html">g.proj</A>,
-<A HREF="g.setproj.html">g.setproj</A>,
-<A HREF="i.rectify.html">i.rectify</A>,
-<A HREF="r.support.html">r.support</A>,
-<A HREF="r.stats.html">r.stats</A>,
-<A HREF="v.proj.html">v.proj</A>,
-<A HREF="v.in.region.html">v.in.region</A>
-</EM>
-<P>
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="g.proj.html">g.proj</a>,
+<a href="g.setproj.html">g.setproj</a>,
+<a href="i.rectify.html">i.rectify</a>,
+<a href="r.support.html">r.support</a>,
+<a href="r.stats.html">r.stats</a>,
+<a href="v.proj.html">v.proj</a>,
+<a href="v.in.region.html">v.in.region</a>
+</em>
+<p>
The 'gdalwarp' and 'gdal_translate' utilities are available from the
-<A HREF="http://www.gdal.org">GDAL</A> project.
+<a href="http://www.gdal.org">GDAL</a> project.
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
Martin Schroeder, University of Heidelberg, Germany<p>
Man page text from S.J.D. Cox, AGCRC, CSIRO Exploration & Mining, Nedlands, WA
<p>
Updated by <a href="mailto:morten at ngb.se">Morten Hulden</a>
-<P>
+<p>
Datum tranformation support and cleanup by Paul Kelly
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.quant/description.html
===================================================================
--- grass/trunk/raster/r.quant/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.quant/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,14 +1,14 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<em>r.quant</em> produces the quantization file for a floating-point map.
-<P>
+<p>
The <em>map</em> parameter defines the map for which the rules be to be
created. If more than one map is specified, then this implies that the
floating-point range is the miniumum and maximum of all the maps together,
unless either basemap=map or fprange=min,max is specified.
-<H2> Quant rules </H2>
+<h2> Quant rules </h2>
The quant rules have to be entered interactively.
<p>
@@ -20,15 +20,15 @@
integers. If cat2 is missing, it is taken to be equal to cat1. All values
can be "*" which means infinity.
-<H2>NOTE</H2>
+<h2>NOTE</h2>
It is an error for both basemap and fprange to be specified.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.support.html">r.support</A></EM>,
-<EM><A HREF="r.null.html">r.null</A></EM>
+<em><a href="r.support.html">r.support</a></em>,
+<em><a href="r.null.html">r.null</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro, Olga Waupotitsch,
U.S.Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.quantile/description.html
===================================================================
--- grass/trunk/raster/r.quantile/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.quantile/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,16 +1,16 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.quantile</EM> computes quantiles in a manner suitable for use with large amounts of data.
+<em>r.quantile</em> computes quantiles in a manner suitable for use with large amounts of data.
It is using two passes.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
<em>
-<A HREF="r.quant.html">r.quant</A>
+<a href="r.quant.html">r.quant</a>
</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Glynn Clements <glynn gclements.plus.com>
<p>
Modified: grass/trunk/raster/r.random/description.html
===================================================================
--- grass/trunk/raster/r.random/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.random/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,165 +1,165 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-The program <EM>r.random</EM> allows the user to create a
+The program <em>r.random</em> allows the user to create a
raster map layer and a vector points map containing
coordinates of points whose locations have been randomly
determined. The program locates these randomly generated
sites (vector points) within the current geographic region and mask (if
any), on non-zero category value data areas within a
user-specified raster map layer. If the user sets the
-<B>-z</B> flag, sites will be randomly generated across all
+<b>-z</b> flag, sites will be randomly generated across all
cells (even those with NULL values).
-<P>
+<p>
-The <EM>raster_output</EM> raster map layer is created in
+The <em>raster_output</em> raster map layer is created in
the user's current mapset. The category values and
corresponding category names already associated with the
-random vector point locations in the <EM>input</EM> map layer are
-assigned to these sites in the <EM>raster_output</EM> map
-layer. If the <B>-z</B> is specified, then a unique entry
-is made for the value used where the <EM>input</EM> was NULL.
+random vector point locations in the <em>input</em> map layer are
+assigned to these sites in the <em>raster_output</em> map
+layer. If the <b>-z</b> is specified, then a unique entry
+is made for the value used where the <em>input</em> was NULL.
This value is at least 1 less than the smallest value in the
-<EM>input</EM> raster and is given a medium gray color.
+<em>input</em> raster and is given a medium gray color.
-<P>
+<p>
-The <EM>vector_output</EM> file created by <EM>r.random</EM>
+The <em>vector_output</em> file created by <em>r.random</em>
contains a listing of the sites' coordinates;
-these coordinates are the <EM>center points</EM> of the
+these coordinates are the <em>center points</em> of the
randomly selected cells. A double attribute contains the cell value
-of the <EM>input</EM> raster (or the assigned value
-when <B>-z</B> is used. The values a stored in the <EM>value</EM>
+of the <em>input</em> raster (or the assigned value
+when <b>-z</b> is used. The values a stored in the <em>value</em>
column in the attached attribute table. <br>
-If a <EM>cover</EM> map is additionally specified, a second
-column <EM>covervalue</EM> is populated with raster values from
-the <EM>cover</EM> map.
+If a <em>cover</em> map is additionally specified, a second
+column <em>covervalue</em> is populated with raster values from
+the <em>cover</em> map.
-<H2>OPTIONS</H2>
+<h2>OPTIONS</h2>
The user may specify the quantity of random locations to be
-generated either as a <EM>positive integer</EM> (e.g., 10),
-or as a <EM>percentage of the raster map layer's cells</EM>
+generated either as a <em>positive integer</em> (e.g., 10),
+or as a <em>percentage of the raster map layer's cells</em>
(e.g., 10%, or 3.05%). The number of cells considered for
-the percentage reflects whether or not the <B>-z</B> flag
+the percentage reflects whether or not the <b>-z</b> flag
was given. Options are 0-100; percentages less than
one percent may be stated as decimals.
-<P>
+<p>
-<EM>r.random</EM> can be run interactively or
+<em>r.random</em> can be run interactively or
non-interactively. The user may provide program arguments
on the command line, specifying an input raster map layer name
-(<B>input=</B><EM>name</EM>), optionally a cover raster map layer name
-(<B>cover=</B><EM>name</EM>), output raster map layer name
-(<B>raster_output=</B><EM>name</EM>), output vector points map
-name (<B>vector_output=</B><EM>name</EM>), and
+(<b>input=</b><em>name</em>), optionally a cover raster map layer name
+(<b>cover=</b><em>name</em>), output raster map layer name
+(<b>raster_output=</b><em>name</em>), output vector points map
+name (<b>vector_output=</b><em>name</em>), and
the number of sites to be randomly generated as a
-total number of sites (<B>n=</B><EM>number</EM>) or as
+total number of sites (<b>n=</b><em>number</em>) or as
a percentage of the map's size
-(<B>n=</B><EM>number</EM><B>%</B>). The user can also
-direct that <EM>r.random</EM> run quietly (using the
-<B>-q</B>)</EM> option, and/or direct <EM>r.random</EM> to
+(<b>n=</b><em>number</em><b>%</b>). The user can also
+direct that <em>r.random</em> run quietly (using the
+<b>-q</b>)</em> option, and/or direct <em>r.random</em> to
also generate random vector point locations against cells
-containing NULL values (using the <B>-z</B> option). The
-<B>-i</B> can be used to get a count of the total cells and
+containing NULL values (using the <b>-z</b> option). The
+<b>-i</b> can be used to get a count of the total cells and
NULL cells given the current region settings.
-<H3>Flags:</H3>
+<h3>Flags:</h3>
-<DL>
-<DT><B>-z</B>
+<dl>
+<dt><b>-z</b>
-<DD>Include NULL cells in the pool
-from which <EM>r.random</EM> will randomly generate vector point locations.
+<dd>Include NULL cells in the pool
+from which <em>r.random</em> will randomly generate vector point locations.
-<DT><B>-i</B>
+<dt><b>-i</b>
-<DD>Print the raster map's name and location,
+<dd>Print the raster map's name and location,
the total number of cells under the current region settings, and
the number of NULL valued cells under the current region settings.
Then exit without doing anything. Useful for deciding on the number
-of sites to have <EM>r.random</EM> create.
+of sites to have <em>r.random</em> create.
-<DT><B>-d</B>
+<dt><b>-d</b>
-<DD>Generate vector points with 3D geometry instead of 2D geometry.
+<dd>Generate vector points with 3D geometry instead of 2D geometry.
The z values correspond to the raster map values.
-</DL>
+</dl>
-<P>
+<p>
-<H3>Parameters:</H3>
+<h3>Parameters:</h3>
-<DL>
-<DT><B>input=</B><EM>name</EM>
-<DD>An existing raster map layer in the user's current mapset search path.
-<EM>r.random</EM> will randomly generate sites on a user-specified portion
-of the cells in this <EM>input</EM> raster map.
+<dl>
+<dt><b>input=</b><em>name</em>
+<dd>An existing raster map layer in the user's current mapset search path.
+<em>r.random</em> will randomly generate sites on a user-specified portion
+of the cells in this <em>input</em> raster map.
-<DT><B>cover=</B><EM>name</EM>
-<DD>An existing raster map layer in the user's current mapset search path.
-<EM>r.random</EM> will extract raster values at the generates random sites
-from this <EM>cover</EM> raster map. The cover map only generates output
-for the <EM>vector_output</EM> map.
+<dt><b>cover=</b><em>name</em>
+<dd>An existing raster map layer in the user's current mapset search path.
+<em>r.random</em> will extract raster values at the generates random sites
+from this <em>cover</em> raster map. The cover map only generates output
+for the <em>vector_output</em> map.
-<DT><B>n=</B><EM>number</EM>
-<DD>Specify the quantity of sites to be randomly generated as
-either a <EM>positive</EM> integer, or as a <EM>percentage</EM> value of
-the number of cells in the <EM>input</EM> map layer.
-If stated as a positive integer, <EM>number</EM> is
+<dt><b>n=</b><em>number</em>
+<dd>Specify the quantity of sites to be randomly generated as
+either a <em>positive</em> integer, or as a <em>percentage</em> value of
+the number of cells in the <em>input</em> map layer.
+If stated as a positive integer, <em>number</em> is
the number of sites (i.e., number of cells) to appear
-in the <EM>raster_output</EM> layer and/or <EM>vector_output</EM> file.
-<BR>
+in the <em>raster_output</em> layer and/or <em>vector_output</em> file.
+<br>
Options: Non-percentage values should be given as positive integer values
less than or equal to the number of cells in the input map layer.
Percentage values given should be within the range 0.00 - 100.00
(decimal values are allowed).
-<DT><B>raster_output=</B><EM>name</EM>
-<DD>The new raster map layer to hold program output. This map will contain
-the sites randomly generated by <EM>r.random</EM>. If the -z flag is not set,
+<dt><b>raster_output=</b><em>name</em>
+<dd>The new raster map layer to hold program output. This map will contain
+the sites randomly generated by <em>r.random</em>. If the -z flag is not set,
all sites will be assigned whatever category values were assigned these
-cell locations in the <EM>input</EM> raster map layer.
+cell locations in the <em>input</em> raster map layer.
If the -z flag is set, all sites except those falling on NULL cells
-in the <EM>input</EM> value will be assigned the category values
+in the <em>input</em> value will be assigned the category values
assigned these cells in the input layer; sites falling on NULL cells
-in the <EM>input</EM> layer will be assigned to a newly created
-category in the <EM>raster_output</EM> layer with at least one integer
-value less than the minimum value in the <EM>input</EM> layer.
+in the <em>input</em> layer will be assigned to a newly created
+category in the <em>raster_output</em> layer with at least one integer
+value less than the minimum value in the <em>input</em> layer.
-<DT><B>vector_output=</B><EM>name</EM>
-<DD>The new GRASS <EM>vector_output</EM> file to hold program output.
-If no <EM>vector_output</EM> file name is given on the command line,
-no <EM>vector_output</EM> file will be created by <EM>r.random</EM>.
-(See <EM>raster_output</EM> parameter description, above.)
+<dt><b>vector_output=</b><em>name</em>
+<dd>The new GRASS <em>vector_output</em> file to hold program output.
+If no <em>vector_output</em> file name is given on the command line,
+no <em>vector_output</em> file will be created by <em>r.random</em>.
+(See <em>raster_output</em> parameter description, above.)
-Note. Although the user need not request that <EM>r.random</EM> output
-both a raster map layer (<EM>raster_output</EM>)
-and a vector points map (<EM>vector_output</EM>), the user must
+Note. Although the user need not request that <em>r.random</em> output
+both a raster map layer (<em>raster_output</em>)
+and a vector points map (<em>vector_output</em>), the user must
specify that at least one of these outputs be produced.
-</DL>
+</dl>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
To create random vector point locations within some, but not all,
non-zero categories of the input raster map layer,
the user must first create a reclassified raster map layer
of the original raster map layer (e.g., using the GRASS
-program <EM><A HREF="r.reclass.html">r.reclass</A></EM>)
+program <em><a href="r.reclass.html">r.reclass</a></em>)
that contains only the desired categories,
-and then use the reclassed raster map layer as input to <EM>r.random</EM>.
-<P>
-If a <EM>cover</EM> raster map is specified and the <EM>cover</EM> map
+and then use the reclassed raster map layer as input to <em>r.random</em>.
+<p>
+If a <em>cover</em> raster map is specified and the <em>cover</em> map
contains NULL (no data) values, these sites are suppressed in the
-resulting <EM>vector_output</EM> map.
+resulting <em>vector_output</em> map.
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
Random vector elevation points sampled from elevation map in the
Spearfish region, result stored in 2D vector map:
@@ -190,25 +190,25 @@
...
</pre></div>
-<H2>BUGS</H2>
+<h2>BUGS</h2>
-It's not possible to use the <B>-i</B> flag and not also specify the <B>n</B>
+It's not possible to use the <b>-i</b> flag and not also specify the <b>n</b>
parameter.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A></EM><br>
-<EM><A HREF="r.reclass.html">r.reclass</A></EM><br>
-<EM><A HREF="v.random.html">v.random</A></EM><br>
+<em><a href="g.region.html">g.region</a></em><br>
+<em><a href="r.reclass.html">r.reclass</a></em><br>
+<em><a href="v.random.html">v.random</a></em><br>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Dr. James Hinthorne,
GIS Laboratory,
Central Washington University
-<P>
+<p>
Modified for GRASS 5.0 by Eric G. Miller
<p>
Cover map support by Markus Neteler, 2007
Modified: grass/trunk/raster/r.random.cells/description.html
===================================================================
--- grass/trunk/raster/r.random.cells/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.random.cells/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,79 +1,79 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.random.cells</EM> generates a random sets of cells that are at
-least <VAR>distance</VAR> apart. The cells are numbered from 1 to the
+<em>r.random.cells</em> generates a random sets of cells that are at
+least <var>distance</var> apart. The cells are numbered from 1 to the
numbers of cells generated. Random cells will not be generated in areas
masked off.
-<H2>PARAMETERS</H2>
+<h2>PARAMETERS</h2>
-<B>output </B> Output map: Random cells. Each random cell has a unique
+<b>output </b> Output map: Random cells. Each random cell has a unique
non-zero cell value ranging from 1 to the number of cells generated. The
heuristic for this algorithm is to randomly pick cells until there are no
-cells outside of the chosen cell's buffer of radius <B>distance</B>.
-<P>
+cells outside of the chosen cell's buffer of radius <b>distance</b>.
+<p>
-<B>distance</B> Input value(s) [default 0.0]: <B>distance</B> determines the
+<b>distance</b> Input value(s) [default 0.0]: <b>distance</b> determines the
minimum distance the centers of the random cells will be apart.
-<P>
-<B>seed</B> Input value [default: random]: Specifies the random seed that
-<EM>r.random.cells</EM> will use to generate the cells. If the random seed
-is not given,<EM> r.random.cells</EM> will get a seed from the process ID
+<p>
+<b>seed</b> Input value [default: random]: Specifies the random seed that
+<em>r.random.cells</em> will use to generate the cells. If the random seed
+is not given,<em> r.random.cells</em> will get a seed from the process ID
number.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
The original purpose for this program was to generate independent random
-samples of cells in a study area. The <B>distance</B> value is the amount of
+samples of cells in a study area. The <b>distance</b> value is the amount of
spatial autocorrelation for the map being studied. The amount of spatial
-autocorrelation can be determined by using <EM>r.2Dcorrelogram</EM> with
-<EM>r.2Dto1D</EM>, or <EM>r.1Dcorrelogram</EM>. With <B>distance</B> set to
-zero, the <B>output</B> map will number each non-masked cell from 1 to the
+autocorrelation can be determined by using <em>r.2Dcorrelogram</em> with
+<em>r.2Dto1D</em>, or <em>r.1Dcorrelogram</em>. With <b>distance</b> set to
+zero, the <b>output</b> map will number each non-masked cell from 1 to the
number of non-masked cells in the study region.
<h2>REFERENCES</h2>
Random Field Software for GRASS by Chuck Ehlschlaeger<p>
-<P>As part of my dissertation, I put together several programs that help
+<p>As part of my dissertation, I put together several programs that help
GRASS (4.1 and beyond) develop uncertainty models of spatial data. I hope
you find it useful and dependable. The following papers might clarify their
-use: </P>
+use: </p>
-<P>"<A HREF="http://www.wiu.edu/users/cre111/older/CGFinal/paper.htm">Visualizing Spatial Data
-Uncertainty Using Animation (final draft)</A>," by Charles R.
+<p>"<a href="http://www.wiu.edu/users/cre111/older/CGFinal/paper.htm">Visualizing Spatial Data
+Uncertainty Using Animation (final draft)</a>," by Charles R.
Ehlschlaeger, Ashton M. Shortridge, and Michael F. Goodchild. Submitted to
Computers in GeoSciences in September, 1996, accepted October, 1996 for
-publication in June, 1997. </P>
+publication in June, 1997. </p>
-<P>"<A HREF="http://www.wiu.edu/users/cre111/older/SDH96/paper.html">Modeling Uncertainty in Elevation Data for
-Geographical Analysis</A>", by Charles R. Ehlschlaeger, and Ashton M.
+<p>"<a href="http://www.wiu.edu/users/cre111/older/SDH96/paper.html">Modeling Uncertainty in Elevation Data for
+Geographical Analysis</a>", by Charles R. Ehlschlaeger, and Ashton M.
Shortridge. Proceedings of the 7th International Symposium on Spatial Data
-Handling, Delft, Netherlands, August 1996. </P>
+Handling, Delft, Netherlands, August 1996. </p>
-<P>"<A HREF="http://www.wiu.edu/users/cre111/older/acm/paper.html">Dealing with Uncertainty in
+<p>"<a href="http://www.wiu.edu/users/cre111/older/acm/paper.html">Dealing with Uncertainty in
Categorical Coverage Maps: Defining, Visualizing, and Managing Data
-Errors</A>", by Charles Ehlschlaeger and Michael Goodchild.
+Errors</a>", by Charles Ehlschlaeger and Michael Goodchild.
Proceedings, Workshop on Geographic Information Systems at the Conference on
-Information and Knowledge Management, Gaithersburg MD, 1994. </P>
+Information and Knowledge Management, Gaithersburg MD, 1994. </p>
-<P>"<A HREF="http://www.wiu.edu/users/cre111/older/gislis/gislis.html">Uncertainty in Spatial Data:
-Defining, Visualizing, and Managing Data Errors</A>", by Charles
+<p>"<a href="http://www.wiu.edu/users/cre111/older/gislis/gislis.html">Uncertainty in Spatial Data:
+Defining, Visualizing, and Managing Data Errors</a>", by Charles
Ehlschlaeger and Michael Goodchild. Proceedings, GIS/LIS'94, pp. 246-253,
-Phoenix AZ, 1994. </P>
+Phoenix AZ, 1994. </p>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
+<em>
r.1Dcorrelogram,
r.2Dcorrelogram,
r.2Dto1D,
-<A HREF="r.random.surface.html">r.random.surface</A>,
+<a href="r.random.surface.html">r.random.surface</a>,
r.random.model,
-<A HREF="r.random.html">r.random</A>
-</EM>
+<a href="r.random.html">r.random</a>
+</em>
-<H2>AUTHOR</H2>
-<P>Charles Ehlschlaeger; National Center for Geographic Information and
+<h2>AUTHOR</h2>
+<p>Charles Ehlschlaeger; National Center for Geographic Information and
Analysis, University of California, Santa Barbara.
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.random.surface/description.html
===================================================================
--- grass/trunk/raster/r.random.surface/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.random.surface/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.random.surface</EM> generates a spatially dependent random surface.
+<em>r.random.surface</em> generates a spatially dependent random surface.
The random surface is composed of values representing the deviation from the
mean of the initial random values driving the algorithm. The initial random
values are independent Gaussian random deviates with a mean of 0 and
@@ -11,36 +11,36 @@
weight based on the weight inputs. The resulting random surface can have
"any" mean and variance, but the theoretical mean of an infinitely
large map is 0.0 and a variance of 1.0. Description of the algorithm is in
-the <B>NOTES</B> section.
+the <b>NOTES</b> section.
-<P>
+<p>
The random surface generated are composed of floating point numbers, and
saved in the category description files of the output map(s). Cell values
are uniformly or normally distributed between 1 and high values inclusive
-(determined by whether the <EM>-u</EM> flag is used). The category names
+(determined by whether the <em>-u</em> flag is used). The category names
indicate the average floating point value and the range of floating point
values that each cell value represents.
-<P>
-<EM>r.random.surface's</EM> original goal is to generate random fields for
-spatial error modeling. A procedure to use <EM>r.random.surface</EM> in
-spatial error modeling is given in the <B>NOTES</B> section.
+<p>
+<em>r.random.surface's</em> original goal is to generate random fields for
+spatial error modeling. A procedure to use <em>r.random.surface</em> in
+spatial error modeling is given in the <b>NOTES</b> section.
-<H3>Parameters:</H3>
-<DL>
-<DT><B>output</B>
-<DD>Output map(s): Random surface(s). The cell values are a random
+<h3>Parameters:</h3>
+<dl>
+<dt><b>output</b>
+<dd>Output map(s): Random surface(s). The cell values are a random
distribution between the low and high values inclusive. The category values
of the output map(s) are in the form "#.# #.# to #.#" where each
#.# is a floating point number. The first number is the average of the
random values the cell value represents. The other two numbers are the range
of random values for that cell value. The "average" mean value of
-generated <TT>output</TT> map(s) is 0. The "average"
+generated <tt>output</tt> map(s) is 0. The "average"
variance of map(s) generated is 1. The random values represent the standard
deviation from the mean of that random surface.
-<DT><B>distance</B>
-<DD>Input value(s) [default 0.0]: distance determines the spatial dependence
+<dt><b>distance</b>
+<dd>Input value(s) [default 0.0]: distance determines the spatial dependence
of the output map(s). The distance value indicates the minimum distance at
which two map cells have no relationship to each other. A distance value of
0.0 indicates that there is no spatial dependence (i.e., adjacent cell
@@ -51,8 +51,8 @@
increases. If multiple values are given, each output map will have multiple
filters, one for each set of distance, exponent, and weight values.
-<DT><B>exponent</B>
-<DD>Input value(s) [default 1.0]: exponent determines the distance decay
+<dt><b>exponent</b>
+<dd>Input value(s) [default 1.0]: exponent determines the distance decay
exponent for a particular filter. The exponent value(s) have the property of
determining the "texture" of the random surface. Texture will
decrease as the exponent value(s) get closer to 1.0. Normally, exponent will
@@ -60,12 +60,12 @@
given an exponent value of 1.0. If there is at least one exponent value
given, there must be one exponent value for each distance value.
-<DT><B>flat</B>
-<DD>Input value(s) [default 0.0]: flat determines the distance at which the
+<dt><b>flat</b>
+<dd>Input value(s) [default 0.0]: flat determines the distance at which the
filter
-<DT><B>weight</B>
-<DD>Input value(s) [default 1.0]: weight determines the relative importance
+<dt><b>weight</b>
+<dd>Input value(s) [default 1.0]: weight determines the relative importance
of each filter. For example, if there were two filters driving the algorithm
and weight=1.0, 2.0 was given in the command line: The second filter would
be twice as important as the first filter. If no weight values are given,
@@ -73,8 +73,8 @@
random field. If weight values exist, there must be a weight value for each
filter of the random field.
-<DT><B>high</B>
-<DD>Input value [default 255]: Specifies the high end of the range of cell
+<dt><b>high</b>
+<dd>Input value [default 255]: Specifies the high end of the range of cell
values in the output map(s). Specifying a very large high value will
minimize the "errors" caused by the random surface's
discretization. The word errors is in quotes because errors in
@@ -82,22 +82,22 @@
statistics are far more sensitive to the initial independent random deviates
than any potential discretization errors.
-<DT><B>seed</B>
-<DD>Input value(s) [default random]: Specifies the random seed(s), one for
-each map, that <EM>r.random.surface</EM> will use to generate the initial
+<dt><b>seed</b>
+<dd>Input value(s) [default random]: Specifies the random seed(s), one for
+each map, that <em>r.random.surface</em> will use to generate the initial
set of random values that the resulting map is based on. If the random seed
-is not given, <EM>r.random.surface</EM> will get a seed from the process ID
+is not given, <em>r.random.surface</em> will get a seed from the process ID
number.
-</DL>
+</dl>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
While most literature uses the term random field instead of random surface,
this algorithm always generates a surface. Thus, its use of random surface.
-<P>
-<EM>r.random.surface</EM> builds the random surface using a filter algorithm
+<p>
+<em>r.random.surface</em> builds the random surface using a filter algorithm
smoothing a map of independent random deviates. The size of the filter is
determined by the largest distance of spatial dependence. The shape of the
filter is determined by the distance decay exponent(s), and the various
@@ -107,66 +107,66 @@
reduction of degrees of freedom. The map of independent random deviates will
ignore the current mask for the same reason.
-<P>
-One of the most important uses for <EM>r.random.surface</EM> is to determine
+<p>
+One of the most important uses for <em>r.random.surface</em> is to determine
how the error inherent in raster maps might effect the analyses done with
those maps. If you wanted to check to see how sensitive your analysis is to
the errors in the DEMs in your study area, see:
-<P>"<A HREF="http://www.geo.hunter.cuny.edu/~chuck/CGFinal/paper.htm">Visualizing Spatial Data Uncertainty Using Animation (final draft)</A>," by Charles R. Ehlschlaeger, Ashton M. Shortridge, and Michael F. Goodchild. Submitted to Computers in GeoSciences in September, 1996, accepted October, 1996 for publication in June, 1997.
+<p>"<a href="http://www.geo.hunter.cuny.edu/~chuck/CGFinal/paper.htm">Visualizing Spatial Data Uncertainty Using Animation (final draft)</a>," by Charles R. Ehlschlaeger, Ashton M. Shortridge, and Michael F. Goodchild. Submitted to Computers in GeoSciences in September, 1996, accepted October, 1996 for publication in June, 1997.
-<P>
-"<A HREF="http://www.geo.hunter.cuny.edu/~chuck/SDH96/paper.html">Modeling Uncertainty in Elevation Data for Geographical Analysis</A>", by Charles R. Ehlschlaeger, and Ashton M. Shortridge. Proceedings of the 7th International Symposium on Spatial Data Handling, Delft, Netherlands, August 1996. </P>
+<p>
+"<a href="http://www.geo.hunter.cuny.edu/~chuck/SDH96/paper.html">Modeling Uncertainty in Elevation Data for Geographical Analysis</a>", by Charles R. Ehlschlaeger, and Ashton M. Shortridge. Proceedings of the 7th International Symposium on Spatial Data Handling, Delft, Netherlands, August 1996. </p>
-<P>
-"<A HREF="http://www.geo.hunter.cuny.edu/~chuck/acm/paper.html">Dealing with Uncertainty in Categorical Coverage Maps: Defining, Visualizing, and Managing Data Errors</A>", by Charles Ehlschlaeger and Michael Goodchild. Proceedings, Workshop on Geographic Information Systems at the Conference on Information and Knowledge Management, Gaithersburg MD, 1994.
+<p>
+"<a href="http://www.geo.hunter.cuny.edu/~chuck/acm/paper.html">Dealing with Uncertainty in Categorical Coverage Maps: Defining, Visualizing, and Managing Data Errors</a>", by Charles Ehlschlaeger and Michael Goodchild. Proceedings, Workshop on Geographic Information Systems at the Conference on Information and Knowledge Management, Gaithersburg MD, 1994.
-<P>
-"<A HREF="http://www.geo.hunter.cuny.edu/~chuck/gislis/gislis.html>Uncertainty in Spatial Data: Defining, Visualizing, and Managing Data Errors</A>", by Charles Ehlschlaeger and Michael Goodchild. Proceedings, GIS/LIS'94, pp. 246-253, Phoenix AZ,
+<p>
+"<a href="http://www.geo.hunter.cuny.edu/~chuck/gislis/gislis.html>Uncertainty in Spatial Data: Defining, Visualizing, and Managing Data Errors</a>", by Charles Ehlschlaeger and Michael Goodchild. Proceedings, GIS/LIS'94, pp. 246-253, Phoenix AZ,
1994.
-<P>
+<p>
If you are interested in creating potential realizations of categorical
-coverage maps, see <EM>r.random.model</EM>.
+coverage maps, see <em>r.random.model</em>.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><a href="r.random.html">r.random</a>,
+<em><a href="r.random.html">r.random</a>,
<a href="r.mapcalc.html">r.mapcalc</a>
-</EM>
+</em>
<h2>REFERENCES</h2>
Random Field Software for GRASS by Chuck Ehlschlaeger<p>
-<P>As part of my dissertation, I put together several programs that help
+<p>As part of my dissertation, I put together several programs that help
GRASS (4.1 and beyond) develop uncertainty models of spatial data. I hope
you find it useful and dependable. The following papers might clarify their
-use: </P>
+use: </p>
-<P>"<A HREF="../../CGFinal/paper.htm">Visualizing Spatial Data
-Uncertainty Using Animation (final draft)</A>," by Charles R.
+<p>"<a href="../../CGFinal/paper.htm">Visualizing Spatial Data
+Uncertainty Using Animation (final draft)</a>," by Charles R.
Ehlschlaeger, Ashton M. Shortridge, and Michael F. Goodchild. Submitted to
Computers in GeoSciences in September, 1996, accepted October, 1996 for
-publication in June, 1997. </P>
+publication in June, 1997. </p>
-<P>"<A HREF="http://www.geo.hunter.cuny.edu/~chuck/paper.html">Modeling Uncertainty in Elevation Data for
-Geographical Analysis</A>", by Charles R. Ehlschlaeger, and Ashton M.
+<p>"<a href="http://www.geo.hunter.cuny.edu/~chuck/paper.html">Modeling Uncertainty in Elevation Data for
+Geographical Analysis</a>", by Charles R. Ehlschlaeger, and Ashton M.
Shortridge. Proceedings of the 7th International Symposium on Spatial Data
-Handling, Delft, Netherlands, August 1996. </P>
+Handling, Delft, Netherlands, August 1996. </p>
-<P>"<A HREF="http://www.geo.hunter.cuny.edu/~chuck/acm/paper.html">Dealing with Uncertainty in
+<p>"<a href="http://www.geo.hunter.cuny.edu/~chuck/acm/paper.html">Dealing with Uncertainty in
Categorical Coverage Maps: Defining, Visualizing, and Managing Data
-Errors</A>", by Charles Ehlschlaeger and Michael Goodchild.
+Errors</a>", by Charles Ehlschlaeger and Michael Goodchild.
Proceedings, Workshop on Geographic Information Systems at the Conference on
-Information and Knowledge Management, Gaithersburg MD, 1994. </P>
+Information and Knowledge Management, Gaithersburg MD, 1994. </p>
-<P>"<A HREF="http://www.geo.hunter.cuny.edu/~chuck/gislis/gislis.html">Uncertainty in Spatial Data:
-Defining, Visualizing, and Managing Data Errors</A>", by Charles
+<p>"<a href="http://www.geo.hunter.cuny.edu/~chuck/gislis/gislis.html">Uncertainty in Spatial Data:
+Defining, Visualizing, and Managing Data Errors</a>", by Charles
Ehlschlaeger and Michael Goodchild. Proceedings, GIS/LIS'94, pp. 246-253,
-Phoenix AZ, 1994. </P>
+Phoenix AZ, 1994. </p>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
Charles Ehlschlaeger, Michael Goodchild, and Chih-chang Lin; National Center
for Geographic Information and Analysis, University of California, Santa
Barbara.
Modified: grass/trunk/raster/r.reclass/description.html
===================================================================
--- grass/trunk/raster/r.reclass/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.reclass/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,41 +1,41 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.reclass</EM> creates an <EM>output</EM> map layer
-based on an <EM>input</EM> raster map layer. The output
+<em>r.reclass</em> creates an <em>output</em> map layer
+based on an <em>input</em> raster map layer. The output
map layer will be a reclassification of the input map layer
-based on reclass rules input to <EM>r.reclass</EM>, and can
+based on reclass rules input to <em>r.reclass</em>, and can
be treated in much the same way that raster maps are
-treated. A <EM>TITLE</EM> for the output map layer may be
+treated. A <em>TITLE</em> for the output map layer may be
(optionally) specified by the user.
-<P>
+<p>
The reclass rules are read from standard input (i.e., from
the keyboard, redirected from a file, or piped through
another program).
-<P>
-Before using <EM>r.reclass</EM> the user must know the following:
+<p>
+Before using <em>r.reclass</em> the user must know the following:
-<OL>
-<LI>The new categories desired; and, which old categories fit into
+<ol>
+<li>The new categories desired; and, which old categories fit into
which new categories.
-<LI>The names of the new categories.
-</OL>
+<li>The names of the new categories.
+</ol>
-<H2>INTERACTIVE PROGRAM USE: EXAMPLE</H2>
+<h2>INTERACTIVE PROGRAM USE: EXAMPLE</h2>
Suppose we want to reclassify the raster map layer
-<EM>roads</EM>, consisting of five categories, into the
+<em>roads</em>, consisting of five categories, into the
three new categories: paved roads, unpaved roads, and
railroad tracks. The user is asked whether the reclass
table is to be established with each category value
initially set to 0, or with each category value initially
set to its own value. A screen like that shown below then
-appears, listing the categories of the <EM>roads</EM>
+appears, listing the categories of the <em>roads</em>
raster map layer to be reclassified and prompting the user
for the new category values to be assigned them.
-<P>
-<PRE>
+<p>
+<pre>
ENTER NEW CATEGORY NUMBERS FOR THESE CATEGORIES
OLD CATEGORY NAME OLD NEW
@@ -49,7 +49,7 @@
AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
(OR <Ctrl-C> TO CANCEL)
-</PRE>
+</pre>
In the following screen the new category values have been
entered beside the appropriate old category names. Cells
@@ -58,7 +58,7 @@
reclassed map; cell data formerly assigned to category
value 5 in the old raster map map are now assigned the new
category value 3 in the reclassed map.
-<PRE>
+<pre>
ENTER NEW CATEGORY NUMBERS FOR THESE CATEGORIES
@@ -73,13 +73,13 @@
AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
(OR <Ctrl-C> TO CANCEL)
-</PRE>
+</pre>
Hitting the escape key <ESC> will bring up the
following screen, which prompts the user to enter a new
-TITLE and category label for the newly <B>reclassed</B>
+TITLE and category label for the newly <b>reclassed</b>
categories.
-<PRE>
+<pre>
ENTER NEW CATEGORY NAMES FOR THESE CATEGORIES
TITLE: Roads Reclassified
@@ -92,12 +92,12 @@
AFTER COMPLETING ALL ANSWERS, HIT <ESC> TO CONTINUE
(OR <Ctrl-C> TO CANCEL)
-</PRE>
+</pre>
Based upon the information supplied by the user in the above sample screens,
the new output map, supporting category, color, history, and header files
are created.
-<H2>NON-INTERACTIVE PROGRAM USE: RECLASS RULES</H2>
+<h2>NON-INTERACTIVE PROGRAM USE: RECLASS RULES</h2>
In non-interactive program use, the names of an input map, output map,
and output map TITLE are given on the command line.
@@ -105,33 +105,33 @@
(i.e., from the keyboard, redirected
from a file, or piped through another program).
-<P>
+<p>
Once the user has specified an input raster map layer,
output map layer name, and (optionally) output map layer
TITLE by typing
-<DL>
-<DD>
-<B>r.reclass input=</B><EM>name </EM><B>output=</B><EM>name </EM>[<B>TITLE=</B><EM>name</EM>]
-</DL>
+<dl>
+<dd>
+<b>r.reclass input=</b><em>name </em><b>output=</b><em>name </em>[<b>TITLE=</b><em>name</em>]
+</dl>
Each line of input must have the following format:
-<DL>
-<DD><B>input_categories=</B><EM>output_category </EM>[<EM>label</EM>]
-</DL>
+<dl>
+<dd><b>input_categories=</b><em>output_category </em>[<em>label</em>]
+</dl>
-<P>
+<p>
where the input lines specify the category values in the
input raster map layer to be reclassified to the new
-<EM>output_category</EM> category value. Specification of
-a <EM>label</EM> to be associated with the new output map
+<em>output_category</em> category value. Specification of
+a <em>label</em> to be associated with the new output map
layer category is optional. If specified, it is recorded
as the category label for the new category value. The
-equal sign = is required. The <EM>input_category(ies)</EM>
+equal sign = is required. The <em>input_category(ies)</em>
may consist of single category values or a range of such
-values in the format "<EM>low</EM> thru <EM>high</EM>." The
+values in the format "<em>low</em> thru <em>high</em>." The
word "thru" must be present.
<p>
To include all (remaining) values the asterix "*" can be used. This
@@ -139,77 +139,77 @@
setting this rule.
<p>
No data have to be spcified with NULL.
-<P>
+<p>
-A line containing only the word <B>end</B> terminates the
+A line containing only the word <b>end</b> terminates the
input.
-<H2>NON-INTERACTIVE PROGRAM USE: EXAMPLES</H2>
+<h2>NON-INTERACTIVE PROGRAM USE: EXAMPLES</h2>
The following examples may help clarify the reclass rules.
-<P>
-<DT>
-<DD>1. This example reclassifies categories 1, 2 and 3 in the input raster
+<p>
+<dt>
+<dd>1. This example reclassifies categories 1, 2 and 3 in the input raster
map layer "roads" to category 1 with category label "good quality" in the output map
layer, and reclassifies input raster map layer categories 4 and 5 to
category 2 with the label "poor quality" in the output map layer.
-<PRE>
+<pre>
1 2 3 = 1 good quality
4 5 = 2 poor quality
-</PRE>
-<P>
-<DD>2. This example reclassifies input raster map layer categories 1 thru 10 to output
+</pre>
+<p>
+<dd>2. This example reclassifies input raster map layer categories 1 thru 10 to output
map layer category 1, input map layer categories 11 thru 20 to output map layer
category 2, and input map layer categories 21 thru 30 to output map layer
category 3, all without labels. The range from 30 to 40 is reclassified as
NULL.
-<PRE>
+<pre>
1 thru 10 = 1
11 thru 20 = 2
21 thru 30 = 3
30 thru 40 = NULL
-</PRE>
+</pre>
-<DD>3. Subsequent rules override previous rules. Therefore, the below example
+<dd>3. Subsequent rules override previous rules. Therefore, the below example
reclassifies input raster map layer categories 1 thru 19 and 51 thru 100
to category 1 in the output map layer,
input raster map layer categories 20 thru 24 and 26 thru 50 to
the output map layer category 2, and input raster map layer category 25
to the output category 3.
-<PRE>
+<pre>
1 thru 100 = 1 poor quality
20 thru 50 = 2 medium quality
25 = 3 good quality
-</PRE>
+</pre>
-<DD>4. This example reclassifies categories 1, 3 and 5 in the input raster map layer to category 1 with category label "poor quality" in the output map layer,
+<dd>4. This example reclassifies categories 1, 3 and 5 in the input raster map layer to category 1 with category label "poor quality" in the output map layer,
and reclassifies input raster map layer categories 2, 4, and 6
to category 2 with the label "good quality" in the output map layer.
All other values are reclassified to NULL.
-<PRE>
+<pre>
1 3 5 = 1 poor quality
2 4 6 = 2 good quality
* = NULL
-</PRE>
-<P>
+</pre>
+<p>
-<DD>5. The previous example could also have been entered as:
-<PRE>
+<dd>5. The previous example could also have been entered as:
+<pre>
1 thru 19 51 thru 100 = 1 poor quality
20 thru 24 26 thru 50 = 2 medium quality
25 = 3 good quality
-</PRE>
+</pre>
or as:
-<PRE>
+<pre>
1 thru 19 = 1 poor quality
51 thru 100 = 1
20 thru 24 = 2
26 thru 50 = 2 medium quality
25 = 3 good quality
-</PRE>
-</DD>
-<P>
+</pre>
+</dd>
+<p>
The final example was given to show how the labels are handled. If a new
category value appears in more than one rule (as is the case with new
@@ -217,32 +217,32 @@
the last label which was specified becomes the label for that category.
In this case the labels are assigned exactly as in the two previous examples.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-In fact, the <EM>r.reclass</EM> program does <EM>not</EM> generate any new
+In fact, the <em>r.reclass</em> program does <em>not</em> generate any new
raster map layers (in the interests of disk space conservation). Instead, a
-<B>reclass table</B> is stored which will be used to reclassify the
+<b>reclass table</b> is stored which will be used to reclassify the
original raster map layer each time the new (reclassed) map name
is requested. As far as the user (and programmer) is concerned, that
raster map has been created.
-Also note that although the user can generate a <EM>r.reclass</EM> map
-which is based on another <EM>r.reclass</EM> map,
-the new <EM>r.reclass</EM> map map will be stored in GRASS as a reclass
-of the <EM>original</EM> raster map on which the first reclassed map was
-based. Therefore, while GRASS allows the user to provide <EM>r.reclass</EM>
+Also note that although the user can generate a <em>r.reclass</em> map
+which is based on another <em>r.reclass</em> map,
+the new <em>r.reclass</em> map map will be stored in GRASS as a reclass
+of the <em>original</em> raster map on which the first reclassed map was
+based. Therefore, while GRASS allows the user to provide <em>r.reclass</em>
map layer information which is based on an already reclassified map
-(for the user's convenience), no <EM>r.reclass</EM> map layer
-(i.e., <EM>reclass table</EM>) will ever be <EM>stored</EM>
-as a <EM>r.reclass</EM> of a <EM>r.reclass</EM>.
+(for the user's convenience), no <em>r.reclass</em> map layer
+(i.e., <em>reclass table</em>) will ever be <em>stored</em>
+as a <em>r.reclass</em> of a <em>r.reclass</em>.
-<P>
+<p>
To convert a reclass map to a regular raster map layer, set your
geographic region settings to match the settings in the header for the
-reclass map (an ASCII file found under the <EM>cellhd</EM> directory, or
-viewable by running <EM><A HREF="r.support.html">r.support</A></EM>) and then run <EM><A HREF="r.resample.html">r.resample</A></EM>.
+reclass map (an ASCII file found under the <em>cellhd</em> directory, or
+viewable by running <em><a href="r.support.html">r.support</a></em>) and then run <em><a href="r.resample.html">r.resample</a></em>.
-<P>
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM> can be used to convert
+<p>
+<em><a href="r.mapcalc.html">r.mapcalc</a></em> can be used to convert
a reclass map to a regular raster map layer:
<div class="code"><pre>
@@ -250,38 +250,38 @@
</pre></div>
-<P>
-where <EM>raster_map</EM> is the name to be given to the new raster map,
-and <EM>reclass_map</EM> is an existing reclass map.
+<p>
+where <em>raster_map</em> is the name to be given to the new raster map,
+and <em>reclass_map</em> is an existing reclass map.
-<H2>BEWARE</H2>
+<h2>BEWARE</h2>
-Because <EM>r.reclass</EM> generates a table referencing some original
+Because <em>r.reclass</em> generates a table referencing some original
raster map layer rather than creating a reclassed raster map layer,
-a <EM>r.reclass</EM> map layer will no longer be accessible if
+a <em>r.reclass</em> map layer will no longer be accessible if
the original raster map layer upon which it was based is later removed.
-<P>
-A <EM>r.reclass</EM> map is not a true raster map layer.
+<p>
+A <em>r.reclass</em> map is not a true raster map layer.
Rather, it is a table of reclassification values which reference the
input raster map layer. Therefore, users who wish to retain reclassified
map layers must also save the original input raster map layers
from which they were generated. Alternatively r.recode can be used.
-<P>
+<p>
Category values which are not explicitly reclassified to a new value
by the user will be reclassified to NULL.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.resample.html">r.resample</A></EM>,
-<EM><A HREF="r.rescale.html">r.rescale</A></EM>,
-<EM><A HREF="r.recode.html">r.recode</A></EM>
+<em><a href="r.resample.html">r.resample</a></em>,
+<em><a href="r.rescale.html">r.rescale</a></em>,
+<em><a href="r.recode.html">r.recode</a></em>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
James Westervelt,
-<BR>
+<br>
Michael Shapiro,
<br>
Modified: grass/trunk/raster/r.recode/description.html
===================================================================
--- grass/trunk/raster/r.recode/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.recode/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<em>r.recode</em> creates an output map layer based on an input raster map
layer. The output map layer will be a recoding of the input map layer based
@@ -13,12 +13,12 @@
hold recoded map, and (optionally) the name of a title for the output map.
Rules are defined in one of these formats:
-<PRE>
+<pre>
old_low:old_high:new_low:new_high
old_low:old_high:new_val (i.e. new_high == new_low)
*:old_val:new_val (interval [inf, old_val])
old_val:*:new_val (interval [old_val, inf])
-</PRE>
+</pre>
<em>r.recode</em> is loosely based on r.reclass and uses the GRASS reclass
library to convert the rasters. It has routines for converting to every
@@ -45,7 +45,7 @@
These four sets of arguments can be given on the command line, or piped via
stdin or a file. More than one set of arguments is accepted.
-<h2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
<b>Map type conversion</b><br>
@@ -72,7 +72,7 @@
</pre>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
CERL
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.region/description.html
===================================================================
--- grass/trunk/raster/r.region/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.region/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,35 +1,35 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-The <EM>r.region</EM> program allows the user to manage the boundaries
+The <em>r.region</em> program allows the user to manage the boundaries
of a raster map. These boundaries can be set by the user directly
and/or set from a region definition file (stored under the
-<KBD>windows</KBD> directory in the user's current mapset), a raster
+<kbd>windows</kbd> directory in the user's current mapset), a raster
or vector map, or a 3dview file.
-<P>
+<p>
-The <B>align</B> parameter allows to set the current resolution equal to
+The <b>align</b> parameter allows to set the current resolution equal to
that of the named raster map, and align the boundaries to a row and column
edge in the named map. Alignment only moves the existing boundaries outward
to the edges of the next nearest cell in the named raster map -- not to the
named map's edges. To perform the latter function, use the
-<B>raster=</B><EM>name</EM> option.
+<b>raster=</b><em>name</em> option.
-<H2>NOTE</H2>
+<h2>NOTE</h2>
After all updates have been applied, the raster map's resolution
settings are recomputed from the boundaries and the number of rows and
columns in the raster map.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.support.html">r.support</A></EM><br>
-<EM><A HREF="g.region.html">g.region</A></EM>
+<em><a href="r.support.html">r.support</a></em><br>
+<em><a href="g.region.html">g.region</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Glynn Clements
-<BR>
+<br>
Based upon g.region
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.report/description.html
===================================================================
--- grass/trunk/raster/r.report/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.report/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.report</EM> allows the user to set up a series of report parameters to
+<em>r.report</em> allows the user to set up a series of report parameters to
be applied to a raster map layer, and creates a report. If invoked with
command line arguments, the report will print out to the screen only.
However, output may be redirected to a file or another program using the
@@ -8,39 +8,39 @@
user is given the option of printing out each report and/or saving output to
a file.
-<P>
+<p>
The report itself consists of two parts, a header section and the main body
of the report.
-<P>
+<p>
The header section of the report identifies the raster map layer(s) (by map
layer name and TITLE), location, mapset, report date, and the region of
interest. The area of interest is described in two parts: the user's current
geographic region is presented, and the mask is presented (if any is used).
-<P>
+<p>
The main body of the report consists of from one to three tables which
present the statistics for each category and the totals for each unit
column.
-<P>
-Note that, unlike <EM><A HREF="r.stats.html">r.stats</A></EM>,
-<EM>r.report</EM> allows the user to select the specific units of measure in
+<p>
+Note that, unlike <em><a href="r.stats.html">r.stats</a></em>,
+<em>r.report</em> allows the user to select the specific units of measure in
which statistics will be reported.
-<P>
-Following is the result of a <EM>r.report</EM> run on the raster map layer
-<EM>geology</EM> (located in the Spearfish, SD sample data base), with the
-units expressed in square miles and acres. Here, <EM>r.report</EM> output is
-directed into the file <EM>report.file</EM>.
+<p>
+Following is the result of a <em>r.report</em> run on the raster map layer
+<em>geology</em> (located in the Spearfish, SD sample data base), with the
+units expressed in square miles and acres. Here, <em>r.report</em> output is
+directed into the file <em>report.file</em>.
-<H2>EXAMPLE:</H2>
-<DL>
-<DD>
-<B>r.report map=</B><EM>geology</EM> <B>units=</B><EM>miles,acres</EM> > <EM>report.file </EM>
-</DL>
+<h2>EXAMPLE:</h2>
+<dl>
+<dd>
+<b>r.report map=</b><em>geology</em> <b>units=</b><em>miles,acres</em> > <em>report.file </em>
+</dl>
-<PRE>
+<pre>
____________________________________________________________
| RASTER MAP CATEGORY REPORT |
| LOCATION: spearfish Fri Sep 2 09:20:09|
@@ -69,29 +69,29 @@
|__________________________________|___________|_____________|
| TOTAL | 65728.60| 102.70 |
|__________________________________|___________|_____________|
-</PRE>
+</pre>
-<H2>NOTES</H2>
-If the user runs <EM>r.report</EM> interactively and saves the report output
+<h2>NOTES</h2>
+If the user runs <em>r.report</em> interactively and saves the report output
in a file, this file will be placed into the user's current working
directory.
-<P>
-If the user runs <EM>r.report</EM> non-interactively, report output can be
+<p>
+If the user runs <em>r.report</em> non-interactively, report output can be
saved by redirecting it to a file or a printer using the UNIX redirection
mechanism.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A>,
-<A HREF="r.coin.html">r.coin</A>,
-<A HREF="r.describe.html">r.describe</A>,
-<A HREF="r.info.html">r.info</A>,
-<A HREF="r.stats.html">r.stats</A>,
-<A HREF="r.univar.html">r.univar</A>
-</EM>
+<em><a href="g.region.html">g.region</a>,
+<a href="r.coin.html">r.coin</a>,
+<a href="r.describe.html">r.describe</a>,
+<a href="r.info.html">r.info</a>,
+<a href="r.stats.html">r.stats</a>,
+<a href="r.univar.html">r.univar</a>
+</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro,
U.S. Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.resamp.interp/description.html
===================================================================
--- grass/trunk/raster/r.resamp.interp/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.resamp.interp/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.resamp.interp</EM> resamples an input raster map by interpolating between
+<em>r.resamp.interp</em> resamples an input raster map by interpolating between
the neighboring cells via a selectable resampling algorithm. All cells
present in the neighborhood of the input raster cell must be non-null to
generate a non-null cell in the output raster map. A choice of three
@@ -15,20 +15,20 @@
This module is intended for reinterpolation of continuous data
to a different resolution rather than for interpolation from scattered data
-(use the <EM>v.surf.*</EM> modules for that purpose).
+(use the <em>v.surf.*</em> modules for that purpose).
</p>
-<P>
+<p>
Note that for bilinear and bicubic interpolation,
cells of the output raster that cannot be bounded by the appropriate number
of input cell centers are set to NULL (NULL propagation). This could occur
due to the input cells being outside the current region, being NULL or MASKed.
</p>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-<P>
+<p>
For longitude-latitude databases, the interpolation algorithm is based on
degree fractions, not on the absolute distances between cell centers. Any
attempt to implement the latter would violate the integrity of the
@@ -36,14 +36,14 @@
</p>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><a href="g.region.html">g.region</a></EM>,
-<EM><a href="r.resample.html">r.resample</a></EM>,
-<EM><a href="r.resamp.rst.html">r.resamp.rst</a></EM>
-<EM><a href="r.resamp.stats.html">r.resamp.stats</a></EM>
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.resample.html">r.resample</a></em>,
+<em><a href="r.resamp.rst.html">r.resamp.rst</a></em>
+<em><a href="r.resamp.stats.html">r.resamp.stats</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Glynn Clements
Modified: grass/trunk/raster/r.resamp.rst/description.html
===================================================================
--- grass/trunk/raster/r.resamp.rst/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.resamp.rst/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,10 +1,10 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<i>r.resamp.rst</i> reinterpolates the values a from given raster map (named
<i>input</i>) to a new raster map (named <i>elev</i>).
This module is intended for reinterpolation of continuous data
to a different resolution rather than for interpolation from scattered data
-(use the <EM>v.surf.*</EM> modules for that purpose).
+(use the <em>v.surf.*</em> modules for that purpose).
Reinterpolation (resampling) is done to higher, same or lower resolution
specified by the <i>ew_res</i> and <i>ns_res</i> parameters.
@@ -100,7 +100,7 @@
<li>rescaling parameter used for normalization (dnorm), which influences the
tension.</li>
</ul>
-<P>
+<p>
The program gives a warning when the user wants to interpolate outside
the region given by the <i>input</i> raster map's header data. Zooming into the
area where the points are is suggested in this case.
Modified: grass/trunk/raster/r.resamp.stats/description.html
===================================================================
--- grass/trunk/raster/r.resamp.stats/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.resamp.stats/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,31 +1,31 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<p>
-<EM>r.resamp.stats</EM> fills a grid cell (raster) matrix with
+<em>r.resamp.stats</em> fills a grid cell (raster) matrix with
aggregated values generated from a set of input layer data points.
</p>
-<P>
-Without the <EM>-w</EM> switch, the aggregate is computed over all of
+<p>
+Without the <em>-w</em> switch, the aggregate is computed over all of
the input cells whose centers lie within the output cell.
-</P>
-<P>
-With the <EM>-w</EM> switch, the aggregate uses the values from all
+</p>
+<p>
+With the <em>-w</em> switch, the aggregate uses the values from all
input cells which intersect the output cell, weighted according to the
proportion of the source cell which lies inside the output cell. This
is slower, but produces a more accurate result.
</p>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><a href="g.region.html">g.region</a></EM>,
-<EM><a href="r.resample.html">r.resample</a></EM>,
-<EM><a href="r.resamp.rst.html">r.resamp.rst</a></EM>
-<EM><a href="r.resamp.interp.html">r.resamp.interp</a></EM>
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.resample.html">r.resample</a></em>,
+<em><a href="r.resamp.rst.html">r.resamp.rst</a></em>
+<em><a href="r.resamp.interp.html">r.resamp.interp</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Glynn Clements
Modified: grass/trunk/raster/r.resample/description.html
===================================================================
--- grass/trunk/raster/r.resample/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.resample/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,47 +1,47 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.resample</EM> resamples the data values in a user-specified raster
-input map layer <EM>name</EM> (bounded by the current geographic region
+<em>r.resample</em> resamples the data values in a user-specified raster
+input map layer <em>name</em> (bounded by the current geographic region
and masked by the current mask), and produces a new raster output map layer
-<EM>name</EM> containing the results of the resampling.
+<em>name</em> containing the results of the resampling.
The category values in the new raster output map layer will be the same
as those in the original, except that the resolution and extent of the
new raster output map layer will match those of the current geographic region
-settings (see <EM><A HREF="g.region.html">g.region</A></EM>).
-<EM>r.resample</EM> is intended for reinterpolation of continuous data
+settings (see <em><a href="g.region.html">g.region</a></em>).
+<em>r.resample</em> is intended for reinterpolation of continuous data
to a different resolution rather than for interpolation from scattered data
-(use the <EM>v.surf.*</EM> modules for that purpose).
+(use the <em>v.surf.*</em> modules for that purpose).
-<H2>NOTES</H2>
+<h2>NOTES</h2>
The method by which resampling is conducted is "nearest neighbor"
-(see <EM><A HREF="r.neighbors.html">r.neighbors</A></EM>).
+(see <em><a href="r.neighbors.html">r.neighbors</a></em>).
The resulting raster map layer will have the same
resolution as the resolution of the current geographic region
-(set using <EM><A HREF="g.region.html">g.region</A></EM>).
+(set using <em><a href="g.region.html">g.region</a></em>).
-<P>
+<p>
The resulting raster map layer may be identical to the original raster
-map layer. The <EM>r.resample</EM> program will copy the color table
+map layer. The <em>r.resample</em> program will copy the color table
and history file associated with the original raster map
layer for the resulting raster map layer and will create a modified
category file which contains description of only those categories
which appear in resampled file.
-<P>
+<p>
-When the user resamples a GRASS <EM>reclass</EM> file, a true raster map
-is created by <EM>r.resample</EM>.
+When the user resamples a GRASS <em>reclass</em> file, a true raster map
+is created by <em>r.resample</em>.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.mfilter.html">r.mfilter</A></EM>,
-<EM><A HREF="r.neighbors.html">r.neighbors</A></EM>,
-<EM><A HREF="r.rescale.html">r.rescale</A></EM>
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.mfilter.html">r.mfilter</a></em>,
+<em><a href="r.neighbors.html">r.neighbors</a></em>,
+<em><a href="r.rescale.html">r.rescale</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro,
U.S.Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.rescale/description.html
===================================================================
--- grass/trunk/raster/r.rescale/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.rescale/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-The <EM>r.rescale</EM> program rescales the range of
+The <em>r.rescale</em> program rescales the range of
category values appearing in a raster map layer. A new
raster map layer, and an appropriate category file and
color table based upon the original raster map layer, are
@@ -9,51 +9,51 @@
is useful for producing representations with a reduced
number of categories from a raster map layer with a large
range of category values (e.g., elevation).
-<EM>Rescaled</EM> map layers are appropriate for use in
+<em>Rescaled</em> map layers are appropriate for use in
such GRASS programs as
-<EM><A HREF="r.stats.html">r.stats</A></EM>,
-<EM><A HREF="r.report.html">r.report</A></EM>, and
-<EM><A HREF="r.coin.html">r.coin</A></EM>.
+<em><a href="r.stats.html">r.stats</a></em>,
+<em><a href="r.report.html">r.report</a></em>, and
+<em><a href="r.coin.html">r.coin</a></em>.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
To rescale an elevation raster map layer with category
values ranging from 1090 meters to 1800 meters into the
range 0-255, the following command line could be used:
-<DL>
-<DD>
-<B>r.rescale input=</B>elevation <B>from=</B>1090,1800 <B>output=</B>elevation.255 <B>to=</B>0,255
-</DL>
+<dl>
+<dd>
+<b>r.rescale input=</b>elevation <b>from=</b>1090,1800 <b>output=</b>elevation.255 <b>to=</b>0,255
+</dl>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
Category values that fall beyond the input range will
become NULL. This allows the user to select a subset of
the full category value range for rescaling if desired.
This also means that the user should know the category
value range for the input raster map layer. The user can
-request the </B><EM>r.rescale</EM> program to determine
+request the </b><em>r.rescale</em> program to determine
this range, or can obtain it using the
-<EM><A HREF="r.describe.html">r.describe</A></EM> or <EM><a href="r.info.html">r.info</A></EM>
+<em><a href="r.describe.html">r.describe</a></em> or <em><a href="r.info.html">r.info</a></em>
command. If the category value range is determined using
-<EM>r.rescale</EM>, the input raster map layer is examined,
+<em>r.rescale</em>, the input raster map layer is examined,
and the minimum and maximum non-NULL category values are
selected as the input range.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.coin.html">r.coin</A></EM>,
-<EM><A HREF="r.describe.html">r.describe</A></EM>,
-<EM><A HREF="r.info.html">r.info</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.reclass.html">r.reclass</A></EM>,
-<EM><A HREF="r.report.html">r.report</A></EM>,
-<EM><A HREF="r.resample.html">r.resample</A></EM>,
-<EM><A HREF="r.stats.html">r.stats</A></EM>
+<em><a href="r.coin.html">r.coin</a></em>,
+<em><a href="r.describe.html">r.describe</a></em>,
+<em><a href="r.info.html">r.info</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.reclass.html">r.reclass</a></em>,
+<em><a href="r.report.html">r.report</a></em>,
+<em><a href="r.resample.html">r.resample</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro,
U.S.Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.rescale.eq/description.html
===================================================================
--- grass/trunk/raster/r.rescale.eq/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.rescale.eq/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-The <EM>r.rescale.eq</EM> program rescales the range of
+The <em>r.rescale.eq</em> program rescales the range of
category values appearing in a raster map layer with equalized histogram.
A new raster map layer, and an appropriate category file and
color table based upon the original raster map layer, are
@@ -9,52 +9,52 @@
is useful for producing representations with a reduced
number of categories from a raster map layer with a large
range of category values (e.g., elevation).
-<EM>Rescaled</EM> map layers are appropriate for use in
+<em>Rescaled</em> map layers are appropriate for use in
such GRASS programs as
-<EM><A HREF="r.stats.html">r.stats</A></EM>,
-<EM><A HREF="r.report.html">r.report</A></EM>, and
-<EM><A HREF="r.coin.html">r.coin</A></EM>.
+<em><a href="r.stats.html">r.stats</a></em>,
+<em><a href="r.report.html">r.report</a></em>, and
+<em><a href="r.coin.html">r.coin</a></em>.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
To rescale an elevation raster map layer with category
values ranging from 1090 meters to 1800 meters into the
range 0-255, the following command line could be used:
-<DL>
-<DD>
-<B>r.rescale.eq input=</B>elevation <B>from=</B>1090,1800 <B>output=</B>elevation.255 <B>to=</B>0,255
-</DL>
+<dl>
+<dd>
+<b>r.rescale.eq input=</b>elevation <b>from=</b>1090,1800 <b>output=</b>elevation.255 <b>to=</b>0,255
+</dl>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
Category values that fall beyond the input range will
become NULL. This allows the user to select a subset of
the full category value range for rescaling if desired.
This also means that the user should know the category
value range for the input raster map layer. The user can
-request the </B><EM>r.rescale.eq</EM> program to determine
+request the </b><em>r.rescale.eq</em> program to determine
this range, or can obtain it using the
-<EM><A HREF="r.describe.html">r.describe</A></EM> or
-<EM><A HREF="r.info.html">r.info</A></EM>
+<em><a href="r.describe.html">r.describe</a></em> or
+<em><a href="r.info.html">r.info</a></em>
command. If the category value range is determined using
-<EM>r.rescale.eq</EM>, the input raster map layer is examined,
+<em>r.rescale.eq</em>, the input raster map layer is examined,
and the minimum and maximum non-NULL category values are
selected as the input range.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.coin.html">r.coin</A></EM>,
-<EM><A HREF="r.describe.html">r.describe</A></EM>,
-<EM><A HREF="r.info.html">r.info</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.reclass.html">r.reclass</A></EM>,
-<EM><A HREF="r.report.html">r.report</A></EM>,
-<EM><A HREF="r.resample.html">r.resample</A></EM>,
-<EM><A HREF="r.stats.html">r.stats</A></EM>
+<em><a href="r.coin.html">r.coin</a></em>,
+<em><a href="r.describe.html">r.describe</a></em>,
+<em><a href="r.info.html">r.info</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.reclass.html">r.reclass</a></em>,
+<em><a href="r.report.html">r.report</a></em>,
+<em><a href="r.resample.html">r.resample</a></em>,
+<em><a href="r.stats.html">r.stats</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro,
U.S.Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.series/description.html
===================================================================
--- grass/trunk/raster/r.series/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.series/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.series</EM> makes each output cell value a function of the values
+<em>r.series</em> makes each output cell value a function of the values
assigned to the corresponding cells in the input raster map layers.
Following methods are available:
@@ -24,42 +24,42 @@
<li>max_raster: raster map number with the maximum time-series value
</ul>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-With <EM>-n</EM> flag, any cell for which any of the corresponding input cells are
+With <em>-n</em> flag, any cell for which any of the corresponding input cells are
NULL is automatically set to NULL (NULL propagation). The aggregate function is not
-called, so all methods behave this way with respect to the <EM>-n</EM> flag.
-<P>
-Without <EM>-n</EM> flag, the complete list of inputs for each cell (including
+called, so all methods behave this way with respect to the <em>-n</em> flag.
+<p>
+Without <em>-n</em> flag, the complete list of inputs for each cell (including
NULLs) is passed to the aggregate function. Individual aggregates can
handle data as they choose. Mostly, they just compute the aggregate
over the non-NULL values, producing a NULL result only if all inputs
are NULL.
<p>
-The <EM>min_raster</EM> and <EM>max_raster</EM> methods generate a map with the
+The <em>min_raster</em> and <em>max_raster</em> methods generate a map with the
number of the raster map that holds the minimum/maximum value of the
-time-series. The numbering starts at <EM>0</EM> up to <EM>n</EM> for the
-first and the last raster listed in <EM>input=</EM>, respectively.
+time-series. The numbering starts at <em>0</em> up to <em>n</em> for the
+first and the last raster listed in <em>input=</em>, respectively.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
-Using <EM>r.series</EM> with wildcards:
+Using <em>r.series</em> with wildcards:
<br>
<tt>r.series input="`g.mlist pattern='insitu_data.*' sep=,`"
output=insitu_data.stddev method=stddev</tt>
-<P>
+<p>
-Note the <EM>g.mlist</EM> script also supports regular expressions for
+Note the <em>g.mlist</em> script also supports regular expressions for
selecting map names.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.mlist.html">g.mlist</A></EM>,
-<EM><A HREF="g.region.html">g.region</A></EM>
+<em><a href="g.mlist.html">g.mlist</a></em>,
+<em><a href="g.region.html">g.region</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Glynn Clements
Modified: grass/trunk/raster/r.statistics/description.html
===================================================================
--- grass/trunk/raster/r.statistics/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.statistics/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.statistics</EM> is a tool to analyse exploratory statistics of a "cover
+<em>r.statistics</em> is a tool to analyse exploratory statistics of a "cover
layer" according to how it intersects with objects in a "base layer". A
variety of standard statistical measures are possible (called "zonal statistics"
in some GIS).
@@ -8,8 +8,8 @@
All cells in the base layer are considered one object for the analysis. For
some applications, one will first want to prepare the input data so that
all areas of contiguous cell category values in the base layer are uniquely
-identified, which can be done with <EM>r.clump</EM>.
-<BR>
+identified, which can be done with <em>r.clump</em>.
+<br>
The available methods are the following (english - german):
<ul>
@@ -29,19 +29,19 @@
The calculations will be performed on each area of data of the
cover layers which fall within each unique value, or category, of the base layer.
-<P>
-Setting the <EM>-c</EM> flag the category lables of the covering raster
+<p>
+Setting the <em>-c</em> flag the category lables of the covering raster
layer will be used. This is nice to avoid the GRASS limitation to interger
in raster maps because using category values floating point numbers can be
stored.
-<P>
+<p>
All calculations except "distribution" create an output layer. The output
layer is a reclassified version of the base layer with identical
category values, but modified category labels - the results of the calculations
are stored in the category labels of the output layer.
-<P>
+<p>
For distributions, the output is printed to the user interface (stdout).
If an output file name was specified, it will be ignored. The result will
be a text table with three columns.
@@ -69,7 +69,7 @@
To transfer the values stored as category labels into cell values,
<em>r.mapcalc</em> can be used ('@' operator).
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
Calculation of average elevation of each field in the Spearfish region:
@@ -80,19 +80,19 @@
r.univar fieldelev
</pre></div>
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="r.average.html">r.average</A>,
-<A HREF="r.clump.html">r.clump</A>,
-<A HREF="r.mode.html">r.mode</A>,
-<A HREF="r.median.html">r.median</A>,
-<A HREF="r.mapcalc.html">r.mapcalc</A>,
-<A HREF="r.neighbors.html">r.neighbors</A>,
-<A HREF="r.univar.html">r.univar</A>
-<A HREF="r.category">r.category</A>
-</EM>
+<h2>SEE ALSO</h2>
+<em>
+<a href="r.average.html">r.average</a>,
+<a href="r.clump.html">r.clump</a>,
+<a href="r.mode.html">r.mode</a>,
+<a href="r.median.html">r.median</a>,
+<a href="r.mapcalc.html">r.mapcalc</a>,
+<a href="r.neighbors.html">r.neighbors</a>,
+<a href="r.univar.html">r.univar</a>
+<a href="r.category">r.category</a>
+</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Martin Schroeder, Geographisches Institut Heidelberg, Germany
<p><i>Last changed: $Date$</i></p>
Modified: grass/trunk/raster/r.stats/description.html
===================================================================
--- grass/trunk/raster/r.stats/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.stats/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.stats</EM> calculates the area present in each of the categories of
+<em>r.stats</em> calculates the area present in each of the categories of
user-selected raster map layer(s). Area statistics are given in units of
square meters and/or cell counts. This analysis uses the current geographic
region and mask settings. Output can be sent to a file in the user's current
@@ -8,21 +8,21 @@
If a single map layer is specified on the command line, a list of areas in
square meters (assuming the map's coordinate system is in meters) for each
-category in the raster map layer will be printed. (If the <EM>-c</EM> option
+category in the raster map layer will be printed. (If the <em>-c</em> option
is chosen, areas will be stated in number of cells.) If multiple raster map
layers are specified on the command line, a cross-tabulation table of areas
for each combination of categories in the map layers will be printed.
-<P>
+<p>
For example, if one raster map layer were specified, the output would look like:
-<PRE>
+<pre>
1:1350000.00
2:4940000.00
3:8870000.00
-</PRE>
-If three raster map layers <EM>a, b</EM>, and <EM>c</EM>, were specified,
+</pre>
+If three raster map layers <em>a, b</em>, and <em>c</em>, were specified,
the output would look like:
-<PRE>
+<pre>
0:0:0:8027500.00
0:1:0:1152500.00
1:0:0:164227500.00
@@ -36,54 +36,54 @@
3:0:0:17140000.00
3:1:0:11270000.00
3:1:1:2500.00
-</PRE>
+</pre>
Within each grouping, the first field represents the category value of map
-layer <EM>a</EM>, the second represents the category values associated with
-map layer <EM>b</EM>, the third represents category values for map layer
-<EM>c</EM>, and the last field gives the area in square meters for the
+layer <em>a</em>, the second represents the category values associated with
+map layer <em>b</em>, the third represents category values for map layer
+<em>c</em>, and the last field gives the area in square meters for the
particular combination of these three map layers' categories. For example,
above, combination 3,1,1 covered 2500 square meters. Fields are separated by
colons.
-<H2>NOTES</H2>
-<EM>r.stats</EM> works in the current geographic region with the current mask.
+<h2>NOTES</h2>
+<em>r.stats</em> works in the current geographic region with the current mask.
-<P>
+<p>
If a nicely formatted output is desired, pipe the output into a command
which can create columnar output. For example, the command:
-<P>
- <B>r.stats input=</B>a,b,c | pr -3 | cat -s
+<p>
+ <b>r.stats input=</b>a,b,c | pr -3 | cat -s
-<P>
+<p>
will create a three-column output
-<PRE>
+<pre>
1:4:4:10000.00 2:1:5:290000.00 2:4:5:2090000.00
1:4:5:1340000.00 2:2:5:350000.00 3:1:2:450000.00
2:1:1:1090000.00 2:4:1:700000.00 3:1:3:5280000.00
2:1:3:410000.00 2:4:3:10000.00 3:1:5:3140000.00
-</PRE>
+</pre>
-The output from <EM>r.stats</EM> on more than one map layer is sorted.
+The output from <em>r.stats</em> on more than one map layer is sorted.
-<P>
+<p>
Note that the user has only the option of printing out cell statistics in
terms of cell counts and/or area totals. Users wishing to use different
units than are available here should use the GRASS program
-<EM><A HREF="r.report.html">r.report</A></EM>.
+<em><a href="r.report.html">r.report</a></em>.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="g.region.html">g.region</A>,
-<A HREF="r.coin.html">r.coin</A>,
-<A HREF="r.describe.html">r.describe</A>,
-<A HREF="r.report.html">r.report</A>,
-<A HREF="r.statistics.html">r.statistics</A>,
-<A HREF="r.univar.html">r.univar</A>
-</EM>
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="r.coin.html">r.coin</a>,
+<a href="r.describe.html">r.describe</a>,
+<a href="r.report.html">r.report</a>,
+<a href="r.statistics.html">r.statistics</a>,
+<a href="r.univar.html">r.univar</a>
+</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.sum/description.html
===================================================================
--- grass/trunk/raster/r.sum/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.sum/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,14 +1,14 @@
-<H2>DESCRIPTION</H2>
-<B><EM>r.sum</EM></B> sums up the raster cell values.
+<h2>DESCRIPTION</h2>
+<b><em>r.sum</em></b> sums up the raster cell values.
For example, it can be used to summarize the population
of a country. Using a raster MASK, raster areas can be
easily selected for the summary.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.surf.area.html">r.surf.area</A></EM>
+<em><a href="r.surf.area.html">r.surf.area</a></em>
-<H2>AUTHOR</H2>
-<A HREF=mailto:brown at gis.uiuc.edu>Bill Brown</A>, UIUC GIS Laboratory
+<h2>AUTHOR</h2>
+<a href=mailto:brown at gis.uiuc.edu>Bill Brown</a>, UIUC GIS Laboratory
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.sun/description.html
===================================================================
--- grass/trunk/raster/r.sun/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.sun/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -10,7 +10,7 @@
for the earth curvature is internally calucated.<br>
The units of the parameters are specified in brackets, a hyphen in the brackets
explains that the parameter has no units.
-<P>
+<p>
For latitude-longitude coordinates it requires that the elevation map is in meters.
The rules are:
<ul>
@@ -18,7 +18,7 @@
<li> Other coordinates: elevation in the same unit as the easting-northing coordinates.
</ul>
-<P>
+<p>
The solar geometry of the model is based on the works of Krcho (1990), later
improved by Jenco (1992). The equations describing Sun – Earth position as
well as an interaction of the solar radiation with atmosphere were originally
@@ -134,7 +134,7 @@
</p>
<h2> OPTIONS</h2>
-<P>Currently, there are two modes of r.sun.
+<p>Currently, there are two modes of r.sun.
In the first mode it calculates solar incidence angle and solar irradiance
raster maps using the set local time. In the second mode daily sums of solar
irradiation [Wh.m-2.day-1] are computed for a specified day.</p>
@@ -173,7 +173,7 @@
city 3.1 3.2 3.5 4.0 4.2 4.3 4.4 4.3 4.0 3.6 3.3 3.1 3.75 <br>
industrial 4.1 4.3 4.7 5.3 5.5 5.7 5.8 5.7 5.3 4.9 4.5 4.2 5.00
</pre>
-<P>
+<p>
Planned improvements include the use of the SOLPOS algorithm for solar
geometry calculations and internal computation of aspect and slope.
@@ -182,7 +182,7 @@
(incidout). Areas with zero values are shadowed. The <em>-s</em> flag
has to be used.
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
Nice looking maps can be created with the model's output as follows:
<div class="code"><pre>
Modified: grass/trunk/raster/r.sunmask/description.html
===================================================================
--- grass/trunk/raster/r.sunmask/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.sunmask/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<em>r.sunmask</em> creates an output map layer based on an input elevation
raster map layer and the sun position. The output map layer contains the
@@ -10,7 +10,7 @@
to specify date/time for sun position calculation by r.sunmask itself have
to be used.
-<P>
+<p>
The module performs sunset/sunrise checks and refraction correction for sun
position calculation. Local coordinate systems are internally transformed to
latitude/longitude for the SOLPOS algorithm. The elevation is not considered
@@ -31,7 +31,7 @@
not specified, the map center's coordinates will be used.
Also <em>g.region -l</em> displays the map center's coordinates.
-<P>
+<p>
Note for module usage with <em>-g</em> flag and calculations
close to sunset/sunrise:
@@ -59,14 +59,14 @@
Acknowledgements: National Renewable Energy Laboratory for their <a href=http://rredc.nrel.gov/solar/codes_algs/solpos/>SOLPOS 2.0</a> sun position
algorithm.
-<H2>SEE ALSO</H2>
-<EM>
+<h2>SEE ALSO</h2>
+<em>
<a href="g.region.html">g.region</a>,
<a href="r.sun.html">r.sun</a>,
<a href="r.slope.aspect.html">r.slope.aspect</a>
-</EM>
+</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Janne Soimasuo, Finland 1994<br>
update to FP by Huidae Cho 2001<br>
added solpos algorithm feature by Markus Neteler 2001
Modified: grass/trunk/raster/r.support.stats/description.html
===================================================================
--- grass/trunk/raster/r.support.stats/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.support.stats/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -16,7 +16,7 @@
<h2>AUTHORS</h2>
-Micharl Shapiro, CERL: Original author<BR>
-<a href="MAILTO:rez at touchofmadness.com">Brad Douglas</a>: GRASS 6 Port<BR>
+Micharl Shapiro, CERL: Original author<br>
+<a href="MAILTO:rez at touchofmadness.com">Brad Douglas</a>: GRASS 6 Port<br>
<p><i>Last changed: $Date$</i> </p>
Modified: grass/trunk/raster/r.surf.area/description.html
===================================================================
--- grass/trunk/raster/r.surf.area/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.surf.area/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,65 +1,65 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.surf.area</EM> Calculates area of regular 3D triangulated points
+<em>r.surf.area</em> Calculates area of regular 3D triangulated points
(centers of cells) in current region by adding areas of triangles.
Therefore, area of a flat surface will be reported as
(rows + cols -1)*(area of cell) less than area of
flat region due to a half row and half column missing around the
perimeter.
-<H2>NOTE</H2>
+<h2>NOTE</h2>
This calculation is heavily dependent on
data resolution (think of it as a fractal shoreline problem, the more
resolution the more detail, the more area, etc). This program uses the
-<EM>CURRENT GRASS REGION</EM>, not the resolution of the map. This is
-especially important for surfaces with <TT>NULL</TT> values and highly
+<em>CURRENT GRASS REGION</em>, not the resolution of the map. This is
+especially important for surfaces with <tt>NULL</tt> values and highly
irregular edges. The program does not [currently] attempt to correct for
-the error introduced by this <EM>edge effect</EM>.
+the error introduced by this <em>edge effect</em>.
-<P>
+<p>
This version actually calculates area twice for each triangle pair,
keeping a running minimum and maximum area depending on the
direction of the diagonal used.
-<P>
+<p>
-<OL>
-<LH>Reported totals are:
-<LI>"Plan" area of <TT>NULL</TT> values within the current GRASS region
-<LI>"Plan" area within calculation region (rows-1 * cols-1 * cellarea)
-<LI>Average of the minimum and maximum calculated 3d triangle area
+<ol>
+<lh>Reported totals are:
+<li>"Plan" area of <tt>NULL</tt> values within the current GRASS region
+<li>"Plan" area within calculation region (rows-1 * cols-1 * cellarea)
+<li>Average of the minimum and maximum calculated 3d triangle area
within this region
-<LI>"Plan" area within current GRASS region (rows * cols * cellarea)
-<LI>Scaling of calculated area to current GRASS region (see
-<A HREF="#note">NOTE</A>)
-</OL>
+<li>"Plan" area within current GRASS region (rows * cols * cellarea)
+<li>Scaling of calculated area to current GRASS region (see
+<a href="#note">NOTE</a>)
+</ol>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-<EM>r.surf.area</EM> works best when the surface being evaluated extends
+<em>r.surf.area</em> works best when the surface being evaluated extends
to the edges of the current GRASS region and the cell resolution is small.
Surfaces which are especially long and thin and have highly irregular
boudaries will tend to have underestimated surface areas. Setting a
high cell resolution (small area) will greatly reduce this impact, but will
cause longer processing times.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.sum.html">r.sum</A></EM>,
-<EM><A HREF="r.surf.idw.html">r.surf.idw</A></EM>,
-<EM><A HREF="r.surf.idw2.html">r.surf.idw2</A></EM>,
-<EM><A HREF="r.surf.fractal.html">r.surf.fractal</A></EM>,
-<EM><A HREF="r.surf.gauss.html">r.surf.gauss</A></EM>,
-<EM><A HREF="r.volume.html">r.volume</A></EM>,
-<EM><A HREF="v.to.rast.html">v.to.rast</A></EM>,
-<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM>,
-<EM><A HREF="g.region.html">g.region</A></EM>
+<em><a href="r.sum.html">r.sum</a></em>,
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="r.surf.fractal.html">r.surf.fractal</a></em>,
+<em><a href="r.surf.gauss.html">r.surf.gauss</a></em>,
+<em><a href="r.volume.html">r.volume</a></em>,
+<em><a href="v.to.rast.html">v.to.rast</a></em>,
+<em><a href="r.slope.aspect.html">r.slope.aspect</a></em>,
+<em><a href="g.region.html">g.region</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Bill Brown, USACERL December 21, 1994
-<P>
+<p>
Modified for floating point rasters and <tt>NULL</tt> values by
Eric G. Miller (October 17, 2000)
Modified: grass/trunk/raster/r.surf.contour/description.html
===================================================================
--- grass/trunk/raster/r.surf.contour/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.surf.contour/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.surf.contour</EM> creates a raster elevation map from a rasterized
+<em>r.surf.contour</em> creates a raster elevation map from a rasterized
contour map. Elevation values are determined using procedures similar
to a manual methods.
To determine the elevation of a point on a contour map, an individual
@@ -9,43 +9,43 @@
(uphill and downhill).
-<P>
+<p>
-<EM>r.surf.contour</EM> works in a similar way. Initially, a vector map of
+<em>r.surf.contour</em> works in a similar way. Initially, a vector map of
the contour lines is made with the elevation of each line as an attribute.
-When the program <EM><A HREF="v.to.rast.html">v.to.rast</A></EM>
+When the program <em><a href="v.to.rast.html">v.to.rast</a></em>
is run on the vector map, continuous "lines" of rasters containing the
-contour line values will be the input for <EM>r.surf.contour</EM>. For each
+contour line values will be the input for <em>r.surf.contour</em>. For each
cell in the input map, either the cell is a contour line cell (which is
given that value), or a flood fill is generated from that spot until the
-fill comes to two unique values. So the <EM>r.surf.contour</EM> algorithm
+fill comes to two unique values. So the <em>r.surf.contour</em> algorithm
<strong>linearly interpolates</strong> between contour lines. The flood fill
is not allowed to cross over
the rasterized contour lines, thus ensuring that an uphill and downhill
-contour value will be the two values chosen. <EM>r.surf.contour</EM>
+contour value will be the two values chosen. <em>r.surf.contour</em>
interpolates from the uphill and downhill values by the true distance.
-<H3>Parameters:</H3>
+<h3>Parameters:</h3>
-<DL>
+<dl>
-<DT><B>input=</B><EM>name</EM>
+<dt><b>input=</b><em>name</em>
-<DD>Name of an existing raster map that contains a set of
+<dd>Name of an existing raster map that contains a set of
initial category values (i.e., some cells contain known elevation
values (denoting contours) while the rest contain NULL values or zeros (0)).
-<DT><B>output=</B><EM>name</EM>
+<dt><b>output=</b><em>name</em>
-<DD>Name to be assigned to new output raster map that represents
+<dd>Name to be assigned to new output raster map that represents
a smooth (e.g., elevation) surface generated from
the known category values in the input raster map layer.
-</DL>
+</dl>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-<EM>r.surf.contour</EM> works well under the following circumstances:
+<em>r.surf.contour</em> works well under the following circumstances:
1) the contour lines extend to the the edge of the current region,
2) the program is run at the same resolution as that of the input map,
3) there are no disjointed contour lines,
@@ -53,47 +53,47 @@
the tops of hills and the bottoms of depressions, on the other hand, improve
the output greatly.
Violating these constraints will cause non-intuitive anomalies to appear in
-the output map. Run <EM> <A HREF="r.slope.aspect.html">r.slope.aspect</A>
-</EM> on <EM>r.surf.contour</EM> results to locate potential anomalies.
+the output map. Run <em> <a href="r.slope.aspect.html">r.slope.aspect</a>
+</em> on <em>r.surf.contour</em> results to locate potential anomalies.
-<P>
-The running of <EM>r.surf.contour</EM> is very sensitive to the resolution of
+<p>
+The running of <em>r.surf.contour</em> is very sensitive to the resolution of
rasterized vector map. If multiple contour lines go through the same raster,
-slight anomalies may occur. The speed of <EM>r.surf.contour</EM> is dependent
+slight anomalies may occur. The speed of <em>r.surf.contour</em> is dependent
on how far "apart" the contour lines are from each other (as measured in
raster cells). Since a flood fill algorithm is used, the program's running
time will grow exponentially with the distance between contour lines.
-<H2>BUGS</H2>
+<h2>BUGS</h2>
-<EM>r.surf.contour</EM> has not been fully updated for NULL support and still
+<em>r.surf.contour</em> has not been fully updated for NULL support and still
considers a value of "<tt>0</tt>" to be NULL. Thus any contour lines at 0
elevation (e.g. the coastline) will be ignored. In such cases converting any
-0 values in the input map to -1 with <EM>r.mapcalc</EM> may be a suitable
+0 values in the input map to -1 with <em>r.mapcalc</em> may be a suitable
work-around.
-<P>
-Currently <EM>r.surf.contour</EM> will only produce CELL (integer) map output.
+<p>
+Currently <em>r.surf.contour</em> will only produce CELL (integer) map output.
If you would like a finer grade output map (i.e. floating point) it is
recommended to multiply the <b>input</b> map by 1000 (for example) using
-<em>r.mapcalc</em>, then divide the resultant <EM>r.surf.contour</EM>
-<b>output</b> map by 1000.0, again with <EM>r.mapcalc</EM>.
-<P>
+<em>r.mapcalc</em>, then divide the resultant <em>r.surf.contour</em>
+<b>output</b> map by 1000.0, again with <em>r.mapcalc</em>.
+<p>
Volunteers are sought to remedy both these issues.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.slope.aspect.html">r.slope.aspect</A></EM>,
-<EM><A HREF="r.surf.idw.html">r.surf.idw</A></EM>,
-<EM><A HREF="r.surf.idw2.html">r.surf.idw2</A></EM>,
-<EM><A HREF="v.digit.html">v.digit</A></EM>,
-<EM><A HREF="v.surf.idw.html">v.surf.idw</A></EM>,
-<EM><A HREF="v.surf.rst.html">v.surf.rst</A></EM>,
-<EM><A HREF="v.to.rast.html">v.to.rast</A></EM>
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.slope.aspect.html">r.slope.aspect</a></em>,
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="v.digit.html">v.digit</a></em>,
+<em><a href="v.surf.idw.html">v.surf.idw</a></em>,
+<em><a href="v.surf.rst.html">v.surf.rst</a></em>,
+<em><a href="v.to.rast.html">v.to.rast</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Chuck Ehlschlaeger, U.S. Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.surf.fractal/description.html
===================================================================
--- grass/trunk/raster/r.surf.fractal/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.surf.fractal/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,41 +1,41 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<b>r.surf.fractal</b> creates a fractal surface of a given fractal
dimension. Uses spectral synthesis method. Can create intermediate layers
showing the build up of different spectral coefficients (see Saupe,
pp.106-107 for an example of this).
-<P>
+<p>
Use this module to generate naturally looking synthetical elevation models
(DEM).
-<H2>NOTE</H2>
+<h2>NOTE</h2>
This module requires the <a href="http://www.fftw.org">FFTW library</a>
for computing Discrete Fourier Transforms.
-<H2>REFERENCE</h2>
+<h2>REFERENCE</h2>
Saupe, D. (1988) Algorithms for random fractals, in Barnsley M.,
Devaney R., Mandelbrot B., Peitgen, H-O., Saupe D., and Voss R.
(1988) The Science of Fractal Images, Ch. 2, pp.71-136. London:
Springer-Verlag.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.surf.contour.html">r.surf.contour</A></EM>,
-<EM><A HREF="r.surf.idw.html">r.surf.idw</A></EM>,
-<EM><A HREF="r.surf.gauss.html">r.surf.gauss</A></EM>,
-<EM><A HREF="r.surf.random.html">r.surf.random</A></EM>,
-<EM><A HREF="r.surf.idw2.html">r.surf.idw2</A></EM>,
-<EM><A HREF="v.surf.idw.html">v.surf.idw</A></EM>,
-<EM><A HREF="v.surf.rst.html">v.surf.rst</A></EM>
+<em><a href="r.surf.contour.html">r.surf.contour</a></em>,
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
+<em><a href="r.surf.gauss.html">r.surf.gauss</a></em>,
+<em><a href="r.surf.random.html">r.surf.random</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="v.surf.idw.html">v.surf.idw</a></em>,
+<em><a href="v.surf.rst.html">v.surf.rst</a></em>
-<ADDRESS>
-<A HREF="MAILTO:jwo at le.ac.uk">jwo at le.ac.uk</A></ADDRESS>
+<address>
+<a href="MAILTO:jwo at le.ac.uk">jwo at le.ac.uk</a></address>
-<BR><A HREF="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</A>
+<br><a href="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</a>
<p>
<i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.surf.gauss/description.html
===================================================================
--- grass/trunk/raster/r.surf.gauss/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.surf.gauss/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,23 +1,23 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<b>r.surf.gauss</b> produces a raster map layer of gaussian deviates whose
mean and standard deviation can be expressed by the user. It uses a gaussian
random number generator. It is essentialy the same as r.surf.random, but uses
a gaussian random number generator instead.
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.surf.contour.html">r.surf.contour</A></EM>,
-<EM><A HREF="r.surf.fractal.html">r.surf.fractal</A></EM>,
-<EM><A HREF="r.surf.idw.html">r.surf.idw</A></EM>,
-<EM><A HREF="r.surf.idw2.html">r.surf.idw2</A></EM>,
-<EM><A HREF="r.surf.random.html">r.surf.random</A></EM>,
-<EM><A HREF="v.surf.rst.html">v.surf.rst</A></EM>
+<h2>SEE ALSO</h2>
+<em><a href="r.surf.contour.html">r.surf.contour</a></em>,
+<em><a href="r.surf.fractal.html">r.surf.fractal</a></em>,
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="r.surf.random.html">r.surf.random</a></em>,
+<em><a href="v.surf.rst.html">v.surf.rst</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
-<ADDRESS>
-<A HREF="MAILTO:jwo at le.ac.uk">jwo at le.ac.uk</A></ADDRESS>
+<address>
+<a href="MAILTO:jwo at le.ac.uk">jwo at le.ac.uk</a></address>
-<BR><A HREF="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</A>
+<br><a href="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</a>
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.surf.idw/description.html
===================================================================
--- grass/trunk/raster/r.surf.idw/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.surf.idw/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,7 +1,7 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.surf.idw</EM> fills a grid cell (raster) matrix with
+<em>r.surf.idw</em> fills a grid cell (raster) matrix with
interpolated values generated from a set of input layer
data points. It uses a numerical approximation technique
based on distance squared weighting of the values of
@@ -9,7 +9,7 @@
to determined the interpolated value of a cell can be
specified by the user (default: 12 nearest data points).
-<P>
+<p>
If there is a current working mask, it applies to the output
raster map. Only those cells falling within the mask will be
@@ -17,18 +17,18 @@
selection of nearest neighboring points will consider all
input data, without regard to the mask.
-The <B>-e</B> flag is the error analysis option that interpolates values
+The <b>-e</b> flag is the error analysis option that interpolates values
only for those cells of the input raster map which have non-zero values and
-outputs the difference (see <A HREF="#minuse.html">NOTES</A> below).
-<P>
-The <B>npoints</B> parameter defines the number of nearest data points used
+outputs the difference (see <a href="#minuse.html">NOTES</a> below).
+<p>
+The <b>npoints</b> parameter defines the number of nearest data points used
to determine the interpolated value of an output raster cell.
-<A NAME="notes.html"><H2>NOTES</H2></A>
+<A NAME="notes.html"><h2>NOTES</h2></a>
-<EM>r.surf.idw</EM> is a surface generation utility which
+<em>r.surf.idw</em> is a surface generation utility which
uses inverse distance squared weighting (as described in
-<B>Applied Geostatistics</B> by E. H. Isaaks and R. M.
+<b>Applied Geostatistics</b> by E. H. Isaaks and R. M.
Srivastava, Oxford University Press, 1989) to assign
interpolated values. The implementation includes a
customized data structure somewhat akin to a sparse matrix
@@ -37,34 +37,34 @@
distances are calculated from point to point along a
geodesic.
-<P>
+<p>
-Unlike <EM><A HREF="r.surf.idw2.html">r.surf.idw2</A></EM>, which processes
-all input data points in each interpolation cycle, <EM>r.surf.idw</EM>
+Unlike <em><a href="r.surf.idw2.html">r.surf.idw2</a></em>, which processes
+all input data points in each interpolation cycle, <em>r.surf.idw</em>
attempts to minimize the number of input data for which distances must be
calculated. Execution speed is therefore a function of the search effort,
and does not increase appreciably with the number of input data points.
-<P>
+<p>
-<EM>r.surf.idw</EM> will generally outperform <EM><A
-HREF="r.surf.idw2.html">r.surf.idw2</A></EM> except when the input data
+<em>r.surf.idw</em> will generally outperform <em><A
+HREF="r.surf.idw2.html">r.surf.idw2</a></em> except when the input data
layer contains few non-zero data, i.e. when the cost of the search exceeds
-the cost of the additional distance calculations performed by <EM><A
-HREF="r.surf.idw2.html">r.surf.idw2</A></EM>. The relative performance of
+the cost of the additional distance calculations performed by <em><A
+HREF="r.surf.idw2.html">r.surf.idw2</a></em>. The relative performance of
these utilities will depend on the comparative speed of boolean, integer and
floating point operations on a particular platform.
-<P>
+<p>
-Worst case search performance by <EM>r.surf.idw</EM> occurs
+Worst case search performance by <em>r.surf.idw</em> occurs
when the interpolated cell is located outside of the region
in which input data are distributed. It therefore behooves
the user to employ a mask when geographic region boundaries
include large areas outside the general extent of the input
data.
-<P>
+<p>
The degree of smoothing produced by the interpolation will
increase relative to the number of nearest data points
@@ -73,9 +73,9 @@
for the former may include unacceptable nonconformities in
the surface pattern.
-<P>
+<p>
-The <A NAME="minuse.html"><B>-e</B></A> flag option provides a standard
+The <A NAME="minuse.html"><b>-e</b></a> flag option provides a standard
surface-generation error analysis facility. It produces an output raster map
of the difference of interpolated values minus input values for those cells
whose input data are non-zero. For each interpolation cycle, the known value
@@ -85,26 +85,26 @@
This procedure may be helpful in choosing the number of nearest neighbors
considered for surface generation.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.surf.contour.html">r.surf.contour</A></EM>,
-<EM><A HREF="r.surf.idw2.html">r.surf.idw2</A></EM>,
-<EM><A HREF="r.surf.gauss.html">r.surf.gauss</A></EM>,
-<EM><A HREF="r.surf.fractal.html">r.surf.fractal</A></EM>,
-<EM><A HREF="r.surf.random.html">r.surf.random</A></EM>,
-<EM><A HREF="v.surf.idw.html">v.surf.idw</A></EM>,
-<EM><A HREF="v.surf.rst.html">v.surf.rst</A></EM>
+<em><a href="r.surf.contour.html">r.surf.contour</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="r.surf.gauss.html">r.surf.gauss</a></em>,
+<em><a href="r.surf.fractal.html">r.surf.fractal</a></em>,
+<em><a href="r.surf.random.html">r.surf.random</a></em>,
+<em><a href="v.surf.idw.html">v.surf.idw</a></em>,
+<em><a href="v.surf.rst.html">v.surf.rst</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Greg Koerper
-<BR>
+<br>
Global Climate Research Project
-<BR>
+<br>
U.S. EPA Environmental Research Laboratory
-<BR>
+<br>
200 S.W. 35th Street, JSB
-<BR>
+<br>
Corvallis, OR 97333
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.surf.idw2/description.html
===================================================================
--- grass/trunk/raster/r.surf.idw2/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.surf.idw2/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.surf.idw2</EM> fills a raster matrix with
+<em>r.surf.idw2</em> fills a raster matrix with
interpolated values generated from a set of irregularly
spaced data points using numerical approximation (weighted
averaging) techniques. The interpolated value of a cell is
@@ -14,11 +14,11 @@
apply to most spatial data.
-The <B>npoints</B> parameter defines the number of points to use for
+The <b>npoints</b> parameter defines the number of points to use for
interpolation. The default is to use the 12 nearest points when
interpolating the value for a particular cell.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
The amount of memory used by this program is related to the
number of non-zero data values in the input map layer. If
@@ -28,40 +28,40 @@
required to execute increases with the number of input data
points.
-<P>
+<p>
If the user has a mask set, then interpolation is only done
for those cells that fall within the mask. However, all
non-zero data points in the input layer are used even if
they fall outside the mask.
-<P>
+<p>
This program does not work with latitude/longitude data
bases. Another surface generation program, named
-<EM><A HREF="r.surf.idw.html">r.surf.idw</A></EM>,
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
should be used with latitude/longitude data bases.
-<P>
+<p>
The user should refer to the manual entries for <br>
-<EM><A HREF="r.surf.idw.html">r.surf.idw</A></EM><br>
-<EM><A HREF="r.surf.contour.html">r.surf.contour</A></EM><br>
-<EM><A HREF="v.surf.rst.html">v.surf.rst</A></EM> <br>to
+<em><a href="r.surf.idw.html">r.surf.idw</a></em><br>
+<em><a href="r.surf.contour.html">r.surf.contour</a></em><br>
+<em><a href="v.surf.rst.html">v.surf.rst</a></em> <br>to
compare this surface generation program with others available in GRASS.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.surf.contour.html">r.surf.contour</A></EM>,
-<EM><A HREF="r.surf.idw.html">r.surf.idw</A></EM>,
-<EM><A HREF="r.surf.gauss.html">r.surf.gauss</A></EM>,
-<EM><A HREF="r.surf.fractal.html">r.surf.fractal</A></EM>,
-<EM><A HREF="r.surf.random.html">r.surf.random</A></EM>,
-<EM><A HREF="r.surf.idw2.html">r.surf.idw2</A></EM>,
-<EM><A HREF="v.surf.rst.html">v.surf.rst</A></EM>
+<em><a href="r.surf.contour.html">r.surf.contour</a></em>,
+<em><a href="r.surf.idw.html">r.surf.idw</a></em>,
+<em><a href="r.surf.gauss.html">r.surf.gauss</a></em>,
+<em><a href="r.surf.fractal.html">r.surf.fractal</a></em>,
+<em><a href="r.surf.random.html">r.surf.random</a></em>,
+<em><a href="r.surf.idw2.html">r.surf.idw2</a></em>,
+<em><a href="v.surf.rst.html">v.surf.rst</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro, U.S.Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.surf.random/description.html
===================================================================
--- grass/trunk/raster/r.surf.random/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.surf.random/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,35 +1,35 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<B>r.surf.random</B> produces a raster map layer of uniform random deviates
+<b>r.surf.random</b> produces a raster map layer of uniform random deviates
whose range can be expressed by the user. It is essentialy the same as
<em>r.surf.gauss</em>, but uses a linear random number generator instead.
It uses the random number generator drand48() or rand()<!-- cite? -->,
depending on the user's platform.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="r.surf.contour.html">r.surf.contour</A>,
-<A HREF="r.surf.fractal.html">r.surf.fractal</A>,
-<A HREF="r.surf.gauss.html">r.surf.gauss</A>,
-<A HREF="r.surf.idw.html">r.surf.idw</A>,
-<A HREF="r.surf.idw2.html">r.surf.idw2</A>,
-<A HREF="v.surf.rst.html">v.surf.rst</A>
-</EM>
+<em>
+<a href="r.surf.contour.html">r.surf.contour</a>,
+<a href="r.surf.fractal.html">r.surf.fractal</a>,
+<a href="r.surf.gauss.html">r.surf.gauss</a>,
+<a href="r.surf.idw.html">r.surf.idw</a>,
+<a href="r.surf.idw2.html">r.surf.idw2</a>,
+<a href="v.surf.rst.html">v.surf.rst</a>
+</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
-Jo Wood<BR>
-Midlands Regional Research Laboratory (ASSIST)<BR>
-University of Leicester<BR>
+Jo Wood<br>
+Midlands Regional Research Laboratory (ASSIST)<br>
+University of Leicester<br>
<i>October 1991</i>
-<BR>
+<br>
<!-- almost certainly no longer valid
-<ADDRESS>jwo at le.ac.uk</ADDRESS>
+<address>jwo at le.ac.uk</address>
-<BR><A HREF="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</A>
+<br><a href="http://www.geog.le.ac.uk/assist/index.html">ASSIST's home</a>
-->
<p>
Modified: grass/trunk/raster/r.terraflow/description.html
===================================================================
--- grass/trunk/raster/r.terraflow/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.terraflow/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,18 +1,18 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<p><EM>r.terraflow</EM> takes as input a raster digital elevation
+<p><em>r.terraflow</em> takes as input a raster digital elevation
model (DEM) and computes the flow direction raster and the flow
accumulation raster, as well as the flooded elevation raster,
sink-watershed raster (partition into watersheds around sinks) and tci
(topographic convergence index) raster.
-<p><EM>r.terraflow</EM> computes these rasters using well-known
+<p><em>r.terraflow</em> computes these rasters using well-known
approaches, with the difference that its emphasis is on the
computational complexity of the algorithms, rather than on modeling
-realistic flow. <EM>r.terraflow</EM> emerged from the necessity of
+realistic flow. <em>r.terraflow</em> emerged from the necessity of
having scalable software able to process efficiently very large
terrains. It is based on theoretically optimal algorithms developed
-in the framework of I/O-efficient algorithms. <EM>r.terraflow</EM>
+in the framework of I/O-efficient algorithms. <em>r.terraflow</em>
was designed and optimized especially for massive grids and is able to
process terrains which were impractical with similar functions
existing in other GIS systems.
@@ -42,19 +42,19 @@
cells which have the same height as all their neighbors (flat areas)
or cells which do not have downslope neighbors (one-cell pits).
<ul>
- <li>On plateaus (flat areas that spill out) <EM>r.terraflow</EM>
+ <li>On plateaus (flat areas that spill out) <em>r.terraflow</em>
routes flow so that globally the flow goes towards the spill cells of
the plateaus.
<li>On sinks (flat areas that do not spill out, including one-cell
-pits) <EM>r.terraflow</EM> assigns flow by flooding the terrain until
+pits) <em>r.terraflow</em> assigns flow by flooding the terrain until
all the sinks are filled and assigning flow directions on the filled
terrain.
</ul>
<p>
-In order to flood the terrain, <EM>r.terraflow</EM> identifies all
+In order to flood the terrain, <em>r.terraflow</em> identifies all
sinks and partitions the terrain into sink-watersheds (a
sink-watershed contains all the cells that flow into that sink),
builds a graph representing the adjacency information of the
@@ -67,11 +67,11 @@
<p>
Once flow directions are computed for every cell in the terrain,
-<EM>r.terraflow</EM> computes flow accumulation by routing water using
+<em>r.terraflow</em> computes flow accumulation by routing water using
the flow directions and keeping track of how much water flows through
each cell.
-<P>
+<p>
If flow accumulation of a cell is larger than the value given by the
<b>d8cut</b> option, then
the flow of this cell is routed to its neighbors using the SFD (D8)
@@ -80,8 +80,8 @@
this option is used for SFD flow it is ignored. The default value of
<b>d8cut</b> is <i>infinity</i>.
-<P>
-<EM>r.terraflow</EM> also computes the tci raster (topographic convergence
+<p>
+<em>r.terraflow</em> also computes the tci raster (topographic convergence
index, defined as the logarithm of the ratio of flow accumulation and
local slope).
@@ -90,77 +90,77 @@
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-One of the techniques used by <EM>r.terraflow</EM> is the
+One of the techniques used by <em>r.terraflow</em> is the
space-time trade-off. In particular, in order to avoid searches, which
-are I/O-expensive, <EM>r.terraflow</EM> computes and works with an
+are I/O-expensive, <em>r.terraflow</em> computes and works with an
augmented elevation raster in which each cell stores relevant
information about its 8 neighbors, in total up to 80B per cell. As a
-result <EM>r.terraflow</EM> works with intermediate temporary files
+result <em>r.terraflow</em> works with intermediate temporary files
that may be up to 80N bytes, where N is the number of cells (rows x
columns) in the elevation raster (more precisely, 80K bytes, where K
is the number of valid (not no-data) cells in the input elevation
raster).
-<P>
+<p>
All these intermediate temporary files are stored in the path specified
by the <b>STREAM_DIR</b> option. Note: <b>STREAM_DIR</b> must contain
enough free disk space in order to store up to 2 x 80N bytes.
-<P>
+<p>
The <b>memory</b> option can be used to set the maximum amount of main
memory (RAM) the module will use during processing. In practice its
-<I>value</I> should be an underestimate of the amount of available
-(free) main memory on the machine. <EM>r.terraflow</EM> will use at
+<i>value</i> should be an underestimate of the amount of available
+(free) main memory on the machine. <em>r.terraflow</em> will use at
all times at most this much memory, and the virtual memory system
(swap space) will never be used. The default value is 300 MB.
<p>
-The internal type used by <EM>r.terraflow</EM> to store elevations
-can be defined at compile-time. By default, <EM>r.terraflow</EM> is
+The internal type used by <em>r.terraflow</em> to store elevations
+can be defined at compile-time. By default, <em>r.terraflow</em> is
compiled to store elevations internally as floats.
A version which is compiled to store elevations internally as
-shorts is available as <EM>r.terraflow.short</EM>. Other versions can
+shorts is available as <em>r.terraflow.short</em>. Other versions can
be created by the user if needed.
<p>
-<EM>r.terraflow.short</EM> uses less space (up to 60B per cell, up
+<em>r.terraflow.short</em> uses less space (up to 60B per cell, up
to 60N intermediate file) and therefore is more space and time
-efficient. <EM>r.terraflow</EM> is intended for use with floating
-point raster data (FCELL), and <EM>r.terraflow.short</EM> with integer
+efficient. <em>r.terraflow</em> is intended for use with floating
+point raster data (FCELL), and <em>r.terraflow.short</em> with integer
raster data (CELL) in which the maximum elevation does not exceed the
value of a short SHRT_MAX=32767 (this is not a constraint for any
terrain data of the Earth, if elevation is stored in meters).
<p>
-Both <EM>r.terraflow</EM> and <EM>r.terraflow.short</EM> work with
+Both <em>r.terraflow</em> and <em>r.terraflow.short</em> work with
input elevation rasters which can be either integer, floating point or
double (CELL, FCELL, DCELL). If the input raster contains a value that
exceeds the allowed internal range (short for
-<EM>r.terraflow.short</EM>, float for <EM>r.terraflow</EM>), the
+<em>r.terraflow.short</em>, float for <em>r.terraflow</em>), the
program exits with a warning message. Otherwise, if all values in the
input elevation raster are in range, they will be converted
(truncated) to the internal elevation type (short for
-<EM>r.terraflow.short</EM>, float for <EM>r.terraflow</EM>). In this
+<em>r.terraflow.short</em>, float for <em>r.terraflow</em>). In this
case precision may be lost and artificial flat areas may be created.
<p>
-For instance, if <EM>r.terraflow.short</EM> is used with floating
+For instance, if <em>r.terraflow.short</em> is used with floating
point raster data (FCELL or DCELL), the values of the elevation will
be truncated as shorts. This may create artificial flat areas, and the
-outpus of <EM>r.terraflow.short</EM> may be less realistic than those
-of <EM>r.terraflow</EM> on floating point raster data.
+outpus of <em>r.terraflow.short</em> may be less realistic than those
+of <em>r.terraflow</em> on floating point raster data.
-The outputs of <EM>r.terraflow.short</EM> and <EM>r.terraflow</EM> are
+The outputs of <em>r.terraflow.short</em> and <em>r.terraflow</em> are
identical for integer raster data (CELL maps).
-<P>
+<p>
The <b>stats</b> option defines the name of the file that contains the
statistics (stats) of the run. The default name is <tt>stats.out</tt>
(in the current directory).
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
<div class="code"><pre>
r.terraflow elev=spearfish filled=spearfish-filled \
@@ -177,23 +177,23 @@
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
<ul>
<li>The <a
href="http://www.cs.duke.edu/geo*/terraflow/">TerraFlow</a> project at Duke University
<li><a href=r.flow.html>r.flow</a>,
- <A HREF="r.basins.fill.html">r.basins.fill</A>,
- <A HREF="r.drain.html">r.drain</A>,
+ <a href="r.basins.fill.html">r.basins.fill</a>,
+ <a href="r.drain.html">r.drain</a>,
<a href="r.topidx.html">r.topidx</a>,
<a href="r.topmodel.html">r.topmodel</a>,
- <A HREF="r.water.outlet.html">r.water.outlet</A>,
- <A HREF="r.watershed.html">r.watershed</A>
+ <a href="r.water.outlet.html">r.water.outlet</a>,
+ <a href="r.watershed.html">r.watershed</a>
</ul>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
<dl>
<dt>Original version of program: The <a
@@ -216,32 +216,32 @@
</dl>
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
<ol>
<li><A NAME="arge:drainage"
HREF="http://www.cs.duke.edu/geo*/terraflow/papers/alenex00_drainage.ps.gz">
I/O-efficient algorithms for problems on grid-based
- terrains</A>. Lars Arge, Laura Toma, and Jeffrey S. Vitter. In
- <EM>Proc. Workshop on Algorithm Engineering and Experimentation</EM>,
- 2000. To appear in <EM>Journal of Experimental Algorithms</EM>.
+ terrains</a>. Lars Arge, Laura Toma, and Jeffrey S. Vitter. In
+ <em>Proc. Workshop on Algorithm Engineering and Experimentation</em>,
+ 2000. To appear in <em>Journal of Experimental Algorithms</em>.
<li><A NAME="terraflow:acmgis01"
HREF="http://www.cs.duke.edu/geo*/terraflow/papers/acmgis01_terraflow.pdf">
- Flow computation on massive grids</A>.
+ Flow computation on massive grids</a>.
Lars Arge, Jeffrey S. Chase, Patrick N. Halpin, Laura Toma,
Jeffrey S. Vitter, Dean Urban and Rajiv Wickremesinghe. In
- <EM>Proc. ACM Symposium on Advances in Geographic Information
- Systems</EM>, 2001.
+ <em>Proc. ACM Symposium on Advances in Geographic Information
+ Systems</em>, 2001.
<li><A NAME="terraflow:geoinformatica"
HREF="http://www.cs.duke.edu/geo*/terraflow/papers/journal_terraflow.pdf">
- Flow computation on massive grid terrains</A>.
+ Flow computation on massive grid terrains</a>.
Lars Arge, Jeffrey S. Chase, Patrick N. Halpin, Laura Toma,
Jeffrey S. Vitter, Dean Urban and Rajiv Wickremesinghe.
- To appear in <EM>GeoInformatica, International Journal on
+ To appear in <em>GeoInformatica, International Journal on
Advances of Computer Science for Geographic Information
- Systems</EM>.
+ Systems</em>.
</ol>
Modified: grass/trunk/raster/r.texture/description.html
===================================================================
--- grass/trunk/raster/r.texture/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.texture/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,10 +1,10 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<em>r.texture</em> - Creates map raster with textural features for
user-specified raster map layer. The module calculates textural features
based on spatial dependence matrices at 0, 45, 90, and 135
degrees for a <em>distance</em> (default = 1).
-<P>
+<p>
<!--
<em>r.texture</em> uses the algorithms of <a href="i.texture.html">i.texture</a>.
-->
@@ -17,14 +17,14 @@
computer could run out of memory. Also, make sure that your raster map has
no more than 255 categories. The output consists into four images for each
textural feature, one for every direction.</p>
-<P>
+<p>
A commonly used texture model is based on the so-called grey level co-occurrence
matrix. This matrix is a two-dimensional histogram of grey levels
for a pair of pixels which are separated by a fixed spatial relationship.
The matrix approximates the joint probability distribution of a pair of pixels.
Several texture measures are directly computed from the grey level co-occurrence
matrix.
-<P>
+<p>
The following are brief explanations of texture measures:
<p>
<ul>
@@ -71,7 +71,7 @@
<b>Haralick, R.M., K. Shanmugam, and I. Dinstein</b> (1973). Textural features for
image classification. <em>IEEE Transactions on Systems, Man, and
Cybernetics</em>, SMC-3(6):610-621.
-<P>
+<p>
<b>Bouman C. A., Shapiro M.</b>,(March
1994).A Multiscale Random Field Model for Bayesian Image
Segmentation, IEEE Trans. on Image Processing, vol. 3, no.2.
Modified: grass/trunk/raster/r.thin/description.html
===================================================================
--- grass/trunk/raster/r.thin/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.thin/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,58 +1,58 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.thin</EM> scans the named <EM>input</EM> raster map
+<em>r.thin</em> scans the named <em>input</em> raster map
layer and thins non-zero cells that denote linear features
into linear features having a single cell width.
-<P>
+<p>
-<EM>r.thin</EM> will thin only the non-zero cells of the
-named <EM>input</EM> raster map layer within the current
+<em>r.thin</em> will thin only the non-zero cells of the
+named <em>input</em> raster map layer within the current
geographic region settings. The cell width of the thinned
-<EM>output</EM> raster map layer will be equal to the cell
+<em>output</em> raster map layer will be equal to the cell
resolution of the currently set geographic region. All of
the thinned linear features will have the width of a single
cell.
-<P>
+<p>
-<EM>r.thin</EM> will create a new <EM>output</EM> raster
+<em>r.thin</em> will create a new <em>output</em> raster
data file containing the thinned linear features.
-<EM>r.thin</EM> assumes that linear features are encoded
+<em>r.thin</em> assumes that linear features are encoded
with positive values on a background of 0's in the
-<EM>input</EM> raster data file.
+<em>input</em> raster data file.
-<H2>NOTE</H2>
+<h2>NOTE</h2>
-<EM>r.thin</EM> only creates raster map layers. You will need to run
-<EM><A HREF="r.to.vect.html">r.to.vect</A></EM>
+<em>r.thin</em> only creates raster map layers. You will need to run
+<em><a href="r.to.vect.html">r.to.vect</a></em>
on the resultant raster map to create a vector
-(<EM><A HREF="v.digit.html">v.digit</A></EM>) map layer.
+(<em><a href="v.digit.html">v.digit</a></em>) map layer.
-<P>
-<EM>r.thin</EM> may create small spurs or "dangling lines"
+<p>
+<em>r.thin</em> may create small spurs or "dangling lines"
during the thinning process. These spurs may be removed
(after creating a vector map layer) by
-<EM><A HREF="v.clean.html">v.clean</A></EM>.
+<em><a href="v.clean.html">v.clean</a></em>.
-<P>
+<p>
-<EM>r.thin</EM> creates a 0/1 output map.
+<em>r.thin</em> creates a 0/1 output map.
-<H2>NOTE</H2>
+<h2>NOTE</h2>
This code implements the thinning algorithm described in
"Analysis of Thinning Algorithms Using Mathematical
Morphology" by Ben-Kwei Jang and Ronlad T. Chin in
-<EM>Transactions on Pattern Analysis and Machine
-Intelligence</EM>, vol. 12, No. 6, June 1990. The
+<em>Transactions on Pattern Analysis and Machine
+Intelligence</em>, vol. 12, No. 6, June 1990. The
definition Jang and Chin give of the thinning process is
"successive removal of outer layers of pixels from an
object while retaining any pixels whose removal would alter
the connectivity or shorten the legs of the sceleton."
-<P>
+<p>
The sceleton is finally thinned when the thinning process
converges; i.e., "no further pixels can be removed without
@@ -65,19 +65,19 @@
object is <= n pixels thick, the algorithm should
converge in <= iterations.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="g.region.html">g.region</A></EM>,
-<EM><A HREF="r.to.vect.html">r.to.vect</A></EM>,
-<EM><A HREF="v.clean.html">v.clean</A></EM>,
-<EM><A HREF="v.digit.html">v.digit</A></EM>,
-<EM><A HREF="v.build.html">v.build</A></EM>
+<em><a href="g.region.html">g.region</a></em>,
+<em><a href="r.to.vect.html">r.to.vect</a></em>,
+<em><a href="v.clean.html">v.clean</a></em>,
+<em><a href="v.digit.html">v.digit</a></em>,
+<em><a href="v.build.html">v.build</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Olga Waupotitsch, U.S.Army Construction Engineering Research Laboratory
-<P>
+<p>
The code for finding the bounding box as well as input/output code
was written by Mike Baba (DBA Systems, 1990) and Jean Ezell (USACERL, 1988).
Modified: grass/trunk/raster/r.timestamp/description.html
===================================================================
--- grass/trunk/raster/r.timestamp/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.timestamp/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,17 +1,17 @@
-<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 raster map is printed. If a date argument is
specified, then the timestamp for the raster map is set to the specified
date(s). See EXAMPLES below.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
Strings containing spaces should be quoted. For specifying a range
of time, the two timestamps should be separated by a forward slash.
-To remove the timestamp from a raster map, use <B>date=</b><em>none</em>.
+To remove the timestamp from a raster map, use <b>date=</b><em>none</em>.
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
<b>r.timestamp map=soils</b><br>
Prints the timestamp for the "soils" raster map. If
@@ -32,7 +32,7 @@
Removes the timestamp for the "soils" 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
@@ -98,10 +98,10 @@
<em><a HREF="v.timestamp.html">v.timestamp</a></em>
-<H2>BUGS</H2>
+<h2>BUGS</h2>
Spaces in the timestamp value are required.
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro, <br>
U.S.Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.to.rast3/description.html
===================================================================
--- grass/trunk/raster/r.to.rast3/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.to.rast3/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,11 +1,11 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
Converts 2D raster map(s) into one G3D raster map.
If the 2d and 3d region settings are different,
the 2d resolution will be adjust to the 3d resolution.
<center>
-<img src=r.to.rast3.png border=0><BR>
+<img src=r.to.rast3.png border=0><br>
<table border=0 width=700>
<tr><td><center>
<i>How r.to.rast3 works</i>
@@ -14,7 +14,7 @@
</center>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
Every 2D raster map is copied as one slice to the G3D raster map. Slices
are counted from bottom to the top, so the bottom slice has to be number 1.
<br><br>
@@ -42,15 +42,15 @@
r.to.rast3 input=prec_1,prec_2,prec_3 output=new_3dmap
</pre></div>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="g.region.html">g.region</A>,
-<A HREF="r3.to.rast.html">r3.to.rast</A>,
-<A HREF="r.to.rast3elev.html">r.to.rast3elev</A>
-</EM>
+<em>
+<a href="g.region.html">g.region</a>,
+<a href="r3.to.rast.html">r3.to.rast</a>,
+<a href="r.to.rast3elev.html">r.to.rast3elev</a>
+</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Soeren Gebbert
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.to.rast3elev/description.html
===================================================================
--- grass/trunk/raster/r.to.rast3elev/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.to.rast3elev/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,11 +1,11 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
Creates a 3D volume map based on 2D elevation and value raster maps.
If the 2d and 3d region settings are different,
the 2d resolution will be adjust to the 3d resolution.
<center>
-<img src=r.to.rast3elev.png border=0><BR>
+<img src=r.to.rast3elev.png border=0><br>
<table border=0 width=700>
<tr><td><center>
<i>How r.to.rast3elev works</i>
@@ -14,7 +14,7 @@
</center>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
The hight of the 2D elevation maps will be used to verify the position
within the 3D region. If the cell value of the elevation raster maps is located within the 3d region, the
cell value of the appropriate 2D input raster maps will be written to the associated 3d cell.
@@ -46,13 +46,13 @@
</pre></div>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.to.rast3.html">r.to.rast3</A></EM><br>
-<EM><A HREF="r3.cross.rast.html">r3.cross.rast</A></EM><br>
-<EM><A HREF="g.region.html">g.region</A></EM><br>
+<em><a href="r.to.rast3.html">r.to.rast3</a></em><br>
+<em><a href="r3.cross.rast.html">r3.cross.rast</a></em><br>
+<em><a href="g.region.html">g.region</a></em><br>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Soeren Gebbert
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.to.vect/description.html
===================================================================
--- grass/trunk/raster/r.to.vect/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.to.vect/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,49 +1,49 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.to.vect</EM> scans the named <B>input</B> raster map
+<em>r.to.vect</em> scans the named <b>input</b> raster map
layer, extracts points, lines or area edge features from it, converts data
to GRASS vector format.
-<H3>Points</H3>
+<h3>Points</h3>
-The <EM>r.to.vect</EM> program extracts data from a GRASS raster map layer and stores output
-in a new GRASS <EM>vector</EM> file.
+The <em>r.to.vect</em> program extracts data from a GRASS raster map layer and stores output
+in a new GRASS <em>vector</em> file.
-<H3>Lines</H3>
-<EM>r.to.vect</EM> assumes that the <EM>input</EM> map has been thinned
-using <EM><A HREF="r.thin.html">r.thin</A></EM>.
+<h3>Lines</h3>
+<em>r.to.vect</em> assumes that the <em>input</em> map has been thinned
+using <em><a href="r.thin.html">r.thin</a></em>.
-<P>
+<p>
-<EM>r.to.vect</EM> extracts vectors (aka, "arcs") from a
+<em>r.to.vect</em> extracts vectors (aka, "arcs") from a
raster map. These arcs may represent linear features
(like roads or streams), or may represent area edge
features (like political boundaries, or soil mapping
units).
-<P>
+<p>
-<EM><A HREF="r.thin.html">r.thin</A></EM> and <EM>r.to.vect</EM>
+<em><a href="r.thin.html">r.thin</a></em> and <em>r.to.vect</em>
may create excessive nodes at every junction, and may create small spurs
or "dangling lines" during the thinning and vectorization process.
These excessive nodes and spurs may be removed using
-<EM><A HREF="v.clean.html">v.clean</A></EM>.
+<em><a href="v.clean.html">v.clean</a></em>.
-<H3>Areas</H3>
+<h3>Areas</h3>
-<EM>r.to.vect</EM> first traces the perimeter of each unique
+<em>r.to.vect</em> first traces the perimeter of each unique
area in the raster map layer and creates vector data to
represent it. The cell category values for the raster map
layer will be used to create attribute information for the
resultant vector area edge data.
-<P>
+<p>
A true vector tracing of the area edges might appear
blocky, since the vectors outline the edges of raster data
that are stored in rectangular cells. To produce a
-better-looking vector map, <EM>r.to.vect</EM> smoothes the
+better-looking vector map, <em>r.to.vect</em> smoothes the
corners of the vector data as they are being extracted. At
each change in direction (i.e., each corner), the two
midpoints of the corner cell (half the cell's height and
@@ -56,48 +56,48 @@
region (and the original data) to estimate the possible
error introduced by smoothing.
-<P>
+<p>
-<EM>r.to.vect</EM> extracts only area edges from the named raster input file.
+<em>r.to.vect</em> extracts only area edges from the named raster input file.
If the raster map contains other data (i.e., line edges, or point data) the
output may be wrong.
-<H2>BUGS</H2>
+<h2>BUGS</h2>
For feature=line the input raster map MUST be thinned by
-<EM><A HREF="r.thin.html">r.thin</A></EM>;
-if not, <EM>r.to.vect</EM> may crash.
+<em><a href="r.thin.html">r.thin</a></em>;
+if not, <em>r.to.vect</em> may crash.
-<H2>AUTHOR</H2>
-<B>Points</B><BR>
-Bill Brown<BR>
-<BR>
+<h2>AUTHOR</h2>
+<b>Points</b><br>
+Bill Brown<br>
+<br>
-<B>Lines</B><BR>
-Mike Baba<BR>
-DBA Systems, Inc.<BR>
-10560 Arrowhead Drive<BR>
-Fairfax, Virginia 22030<BR>
-<BR>
+<b>Lines</b><br>
+Mike Baba<br>
+DBA Systems, Inc.<br>
+10560 Arrowhead Drive<br>
+Fairfax, Virginia 22030<br>
+<br>
-<B>Areas</B><BR>
-<EM>Original</EM> version of <EM>r.poly</EM>:
-<BR>
+<b>Areas</b><br>
+<em>Original</em> version of <em>r.poly</em>:
+<br>
Jean Ezell and Andrew Heekin,
<br>
U.S. Army Construction Engineering
Research Laboratory
-<P>
-<EM>Modified</EM> program for smoothed lines:
-<BR>
+<p>
+<em>Modified</em> program for smoothed lines:
+<br>
David Satnik,
Central Washington University
<br>
-Updated 2001 by Andrea Aime, Modena, Italy<BR>
-<BR>
+Updated 2001 by Andrea Aime, Modena, Italy<br>
+<br>
-<B>Update</B><BR>
+<b>Update</b><br>
Original r.to.sites, r.line and r.poly merged and updated to 5.7 by Radim Blazek
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.topidx/description.html
===================================================================
--- grass/trunk/raster/r.topidx/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.topidx/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,29 +1,29 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.topidx</EM> creates topographic index (wetness index), ln(a/tan(beta)), map from
+<em>r.topidx</em> creates topographic index (wetness index), ln(a/tan(beta)), map from
elevation map
-<P>
+<p>
where
-<DL>
-<DD>a: the area of the hillslope per unit contour length that drains through any point,
-<P>
-<DD>tan(beta): the local surface topographic slope (delta vertical) / (delta horizontal).
-</DL>
-<P>
+<dl>
+<dd>a: the area of the hillslope per unit contour length that drains through any point,
+<p>
+<dd>tan(beta): the local surface topographic slope (delta vertical) / (delta horizontal).
+</dl>
+<p>
Input maps may have NULL values. For example, if you have a MASK for
-a watershed (basin map from <EM>r.water.outlet</EM>), the
+a watershed (basin map from <em>r.water.outlet</em>), the
following command will create a masked elevation map (belev):
<div class="code"><pre>
r.mapcalc "belev = if(isnull(basin), basin, elev)"
</pre></div>
-<P>
+<p>
-<EM>r.stats -Anc</EM> prints out averaged statistics for topographic index.
+<em>r.stats -Anc</em> prints out averaged statistics for topographic index.
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.topmodel.html">r.topmodel</A></EM>,
-<EM><A HREF="r.water.outlet.html">r.water.outlet</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>
+<h2>SEE ALSO</h2>
+<em><a href="r.topmodel.html">r.topmodel</a></em>,
+<em><a href="r.water.outlet.html">r.water.outlet</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>
<h2>REFERENCE</h2>
@@ -31,12 +31,12 @@
modeling: A review of hydrological, geomorphological, and biological
applications. Hydrol. Processes 5:3-30.
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
Main algorithm sources are rewritten from GRIDATB.FOR.
-<BR>
+<br>
Thanks to Keith Beven.
-<P>
-GRASS port by <A HREF=mailto:grass4u gmail com>Huidae Cho</A><BR>
+<p>
+GRASS port by <a href=mailto:grass4u gmail com>Huidae Cho</a><br>
Hydro Laboratory, Kyungpook National University, South Korea
<p><i>Last changed: $Date$</i></p>
Modified: grass/trunk/raster/r.topmodel/description.html
===================================================================
--- grass/trunk/raster/r.topmodel/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.topmodel/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,60 +1,60 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<B><EM>r.topmodel</EM></B> simulates TOPMODEL which is a physically based
+<b><em>r.topmodel</em></b> simulates TOPMODEL which is a physically based
hydrologic model.
-<P>
+<p>
Note: (i) means input; (o) means output; (o/i) means input or output
-<P>
-The <B>-i</B> flag indicates that input data are given for (o/i). Without this
+<p>
+The <b>-i</b> flag indicates that input data are given for (o/i). Without this
flag, all inputs (i) and intermediate outputs (o/i) should be given. For
example, [belevation] map will be created from [elevation] and [basin] in every
run. However, given the same [elevation] and [basin], [belevation] output will
be the same all the time, so r.topmodel can directly take [belevation] as an
input with this flag to save time.
-<P>
+<p>
-<H3>Selected Parameters:</H3>
+<h3>Selected Parameters:</h3>
-<DL>
-<DT><B>depressionless</B> map is created as follows:</DT>
-<DD><div class="code"><pre>
+<dl>
+<dt><b>depressionless</b> map is created as follows:</dt>
+<dd><div class="code"><pre>
r.fill.dir input=elevation elev=depressionless dir=direction type=grass
</pre></div>
This option can be omitted if [elevation] map is already depressionless.
-</DD>
-<P>
+</dd>
+<p>
-<DT><B>belevation</B> map is created from [elevation] with [basin] mask applied:</DT>
-<DD><div class="code"><pre>
+<dt><b>belevation</b> map is created from [elevation] with [basin] mask applied:</dt>
+<dd><div class="code"><pre>
r.mapcalc "belevation = if(basin == 0 || isnull(basin), null(), elevation)"
-</pre></div></DD>
-<P>
+</pre></div></dd>
+<p>
-<DT><B>topidx</B> map is created as follows:</DT>
-<DD><div class="code"><pre>
+<dt><b>topidx</b> map is created as follows:</dt>
+<dd><div class="code"><pre>
r.topidx input=elevation output=topidx
-</pre></div></DD>
-<P>
+</pre></div></dd>
+<p>
-<DT><B>Qobs</B></DT>
-<DD>Compare simulated flows with observed flows and calculate model
+<dt><b>Qobs</b></dt>
+<dd>Compare simulated flows with observed flows and calculate model
efficiency.
-</DD>
-<P>
-</DL>
+</dd>
+<p>
+</dl>
-<H2>SEE ALSO</H2>
-<EM><A HREF="r.fill.dir.html">r.fill.dir</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.topidx.html">r.topidx</A></EM>,
-<EM><A HREF="http://geni.ath.cx/r.topmodel.html">How to run r.topmodel</A></EM>
+<h2>SEE ALSO</h2>
+<em><a href="r.fill.dir.html">r.fill.dir</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.topidx.html">r.topidx</a></em>,
+<em><a href="http://geni.ath.cx/r.topmodel.html">How to run r.topmodel</a></em>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
Main algorithm sources are rewritten in C based on TMOD9502.FOR.
-<BR>
+<br>
Thanks to Keith Beven.
-<P>
-GRASS port by <A HREF=mailto:grass4u gmail com>Huidae Cho</A><BR>
+<p>
+GRASS port by <a href=mailto:grass4u gmail com>Huidae Cho</a><br>
Hydro Laboratory, Kyungpook National University, South Korea
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.transect/description.html
===================================================================
--- grass/trunk/raster/r.transect/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.transect/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
This program outputs, in ASCII, the values in a raster map
which lie along one or more user-defined transect lines.
@@ -9,37 +9,37 @@
wide lines, or multiple-cell wide lines. The output, for
each transect, may be the values at each of the cells, or a
single aggregate value (e.g., average or median value). -->
-<P>
+<p>
-The <B>line</B> parameter is a definition of (each) transect line,
-specified by the geographic coordinates of its starting point (<EM>easting,
-northing</EM>), the angle and direction of its travel (<EM>azimuth</EM>),
-and its distance (<EM>distance</EM>).
+The <b>line</b> parameter is a definition of (each) transect line,
+specified by the geographic coordinates of its starting point (<em>easting,
+northing</em>), the angle and direction of its travel (<em>azimuth</em>),
+and its distance (<em>distance</em>).
-<P>
-The <EM>azimuth</EM> is an angle, in degrees, measured to
-the east of north. The <EM>distance</EM> is in map units
+<p>
+The <em>azimuth</em> is an angle, in degrees, measured to
+the east of north. The <em>distance</em> is in map units
(meters for a metered database, like UTM).
-<P>
-The <B>null</B> parameter can optionally be set to change the character
+<p>
+The <b>null</b> parameter can optionally be set to change the character
string representing null values.
-<H2>NOTES</H2>
+<h2>NOTES</h2>
-This program is a front-end to the <EM>
-<A HREF="r.profile.html">r.profile</A></EM> program. It simply converts the
-azimuth and distance to an ending coordinate and then runs <EM>
-<A HREF="r.profile.html">r.profile</A></EM>.
+This program is a front-end to the <em>
+<a href="r.profile.html">r.profile</a></em> program. It simply converts the
+azimuth and distance to an ending coordinate and then runs <em>
+<a href="r.profile.html">r.profile</a></em>.
-There once were <B>width=</B> and <B>result=</B><EM>raw|median|average</EM>
+There once were <b>width=</b> and <b>result=</b><em>raw|median|average</em>
options which are not currently implemented.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.profile.html">r.profile</A></EM>,
+<em><a href="r.profile.html">r.profile</a></em>,
<em><a href="gm_profile.html">gis.m: PROFILE TOOL</a></em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro, U.S. Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.volume/description.html
===================================================================
--- grass/trunk/raster/r.volume/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.volume/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<em>r.volume</em> is a tool for summing cell values within clumps
and calculating volumes and centroids of patches or clumps.
@@ -20,7 +20,7 @@
notification otherwise. - EP
-->
-<H2>NOTES</H2>
+<h2>NOTES</h2>
<p>
If a clump map is not given and a MASK not set, the program exits
with an error message.
@@ -28,7 +28,7 @@
<em>r.volume</em> works in the current region and respects the current MASK.
<p>
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
The following report was generated by the command:
(spearfish data base; fields.only is the fields layer without the
@@ -70,7 +70,7 @@
of the appropriate category, thus they are not always the true,
mathematical centroid. They will always fall at a cell center.
-<h3>FORMAT OF CENTROIDS table<BR></h3>
+<h3>FORMAT OF CENTROIDS table<br></h3>
For each line of above table the vector points table contains
these columns:
<tt>
@@ -100,8 +100,8 @@
finding water volumes in potential reservoirs. Data layers of
other measures of real values.
-<H2>AUTHOR</H2>
-Dr. James Hinthorne, Central Washington University GIS Laboratory<BR>
+<h2>AUTHOR</h2>
+Dr. James Hinthorne, Central Washington University GIS Laboratory<br>
December 1988.
Modified: grass/trunk/raster/r.walk/description.html
===================================================================
--- grass/trunk/raster/r.walk/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.walk/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,4 +1,4 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
<em>r.walk</em> outputs a raster map layer showing the lowest
cumulative cost of moving between each cell and the user-specified
@@ -68,7 +68,7 @@
<p>
The minimum cumulative costs are computed using Dijkstra's
algorithm, that find an optimum solution (for more details see
-<EM>r.cost</EM>, that uses the same algorithm).
+<em>r.cost</em>, that uses the same algorithm).
<p>
Once <em>r.walk</em> computes the cumulative cost map as a linear
combination of friction cost (from friction map) and the altitude and
@@ -76,16 +76,16 @@
can be used to find the minimum cost path.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM><A HREF="r.cost.html">r.cost</A></EM>,
-<EM><A HREF="r.drain.html">r.drain</A></EM>,
-<EM><A HREF="r.in.ascii.html">r.in.ascii</A></EM>,
-<EM><A HREF="r.mapcalc.html">r.mapcalc</A></EM>,
-<EM><A HREF="r.out.ascii.html">r.out.ascii</A></EM>
+<em><a href="r.cost.html">r.cost</a></em>,
+<em><a href="r.drain.html">r.drain</a></em>,
+<em><a href="r.in.ascii.html">r.in.ascii</a></em>,
+<em><a href="r.mapcalc.html">r.mapcalc</a></em>,
+<em><a href="r.out.ascii.html">r.out.ascii</a></em>
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
<ul>
<li>Aitken, R. 1977. Wilderness areas in Scotland. Unpublished Ph.D. thesis.
@@ -98,36 +98,36 @@
Sports Council/MLTB. Cordee, Leicester.
</ul>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
-<B>Based on r.cost written by :</B>
-<P>
-Antony Awaida,<BR>
-Intelligent Engineering<BR>
-Systems Laboratory,<BR>
-M.I.T.<BR>
-<BR>
-James Westervelt,<BR>
+<b>Based on r.cost written by :</b>
+<p>
+Antony Awaida,<br>
+Intelligent Engineering<br>
+Systems Laboratory,<br>
+M.I.T.<br>
+<br>
+James Westervelt,<br>
U.S.Army Construction Engineering Research Laboratory
-<P>Updated for Grass 5<BR>
+<p>Updated for Grass 5<br>
Pierre de Mouveaux (pmx at audiovu.com)
-<P>
-<B>Initial version of r.walk:</B>
-<P>
+<p>
+<b>Initial version of r.walk:</b>
+<p>
Steno Fontanari, 2002
-<P>
-<B>Current version of r.walk:</B>
-<P>
+<p>
+<b>Current version of r.walk:</b>
+<p>
Franceschetti Simone, Sorrentino Diego, Mussi Fabiano and Pasolli Mattia<br>
Correction by: Fontanari Steno, Napolitano Maurizio and Flor Roberto<br>
In collaboration with: Franchi Matteo, Vaglia Beatrice, Bartucca Luisa, Fava Valentina and Tolotti Mathias, 2004
-<P>
-<B>Updated for Grass 6.1</B>
-<P>
+<p>
+<b>Updated for Grass 6.1</b>
+<p>
Roberto Flor and Markus Neteler
<p><i>Last changed: $Date$</i>
Modified: grass/trunk/raster/r.water.outlet/description.html
===================================================================
--- grass/trunk/raster/r.water.outlet/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.water.outlet/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,15 +1,15 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.water.outlet</EM> generates a watershed basin from a drainage
-direction map (from <EM><A HREF="r.watershed.html">r.watershed</A></EM>) and
+<em>r.water.outlet</em> generates a watershed basin from a drainage
+direction map (from <em><a href="r.watershed.html">r.watershed</a></em>) and
a set of coordinates representing the outlet point of watershed.
-<H3>Selected Parameters</H3>
-<DL>
+<h3>Selected Parameters</h3>
+<dl>
-<DT><B>drainage=</B><EM>name</EM>
+<dt><b>drainage=</b><em>name</em>
-<DD>Input map: drainage direction. Indicates the "aspect" for each
+<dd>Input map: drainage direction. Indicates the "aspect" for each
cell. Multiplying positive values by 45 will give the direction in
degrees that the surface runoff will travel from that cell. The
value -1 indicates that the cell is a depression area.
@@ -17,24 +17,24 @@
surface runoff is leaving the boundaries of the current geographic
region. The absolute value of these negative cells indicates the
direction of flow. This map is generated from
-<EM><A HREF="r.watershed.html">r.watershed</A></EM>.
+<em><a href="r.watershed.html">r.watershed</a></em>.
-<DT><B>basin=</B><EM>name</EM>
+<dt><b>basin=</b><em>name</em>
-<DD>Output map: Values of one (1) indicate the watershed
+<dd>Output map: Values of one (1) indicate the watershed
basin. Values of zero are not in the watershed basin.
-<DT><B>easting=</B><EM>value</EM>
+<dt><b>easting=</b><em>value</em>
-<DD>Input value: Easting value of outlet point.
+<dd>Input value: Easting value of outlet point.
-<DT><B>northing=</B><EM>value</EM>
+<dt><b>northing=</b><em>value</em>
-<DD>Input value: Northing value of outlet point.
+<dd>Input value: Northing value of outlet point.
-</DL>
+</dl>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
In the context of this program, a watershed basin is the
region upstream of an outlet point. Thus, if the user
@@ -42,15 +42,15 @@
will be a thin silver of land representing the overland
slope uphill of the point.
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="d.where.html">d.where</A>,
-<A HREF="r.watershed.html">r.watershed</A>,
-<A HREF="r.topidx.html">r.topidx</A>
-</EM>
+<em>
+<a href="d.where.html">d.where</a>,
+<a href="r.watershed.html">r.watershed</a>,
+<a href="r.topidx.html">r.topidx</a>
+</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Charles Ehlschlaeger, U.S. Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.what/description.html
===================================================================
--- grass/trunk/raster/r.what/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.what/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,37 +1,37 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.what</EM> outputs the category values and (optionally) the category
+<em>r.what</em> outputs the category values and (optionally) the category
labels associated with user-specified locations on raster input map(s).
Locations are specified as geographic x,y coordinate pairs (i.e., pair of
eastings and northings); the user can also (optionally) associate a label
with each location.
-<P>
+<p>
The input coordinates can be entered directly on the command line, or
redirected via <tt>stdin</tt> from an input text file, script, or piped from
-another program (like <EM><A HREF="d.where.html">d.where</A></EM>).
-<P>
+another program (like <em><a href="d.where.html">d.where</a></em>).
+<p>
If none of the above input methods are used and the module is run from the
terminal prompt, the program will interactively query the user for point
locations and labels.
-<P>
+<p>
Each line of the input consists of an easting, a northing, and an optional
label, which are separated by spaces. In interactive mode, the word
"<tt>end</tt>" must be typed after the last pair of input coordinates.
-<P>
-<EM>r.what</EM> output consists of the input geographic location and label,
+<p>
+<em>r.what</em> output consists of the input geographic location and label,
and, for each user-named raster map layer, the category value, and (if
-the <B>-f</B> label flag is specified) the category label associated with
+the <b>-f</b> label flag is specified) the category label associated with
the cell(s) at this geographic location.
-<H2>EXAMPLES</H2>
+<h2>EXAMPLES</h2>
<h4>Input from <tt>stdin</tt> on the command line</h4>
Input coordinates may be given directly from <tt>stdin</tt>, for example:
-<BR> (input data appears between the "<tt>EOF</tt>" markers)
+<br> (input data appears between the "<tt>EOF</tt>" markers)
<div class="code"><pre>
r.what input=soils,aspect << EOF
@@ -52,7 +52,7 @@
<h4>Input from a text file containing coordinates</h4>
-The contents of an ASCII text file can be redirected to <EM>r.what</EM>
+The contents of an ASCII text file can be redirected to <em>r.what</em>
as follows. If we have a file called <i>input_coord.txt</i> containing the
coordinates and labels given in the example above:
@@ -102,7 +102,7 @@
<h4>Output containing raster map category labels</h4>
-Here we use the <B>-f</B> label flag to enable the output of category labels
+Here we use the <b>-f</b> label flag to enable the output of category labels
associated with the raster cell(s), as well as values. (categorical maps only)
<div class="code"><pre>
@@ -117,27 +117,27 @@
-<H2>NOTE</H2>
+<h2>NOTE</h2>
The maximum number of raster map layers that can be queried at one time is 150.
<!-- as given by raster/r.what/main.c "#define NFILES 150" -->
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="d.where.html">d.where</A>,
-<A HREF="r.category.html">r.category</A>,
-<A HREF="r.report.html">r.report</A>,
-<A HREF="r.stats.html">r.stats</A>,
-<A HREF="r.series.html">r.series</A>,
-<A HREF="r.univar.html">r.univar</A>,
-<A HREF="v.what.html">v.what</A>,
-<A HREF="v.what.rast.html">v.what.rast</A>,
-<A HREF="v.what.vect.html">v.what.vect</A>
-</EM>
+<em>
+<a href="d.where.html">d.where</a>,
+<a href="r.category.html">r.category</a>,
+<a href="r.report.html">r.report</a>,
+<a href="r.stats.html">r.stats</a>,
+<a href="r.series.html">r.series</a>,
+<a href="r.univar.html">r.univar</a>,
+<a href="v.what.html">v.what</a>,
+<a href="v.what.rast.html">v.what.rast</a>,
+<a href="v.what.vect.html">v.what.vect</a>
+</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Michael Shapiro,
U.S. Army Construction Engineering Research Laboratory
Modified: grass/trunk/raster/r.what.color/description.html
===================================================================
--- grass/trunk/raster/r.what.color/description.html 2008-05-16 17:53:06 UTC (rev 31373)
+++ grass/trunk/raster/r.what.color/description.html 2008-05-16 18:37:23 UTC (rev 31374)
@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
-<EM>r.what.color</EM> outputs the color associated with user-specified
+<em>r.what.color</em> outputs the color associated with user-specified
category values in a raster input map.
<p>
Values may be specified either using the <b>values=</b> option, or by
@@ -58,19 +58,19 @@
1500: 1f:7f:df
</pre></div>
-<P>
-Common formats:<BR>
+<p>
+Common formats:<br>
<ul>
<li>Tcl/Tk: <tt>format="#%02x%02x%02x"</tt>
<li>WxPython: <tt>format='"#%02x%02x%02x"'</tt> or <tt>format='"(%d,%d,%d)"'</tt>
</ul>
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
-<EM>
-<A HREF="r.what.html">r.what</A>
-</EM>
+<em>
+<a href="r.what.html">r.what</a>
+</em>
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
Glynn Clements
More information about the grass-commit
mailing list