[GRASS-SVN] r43477 - in grass/branches/releasebranch_6_4: display/d.graph display/d.his general/g.message ps/ps.map raster/r.basins.fill raster/r.cost raster/r.in.xyz raster/r.out.gdal raster/r.proj raster/r.proj.seg raster/r.watershed/front raster/r.what scripts/m.proj vector/lidar/v.lidar.correction vector/lidar/v.lidar.edgedetection vector/lidar/v.lidar.growing vector/lidar/v.outlier vector/lidar/v.surf.bspline vector/v.reclass vector/v.segment

svn_grass at osgeo.org svn_grass at osgeo.org
Thu Sep 16 03:25:59 EDT 2010 

Author: neteler
Date: 2010-09-16 07:25:59 +0000 (Thu, 16 Sep 2010)
New Revision: 43477

Modified:
   grass/branches/releasebranch_6_4/display/d.graph/description.html
   grass/branches/releasebranch_6_4/display/d.his/description.html
   grass/branches/releasebranch_6_4/general/g.message/description.html
   grass/branches/releasebranch_6_4/ps/ps.map/description.html
   grass/branches/releasebranch_6_4/raster/r.basins.fill/description.html
   grass/branches/releasebranch_6_4/raster/r.cost/description.html
   grass/branches/releasebranch_6_4/raster/r.in.xyz/description.html
   grass/branches/releasebranch_6_4/raster/r.out.gdal/description.html
   grass/branches/releasebranch_6_4/raster/r.proj.seg/description.html
   grass/branches/releasebranch_6_4/raster/r.proj/description.html
   grass/branches/releasebranch_6_4/raster/r.watershed/front/description.html
   grass/branches/releasebranch_6_4/raster/r.what/description.html
   grass/branches/releasebranch_6_4/scripts/m.proj/description.html
   grass/branches/releasebranch_6_4/vector/lidar/v.lidar.correction/description.html
   grass/branches/releasebranch_6_4/vector/lidar/v.lidar.edgedetection/description.html
   grass/branches/releasebranch_6_4/vector/lidar/v.lidar.growing/description.html
   grass/branches/releasebranch_6_4/vector/lidar/v.outlier/description.html
   grass/branches/releasebranch_6_4/vector/lidar/v.surf.bspline/description.html
   grass/branches/releasebranch_6_4/vector/v.reclass/description.html
   grass/branches/releasebranch_6_4/vector/v.segment/description.html
Log:
backport of HTML fixes extracted from r43469

Modified: grass/branches/releasebranch_6_4/display/d.graph/description.html
===================================================================
--- grass/branches/releasebranch_6_4/display/d.graph/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/display/d.graph/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -185,14 +185,14 @@
 A dynamic example can be found in the <em>d.polar</em> shell script.
 
 
-<h4>Draw a "star" symbol at a given map coordinate</h4>
+<h3>Draw a "star" symbol at a given map coordinate</h3>
 
 <div class="code"><pre>
 echo "symbol basic/star 20 2264417 5413182 black red" | d.graph -m
 </pre></div>
 
 
-<h4>Split the screen into quadrants:</h4>
+<h3>Split the screen into quadrants:</h3>
 
 <div class="code"><pre>
 d.frame -s full_screen

Modified: grass/branches/releasebranch_6_4/display/d.his/description.html
===================================================================
--- grass/branches/releasebranch_6_4/display/d.his/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/display/d.his/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -112,7 +112,7 @@
 
 
 <H2>EXAMPLE</H2>
-<h4>Spearfish dataset</h4>
+<h3>Spearfish dataset</h3>
 
 <div class="code"><pre>
   g.region rast=elevation.dem

Modified: grass/branches/releasebranch_6_4/general/g.message/description.html
===================================================================
--- grass/branches/releasebranch_6_4/general/g.message/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/general/g.message/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -44,7 +44,7 @@
 <tt>$VARIABLE</tt> expansion.
 <P>
 
