Even Rouault <even.rouault <at> mines-paris.org> writes: > Hum, the OGR driver was indeed written a bit too naively, assuming that > MBRIntersects() would be similar to the && operator in PostGIS. Apparently > not. > Strange that this hasn't been reported before, but I assume you can only > see the > difference with big amount of data, like your OSM database (and the > MBRIntersects() test must be faster than evaluating the spatial filter on OGR > side, so that's perhaps why it wasn't seen at implementation time). Anyway, > would you mind opening a Trac ticket about this ? Changing the request to use > the spatial index table should not be too difficult.
Ticket [GDAL] #4212 done with sample requests which should show the speed difference and a download link to a test database which is created with ogr2ogr v. 1.8.1. -Jukka Rahkonen- _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
