[GRASS-user] v.to.rast

[patrick s.]

Thx, Markus.

This explains a lot. Initial setup was GRASS 6- so it kept being dbf.

Also good to know, how much more efficient sqlite is.

Speaking of efficiency:
Is the speed of PostgreSQL as backend comparable to sqlite? I can't
find any benchmarks on db-usage here:
http://grasswiki.osgeo.org/wiki/GRASS_GIS_Performance


Patrick

On 02.08.2015 20:05, Markus Neteler wrote:
>> However, I was surprised that GRASS70 was running with dbf. while it should
>> be sqlite by default.
> It is.
> But if the location had been generated with GRASS 6, then DBF remains
> as before unless you run the earlier indicated update procedure.
>
>> 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?
> You simply need to switch to the SQLite driver by
>
> # define new default DB connection (switch from DBF to SQLite)
> db.connect -d
>
> http://grass.osgeo.org/grass70/manuals/db.connect.html#sqlite-%28default-backend%29
>
> That's fine also for GRASS 6.
>
> Concerning the vector geometry: in order to switch back and forth
> between G6 and G7, you need to rebuild the topology using
>
> # first rebuild topology for all vector maps in current mapset
> v.build.all
>
> which is available in both G6 and G7.
>
> Hope this helps,
> Markus