-<h4>VERBOSITY LEVELS</h4>
+<h3>VERBOSITY LEVELS</h3>
 Controlled by the "<tt>GRASS_VERBOSE</tt>" environment variable. Typically this
 is set using the <tt>--quiet</tt> or <tt>--verbose</tt> command line options.
 <ul>
@@ -54,7 +54,7 @@
 <li>3 - additional verbose messages are printed
 </ul>
 
-<h4>DEBUG LEVELS</h4>
+<h3>DEBUG LEVELS</h3>
 Controlled by the "<tt>DEBUG</tt>" GRASS <i>gisenv</i> variable. (set with
 <em><a href="g.gisenv.html">g.gisenv</a></em>)
 <BR>

Modified: grass/branches/releasebranch_6_4/ps/ps.map/description.html
===================================================================
--- grass/branches/releasebranch_6_4/ps/ps.map/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/ps/ps.map/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -280,7 +280,7 @@
 legends.
 
 
-<h4>Categorical (CELL) Maps</h4>
+<h3>Categorical (CELL) Maps</h3>
 
 Adding the <B>nodata N</B> instruction will prevent the "no data" box 
 from being drawn (category based legends only). If you have manually
@@ -299,7 +299,7 @@
 module.
 
 
-<h4>Floating point (FCELL and DCELL) Maps</h4>
+<h3>Floating point (FCELL and DCELL) Maps</h3>
 
 The legend's <B>range</B> can be adjusted for floating point rasters, but if
 set beyond the extent of the map's range be sure that you have set up color 
@@ -1614,7 +1614,7 @@
 
 The following are examples of <EM>ps.map</EM> script files.
 <P>
-<h4>Simple example</h4>
+<h3>Simple example</h3>
 The file has been named <EM>spear.basic</EM>:
 
 <PRE>
@@ -1634,7 +1634,7 @@
 </PRE>
 
 
-<h4>More complicated example</h4>
+<h3>More complicated example</h3>
 The file has been named <EM>spear.soils</EM>:
 
 <PRE>

Modified: grass/branches/releasebranch_6_4/raster/r.basins.fill/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster/r.basins.fill/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/raster/r.basins.fill/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -40,7 +40,6 @@
 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>.
 
-<p>
 <em><a href="r.watershed.html">r.watershed</a></em>,
 <em><a href="v.digit.html">v.digit</a></em>
 

Modified: grass/branches/releasebranch_6_4/raster/r.cost/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster/r.cost/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/raster/r.cost/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -118,7 +118,7 @@
 This problem doesn't arise with floating point maps.
 
 
-<h4>Algorithm notes</h4>
+<h3>Algorithm notes</h3>
 
 The fundamental approach to calculating minimum travel cost is as
 follows:<p> The user generates a raster map indicating the cost of
@@ -199,7 +199,7 @@
 those that are different between operations using and not using the
 Knight's move (<b>-k</b>) option.
 
-<h4>Output analysis</h4>
+<h3>Output analysis</h3>
 
 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>
@@ -209,7 +209,7 @@
 used together, generate least-cost paths or corridors between any two
 map locations (cells). 
 
-<h4>Shortest distance surfaces</h4>
+<h3>Shortest distance surfaces</h3>
 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

Modified: grass/branches/releasebranch_6_4/raster/r.in.xyz/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster/r.in.xyz/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/raster/r.in.xyz/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -39,7 +39,7 @@
 
 <h2>NOTES</h2>
 
-<h4>Gridded data</h4>
+<h3>Gridded data</h3>
 
 If data is known to be on a regular grid <em>r.in.xyz</em> can reconstruct
 the map perfectly as long as some care is taken to set up the region
@@ -59,7 +59,7 @@
 should be identical regardless of which of those methods are used.
 
 
-<h4>Memory use</h4>
+<h3>Memory use</h3>
 
 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).
