NC examples added; HTML updated

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

scripts/v.build.all/v.build.all.html

@@ -1,9 +1,10 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.build.all</EM> will run <em><a href="v.build.html">v.build</a></em>
+<em>v.build.all</em> runs <em><a href="v.build.html">v.build</a></em>
 for all vectors in the current mapset.
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Radim Blazek
+
 <p>
 <i>Last changed: $Date$</i>

scripts/v.centroids/v.centroids.html

@@ -1,37 +1,34 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 GRASS defines vector areas as composite entities consisting of a set of
 closed boundaries and a centroid. The attribute information associated
-with that area is linked to the centroid. The <EM>v.centroids</EM> module
+with that area is linked to the centroid. The <em>v.centroids</em> module
 adds centroids to closed boundaries in the <b>input</b> file and assigns a
 category number to them. The starting value as well as the increment size
 may be set using optional parameters. 
-<P>
+<p>
 Multiple attributes may be linked to a single vector entity through
 numbered fields referred to as layers. Refer to <em>v.category</em>
-for more details, as <EM>v.centroids</EM> is simply a frontend to that
+for more details, as <em>v.centroids</em> is simply a frontend to that
 module.
-<P>
+<p>
 The boundary itself is often stored without any category reference as it
 can mark the border between two adjacent areas. Thus it would be ambiguous
 as to which feature the attribute would belong. In some cases it may, for
 example, represent a road between two parcels of land. In this case it
 is entirely appropriate for the boundary to contain category information.
-<p>
-
-<EM>(GRASS Shell Script)</EM>
 
 <H2>SEE ALSO</H2>
 
 <em>
-<A HREF="v.category.html">v.category</A>
+<a href="v.category.html">v.category</a>
 </em>
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 module: M. Hamish Bowman, Dept. Marine Science, Otago University, New Zealand
-<BR>
+<br>
 help page: Trevor Wiens
 
-<P>
+<p>
 <i>Last changed: $Date$</i>

scripts/v.convert.all/v.convert.all.html

@@ -1,20 +1,22 @@
 <h2>DESCRIPTION</h2>
 
 <em>v.convert.all</em> converts all GRASS 5.0/5.3/5.4 vectors in the current
-mapset into GRASS 6.0 vectors.
+mapset into GRASS 7 vectors.
 
 <h2>NOTES</h2>
 
-Vector maps from 5.0/5.3/5.4 and 6.0 do not interfere. They are stored in different 
-directories, so you can use the same names. Old vector maps can be listed with
+Vector maps from 5.0/5.3/5.4 and 7 do not interfere. They are stored in different 
+directories, so the same names can be kept. Old vector maps can be listed with
 <em>g.list oldvect</em>.
 
-<P>
-If you need to convert back from 6.0 into the 5.0/5.3/5.4 vector format,
+<p>
+To convert back from 7 to 6 vector format, use <em>v.build</em> in GRASS 6.
+<p>
+To convert back from 6.0 into the 5.0/5.3/5.4 vector format,
 use <em>v.out.ogr</em> (to SHAPE format) and then <em>v.in.shape</em>
 in the old GRASS program.
-Alternatively use "<em>v.out.ascii -o</em>" and <em>v.in.ascii</em>.
-<P>
+<p>
+
 As this GRASS version uses SQL for attribute management, there are
 some <a href=sql.html>SQL restrictings concerning the file names</a>.
 This script changes dots (e.g. "foo.bar") in old vector map names into
@@ -23,17 +25,19 @@ underline(s) (e.g. "foo_bar").
 <h2>EXAMPLE</h2>
 
 To convert all old vector maps in the current mapset to the new vector format:
-<br>
-<tt>
-v.convert.all -r
-</tt>
+<p>
+<div class="code"><pre>
+v.convert.all
+</pre></div>
 
 <h2>SEE ALSO</h2>
 
-<em><A HREF="g.list.html">g.list</A>,
-<A HREF="v.convert.html">v.convert</A>,
-<A HREF="v.out.ascii.html">v.out.ascii</A>,
-<A HREF="v.out.ogr.html">v.out.ogr</A></em>
+<em>
+<a href="g.list.html">g.list</a>,
+<a href="v.convert.html">v.convert</a>,
+<a href="v.out.ascii.html">v.out.ascii</a>,
+<a href="v.out.ogr.html">v.out.ogr</a>
+</em>
 
 
 <h2>AUTHOR</h2>

scripts/v.db.addcolumn/v.db.addcolumn.html

@@ -6,39 +6,43 @@ specified layer.
 
 <h2>NOTES</h2>
 
