[GRASS-SVN] r69097 - in grass/branches/releasebranch_7_0: scripts/v.import vector/v.in.ogr

Sat Aug 6 09:35:16 PDT 2016

Author: neteler
Date: 2016-08-06 09:35:16 -0700 (Sat, 06 Aug 2016)
New Revision: 69097

Modified:
   grass/branches/releasebranch_7_0/scripts/v.import/v.import.html
   grass/branches/releasebranch_7_0/vector/v.in.ogr/v.in.ogr.html
Log:
v.in.ogr + v.import manual: description extended

Modified: grass/branches/releasebranch_7_0/scripts/v.import/v.import.html
===================================================================

--- grass/branches/releasebranch_7_0/scripts/v.import/v.import.html	2016-08-06 16:34:49 UTC (rev 69096)
+++ grass/branches/releasebranch_7_0/scripts/v.import/v.import.html	2016-08-06 16:35:16 UTC (rev 69097)
@@ -1,12 +1,27 @@
 <h2>DESCRIPTION</h2>
 
-<em>v.import</em> imports selected layers from a OGR vector datasource
-into the current location and mapset. If the projection of the input
+<em>v.import</em> imports vector data from files and database connections
+supported by the <a href="http://www.gdal.org/">OGR</a> library) into the
+current location and mapset. If the projection of the input
 does not match the projection of the location, the input is reprojected
-into the current location. If the projection of the input does match
-the projection of the location, the input is imported directly with
-<a href="v.in.ogr.html">v.in.ogr</a>.
+into the current location. In case that the projection of the input map
+does match the projection of the location, the input is imported directly.
 
+<h3>Supported Vector Formats</h3>
+
+<em>v.import</em> uses the OGR library which supports various vector data
+formats including <a href="http://www.gdal.org/drv_shapefile.html">ESRI
+Shapefile</a>, <a href="http://www.gdal.org/drv_mitab.html">Mapinfo
+File</a>, UK .NTF, SDTS, TIGER, IHO S-57 (ENC), DGN, GML, GPX, AVCBin, REC,
+Memory, OGDI, and PostgreSQL, depending on the local OGR installation.
+For details see the <a href="http://www.gdal.org/ogr_formats.html">OGR web
+site</a>. The OGR (Simple Features Library) is part of the
+<a href="http://www.gdal.org">GDAL</a> library, hence GDAL needs to be
+installed to use <em>v.in.ogr</em>.
+
+<p>
+The list of actually supported formats can be printed by <b>-f</b> flag.
+
 <h2>NOTES</h2>
 
 <h3>Topology cleaning</h3>

Modified: grass/branches/releasebranch_7_0/vector/v.in.ogr/v.in.ogr.html
===================================================================
--- grass/branches/releasebranch_7_0/vector/v.in.ogr/v.in.ogr.html	2016-08-06 16:34:49 UTC (rev 69096)
+++ grass/branches/releasebranch_7_0/vector/v.in.ogr/v.in.ogr.html	2016-08-06 16:35:16 UTC (rev 69097)
@@ -1,11 +1,9 @@
 <h2>DESCRIPTION</h2>
 
-<em>v.in.ogr</em> imports vector data
-using <a href="http://www.gdal.org/">OGR</a> library to GRASS
-vector map. OGR (Simple Features Library) is part of the
-<a href="http://www.gdal.org">GDAL</a> library, so you need to
-install GDAL to use <em>v.in.ogr</em>.
- 
+<em>v.in.ogr</em> imports vector data from files and database connections
+supported by the <a href="http://www.gdal.org/">OGR</a> library) into the
+current location and mapset.
+
 <p>
 If the <b>layer</b> parameter is not given, all available OGR layers
 are imported as separate GRASS layers into one GRASS vector map. If
@@ -21,6 +19,21 @@
 region settings as the spatial bounds
 (see <em><a href="g.region.html">g.region</a></em>).
 
+<h3>Supported Vector Formats</h3>
+
+<em>v.in.ogr</em> uses the OGR library which supports various vector data
+formats including <a href="http://www.gdal.org/drv_shapefile.html">ESRI
+Shapefile</a>, <a href="http://www.gdal.org/drv_mitab.html">Mapinfo
+File</a>, UK .NTF, SDTS, TIGER, IHO S-57 (ENC), DGN, GML, GPX, AVCBin, REC,
+Memory, OGDI, and PostgreSQL, depending on the local OGR installation.
+For details see the <a href="http://www.gdal.org/ogr_formats.html">OGR web
+site</a>. The OGR (Simple Features Library) is part of the
+<a href="http://www.gdal.org">GDAL</a> library, hence GDAL needs to be
+installed to use <em>v.in.ogr</em>.
+
+<p>
+The list of actually supported formats can be printed by <b>-f</b> flag.
+
 <h3>Topology cleaning</h3>
 Topology cleaning on areas is automatically performed, but may fail in
 special cases. In these cases, a <b>snap</b> threshold value is 
@@ -43,19 +56,6 @@
 larger than the threshold. Snapping is by default disabled with
 -1. See also the <em><a href="v.clean.html">v.clean</a></em> manual.
 
-<h3>Supported OGR Vector Formats</h3>
-
-OGR library supports various vector data formats
-including <a href="http://www.gdal.org/drv_shapefile.html">ESRI
-Shapefile</a>, <a href="http://www.gdal.org/drv_mitab.html">Mapinfo
-File</a>, UK .NTF, SDTS, TIGER, IHO S-57 (ENC), DGN, GML, AVCBin, REC,
-Memory, OGDI, and PostgreSQL depend on the local installation, for
-details see <a href="http://www.gdal.org/ogr_formats.html">OGR web
-site</a>.
-
-<p>
-List of locally supported formats can be printed by <b>-f</b> flag.
-
 <h3>Overlapping polygons</h3>
 
 When importing overlapping polygons, the overlapping parts will become
@@ -83,8 +83,7 @@
 <p>
 If the user wishes to ignore the difference between the apparent
 coordinate system of the source data and the current location, they
-may pass the
-<b>-o</b> flag to override the projection check.
+may pass the <b>-o</b> flag to override the projection check.
 
 <p>
 If the user wishes to import the data with the full projection
@@ -95,10 +94,15 @@
 of the command, a new location will have been created (with only a
 PERMANENT mapset), and the vector map will have been imported with the
 indicated <b>output</b> name into the PERMANENT mapset.
+<p>
+An interesting wrapper command around <em>v.in.ogr</em> is
+<a href="v.import.html">v.import</a> which reprojects (if needed) the
+vector dataset during import to the projection of the current location.
 
 <h2>NOTES</h2>
 
-The characters used for table column names are limited. Supported are:
+The characters which are eligible for table column names are limited
+by the SQL standard. Supported are:
 
 <div class="code"><pre>
 [A-Za-z][A-Za-z0-9_]*

