[GRASS-SVN] r73037 - grass/trunk/scripts/v.what.vect

[svn_grass at osgeo.org]

Author: veroandreo
Date: 2018-08-03 11:49:03 -0700 (Fri, 03 Aug 2018)
New Revision: 73037

Modified:
   grass/trunk/scripts/v.what.vect/v.what.vect.html
Log:
v.what.vect manual: general cosmetics, add sentence about dmax in ll locations

Modified: grass/trunk/scripts/v.what.vect/v.what.vect.html
===================================================================
--- grass/trunk/scripts/v.what.vect/v.what.vect.html	2018-08-03 14:58:22 UTC (rev 73036)
+++ grass/trunk/scripts/v.what.vect/v.what.vect.html	2018-08-03 18:49:03 UTC (rev 73037)
@@ -1,31 +1,36 @@
 <h2>DESCRIPTION</h2>
 
-<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>map</b> map. The script is based on <em>v.distance</em>.
+<em>v.what.vect</em> transfers attributes from the <b>query_map</b>'s
+attribute table into the <b>map</b>'s attribute table. The module can
+be used to transfer attributes from the table of a polygon map into the
+attribute table of a point vector map, as well as the other way around,
+i.e., from a point map into the attribute table of a polygon map (See
+examples). 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>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>query_map</b> features). For more options, use
-<em>v.distance</em> instead.
-<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
+The upload <b>column</b> into which the query results are stored must be
+present in <b>map</b>. Use <em>v.db.addcolumn</em> to add one if needed.
+<p>Use the <b>dmax</b> parameter to control the query distance tolerance, i.e.,
+how far <b>map</b>'s points/centroids can be from the <b>query_map</b> features. 
+For further options, use <em>v.distance</em>.
+<p>In case of a multipoint input <b>map</b> 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>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).
-<p>In case that one or both input vector maps are 3D, features need to touch also
-in the 3rd dimension (z coordinate) in order to transfer attributes.
+<p>When transferring attributes from a point map into a polygon map,
+<b>dmax</b> has to be larger than zero, i.e., it will be determined by the
+distance between query points and polygon centroids. Importantly, distance
+is in meters for latitude-longitude locations.
+<p>In case that one or both input vector maps are 3D, features need to 
+touch also in the 3rd dimension (z coordinate) in order to transfer
+attributes.
 
 <h2>EXAMPLES</h2>
 
 In this example, the 'hospitals' point map in the North Carolina location is
 copied to the current mapset, a new attribute column is added and the urban
-names from the 'urbanarea' polygon map are transferred to the 'myhospitals'
-map at the hospital points' locations:
+names from the 'urbanarea' polygon map are transferred to hospital points
+locations in 'myhospitals' map:
 
 <div class="code"><pre>
 g.copy vect=hospitals,myhospitals
@@ -35,12 +40,12 @@
 v.db.select myhospitals
 </pre></div>
 <p>
-In this example, city names, population data and more from
+In this example, city names, population data and others from
 <a href="http://download.geonames.org/export/dump/">Geonames.org country files</a> are
 transferred to selected EU CORINE landuse/landcover classes
 ("Continuous urban fabric", 111, and "Discontinuous urban fabric", 112).
-Note: Example in UTM projection to which the input maps have been projected
-beforehand to have metric distances support:
+Note: The example is in UTM projection to which the input maps have been
+projected beforehand.
 
 <div class="code"><pre>
 # extract populated places from geonames
@@ -51,7 +56,7 @@
 v.what.vect corine_code111_112_cities query_map=geonames_IT_cities column=gnameid \
             query_column=geonameid dmax=3000
 # now gnameid can be used for v.db.join to join further
-# attributes in from geonames.org
+# attributes from geonames.org
 </pre></div>
 
 <h2>SEE ALSO</h2>