NC examples added; HTML updated

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

scripts/v.db.update/v.db.update.html

@@ -7,20 +7,33 @@ be copied from another column in the table.
 <h2>NOTES</h2>
 
 <em>v.db.update</em> is just a front-end to <em>db.execute</em> to allow easier usage.
+<p>
 For complex SQL UPDATE statements, <em>db.execute</em> should be used.
 
 <h2>EXAMPLES</h2>
 
-Spearfish: adding new column, inserting selectively a specified value:
+In this example, selectively display lakes without (blue) and with NULL (red)
+are shown to find out which type is undefined. In the original map there are
+lakes missing FTYPE attribute which are wetlands along streams. These NULL
+attributes are replaced with the landuse type WETLAND:
+
 <div class="code"><pre>
-g.copy vect=fields,myfields
-v.db.addcolumn myfields col="polynum integer"
-v.db.update myfields col=polynum val=42 where="label='V. White#1'"
-v.db.select myfields
-</pre></div>
+g.copy vect=lakes,mylakes
+v.db.select mylakes
+v.db.select mylakes where="FTYPE IS NULL"
+
+# display the lakes, show undefined FTYPE lakes in red
+g.region vect=mylakes
+d.mon wx0
+d.vect mylakes where="FTYPE NOT NULL" type=area col=blue
+d.vect mylakes where="FTYPE IS NULL" type=area col=red
 
+# replace NULL with FTYPE WETLAND
+v.db.update mylakes col=FTYPE value=WETLAND \
+            where="FTYPE IS NULL"
+v.db.select mylakes
 <p>
-Spearfish: adding new column, copying values from other table column with
+Spearfish example: adding new column, copying values from other table column with
 on the fly calculation:
 <div class="code"><pre>
 g.copy vect=fields,myfields
@@ -32,20 +45,23 @@ v.db.select myfields
 <p>
 Type cast (type conversion) of strings to double precision (unsupported by DBF driver):
 <div class="code"><pre>
+g.copy vect=geodetic_pts,mygeodetic_pts
 v.db.update mygeodetic_pts col=zval qcol="CAST(z_value AS double precision)" \
             where="z_value &lt;&gt; 'N/A'"
 </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.droptable.html">v.db.droptable</a></em>,
-<em><a HREF="v.db.join.html">v.db.join</a></em>,
-<em><a HREF="v.db.select.html">v.db.select</a></em><br>
-<em><a href="sql.html">GRASS SQL interface</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.droptable.html">v.db.droptable</a>,
+<a HREF="v.db.join.html">v.db.join</a>,
+<a HREF="v.db.select.html">v.db.select</a><br>
+<a href="sql.html">GRASS SQL interface</a>
+</em>
 
 
 <h2>AUTHOR</h2>

scripts/v.dissolve/v.dissolve.html

@@ -1,6 +1,6 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-The <EM>v.dissolve</EM> module is used to merge adjacent areas in a vector
+The <em>v.dissolve</em> module is used to merge adjacent areas in a vector
 map which share the same category value. The resulting merged area(s) retains
 this category value. Alternatively an integer or string column can be defined
 which is used to find adjacent polygons with identical attribute for common
@@ -13,19 +13,19 @@ values of the new key column. See the <em>v.reclass</em> help page for details.
 GRASS defines a vector area as composite entity consisting of a set of
 closed boundaries and a centroid. The centroids must contain a
 category number
-(see <em><a href="v.centroids.html">v.centroids</a></em>), this number
-is linked to area attributes and database links.
-<P>
+(see <em>v.centroids</em>), this number is linked to area attributes and
+database links.
+<p>
 Multiple attributes may be linked to a single vector entity through
-numbered fields referred to as layers. Refer
-to <em><a href="v.category.html">v.category</a></em> for more details.
+numbered fields referred to as layers. Refer to <em>v.category</em> for
+more details.
 
-<P>
+<p>
 Merging of areas can also be accomplished using
