[GRASS-dev] v.in.osm working?

[Markus Metz]

On Thu, Aug 31, 2017 at 7:21 PM, Markus Metz <markus.metz.giswork at gmail.com>
wrote:
>
> I am not sure if v.in.ogr should be modified to use this special reading
mode for one single OGR supported format. The GDAL/OGR API is very
convenient because applications do not need to bother about particular
formats. If we start implementing code for particular formats in v.in.ogr,
we might open a Pandora's box...

Interleaved reading for OSM input has been added to v.in.ogr in trunk
r71464.

OSM import remains challenging. For v.in.ogr you need define a custom
OSM_CONFIG_FILE because the default osmconf.ini file will add all tags not
defined with attributes into "other_tags", potentially causing buffer
overflow. OSM polygons are overlapping which is correct because e.g.
administrative boundaries for multiple administrative levels are imported.

Markus M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20170904/92df5882/attachment.html>