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

[Markus Neteler]

On Mon, Sep 4, 2017 at 8:32 PM, Markus Metz
<markus.metz.giswork at gmail.com> wrote:
> On Thu, Aug 31, 2017 at 7:21 PM, Markus Metz <markus.metz.giswork at gmail.com>
>>
>> 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.

Thanks for that!

> 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.

Perhaps we can cook up some examples in the GRASS Wiki for common use
cases (or add to the manual page of v.in.ogr)?

markusN