-"<em>v.extract <b>-d</b></em>" which provides some additional options.
-In fact, <a href="v.dissolve.html">v.dissolve</a> is simply a
-front-end to that module. The use of the <EM>column</EM> parameter
-adds a call to <em><a href="v.reclass.html">v.reclass</a></em> before.
+<tt>v.extract -d</tt> which provides some additional options.
+In fact, <em>v.dissolve</em> is simply a
+front-end to that module. The use of the <em>column</em> parameter
+adds a call to <em>v.reclass</em> before.
 
 
 <h2>EXAMPLES</h2>
@@ -36,12 +36,12 @@ v.dissolve input=undissolved output=dissolved
 </pre></div>
 
 <h3>Dissolving based on column attributes</h3>
-<div class="code"><pre>
-# check column names:
-v.info -c polbnda_italy
 
-# dissolve based on column attributes:
-v.dissolve input=polbnda_italy output=pol_italy_regions col=vmap_nam
+North Carolina data set:
+
+<div class="code"><pre>
+g.copy vect=soils_general,mysoils_general
+v.dissolve mysoils_general output=mysoils_general_families column=GSL_NAME
 </pre></div>
 
 <h3>Dissolving adjacent SHAPE files to remove tile boundaries</h3>
@@ -52,7 +52,7 @@ boundaries:
 
 <div class="code"><pre>
 # patch tiles after import:
-v.patch -e `g.mlist type=vect pat="clc2000_*" sep=,` out=clc2000_patched
+v.patch -e `g.mlist type=vect pat="clc2000_*" fs=","` out=clc2000_patched
 
 # remove duplicated tile boundaries:
 v.clean clc2000_patched out=clc2000_clean tool=snap,break,rmdupl thresh=.01
@@ -62,21 +62,21 @@ v.dissolve input=clc2000_clean output=clc2000_final col=CODE_00
 </pre></div>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
 
-<EM>
-<A HREF="v.category.html">v.category</A>,
-<A HREF="v.centroids.html">v.centroids</A>,
-<A HREF="v.extract.html">v.extract</A>,
-<A HREF="v.reclass.html">v.reclass</A>
-</EM>
+<em>
+<a href="v.category.html">v.category</a>,
+<a href="v.centroids.html">v.centroids</a>,
+<a href="v.extract.html">v.extract</a>,
+<a href="v.reclass.html">v.reclass</a>
+</em>
 
 
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 
 module: M. Hamish Bowman, Dept. Marine Science, Otago University, New Zealand<br>
-Markus Neteler for column support<BR>
+Markus Neteler for column support<br>
 help page: Trevor Wiens
 
-<P>
+<p>
 <i>Last changed: $Date$</i>

scripts/v.in.e00/v.in.e00.html

@@ -12,13 +12,13 @@ automatically detects the presence of such multiple files.
 <H2>REFERENCES</H2>
 
 <a href="http://avce00.maptools.org">AVCE00 library</a> (providing 'avcimport' and 'e00conv')<br>
-<a href="http://www.remotesensing.org/gdal/ogr/">OGR vector library</a>
+<a href="http://www.gdal.org/ogr/">OGR vector library</a>
 
 <h2>SEE ALSO</h2>
 
 <em><a HREF="v.in.ogr.html">v.in.ogr</a></em>
 
-<h2>AUTHOR</h2>
+<h2>AUTHORS</h2>
 
 Markus Neteler, Otto Dassau, <a href="http://www.gdf-hannover.de/">GDF Hannover bR</a>, Germany
 

scripts/v.in.garmin/v.in.garmin.html

@@ -1,17 +1,13 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.in.garmin</EM> allows the user to import waypoint, route, and track
+<em>v.in.garmin</em> allows the user to import waypoint, route, and track
  data from a locally connected Garmin GPS receiver via the 
-<EM><A HREF="http://gpstrans.sourceforge.net">gpstrans</a></EM>
+<em><a href="http://gpstrans.sourceforge.net">gpstrans</a></em>
  program by Carsten Tschach or the
-<EM><A HREF="http://www.snafu.org">gardump</a></EM>
+<em><a href="http://www.snafu.org">gardump</a></em>
  program by Marc Hyman. 
 
