Just for the record:
osm2pgsql creates from toscana.osm:
184189 points
241755 lines from ways
8420 lines from route relations
309712 polygons from closed ways and multipolygon relations
Using ogr2ogr to export the .osm into a sqlite database, I get
184141 points
243147 lines from ways
1476 m
Hi Giovanni,
It's 2.2. Anyway I don't think it's a problem with IDs. Data is read from
the Sqlite DB and written to the same DB as Spatialite tables. They aren't
loaded as QGIS layers, neither data provider nor features are instanciated
during the process (afaik).
Giovanni
2014-05-16 9:09 GMT+02
Mmm, I wasn't aware of such numbers. Anyway, a lot of ways are linestrings,
not polygons. Imposm import the correctly. I haven't trie
spatialite_osm_map and ogr2ogr yet, but I can't understand why simple
linestrings happen to get dropped during this phase...
giovanni
2014-05-15 22:47 GMT+02:00 A
Am 15.05.2014 16:56, schrieb G. Allegri:
Here are the counts on the tables generated by QGIS' OSM utilities:
SELECT count(*) FROM ways
union
SELECT count(*) FROM toscana_osm_polylines
count
--
221335
568129
More then a half ways are not translated.
No, its not that bad.
From 56812
Running the QGIS OSM utilites to create a Spatialite db, I've noticed that
during the last phase (converting nodes.ways to spatialite tables) a lot of
data got lost.
I tested the Tuscany .osm file [1]
and I extracted a portion of it with osmosis:
toscana.osm.bz2 | ./osmosis --rx /dev/stdin --bou
