Re: [gdal-dev] SQLite driver hit and miss with spatial index

2017-04-06 Thread Jan Heckman
Hi, Out of interest, I tried the tack of converting to shapefile with a .dbf only containing the primary index OGC_FID. This might provide an alternative for indexed access to the geometry. I see it isn't needed anymore, but anyway, for info and comparison: What worked: - shapefile record count 252

Re: [gdal-dev] SQLite driver hit and miss with spatial index

2017-04-06 Thread jratike80
w FDO vs. Spatialite speeds differ in non-indexed searches but I guess you prefer making controlled tests by change only one thing at a time. -Jukka Rahkonen- -- View this message in context: http://osgeo-org.1560.x6.nabble.com/gdal-dev-SQLite-driver-hit-and-miss-with-spatial-index-tp5316090p5

Re: [gdal-dev] SQLite driver hit and miss with spatial index

2017-04-06 Thread Frederik Ramm
Hi, while what I wrote in the previous post is still interesting and a bit strange, I have meanwhile upgraded to GDAL 2 packages from the ubuntugis-unstable repository for Xenial, and now the behaviour is as I would expect it: The ogr2ogr -spat command *with* indexes takes practically no time (

[gdal-dev] SQLite driver hit and miss with spatial index

2017-04-06 Thread Frederik Ramm
Dear gdal folks, TL;DR: ogrinfo uses an SQLite spatial index but ogr2ogr doesn't? I'm debugging a performance issue with my "OSM Inspector" web site, where I use a large number of SQLite files in Mapserver, and Mapserver takes very long to pick the data it wants to display. I have managed to boi