update manual pages (https://trac.osgeo.org/grass/ticket/2409)

       (merge https://trac.osgeo.org/grass/changeset/63250 from trunk)


git-svn-id: https://svn.osgeo.org/grass/grass/branches/releasebranch_7_0@63251 15284696-431f-4ddb-bdfa-cd5b030d7da7

display/d.colortable/d.colortable.html

@@ -28,7 +28,7 @@ The user running the command:
 <b>d.colortable map=</b><em>soils</em> 
   <b>color=</b><em>red</em>
   <b>lines=</b><em>1</em>
-  <b>cols=</b><em>3</em>
+  <b>columns =</b><em>3</em>
 </dl>
 would see the active graphics frame divided into three columns 
 extending the full frame height. The lines dividing the color table 

display/d.vect.chart/d.vect.chart.html

@@ -22,7 +22,7 @@ The 'sizecol' parameter is proportionate to the radius.
 The optional <b>max_ref</b> parameter accepts a list of values that
 represent the maximum value for each column listed in the values for the
 parameter <b>columns</b>. These values are used to create a framed bar
-plot if <b>ctype</b> is <em>bar</em> (See Example 2).
+plot if <b>chart_type</b> is <em>bar</em> (See Example 2).
 
 <h2>EXAMPLES</h2>
 

display/d.vect/d.vect.html

@@ -10,7 +10,7 @@ map=vector_map</tt>. There are a large variety of optional parameters
 which allow the user to specify vector type, colors, data fields, SQL
 queries, label size and justification, etc.
 
-<p>By default <em>d.vect</em> areas are filled with <b>fcolor</b> and 
+<p>By default <em>d.vect</em> areas are filled with <b>fill_color</b> and 
 outlined with <b>color</b>. Area outlines can be suppressed with
 <div class="code"><pre>
 d.vect map=vector_map color=none

imagery/i.fft/i.fft.html

@@ -2,17 +2,17 @@
 
 <em>i.fft</em> is an image processing program based on the FFT algorithm
 given by Frigo et al. (1998), that processes a single input raster map layer
-(<b>input_image</b>) and constructs the real and imaginary Fourier
+(<b>input</b>) and constructs the real and imaginary Fourier
 components in frequency space.
 
 <h2>NOTES</h2>
 
 The real and imaginary components are stored into the
-<b>real_image</b> and <b>imaginary_image</b> raster map
+<b>real</b> and <b>imaginary</b> raster map
 layers.  In these raster map
 layers the low frequency components are in the center and
 the high frequency components are toward the edges.  The
-<b>input_image</b> need not be square. A
+<b>input</b> need not be square. A
 color table is assigned to the resultant map layer.
 
 

misc/m.transform/m.transform.html

@@ -6,7 +6,7 @@ based upon GCPs and output error measurements.
 
 <h2>NOTES</h2>
 
-For coordinates given with the <b>coords</b> file option or fed from
+For coordinates given with the <b>input</b> file option or fed from
 <tt>stdin</tt>, the input format is "x y" with one coordinate pair per
 line.
 

raster/r.cost/r.cost.html

@@ -24,18 +24,18 @@ name of the resultant raster map of movement directions (see <a href="#move">Mov
 <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>start_coordinate</b> on the command line, from a vector
+provided as specified <b>start_coordinates</b> on the command line, from a vector
 points file, or from a raster map.
 All non-NULL cells are considered to be starting points.
 <p>
-Each <em>x,y</em> <b>start_coordinate</b> pair gives the geographic location of a
+Each <em>x,y</em> <b>start_coordinates</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_points</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_coordinate</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_points</b> option. During execution, once the cumulative cost to all 
 stopping points has been determined, processing stops.<br>

raster/r.drain/r.drain.html

@@ -3,7 +3,7 @@
 <em>r.drain</em> traces a flow through a least-cost path in an
 elevation model or cost surface. For cost surfaces, a movement
 direction map must be specified with the
-<b>indir</b> option and the <b>-d</b> flag to trace a flow path following 
+<b>direction</b> option and the <b>-d</b> flag to trace a flow path following 
 the given directions. Such a movement direction map can be generated with 
 <em><a href="r.walk.html">r.walk</a></em>, 
 <em><a href="r.cost.html">r.cost</a></em>, 

raster/r.out.mpeg/r.out.mpeg.html

@@ -34,11 +34,11 @@ higher frame rates and smoother animations.
 <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.
 
-<p>A quality value of <b>qual=1</b> will yield higher quality images,
+<p>A quality value of <b>quality=1</b> 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 <b>qual=5</b> will usually be about 60% the size
-of the MPEG produced using <b>qual=1</b>.
+MPEG produced using <b>quality=5</b> will usually be about 60% the size
+of the MPEG produced using <b>quality=1</b>.
 
 <h2>Example</h2>
 

raster/r.slope.aspect/r.slope.aspect.html

@@ -5,7 +5,7 @@ first and second order partial derivatives from a raster map of true
 elevation values. The user must specify the input <b>elevation</b> raster map
 and at least one output raster maps. The user can also specify the
 <b>format</b> for slope (degrees, percent; default=degrees), and the 
-<b>zfactor</b>: multiplicative factor to convert elevation units to meters;
+<b>zscale</b>: multiplicative factor to convert elevation units to meters;
 (default 1.0).
 
 <p>
@@ -13,7 +13,7 @@ The <b>elevation</b> input raster map specified by the user must contain true
 elevation values, <em>not</em> rescaled or categorized data. If the elevation
 values are in feet or other units than meters (with a conversion factor
 <i>meters:</i>, defined in PROJ_UNITS), they must be converted to meters using
-the parameter <b>zfactor</b>.
+the parameter <b>zscale</b>.
 
 <p>
 The <b>aspect</b> output raster map indicates the direction that slopes are

raster/r.spreadpath/r.spreadpath.html

@@ -29,7 +29,7 @@ coordinates.
 <dt><b>y_input=</b><em>name</em>
 <dd>Name of input raster map layer containing backlink UTM northing coordinates.
 
-<dt><b>coordinate=</b><em>x,y[,x,y,x,y, ...]</em>
+<dt><b>coordinates =</b><em>x,y[,x,y,x,y, ...]</em>
 <dd>Each x,y coordinate pair gives the easting and northing 
 (respectively) geographic coordinates of a target point from which to 
 backwards trace the least cost path. As many points as desired can be 

raster/r.topmodel/r.topmodel.html

@@ -110,25 +110,21 @@ class at the same time. If no topidxclass is given, output will be generated
 for all the topographic index classes.
 </dd>
 
-<dt><b>topidxclass</b></dt>
+<dt><b>toptopidxclass</b></dt>
 <dd>
 If a topographic index class is specified, output will be generated for the
 given topographic index class. This parameter can be combined with timestep. If
 no timestep is given, output will be generated for all the time steps.
 </dd>
 
-<dt><b>topidx</b>, <b>ntopidxclasses</b>, <b>outtopidxstats</b></dt>
+<dt><b>topidx</b>, <b>ntoptopidxclasses</b>, <b>outtoptopidxstats</b></dt>
 <dd>
 The <b>topidx</b> map can optionally be used for creating a new topographic
 index statistics file. This map has to be already clipped to the catchment
 boundary. The entire range of topographic index values will be divided into
-<b>ntopidxclasses</b> and the number of cells in each class will be reported in
-the <b>outtopidxstats</b> file using the following command:
-<div class="code"><pre>
-r.stats -Anc input=[topidx] output=[outtopidxstats] nsteps=[ntopidxclasses]
-</pre></div>
-These three parameters can be omitted unless a new topidxstats file needs to be
-created.
+<b>ntoptopidxclasses</b> and the area ratio of each class will be reported in the
+<b>outtoptopidxstats</b> file. These three parameters can be omitted unless a new
+topidxstats file needs to be created.
 </dd>
 </dl>
 

scripts/d.polar/d.polar.html

@@ -19,7 +19,7 @@ are used.
 
 <h2>NOTES</h2>
 
-If the <b>eps</b> parameter is used, the diagram is generated
+If the <b>output</b> parameter is used, the diagram is generated
 as EPS file. If the <b>-x</b> flag is used <em>xgraph</em> is lauched.
 Otherwise <em>d.polar</em> will use <em>d.graph</em> to draw the plot
 in the current display frame.

scripts/v.what.vect/v.what.vect.html

@@ -1,19 +1,19 @@
 <h2>DESCRIPTION</h2>
 
-<em>v.what.vect</em> transfers attributes from the <b>qvector</b>'s map
+<em>v.what.vect</em> transfers attributes from the <b>query_map</b>'s map
 attribute table into the attribute table of <u>points</u> present in the
-<b>vector</b> map. The script is based on <em>v.distance</em>.
+<b>map</b> map. The script is based on <em>v.distance</em>.
 
 <h2>NOTES</h2>
 
 The upload <b>column</b>, into which the query results are stored, must be
-present in the <b>vector</b> map. Use <em>v.db.addcolumn</em> to add one if needed.
+present in the <b>map</b> map. Use <em>v.db.addcolumn</em> to add one if needed.
 <p>Use dmax parameter to control query distance tolerance (how far points/centroids
-can be from <b>qvector</b> features). For more options, use
+can be from <b>query_map</b> features). For more options, use
 <em>v.distance</em> instead.
-<p>In case of a multipoint input <b>vector</b> map, with several points having the
+<p>In case of a multipoint input <b>map</b> map, with several points having the
 same category number, it can happen, that the query result is NULL, if the same
-category number falls into different <b>qvector</b> polygons.
+category number falls into different <b>query_map</b> polygons.
 <p>When transferring attributes from a point map to a polygon map, usually <b>dmax</b>
 has to be larger than zero (determined by distance between query points and
 polygon centroids).

vector/v.edit/v.edit.html

@@ -15,7 +15,7 @@ number <b>cats</b>, coordinates <b>coords</b>, bounding
 box <b>bbox</b>, <b>polygon</b>, <b>where</b> statement (attribute
 data) or by <b>query</b>. Selecting features by coordinates is
 affected by the current 2D resolution or by the threshold distance
-given by <b>thresh</b>. The options are <em>orthogonal</em>, i.e. can
+given by <b>threshold</b>. The options are <em>orthogonal</em>, i.e. can
 be used in various combinations. For example:
 
 <div class="code"><pre>
@@ -43,7 +43,7 @@ Vector features can be selected in several ways:
     <li><b>ids</b> - using internal (unique) feature id's</li>
     <li><b>cats</b> - using category numbers</li>
     <li><b>coords</b> - using x,y coordinate pairs (center of bounding
-    box, size defined by <b>thresh</b>)</li>
+    box, size defined by <b>threshold</b>)</li>
     <li><b>bbox</b> - using bounding box</li>
     <li><b>polygon</b> - using polygon (at least 3 coordinate pairs have to be set)</li>
     <li><b>where</b> - using where statement (attribute data)
@@ -54,7 +54,7 @@ Additional parameters for vector feature specification are:
 <ul>
     <li><b>layer</b> - layer number (currently used only
     with <b>cats</b> or <b>where</b> option)</li>
-    <li><b>thresh</b> - threshold distance used for selecting vector
+    <li><b>threshold</b> - threshold distance used for selecting vector
     features by coordinates</li>
 </ul>
 
@@ -73,7 +73,7 @@ Additional parameters for vector feature specification are:
     from the given text file (<b>input</b> option). If no header is
     given, the <b>-n</b> flag must be used. Added features can be
     snapped (defined by <b>snap</b> parameter) to nodes or vertices
-    based on threshold distance <b>thresh</b>.</li>
+    based on threshold distance <b>threshold</b>.</li>
 
     <li><b>delete</b> - Delete selected vector features from existing
     vector map.</li>
@@ -87,7 +87,7 @@ Additional parameters for vector feature specification are:
     <b>move</b> option. The option defines coordinates of the movement
     direction. Moved features can be snapped (defined by <b>snap</b>
     parameter) to nodes or vertices based on threshold
-    distance <b>thresh</b>.</li>
+    distance <b>threshold</b>.</li>
 
     <li><b>flip</b> - Flip direction of selected vector lines
     (lines or boundaries).</li>
@@ -119,7 +119,7 @@ Additional parameters for vector feature specification are:
     first given line is connected to the second one. The second line
     is broken if necessary. The lines are connected only if distance
     between them is not greater than snapping threshold
-    distance <b>thresh</b>.</li>
+    distance <b>threshold</b>.</li>
 
     <li><b>chtype</b> - Change feature type of selected geometry
     objects. Points are converted to centroids, centroids to points,
@@ -139,7 +139,7 @@ Additional parameters for vector feature specification are:
     the <b>move</b> option. If -1 is given only first found
     line or boundary in bounding box is modified. Moved vertex can be
     snapped (defined <b>snap</b>) to nodes or vertices based on
-    threshold distance <b>thresh</b>.</li>
+    threshold distance <b>threshold</b>.</li>
     
     <li><b>zbulk</b> - Assign z coordinate to 3D vector lines in given
     bounding box. The first found line will get z coordinate based on

vector/v.kcv/v.kcv.html

@@ -1,7 +1,7 @@
 <h2>DESCRIPTION</h2>
 
 <em>v.kcv</em> randomly divides a points lists into <em>k</em> sets of
-test/train data (for <b>k</b>-fold <b>c</b>ross <b>v</b>alidation).
+test/train data (for <b>npartitions</b>-fold <b>c</b>ross <b>v</b>alidation).
 Test partitions are mutually exclusive. That is, a point will appear in
 only one test partition and <em>k-1</em> training partitions.
 

vector/v.kernel/v.kernel.html

@@ -15,7 +15,7 @@ and can be enabled with <b>node=split</b>.
 
 <h2>NOTES</h2>
 
-The <b>mult</b> option is needed to overcome the limitation that
+The <b>multiplier</b> option is needed to overcome the limitation that
 the resulting density in case of a vector map output is stored as category
 (integer). The density result stored as category may be multiplied by this number.
 <p>

vector/v.out.postgis/v.out.postgis.html

@@ -54,7 +54,7 @@ ignored by <em>v.out.postgis</em>.
 
 <p>
 <em>v.out.postgis</em> optionally also creates a new vector map in the
-current mapset if <b>olink</b> is defined.
+current mapset if <b>output_link</b> is defined.
 
 <h2>NOTES</h2>
 
@@ -161,7 +161,7 @@ topological access to the data.
 <h3>Export data into specific database schema</h3>
 
 Database schema for storing exported data can be defined
-by <b>olayer</b> as
+by <b>output_layer</b> as
 <tt>&lt;schema_name&gt;.&lt;table_name&gt;</tt>. If the specified
 schema doesn't exist in the database, then it's automatically created.
 
@@ -187,7 +187,7 @@ v.out.postgis input=roadsmajor output="PG:dbname=grass" options="GEOMETRY_NAME=w
 <h3>Link exported data</h3>
 
 Exported data can be linked as vector map created in the current
-mapset by specifying <b>olink</b> parameter. In the example below
+mapset by specifying <b>output_link</b> parameter. In the example below
 vector map &quot;busstopsall&quot; from PERMANENT mapset is exported
 into &quot;grass&quot; PostGIS database. <em>v.out.postgis</em> after
 successful export also creates in the current mapset GRASS vector map

vector/v.qcount/v.qcount.html

@@ -1,7 +1,7 @@
 <h2>DESCRIPTION</h2>
 
-<em>v.qcount</em> chooses <b>n</b> circular quadrats of
-radius <b>r</b> such that they are completely within the
+<em>v.qcount</em> chooses <b>nquadradius ants</b> circular quadrats of
+radius <b>radius</b> such that they are completely within the
 bounds of the current region and no two quadrats overlap.
 The number of points falling within each quadrat are counted
 and indices are calculated to estimate the departure of

vector/v.surf.rst/v.surf.rst.html

@@ -47,7 +47,7 @@ preserving the geometrical properties of the surface.  With the
 smoothing parameter set to zero (<b>smooth=0</b>) the resulting
 surface passes exactly through the data points (spatial interpolation
 is performed). When smoothing parameter is used, it is also possible
-to output a vector point map <b>devi</b> containing deviations of the
+to output a vector point map <b>deviations</b> containing deviations of the
 resulting surface from the given data.
 
 <p>
@@ -162,7 +162,7 @@ stability of the computation):
     depend on the actual scale (distances) of the original data (which
     can be km for regional applications or cm for field
     experiments).</li>