-<P>
-Use at your own risk. This software comes with absolutely no warranty.
-
-<P>
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 If the GPS is set up to output WGS84 Lat/Lon, <em>v.in.garmin</em> will
 attempt to automatically transform the coordinates to the current projection.
 In all other cases, no checks are performed for datum, projection and format of data.
@@ -19,13 +15,13 @@ You must check for yourself that your receiver, gpstrans and GRASS
 use the same map datum and projection.
 The automatic transform may be skipped by using the <b>-k</b> flag.
 
-<P>
-Route and Track data may be uploaded as points by using the <B>-p</B> flag, 
-otherwise they will be imported as a line. You can run <EM>v.in.garmin</EM>
-multiple times and merge the line and point vectors with the <EM>v.patch</EM>
+<p>
+Route and Track data may be uploaded as points by using the <em>-p</em> flag, 
+otherwise they will be imported as a line. You can run <em>v.in.garmin</em>
+multiple times and merge the line and point vectors with the <em>v.patch</em>
 command if you want, but take care when merging dissimilar attribute tables.
 
-<P>
+<p>
 Future versions of GRASS will use <em>gardump</em> as the default download
 program. It can talk to newer Garmin GPSs, while <em>gpstrans</em> seems to
 be mostly abandoned these days and only works with older GPSs. The current
@@ -34,43 +30,41 @@ you can try the <em>v.in.gpsbabel</em> module for those. The <em>gardump</em>
 code has been tested with an older Garmin GPS 45 and a newer GPS V and is
 expected to work with everything in between.
 
-<P>
-Before running <EM>v.in.garmin</EM>, <em>gpstrans</em> should be set up 
-to output WGS84 latitude-longitude, as follows: <BR>
+<p>
+Before running <em>v.in.garmin</em>, <em>gpstrans</em> should be set up 
+to output WGS84 latitude-longitude, as follows: <br>
 <tt>
-$ <B>gpstrans -s</B><BR>
-datum:  100 (WGS84)<BR>
-format: 2 - lat/lon  ddd.ddddd<BR>
+$ <b>gpstrans -s</b><br>
+datum:  100 (WGS84)<br>
+format: 2 - lat/lon  ddd.ddddd<br>
 </tt>
 
-<P>
-<H2>SEE ALSO</H2>
-<EM>
-<A HREF="db.execute.html">db.execute</A><BR>
-<A HREF="v.in.ascii.html">v.in.ascii</A><BR>
-<A HREF="v.in.gpsbabel.html">v.in.gpsbabel</A><BR>
-<A HREF="v.db.connect.html">v.db.connect</A><BR>
-<A HREF="v.patch.html">v.patch</A>
-</EM>
-<BR>
-<BR>
+<h2>SEE ALSO</h2>
 
-<A HREF="http://gpstrans.sourceforge.net">gpstrans</a> manual<BR>
-<A HREF="http://www.snafu.org">gardump</a> from the "garmin-utils" package<BR>
-cs2cs from <A HREF="http://proj.maptools.org">PROJ.4</a><BR>
+<em>
+<a href="db.execute.html">db.execute</a>,
+<a href="v.in.ascii.html">v.in.ascii</a>,
+<a href="v.in.gpsbabel.html">v.in.gpsbabel</a>,
+<a href="v.db.connect.html">v.db.connect</a>,
+<a href="v.patch.html">v.patch</A>
+</em>
+
+<p>
+<a href="http://gpstrans.sourceforge.net">gpstrans</a> manual<br>
+<a href="http://www.snafu.org">gardump</a> from the "garmin-utils" package<br>
+cs2cs from <a href="http://trac.osgeo.org/proj/">PROJ.4</a><br>
 The <tt>awk</tt> user manual
 
-<P>
-<H2>AUTHORS</H2>
+<p>
+<h2>AUTHORS</h2>
 Based on <em>v.in.garmin.sh</em> for GRASS 5.0 by Andreas Lange
-<BR>&nbsp;&nbsp;&nbsp;&nbsp;
+<br>&nbsp;&nbsp;&nbsp;&nbsp;
 with bug fixes by Glynn Clements and Markus Neteler
