[Qgis-user] ogr2ogr, osm, and spatialite

Maurizio Trevisani maurizio.trevisani at gmail.com
Sun Aug 31 14:21:41 PDT 2014


Qgis performance in accessing spatialite large tables depends on
spatial index and statistics.
Maybe RecoverSpatialIndex, InvalidateLayerStatistics and
UpdateLayerStatistics could help.
Maurizio

2014-08-31 22:03 GMT+02:00, Jukka Rahkonen <jukka.rahkonen at mmmtike.fi>:
> Even Rouault <even.rouault at ...> writes:
>
>>
>> Le dimanche 31 août 2014 21:50:31, Jukka Rahkonen a écrit :
>> > Thomas Endres <endres.thomas <at> ...> writes:
>
>> Actually, this warning is just a warning, and not a critical error that
>> will
>> stop conversion. When this occurs, the way/relation will be skipped. Due
>> to
>> the way the OSM database is done, it is possible to have non-valid
>> polygons,
>> and indeed there are such polygons.
>> So you can safely ignore those warnings about organizePolygons()
>
> Then the database is probably OK but Thomas has still a real problem with it
> and QGIS. Does QGIS possibly do some heavy queries for getting layer extents
> or some other metadata like that? The 33 GB Spatialite file is biggish but I
> have been testing one 250 GB Spatialite db and if works well if queries are
> selective and there are indexes to support those.
>
> -Jukka Rahkonen-
>
> _______________________________________________
> Qgis-user mailing list
> Qgis-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-user



More information about the Qgis-user mailing list