-  <li>Flag<b> -t </b>: The given <b>tension</b> is applied to
+  <li>Flag<b>-t</b>: The given <b>tension</b> is applied to
     un-normalized data (rescaled <em>tension = tension*dnorm/1000</em>
     is applied to normalized data (<em>x/dnorm</em>) and
     therefore <b>dnorm</b> cancels out) so here <b>tension</b> truly
@@ -262,7 +262,7 @@ must be done outside <em>v.surf.rst</em>.
 
 <p>
 The &quot;optimal&quot; approximation parameters for given data can be
-found using a cross-validation (CV) procedure (<b>-c </b>flag).  The
+found using a cross-validation (CV) procedure (<b>-c</b>flag).  The
 CV procedure is based on removing one input data point at a time,
 performing the approximation for the location of the removed point
 using the remaining data points and calculating the difference between

vector/v.to.points/v.to.points.html

@@ -15,7 +15,7 @@ are <em>lcat</em> - the category of the input line and <em>along</em>
 
 <p>
 By default only features with category are processed,
-see <b>llayer</b> parameter for details.
+see <b>layer</b> parameter for details.
 
 <h2>NOTES</h2>
 
@@ -25,9 +25,9 @@ the vector line the user should use
 <em><a href="v.segment.html">v.segment</a></em>.
 
 <p>