@@ -84,7 +84,7 @@
 If reading data from a <tt>stdin</tt> stream, the program can only run using
 a single pass.
 
-<h4>Setting region bounds and resolution</h4>
+<h3>Setting region bounds and resolution</h3>
 
 You can use the <b>-s</b> scan flag to find the extent of the input data
 (and thus point density) before performing the full import. Use
@@ -114,7 +114,7 @@
 as well use "<tt>v.in.ascii&nbsp;-zbt</tt>" directly.
 
 
-<h4>Filtering</h4>
+<h3>Filtering</h3>
 
 Points falling outside the current region will be skipped. This includes
 points falling <em>exactly</em> on the southern region bound.
@@ -147,13 +147,13 @@
 <em>r.neighbors</em> to smooth the stddev map before further use.]
 
 
-<h4>Reprojection</h4>
+<h3>Reprojection</h3>
 
 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>.
 
-<h4>Interpolation into a DEM</h4>
+<h3>Interpolation into a DEM</h3>
 
 The vector engine's topographic abilities introduce a finite memory overhead
 per vector point which will typically limit a vector map to approximately

Modified: grass/branches/releasebranch_6_4/raster/r.out.gdal/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster/r.out.gdal/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/raster/r.out.gdal/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -80,7 +80,7 @@
 for details.
 
 
-<h4>Ranges of GDAL data types</h4>
+<h3>Ranges of GDAL data types</h3>
 <pre>
   GDAL data type	       minimum  	maximum
 
@@ -120,7 +120,7 @@
 stretching the color table to actual min/max would help (sometimes under
 symbology).
 
-<h4>GeoTIFF caveats</h4>
+<h3>GeoTIFF caveats</h3>
 
 GeoTIFF exports can only be displayed by standard image viewers
 if the GDAL data type was set to Byte and the GeoTIFF contains either
@@ -137,7 +137,7 @@
 This issue only arises when writing out multi-band imagery groups.
 <p>
 
-<h4>Improving GeoTIFF compatibility</h4>
+<h3>Improving GeoTIFF compatibility</h3>
 
 To create a GeoTIFF that is highly compatible with various other GIS
 software packages, it is recommended to keep the GeoTIFF file as simple
@@ -175,31 +175,31 @@
 
 <h2>EXAMPLES</h2>
 
-<h4>Export the integer raster roads map to GeoTIFF format:</h4>
+<h3>Export the integer raster roads map to GeoTIFF format:</h3>
 <div class="code"><pre>
 r.out.gdal input=roads output=roads.tif type=UInt16
 </pre></div>
 <p>
 
-<h4>Export a DCELL raster map in GeoTIFF format suitable for ESRI software:</h4>
+<h3>Export a DCELL raster map in GeoTIFF format suitable for ESRI software:</h3>
 <div class="code"><pre>
 r.out.gdal in=elevation.10m out=ned_elev10m.tif type=Float64 createopt="PROFILE=GeoTIFF,TFW=YES"
 </pre></div>
 <p>
 
-<h4>Export R,G,B imagery bands in GeoTIFF format suitable for ESRI software:</h4>
+<h3>Export R,G,B imagery bands in GeoTIFF format suitable for ESRI software:</h3>
 <div class="code"><pre>
 i.group group=nc_landsat_rgb input=lsat7_2002_30,lsat7_2002_20,lsat7_2002_10
 r.out.gdal in=nc_landsat_rgb out=nc_landsat_rgb.tif type=Byte createopt="PROFILE=GeoTIFF,INTERLEAVE=PIXEL,TFW=YES"
 </pre></div>
 <p>
 
-<h4>Export the floating point raster elevation map to ERDAS/IMG format:</h4>
+<h3>Export the floating point raster elevation map to ERDAS/IMG format:</h3>
 <div class="code"><pre>
 r.out.gdal input=elevation.10m output=elev_dem10.img format=HFA type=Float32
 </pre></div>
 
