On Mon, Feb 8, 2010 at 5:18 AM, Hamish <hamis...@yahoo.com> wrote: > Markus Metz wrote: ... >> I forgot to mention, there is a problem with sqlite, it is much slower >> than dbf, no idea if this is a problem of my system or of the grass >> sqlite driver or of the way auxiliary tables are accessed by the lidar >> tools. > > that sounds vaguely familiar, but as a general thing not necessarily > to do with v.lidar. probably something about it in the archives?
I found some older conversation incl. patches and speed tests: http://lists.osgeo.org/pipermail/grass-user/2009-June/051009.html ... perhaps useful? On Mon, Feb 8, 2010 at 9:17 AM, Markus Metz <markus.metz.gisw...@googlemail.com> wrote: > I discovered two little tricks: first, create the table, close database and > driver, open database and driver again, work with table, second, creating an > index on the table if possible helps too. Tested with sqlite and dbf. I wonder if sqlite is creating some index when creating/closing/opening again? Markus _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