-Set <b>llayer</b> to -1 to process features from all layers including
+Set <b>layer</b> to -1 to process features from all layers including
 features without category. Features will be assigned new unique
-categories at layer 1. Option <b>llayer=-1</b> should be used to
+categories at layer 1. Option <b>layer=-1</b> should be used to
 convert boundaries, as in most of cases boundaries lack category
 values.
 

vector/v.vol.rst/v.vol.rst.html

@@ -4,21 +4,21 @@
 3-dimensional point data (e.g. temperature, rainfall data from climatic
 stations, concentrations from drill holes etc.) given in a 3-D vector
 point file named <b>input</b>.&nbsp; The size of the output 
-3D raster map <b>elev</b> is given by the current 3D region. Sometimes, the
+3D raster map <b>elevation</b> is given by the current 3D region. Sometimes, the
 user
 may want to get a 2-D map showing a modelled phenomenon at a
-crossection surface. In that case, <b>cellinp</b> and <b>cellout</b>
-options must be specified, with the output 2D raster map <b>cellout</b>
+crossection surface. In that case, <b>cross_input</b> and <b>cross_output</b>
+options must be specified, with the output 2D raster map <b>cross_output</b>
 containing the crossection of the interpolated volume with a surface 
-defined by <b>cellinp</b>
+defined by <b>cross_input</b>
 2D raster map. As an option, simultaneously with interpolation, 
 geometric parameters of the interpolated
 phenomenon can be computed (magnitude of gradient, direction of
 gradient defined by horizontal and vertical angles), change of gradient,
 Gauss-Kronecker curvature, or mean curvature). These geometric
 parameteres are saved as
