v.in.ogr manual: hint for Latitude-longitude data (fix trac https://trac.osgeo.org/grass/ticket/1443); subtitles added in NOTES section

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

vector/v.in.ogr/v.in.ogr.html

@@ -101,6 +101,7 @@ vector dataset during import to the projection of the current location.
 
 <h2>NOTES</h2>
 
+<h3>Table column names: supported characters</h3>
 The characters which are eligible for table column names are limited
 by the SQL standard. Supported are:
 
@@ -132,14 +133,15 @@ unique. (hint: copy and modify the list given with the error message).
 Alternatively, change the local DB with
 <em><a href="db.connect.html">db.connect</a></em>.
 
-<p>
-When importing Esri Shapefiles the OGR library tries to read the
+<h3>File encoding</h3>
+When importing ESRI Shapefiles the OGR library tries to read the
 LDID/codepage setting from the .dbf file and use it to translate
 string fields to UTF-8. LDID &quot;87 / 0x57&quot; is treated as
 ISO8859_1 which may not be appropriate for many
 languages. Unfortunately it is not clear what other values may be
 appropriate (see example below). To change encoding the user can set
-up <tt>SHAPE_ENCODING</tt> environmental variable or simply to define
+up <tt><a href="https://trac.osgeo.org/gdal/wiki/ConfigOptions#SHAPE_ENCODING">SHAPE_ENCODING</a></tt>
+environmental variable or simply to define
 encoding value using <b>encoding</b> parameter. Note that recoding
 support is new for GDAL/OGR 1.9.0.
 
@@ -147,19 +149,23 @@ support is new for GDAL/OGR 1.9.0.
 Value for <b>encoding</b> also affects text recoding when importing
 DXF files. For other formats has encoding value no effect.
 
-<p>
-Option <b>key</b> specifies column name used for feature
+<h3>Defining the key column</h3>
+Option <b>key</b> specifies the column name used for feature
 categories. This column must be integer. If not specified, categories
 numbers are generated starting with 1 and stored in the column named
 &quot;cat&quot;.
 
-<p>
+<h3>Supports of multiple geometry columns</h3>
 Starting with GDAL 1.11 the library supports multiple geometry columns
 in OGR. By default <em>v.in.ogr</em> reads all geometry columns from
 given layer. The user can choose desired geometry column
 by <b>geometry</b> option,
 see <a href="#multiple-geometry-columns">example below</a>.
 
+<h3>Latitude-longitude data: Vector postprocessing after import</h3>
+For vector data like a grid, horizontal lines need to be broken at their
+intersections with vertical lines (<b>v.clean ... tool=break</b>).
+
 <h2>EXAMPLES</h2>
 
 The command imports various vector formats: