[GRASS-user] GRASS7.2: v.in.osm add-on / Windows 8

[Helmut Kudrnovsky]

Helmut Kudrnovsky wrote
> just imported all lines where there is an entry in the "highway" column
> for me.
> 
> it's what in
> https://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.in.osm/v.in.osm.py#L117
> 
> 117	            grass.run_command('v.in.ogr',
> 118	                             quiet=True,
> 119	                             input=options['input'],
> 120	                             output=self.getNewTmp('ogr'),
> 121	                             layer=options['table'],
> 122	                             where=options['where'],
> 123	                             type=options['type'],
> 124	                             flags=flags['o']
> 125	                            )

and when i mimic the manual example by choosing points and lines layer:

v.in.osm input=saarland-latest.osm.pbf table=lines type=point,line
output=roads \
         where="highway is not null"

by

v.in.ogr input=D:\dl\osm\saarland-latest.osm.pbf layer=lines,points
output=roadsvingor where=highway is not null
WARNING: The 'where' option is applied only to the first OGR layer
Check if OGR layer <lines> contains polygons...
Check if OGR layer <points> contains polygons...
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!
Importing -1 features (OGR layer <lines>)...
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 barrier 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 ref set to 255 (was not specified by OGR), some
strings may be truncated!
WARNING: Width for column address set to 255 (was not specified by OGR),
some strings may be truncated!
WARNING: Width for column is_in set to 255 (was not specified by OGR), some
strings may be truncated!
WARNING: Width for column place 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!
Importing -1 features (OGR layer <points>)...
-----------------------------------------------------
Building topology for vector map <roadsvingor at osm>...
Registering primitives...
167878 primitives registered
844331 vertices registered
Building areas...
0 areas built
0 isles built
Attaching islands...
Attaching centroids...
Number of nodes: 143707
Number of primitives: 167878
Number of points: 63070
Number of lines: 104808
Number of boundaries: 0
Number of centroids: 0
Number of areas: 0
Number of isles: 0

it imports lines in layer1 and points in layer2; although in layer 2 it
claims that there is an inconsistent number of columns in the layer 2's
table.

anyone any idea why v.in.osm doesn't work?



-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GRASS7-2-v-in-osm-add-on-Windows-8-tp5304461p5304475.html
Sent from the Grass - Users mailing list archive at Nabble.com.