-<h4>Export group of image maps as multi-band file</h4>
+<h3>Export group of image maps as multi-band file</h3>
 <div class="code"><pre>
 g.list group
 i.group group=tm7 subgroup=tm7 input=tm7_10,tm7_20,tm7_30,tm7_40,tm7_50,tm7_60,tm7_70

Modified: grass/branches/releasebranch_6_4/raster/r.proj/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster/r.proj/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/raster/r.proj/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -7,9 +7,9 @@
 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>
+<h3>Introduction</h3>
 
-<h5>Map projections</h5>
+<h4>Map projections</h4>
 
 Map projections are a method of representing information from a
 curved surface (usually a spheroid) in two dimensions, typically to allow
@@ -81,7 +81,7 @@
 GRASS location.
 <br><br>
 
-<h4>Design of r.proj</h4>
+<h3>Design of r.proj</h3>
 
 As discussed briefly above, the fundamental step in re-projecting a
 raster is resampling the source grid at locations corresponding to the

Modified: grass/branches/releasebranch_6_4/raster/r.proj.seg/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster/r.proj.seg/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/raster/r.proj.seg/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -7,9 +7,9 @@
 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>
+<h3>Introduction</h3>
 
-<h5>Map projections</h5>
+<h4>Map projections</h4>
 
 Map projections are a method of representing information from a
 curved surface (usually a spheroid) in two dimensions, typically to allow
@@ -81,7 +81,7 @@
 GRASS location.
 <br><br>
 
-<h4>Design of r.proj</h4>
+<h3>Design of r.proj</h3>
 
 As discussed briefly above, the fundamental step in re-projecting a
 raster is resampling the source grid at locations corresponding to the

Modified: grass/branches/releasebranch_6_4/raster/r.watershed/front/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster/r.watershed/front/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/raster/r.watershed/front/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -184,7 +184,7 @@
 
 <h2>NOTES</h2>
 
-<h4>A<sup>T</sup> least-cost search algorithm</h4>
+<h3>A<sup>T</sup> least-cost search algorithm</h3>
 <em>r.watershed</em> uses an A<sup>T</sup> least-cost search algorithm 
 (see <a href="#references">REFERENCES</a> section) designed to minimize 
 the impact of DEM data errors. Compared to <em>r.terraflow</em>, this 
@@ -209,7 +209,7 @@
 <em><a href="r.cost.html">r.cost</a></em> and
 <em><a href="r.drain.html">r.drain</a></em> on every cell on the map.
 
-<h4>Multiple flow direction (MFD)</h4>
+<h3>Multiple flow direction (MFD)</h3>
 
 <em>r.watershed</em> offers two methods to calculate surface flow: 
 single flow direction (SFD, D8) and multiple flow direction (MFD). With 
@@ -224,7 +224,7 @@
 with MFD, setting the convergence factor to a higher value can reduce 
 the amount of small sliver basins.
 
-<h4>In-memory mode and disk swap mode</h4>
+<h3>In-memory mode and disk swap mode</h3>
 There are two versions of this program: <em>ram</em> and <em>seg</em>.
 <em>ram</em> is used by default, <em>seg</em> can be used by setting 
 the <em>-m</em> flag.
@@ -250,7 +250,7 @@
 The <em>r.terraflow</em> module was specifically designed with huge
 regions in mind and may be useful here as an alternative.
 
-<h4>Large regions with many cells</h4>
+<h3>Large regions with many cells</h3>
 In some situations, the region size (number of cells) may be too large for
 the amount of time or memory available. Running <em>r.watershed</em> may
 then require use of a coarser resolution. To make the results more closely
@@ -267,7 +267,7 @@
 using the values from the <em>neighborhood</em> output map layer that
 represents the minimum elevation within the region of the coarser cell.
 
-<h4>Basin threshold</h4>
+<h3>Basin threshold</h3>
 The minimum size of drainage basins, defined by the <em>threshold</em>
 parameter, is only relevant for those watersheds with a single stream
 having at least the <em>threshold</em> of cells flowing into it.