-v.db.addcolumn is a front-end to <em>db.execute</em> to allow easier usage.
+<em>v.db.addcolumn</em> is a front-end to <em>db.execute</em> to allow easier usage.
 
 The supported types of columns depend on the database backend. However, all
-backends should support VARCHAR, INT, DOUBLE PRECISION and DATE. The default
-dbf backend supports only these types.
-
+backends should support VARCHAR, INT, DOUBLE PRECISION and DATE.
+<p>
 The existing database connection(s) can be verified with <em>v.db.connect</em>.
 
 <h2>EXAMPLES</h2>
 
 Adding a single column:<br>
 <div class="code"><pre>
-v.db.addcolumn sentiero_brenta_points columns="slope double precision"
-v.info -c sentiero_brenta_points
+g.copy vect=roadsmajor,myroads
+v.db.addcolumn myroads columns="slope double precision"
+v.info -c myroads
 </pre></div>
 
 <p>
 Adding two columns:<br>
 <div class="code"><pre>
-v.db.addcolumn sentiero_brenta_points columns="slope double precision,myname varchar(15)"
-v.info -c sentiero_brenta_points
+g.copy vect=roadsmajor,myroads
+v.db.addcolumn myroads columns="slope double precision,myname varchar(15)"
+v.info -c myroads
 </pre></div>
 
 <h2>SEE ALSO</h2>
 
-<em><a href="db.execute.html">db.execute</a></em>,
-<em><a href="v.db.addtable.html">v.db.addtable</a></em>,
-<em><a href="v.db.connect.html">v.db.connect</a></em>,
-<em><a href="v.db.dropcolumn.html">v.db.dropcolumn</a></em>,
-<em><a href="v.db.droptable.html">v.db.droptable</a></em>,
-<em><a href="v.db.select.html">v.db.select</a></em>,
-<em><a href="v.db.update.html">v.db.update</a></em>,<br>
-<em><a href="sql.html">GRASS SQL interface</a></em>
+<em>
+<a href="db.connect.html">db.connect</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="v.db.addtable.html">v.db.addtable</a>,
+<a href="v.db.connect.html">v.db.connect</a>,
+<a href="v.db.dropcolumn.html">v.db.dropcolumn</a>,
+<a href="v.db.droptable.html">v.db.droptable</a>,
+<a href="v.db.select.html">v.db.select</a>,
+<a href="v.db.update.html">v.db.update</a><br>
+<a href="sql.html">GRASS SQL interface</a>
+</em>
 
 
 <h2>AUTHOR</h2>

scripts/v.db.addtable/v.db.addtable.html

@@ -13,47 +13,51 @@ usage.
 v.db.addtable will only insert category values into the table for those features 
 which actually have a category value in the relevant layer. The use can add 
 category values automatically by using <em>v.category</em> or manually with 
-<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em> before running v.db.addtable. Or one can run v.db.addtable first
+<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em>
+before running v.db.addtable. Or one can run v.db.addtable first
 and then use either a combinatino of <em>v.category</em> + <em>v.to.db</em> or 
-<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em> to add the relevant lines to the table.
+<em><a href="wxGUI.Vector_Digitizing_Tool.html">wxGUI vector digitizer</a></em>
+to add the relevant lines to the table.
 
 The supported types of columns depend on the database backend. However, all
 backends should support VARCHAR, INT, DOUBLE PRECISION and DATE.
-The dbf backend supports only these types.
-
+<p>
 The existing database connection(s) can be verified with <em>v.db.connect</em>.
 
 <h2>EXAMPLE</h2>
 
 Adding a new attribute table with a single column to default layer 1:<br>
 <div class="code"><pre>
-v.db.addtable sentiero_brenta_points columns="slope double precision"
-v.db.connect -p sentiero_brenta_points
-v.info -c sentiero_brenta_points
+g.copy vect=roadsmajor,myroads
+v.db.addtable myroads columns="slope double precision"
+v.db.connect -p myroads
+v.info -c myroads
 </pre></div>
 
 <p>
 Adding a new attribute table with two columns to layer 2:<br>
 <div class="code"><pre>
