patrick_gis at gmx.net
Sun Aug 2 07:56:53 PDT 2015
Thank you Stefan and Markus!
Had to finish a current a running process first, before being able to
test your proposal. Dbf-driver still very slow (same speed after
reboot), but with sqlite I can write approx 200.000points in 3 Minutes.
So only option for me sqlite.
However, I was surprised that GRASS70 was running with dbf. while it
should be sqlite by default. My workspace of GRASS is used by GRASS64
and GRASS70. As I could not convert all our code to 7.0, I need to have
the option of running 6.4 OR 7.0. The worksapce is emptied at the
beginning of each skript, so that I never rebuilt the topology. Is it
for that reason that GRASS70 runs/changes to dbf?
On 30.07.2015 21:17, Markus Neteler wrote:
> On Thu, Jul 30, 2015 at 2:26 PM, patrick s. <patrick_gis at gmx.net> wrote:
>> Thanks Stefan
>> It seems first of all v.out.ascii is slow. Following your proposaI, the
>> tmp-file has only 5300 observations after 9min15s. As I have 650.000 points
>> this export will need approx. 18h! Can I speed this up somehow?
>> (Database-driver is dbf)
> Yes: use the SQLite backend instead of DBF.
> You can convert it all automatically:
> "Convert automatically all GRASS 6 vector maps to GRASS 7 (including
> attribute transfer from DBF to SQLite)"
> and then enjoy the speed.
More information about the grass-user