@@ -277,7 +277,7 @@
 an interior stream segment is determined by the distance between the
 tributaries flowing into it.
 
-<h4>MASK and no data</h4>
+<h3>MASK and no data</h3>
 <p>
 The <em>r.watershed</em> program does not require the user to have the
 current geographic region filled with elevation values.  Areas without
@@ -296,7 +296,7 @@
 <p>
 Zero (0) and negative values will be treated as elevation data (not no_data).
 
-<h4>Further processing of output layers</h4>
+<h3>Further processing of output layers</h3>
 <p>
 To isolate an individual river network using the output of this module,
 a number of approaches may be considered.

Modified: grass/branches/releasebranch_6_4/raster/r.what/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster/r.what/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/raster/r.what/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -28,7 +28,7 @@
 <h2>EXAMPLES</h2>
 
 
-<h4>Input from <tt>stdin</tt> on the command line</h4>
+<h3>Input from <tt>stdin</tt> on the command line</h3>
 
 Input coordinates may be given directly from <tt>stdin</tt>, for example:
 <br> (input data appears between the "<tt>EOF</tt>" markers)
@@ -50,7 +50,7 @@
 </pre></div>
 
 
-<h4>Input from a text file containing coordinates</h4>
+<h3>Input from a text file containing coordinates</h3>
 
 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
@@ -64,7 +64,7 @@
 </pre></div>
 
 
-<h4>Input coordinates given as a module option</h4>
+<h3>Input coordinates given as a module option</h3>
 
 The module's <b>east_north</b> parameter can be used to enter coordinate
 pairs directly. The maximum number of pairs will be limited by your system's
@@ -78,7 +78,7 @@
 </pre></div>
 
 
-<h4>Input coordinates piped from another program</h4>
+<h3>Input coordinates piped from another program</h3>
 
 The input coordinates may be "piped" from the <tt>stdout</tt> of another program.
 For example:
@@ -100,7 +100,7 @@
 v.out.ascii bugsites fs=' ' | r.what input=soils,aspect
 </pre></div>
 
-<h4>Output containing raster map category labels</h4>
+<h3>Output containing raster map category labels</h3>
 
 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)

Modified: grass/branches/releasebranch_6_4/scripts/m.proj/description.html
===================================================================
--- grass/branches/releasebranch_6_4/scripts/m.proj/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/scripts/m.proj/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -130,7 +130,7 @@
 If a datum is specified there is no need for the '<tt>+ellps=</tt>' or underlying
 parameters, '<tt>+a=</tt>', '<tt>+es=</tt>', etc.
 <p>
-<h4>Another custom parameter usage example:</h4>
+<h3>Another custom parameter usage example:</h3>
 
 <div class="code"><pre>
 m.proj <B>proj_in</B>="+proj=tmerc +datum=ire65 +lat_0=53.5 +lon_0=-8 +x_0=200000 \

Modified: grass/branches/releasebranch_6_4/vector/lidar/v.lidar.correction/description.html
===================================================================
--- grass/branches/releasebranch_6_4/vector/lidar/v.lidar.correction/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/vector/lidar/v.lidar.correction/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -50,12 +50,12 @@
 
 <h2>EXAMPLES</h2>
 
-<h4>Basic correction procedure</h4>
+<h3>Basic correction procedure</h3>
 <div class="code"><pre>
 v.lidar.correction input=growing output=correction out_terrain=only_terrain
 </pre></div>
 
-<h4>Second correction procedure</h4>
+<h3>Second correction procedure</h3>
 <div class="code"><pre>
 v.lidar.correction input=correction output=correction_bis out_terrain=only_terrain_bis
 </pre></div>

Modified: grass/branches/releasebranch_6_4/vector/lidar/v.lidar.edgedetection/description.html
===================================================================
--- grass/branches/releasebranch_6_4/vector/lidar/v.lidar.edgedetection/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/vector/lidar/v.lidar.edgedetection/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -63,7 +63,7 @@
 
 <h2>EXAMPLES</h2>
 