-v.db.addtable sentiero_brenta_points columns="slope double precision,myname varchar(15)" layer=2
-v.db.connect -p sentiero_brenta_points
-v.info -c sentiero_brenta_points
+g.copy vect=roadsmajor,myroads
+v.db.addtable myroads columns="slope double precision, roadname varchar(15)" layer=2
+v.db.connect -p myroads
+v.info -c myroads
+v.info -c myroads layer=2
 </pre></div>
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="db.connect.html">db.connect</a></em>,
-<em><a HREF="db.droptable.html">db.droptable</a></em>,
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.category.html">v.category</a></em>,
-<em><a HREF="v.db.addcolumn.html">v.db.addcolumn</a></em>,
-<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
-<em><a HREF="v.db.dropcolumn.html">v.db.dropcolumn</a></em>,
-<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
-<em><a HREF="v.db.select.html">v.db.select</a></em>,
-<em><a HREF="v.db.update.html">v.db.update</a></em><br>
-<em><a href="sql.html">GRASS SQL interface</a></em>
-
+<em>
+<a href="db.connect.html">db.connect</a>,
+<a href="db.droptable.html">db.droptable</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="v.db.addtable.html">v.db.addtable</a>,
+<a href="v.db.connect.html">v.db.connect</a>,
+<a href="v.db.dropcolumn.html">v.db.dropcolumn</a>,
+<a href="v.db.droptable.html">v.db.droptable</a>,
+<a href="v.db.select.html">v.db.select</a>,
+<a href="v.db.update.html">v.db.update</a><br>
+<a href="sql.html">GRASS SQL interface</a>
+</em>
 
 <h2>AUTHOR</h2>
 

scripts/v.db.dropcolumn/v.db.dropcolumn.html

@@ -7,29 +7,33 @@ relevant to keep the connection between vector map and table.
 
 <h2>NOTES</h2>
 
-v.db.dropcolumn is a front-end to <em>db.execute</em> to allow easier usage.
-
+<em>v.db.dropcolumn</em> is a front-end to <em>db.execute</em> to allow easier usage.
+<p>
 The existing database connection(s) can be verified with <em>v.db.connect</em>.
 
 <h2>EXAMPLES</h2>
 
 Dropping a column:<br>
 <div class="code"><pre>
-v.db.dropcolumn sentiero_brenta_points column=slope
-v.info -c sentiero_brenta_points
+g.copy vect=roadsmajor,myroads
+v.info -c myroads
+v.db.dropcolumn myroads column=SHAPE_LEN
+v.info -c myroads
 </pre></div>
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="db.droptable.html">db.droptable</a></em>,
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcolumn.html">v.db.addcolumn</a></em>,
-<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
-<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
-<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
-<em><a HREF="v.db.select.html">v.db.select</a></em>,
-<em><a HREF="v.db.update.html">v.db.update</a></em>
-
+<em>
+<a href="db.connect.html">db.connect</a>,
+<a href="db.dropcolumn.html">db.dropcolumn</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="v.db.addcolumn.html">v.db.addcolumn</a>,
+<a href="v.db.connect.html">v.db.connect</a>,
+<a href="v.db.droptable.html">v.db.droptable</a>,
+<a href="v.db.select.html">v.db.select</a>,
+<a href="v.db.update.html">v.db.update</a><br>
+<a href="sql.html">GRASS SQL interface</a>
+</em>
 
 <h2>AUTHOR</h2>
 

scripts/v.db.droptable/v.db.droptable.html

@@ -7,27 +7,32 @@ given then nothing is removed.
 <h2>NOTES</h2>
 
 <em>v.db.droptable</em> is a front-end to <em>db.execute</em> to allow easier usage.
-
+<p>
 The existing database connection(s) can be verified with <em>v.db.connect</em>.
 
 <h2>EXAMPLE</h2>
 
-Removing attribute table connected to layer 2:<br>
+Removing attribute table connected to layer 1:<br>
 <div class="code"><pre>
-v.db.droptable sentiero_brenta_points layer=2
-v.db.connect -p sentiero_brenta_points
+g.copy vect=roadsmajor,myroads
+v.db.droptable myroads
+v.db.droptable myroads -f
+v.db.connect -p myroads
 </pre></div>
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="db.droptable.html">db.droptable</a></em>,
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcolumn.html">v.db.addcolumn</a></em>,
-<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
-<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
-<em><a HREF="v.db.dropcolumn.html">v.db.dropcolumn</a></em>,
-<em><a HREF="v.db.select.html">v.db.select</a></em>,
-<em><a HREF="v.db.update.html">v.db.update</a></em>
+<em>
+<a href="db.addtable.html">db.addtable</a>,
+<a href="db.connect.html">db.connect</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="v.db.addtable.html">v.db.addtable</a>,
+<a href="v.db.connect.html">v.db.connect</a>,
+<a href="v.db.dropcolumn.html">v.db.dropcolumn</a>,
+<a href="v.db.select.html">v.db.select</a>,
+<a href="v.db.update.html">v.db.update</a><br>
+<a href="sql.html">GRASS SQL interface</a>
+</em>
 
 
 <h2>AUTHOR</h2>

scripts/v.db.reconnect.all/v.db.reconnect.all.html

@@ -1,17 +1,17 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.db.reconnect.all</EM> changes database connection of all layers of
+<em>v.db.reconnect.all</em> changes database connection of all layers of
 all vectors in the current mapset from old_database to database. If a link
 does not match the old_database it is left untouched.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 The value of the <em>old_database</em> option needs to be the exact
 string which appears as the fourth field printed by
-<code>'v.db.connect -g'</code>, i.e. with substituted variables.
+<tt>v.db.connect -g</tt>, i.e. with substituted variables.
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 Radim Blazek
 
 <p>

scripts/v.db.renamecolumn/v.db.renamecolumn.html

@@ -19,29 +19,29 @@ case, i.e., upper-to-lowercase, or lower-to-uppercase. The SQLite protocol consi
 and "name" to be identical column names. In cases like these, the user should rename the original
 column to an intermediary name, then rename the intermediary to the final name.
 
-<p>
-
-
 <h2>EXAMPLES</h2>
 
 Renaming a column:<br>
 <div class="code"><pre>
+g.copy vect=roadsmajor,myroads
 v.info -c myroads
-v.db.renamecolumn myroads column=label,roadtype
+v.db.renamecolumn myroads column=ROAD_NAME,roadname
 v.info -c myroads
 </pre></div>
 
 <h2>SEE ALSO</h2>
 
-<em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcolumn.html">v.db.addcolumn</a></em>,
-<em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
-<em><a HREF="v.db.connect.html">v.db.connect</a></em>,
-<em><a HREF="v.db.dropcolumn.html">v.db.dropcolumn</a></em>,
-<em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,
-<em><a HREF="v.db.select.html">v.db.select</a></em>,
-<em><a HREF="v.db.update.html">v.db.update</a></em>
-
+<em>
+<a href="db.execute.html">db.execute</a>,
+<a href="v.db.addcolumn.html">v.db.addcolumn</a>,
+<a href="v.db.addtable.html">v.db.addtable</a>,
+<a href="v.db.connect.html">v.db.connect</a>,
+<a href="v.db.dropcolumn.html">v.db.dropcolumn</a>,
+<a href="v.db.droptable.html">v.db.droptable</a>,
+<a href="v.db.select.html">v.db.select</a>,
+<a href="v.db.update.html">v.db.update</a><br>
+<a href="sql.html">GRASS SQL interface</a>
+</em>
 
 <h2>AUTHOR</h2>
 

scripts/v.db.univar/v.db.univar.html

@@ -1,42 +1,43 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-
-<EM><b>v.db.univar</b></EM>  - Calculates basic univariate statistics for numeric
+<em>v.db.univar</em> calculates basic univariate statistics for numeric
 attributes in a data table. It will calculate minimum, maximum, range, mean,
 standard deviation, variance, coefficient of variation, quartiles, median, and
 90th percentile.
 It uses <em>db.select</em> to create list values for statistical calculations.
 
-<EM>(GRASS Shell Script)</EM>
-
-<H2>NOTES</H2>
+<em>NOTES</em>
 
 If the database and driver are not specified, the default values set in
 <em>db.connect</em> will be used.
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
+In this example, random points are sampled from the elevation map
+(North Carolina sample dataset) and univariate statistics performed:
 <div class="code"><pre>
-g.region rast=elevation.10m -p
-v.random out=samples n=100
-v.db.addtable samples col="heights double precision"
-v.what.rast samples rast=elevation.10m col=heights
+g.region rast=elevation -p
+v.random output=samples n=100
+v.db.addtable samples column="heights double precision"
+v.what.rast samples raster=elevation colum=heights
 v.db.select samples
 
-v.db.univar samples col=heights
+v.db.univar samples colum=heights
 </pre></div>
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
-<A HREF="r.univar.html">r.univar</A>,
-<A HREF="v.univar.html">v.univar,</A>,
-<A HREF="db.select.html">db.select</A>,
-<A HREF="d.vect.thematic.html">d.vect.thematic</A></EM>
+<em>
+<a href="r.univar.html">r.univar</a>,
+<a href="v.univar.html">v.univar,</a>,
+<a href="db.select.html">db.select</a>,
+<a href="d.vect.thematic.html">d.vect.thematic</a>
+</em>
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
  Michael Barton, Arizona State University
 <p>
 and authors of <em>r.univar.sh</em>
+
 <p>
 <i>Last changed: $Date$</i>