[GRASS-user] getting from DBF to SQLite

Hamish hamish_b at yahoo.com
Thu Feb 14 15:42:39 PST 2013


Markus Metz wrote:
> In GRASS 6.4.1- it was possible to have a separate sqlite db
> for each vector in $MAPSET/vector/$MAP/sqlite.db. I have no
> idea why this option has been disabled. The VAR file can be
> 
> DB_DRIVER: sqlite
> DB_DATABASE:
> $GISDBASE/$LOCATION_NAME/$MAPSET/vector/$MAP/sqlite.db
> 
> Should we revert the changes that make it now impossible to
> have a separate sqlite db for each vector?

AFAIK it's still possible to have a separate sqlite db for each
vector if you use v.db.connect (see v.pack.py), it's just that
you can't tell db.connect to make that the default for all new
maps.

perhaps if [v.]db.connect understood to parse '$MAP' you could
have a portable 
database='$GISDBASE/$LOCATION_NAME/$MAPSET/vector/$MAP/sqlite.db'

string saved in the VAR file? (and so, by default but user-
alterable, all sqlite layers for that map saved in the same file)


"db.sqlite" or "sqlite.db" for the filename?


Hamish


More information about the grass-user mailing list