-<h4>Basic edge detection</h4>
+<h3>Basic edge detection</h3>
 <div class="code"><pre>
 v.lidar.edgedetection input=vector_last output=edge see=8 sen=8 lambda_g=0.5
 </pre></div>

Modified: grass/branches/releasebranch_6_4/vector/lidar/v.lidar.growing/description.html
===================================================================
--- grass/branches/releasebranch_6_4/vector/lidar/v.lidar.growing/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/vector/lidar/v.lidar.growing/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -42,7 +42,7 @@
 
 <h2>EXAMPLES</h2>
 
-<h4>Basic region growing procedure</h4>
+<h3>Basic region growing procedure</h3>
 <div class="code"><pre>
 v.lidar.growing input=edge output=growing first=firstpulse
 </pre></div>

Modified: grass/branches/releasebranch_6_4/vector/lidar/v.outlier/description.html
===================================================================
--- grass/branches/releasebranch_6_4/vector/lidar/v.outlier/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/vector/lidar/v.outlier/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -14,7 +14,7 @@
 
 <h2>EXAMPLES</h2>
 
-<h4>Basic outlier removal</h4>
+<h3>Basic outlier removal</h3>
 
 <div class="code"><pre>
 v.outlier input=vector_map output=vector_output outlier=vector_outlier thres_O=25
@@ -22,7 +22,7 @@
 
 In this case, a basic outlier removal is done with a threshold of 25 m.
 
-<h4>Basic outlier removal</h4>
+<h3>Basic outlier removal</h3>
 
 <div class="code"><pre>
 v.outlier -q input=vector_map output=vector_output outlier=vector_outlier qgis=vector_qgis

Modified: grass/branches/releasebranch_6_4/vector/lidar/v.surf.bspline/description.html
===================================================================
--- grass/branches/releasebranch_6_4/vector/lidar/v.surf.bspline/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/vector/lidar/v.surf.bspline/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -89,7 +89,7 @@
 
 <h2>EXAMPLES</h2>
 
-<h4>Basic interpolation</h4>
+<h3>Basic interpolation</h3>
 
 <div class="code"><pre>
 v.surf.bspline input=point_vector output=interpolate_surface type=bicubic

Modified: grass/branches/releasebranch_6_4/vector/v.reclass/description.html
===================================================================
--- grass/branches/releasebranch_6_4/vector/v.reclass/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/vector/v.reclass/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -36,7 +36,7 @@
 <H2>EXAMPLES</H2>
 
 
-<H4>Example 1: Reclass by rules</H4>
+<H3>Example 1: Reclass by rules</H3>
 
 <div class="code"><pre>
 v.reclass input=land output=land_u type=boundary rules=land.rcl
@@ -64,7 +64,7 @@
 <tt>select id from tland where use = 'E14'</tt> changed to category 2.
 
 
-<H4>Example 2: Reclass by attribute column</H4>
+<H3>Example 2: Reclass by attribute column</H3>
 
 (North Carolina sample dataset)<br>
 

Modified: grass/branches/releasebranch_6_4/vector/v.segment/description.html
===================================================================
--- grass/branches/releasebranch_6_4/vector/v.segment/description.html	2010-09-16 07:22:50 UTC (rev 43476)
+++ grass/branches/releasebranch_6_4/vector/v.segment/description.html	2010-09-16 07:25:59 UTC (rev 43477)
@@ -10,7 +10,7 @@
 L &lt;segment id&gt; &lt;line cat&gt; &lt;start offset&gt; &lt;end offset&gt; [&lt;side offset&gt;]
 </pre></div>
 
-<h4>EXAMPLE</h4>
+<h3>EXAMPLE</h3>
 
 The user could send to <tt>stdin</tt> something like:
 <div class="code"><pre>

More information about the grass-commit mailing list