[GRASS-SVN] r71536 - grass/trunk/vector/v.in.ogr
svn_grass at osgeo.org
svn_grass at osgeo.org
Sat Oct 7 12:25:43 PDT 2017
Author: mmetz
Date: 2017-10-07 12:25:43 -0700 (Sat, 07 Oct 2017)
New Revision: 71536
Modified:
grass/trunk/vector/v.in.ogr/v.in.ogr.html
Log:
v.in.ogr: add explanation for OSM import
Modified: grass/trunk/vector/v.in.ogr/v.in.ogr.html
===================================================================
--- grass/trunk/vector/v.in.ogr/v.in.ogr.html 2017-10-07 17:42:57 UTC (rev 71535)
+++ grass/trunk/vector/v.in.ogr/v.in.ogr.html 2017-10-07 19:25:43 UTC (rev 71536)
@@ -21,15 +21,17 @@
<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>.
+<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 <b>-f</b> prints a list of the vector formats supported
+by the system's OGR (Simple Features Library). 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.
@@ -298,6 +300,41 @@
</pre></div>
--->
+<h3>OpenStreetMap (OSM)</h3>
+
+<a href="http://gdal.org/drv_osm.html">OSM data</a> are available in
+.osm (XML based) and .pbf (optimized binary) formats. The .pbf format
+is recommended because file sizes are smaller. The OSM driver will
+categorize features into 5 layers :
+<ul>
+ <li><b>points</b>: "node" features that have significant tags attached.
+ <li><b>lines</b>: "way" features that are recognized as non-area.
+ <li><b>multilinestrings</b>: "relation" features that form a
+multilinestring(type = 'multilinestring' or type = 'route').
+ <li><b>multipolygons</b>: "relation" features that form a multipolygon (type
+= 'multipolygon' or type = 'boundary'), and "way" features that are
+recognized as area.
+ <li><b>other_relations</b>: "relation" features that do
+not belong to any of the above layers.
+</ul>
+
+It is recommended to import one layer at a time.
+
+<p>
+Import of OSM data requires a configuration file, defined with the
+OSM_CONFIG_FILE configuration option. In the data folder of the GDAL
+distribution, you can find a osmconf.ini file that can be customized to
+fit your needs. See
+<a href="http://wiki.openstreetmap.org/wiki/Map_Features">OSM map features</a>
+for keys and their values. You should set "other_tags=no" to
+avoid problems with import or querying the imported vector. Once a
+OSM_CONFIG_FILE has been created, OSM data can be imported with e.g.
+
+<div class="code"><pre>
+export OSM_CONFIG_FILE=/path/to/osmconf.ini
+v.in.ogr input=name.pbf layer=lines output=osm_data
+</pre></div>
+
<h3>Oracle Spatial</h3>
Note that you have to set the environment-variables <tt>ORACLE_BASE,
More information about the grass-commit
mailing list