-3D raster maps <b>gradient, aspect1, aspect2, ncurv, gcurv, mcurv</b>,
-respectively. Maps <b>aspect1</b> and <b>aspect2</b> are in degrees.
+3D raster maps <b>gradient, aspect_horizontal, aspect_vertical, ncurvature, gcurvature, mcurvature</b>,
+respectively. Maps <b>aspect_horizontal</b> and <b>aspect_vertical</b> are in degrees.
 
 <p>At first, data points are checked for identical positions and points
 that are closer to each other than given <b>dmin</b> are removed.
@@ -43,7 +43,7 @@ is possible to define a global smoothing parameter, <b>smooth</b>.
 With the
 smoothing parameter set to zero (<b>smooth=0</b>) the resulting volume
 passes exactly through the data points. 
-When smoothing is used, it is possible to output a vector map <b>devi</b>
+When smoothing is used, it is possible to output a vector map <b>deviations</b>
 containing deviations of the resulting volume from the given data. 
 <p>The user can define a 2D raster map named <b>maskmap</b>, which will
 be used as a mask. The interpolation is skipped for 3-dimensional cells
@@ -127,9 +127,9 @@ interpolation from point data (as described in Mitasova and Mitas,
 on Oct-trees which enhances the efficiency for large data sets. 
 
 <p>Geometric parameters - magnitude of gradient (<b>gradient</b>),
-horizontal (<b>aspect1</b>) and vertical (<b>aspect2) </b>aspects,
-change of gradient (<b>ncurv</b>), Gauss-Kronecker (<b>gcurv</b>) and
-mean curvatures (<b>mcurv</b>) are computed directly from the
+horizontal (<b>aspect_horizontal</b>) and vertical (<b>aspect_vertical)</b>aspects,
+change of gradient (<b>ncurvature</b>), Gauss-Kronecker (<b>gcurvature</b>) and
+mean curvatures (<b>mcurvature</b>) are computed directly from the
 interpolation function so that the important relationships between
 these parameters are preserved. More information on these parameters
 can be found in Mitasova et al., 1995 or Thorpe, 1979.
@@ -223,7 +223,7 @@ paraview --data=volume.vtk
 </pre></div>
 
 <h2>BUGS</h2>
-<b>devi</b> file is written as 2D and deviations are not written as attributes.
+<b>deviations</b> file is written as 2D and deviations are not written as attributes.
 
 <h2>REFERENCES</h2>
 <p>Hofierka J., Parajka J., Mitasova H., Mitas L., 2002, Multivariate