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

Markus Metz markus.metz.giswork at gmail.com
Thu Aug 24 00:30:22 PDT 2017


On Tue, Aug 22, 2017 at 8:37 PM, Markus Neteler <neteler at osgeo.org> wrote:
>
> Hi,
>
> does v.in.osm actually work? I am trying to import from a OSM PBF
> file, for example:
>
> http://download.geofabrik.de/europe/germany/berlin.html
> --> berlin-latest.osm.pbf (51MB)
>
> grass72 ~/grassdata/latlong_wgs84/osm
> g.extension v.in.osm
>
> v.in.osm input=Downloads/berlin-latest.osm.pbf table=lines
> type=point,line output=roads --o
> WARNING: Width for column osm_id set to 255 (was not specified by OGR),
>          some strings may be truncated!
> WARNING: Width for column name set to 255 (was not specified by OGR), some
>          strings may be truncated!
> WARNING: Width for column highway set to 255 (was not specified by OGR),
>          some strings may be truncated!
> WARNING: Width for column waterway set to 255 (was not specified by OGR),
>          some strings may be truncated!
> WARNING: Width for column aerialway set to 255 (was not specified by OGR),
>          some strings may be truncated!
> WARNING: Width for column barrier set to 255 (was not specified by OGR),
>          some strings may be truncated!
> WARNING: Width for column man_made set to 255 (was not specified by OGR),
>          some strings may be truncated!
> WARNING: Width for column other_tags set to 255 (was not specified by
OGR),
>          some strings may be truncated!
> WARNING: Vector map <roads> already exists and will be overwritten
> WARNING: No data base element files found
>
> v.info -t roads
> nodes=0
> points=0
> lines=0
> boundaries=0
> centroids=0
> areas=0
> islands=0
> primitives=0
> map3d=0

You can use v.in.ogr directly for OSM PBF files (
http://gdal.org/drv_osm.html).

BTW, with GDAL 2.2.1, using OGR_INTERLEAVED_READING=YES does not work for
me (empty vector).

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


More information about the grass-dev mailing list