-<BR>Rewritten for GRASS 5.3 and 5.7 by Hamish Bowman
-<BR><tt>gardump</tt> and 3D track support by Hamish Bowman
-<P>
-gpstrans was written by Carsten Tschach<BR>
-gardump was written by Marc Hyman<BR>
-<BR>
+<br>Rewritten for GRASS 5.3 and 5.7 by Hamish Bowman
+<br><tt>gardump</tt> and 3D track support by Hamish Bowman
+<p>
+gpstrans was written by Carsten Tschach<br>
+gardump was written by Marc Hyman<br>
 
 <p>
 <i>Last changed: $Date$</i>

scripts/v.in.geonames/v.in.geonames.html

@@ -11,7 +11,7 @@ is maintained in the GRASS database.
 <h2>NOTES</h2>
 
 The current DB connection is used to write the database table.
-<P>
+<p>
 If importing into a DBF database, the original column names longer that 10 characters
 are shortened to 10 characters to meet the DBF column name restrictions. If this is a
 problem consider choosing another database driver with <em>db.connect</em>.
@@ -48,7 +48,7 @@ modification date : date of last modification in yyyy-MM-dd format
 <a HREF="v.select.html">v.select</a>
 </em>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://www.geonames.org">GeoNames Web site</a><br>
 <a href="http://download.geonames.org/export/dump/">GeoNames Data Dump Server</a>

scripts/v.in.gns/v.in.gns.html

@@ -10,11 +10,11 @@ is maintained in the GRASS database.
 <h2>NOTES</h2>
 
 The current DB connection is used to write the database table.
-<P>
+<p>
 Generally, column names longer that 10 characters are shortened to
 10 characters to meet the DBF column name restrictions. If this is a
 problem consider choosing another database driver with <em>db.connect</em>.
-<P>
+<p>
 To filter outliers (points outside of a country), the <em>v.select</em>
 module can be used to perform point-in-polygon tests. <em>v.select</em>
 saves only the GNS points falling into a country polygon into the new
@@ -27,14 +27,14 @@ points map.
 <a HREF="v.select.html">v.select</a>
 </em>
 
-<H2>REFERENCES</H2>
+<h2>REFERENCES</h2>
 
 <a href="http://earth-info.nga.mil/gns/html/">GEOnet Names Server files for countries and territories</a><br>
 <a href="http://earth-info.nga.mil/gns/html/help.htm">Column names explanations</a>
 
 <h2>AUTHOR</h2>
 
-Markus Neteler, <a href="http://mpa.itc.it/">MPBA Group, ITC-irst</a>
+Markus Neteler, MPBA Group, ITC-irst, Trento, Italy
 
 <p>
 <i>Last changed: $Date$</i>

scripts/v.in.lines/v.in.lines.html

@@ -1,21 +1,21 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
 Imports a stream of ASCII x,y[,z] coordinates as a line or series of lines.
 
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 Input ASCII coordinates are simply a series of "x&nbsp;y" data points.
 Lines are separated by a row containing "<tt>NaN&nbsp;NaN</tt>".
 <!-- TODO:? Line categories start at 1 and increase sequentially. -->
-<P>
-You can import 3D lines by providing 3 columns of data in the input
-stream and using the <B>-z</B> flag.
-<P>
+<p>
+The user can import 3D lines by providing 3 columns of data in the input
+stream and using the <b>-z</b> flag.
+<p>
 This script is a simple wrapper around the <em>v.in.mapgen</em> module.
 
 
-<H2>EXAMPLE</H2>
+<h2>EXAMPLE</h2>
 
 <div class="code"><pre>
 v.in.lines in=- out=two_lines fs=, &lt;&lt;EOF
@@ -37,19 +37,20 @@ v.category in=two_lines out=lines_with_cats option=add
 </pre></div>
 
 
-<H2>SEE ALSO</H2>
+<h2>SEE ALSO</h2>
+
 <em>
