[GRASS-CVS] hamish: grass6/vector/v.to.db description.html, 1.23, 1.24

[grass at intevation.de]

Author: hamish

Update of /grassrepository/grass6/vector/v.to.db
In directory doto:/tmp/cvs-serv2511/grass6/vector/v.to.db

Modified Files:
	description.html 
Log Message:
note that the International Foot is always used for distances and acres


Index: description.html
===================================================================
RCS file: /grassrepository/grass6/vector/v.to.db/description.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -d -r1.23 -r1.24
--- description.html	13 Oct 2007 11:18:21 -0000	1.23
+++ description.html	19 Nov 2007 01:01:10 -0000	1.24
@@ -4,19 +4,24 @@
 or prints them (or the SQL queries used to obtain them) in a form of a
 human-readable report.
 
+
 <H2>NOTES</H2>
 The units <em>miles</em>, <em>feet</em>, <em>meters</em> and
 <em>kilometers</em> are square for <em>option=area</em>.
-<p>
-When using <em>option=coor</em> on a vector area map, 
-only coordinates of centroids with unique category will be reported.
+<P>
+Feet and acre units are always reported in their common versions
+(i.e. the International Foot, exactly 5280 feet in a mile), even
+when the location's standard map unit is the US Survey foot.
 <p>
 When calculating perimeters in Latitude-Longitude locations, the geodesic
 distance between the vertices is used.
 <p>
-If the module is apparently slow <em>and</em> the map attributes are stored in
-an external DBMS such as PostgreSQL, it is highly recommended to create an index
-on the key (category) column.
+When using <em>option=coor</em> on a vector area map, 
+only coordinates of centroids with unique category will be reported.
+<p>
+If the module is apparently slow <em>and</em> the map attributes are
+stored in an external DBMS such as PostgreSQL, it is highly recommended
+to create an index on the key (category) column.
 <p>
 Uploading the vector map attributes to a database requires a table attached to
 a given input vector <em>layer</em>. The <b>print only</b> (<b>-p</b>) mode
@@ -30,6 +35,7 @@
 <em><a href=v.db.addcol.html>v.db.addcol</a></em> to add new columns if
 needed.
 
+
 <H2>EXAMPLES</H2>
 
 <h3>Updating attribute tables</h3>
@@ -118,20 +124,25 @@
 v.to.db -p roads option=count type=line
 </pre></div>
 
+
 <h2>SEE ALSO</h2>
 
 <em>
-<a href="v.category.html">v.category</a>
-<a href="v.db.addtable.html">v.db.addtable</a>
-<a href="v.db.addcol.html">v.db.addcol</a>
-<a href="v.db.connect">v.db.connect</a>
-<a href="v.distance.html">v.distance</a>
-<a href="db.execute.html">db.execute</a>
+<a href="d.what.vect.html">d.what.vect</a>,
+<a href="db.execute.html">db.execute</a>,
+<a href="v.category.html">v.category</a>,
+<a href="v.db.connect">v.db.connect</a>,
+<a href="v.db.addtable.html">v.db.addtable</a>,
+<a href="v.db.addcol.html">v.db.addcol</a>,
+<a href="v.db.connect">v.db.connect</a>,
+<a href="v.distance.html">v.distance</a>,
+<a href="v.report.html">v.report</a>,
+<a href="v.univar.html">v.univar</a>,
 <a href="v.what.html">v.what</a>
-<a href="d.what.vect.html">d.what.vect</a>
 </em>
 
 <H2>AUTHOR</H2>
 Radim Blazek
 
-<p><i>Last changed: $Date$</i>
+<p>
+<i>Last changed: $Date$</i>