-<A HREF="v.in.ascii.html">v.in.ascii</A><br>
-<A HREF="v.in.mapgen.html">v.in.mapgen</A><br>
-<A HREF="v.out.ascii.html">v.out.ascii</A><br>
-<A HREF="d.graph.html">d.graph</a><br>
-<A HREF="r.in.poly.html">r.in.poly</A>
+<a href="v.in.ascii.html">v.in.ascii</a>,
+<a href="v.in.mapgen.html">v.in.mapgen</a>,
+<a href="v.out.ascii.html">v.out.ascii</a>,
+<a href="d.graph.html">d.graph</a>,
+<a href="r.in.poly.html">r.in.poly</a>
 </em>
 
 
-<H2>AUTHOR</H2>
+<h2>AUTHOR</h2>
 
-Hamish Bowman<BR>
+Hamish Bowman<br>
 Dunedin, New Zealand
 
 <p>

scripts/v.in.mapgen/v.in.mapgen.html

@@ -1,37 +1,34 @@
-<H2>DESCRIPTION</H2>
+<h2>DESCRIPTION</h2>
 
-<EM>v.in.mapgen</EM> allows the user to import Mapgen or Matlab vector maps 
+<em>v.in.mapgen</em> allows the user to import Mapgen or Matlab vector maps 
 into GRASS.
 
-<H2>NOTES</H2>
+<h2>NOTES</h2>
 
 This module only imports data into vector lines.
-<P>
-You can get coastline data in Mapgen or Matlab format from NOAA's Coastline 
+<p>
+The user can get coastline data in Mapgen or Matlab format from NOAA's Coastline 
 Extractor at <a href="http://www.ngdc.noaa.gov/mgg/shorelines/shorelines.html">http://www.ngdc.noaa.gov/mgg/shorelines/shorelines.html</a>.
-<P>
+<p>
 Matlab vector line maps are simply a series of "x y" data points. Lines
 are separated by a row containing <tt>NaN NaN</tt>.
 
 Output from Matlab with this command:
-<BR>
+<br>
 <div class="code"><pre>
     save filename.txt arrayname -ASCII
 </pre></div>
-<P>
-You can import 3D lines from Matlab by exporting a 3 column array and
+<p>
+The user can import 3D lines from Matlab by exporting a 3 column array and
 using the <B>-z</B> flag.
 
 
-<H2>SEE ALSO</H2>
-<EM><A HREF="v.in.ascii.html">v.in.ascii</A></EM><BR>
-<BR>
+<h2>SEE ALSO</h2>
+<em><a href="v.in.ascii.html">v.in.ascii</a></em>
 
-<P>
-<H2>AUTHORS</H2>
+<h2>AUTHORS</h2>
 Based on <em>v.in.mapgen.sh</em> for GRASS 5.0 by Andreas Lange
-<BR>Rewritten for GRASS 6 by Hamish Bowman
-<BR>
+<br>Rewritten for GRASS 6 by Hamish Bowman
 
 <p>
 <i>Last changed: $Date$</i>

scripts/v.in.sites.all/v.in.sites.all.html

@@ -19,15 +19,15 @@ new vector map name.
 
 To convert all old vector maps in the current mapset to the new vector format:
 <br>
-<tt>
-v.in.sites.all -r
-</tt>
+<div class="code"><pre>
+v.in.sites.all
+</pre></div>
 
 <h2>SEE ALSO</h2>
 
 <em>
-<A HREF="g.list.html">g.list</A>,
-<A HREF="v.in.sites.html">v.in.sites</A>
+<a href="g.list.html">g.list</a>,
+<a href="v.in.sites.html">v.in.sites</a>
 </em>
 
 

scripts/v.in.wfs/v.in.wfs.html

@@ -10,7 +10,7 @@ Import of GRASS user map:
 <div class="code"><pre>
 # run in LatLong location:
 v.in.wfs \
- wfs="http://mapserver.gdf-hannover.de/cgi-bin/grassuserwfs?REQUEST=GetFeature&amp;SERVICE=WFS&amp;VERSION=1.0.0" out=grass_users
+ url="http://mapserver.gdf-hannover.de/cgi-bin/grassuserwfs?REQUEST=GetFeature&amp;SERVICE=WFS&amp;VERSION=1.0.0" out=grass_users
 
 v.db.select grass_users where="name ~ 'Markus'"
 </pre></div>