[GRASS-user] Re: getting from DBF to SQLite

GRASS GRASS user
1

Hi, Richard.

Is it is possible to set a single SQLite database for the entire GRASS GIS
database or each mapset requires its own sqlite db file?

Use <db.connect> and then <v.db.reconnect.all> to reconnect from DBF.

For my own needs I wrote small shell-script that makes one SQLite DB in mapset (with the mapset name) and copies all tables from DBF to SQLite (https://raw.github.com/amuriy/GRASS-scripts/f5157c8d2c8a5b3a9149cf207b62ef088a51d1ef/dbf2sqlite)

Best regards,
Alexander.

2

On Mon, Apr 9, 2012 at 1:27 PM, Alexander Muriy <amuriy@gmail.com> wrote:

Hi, Richard.

Is it is possible to set a single SQLite database for the entire GRASS GIS
database or each mapset requires its own sqlite db file?

Use <db.connect> and then <v.db.reconnect.all> to reconnect from DBF.

For my own needs I wrote small shell-script <dbf2sqlite> that makes one

...

For the record: there is now this simplified procedure available:

http://grasswiki.osgeo.org/wiki/Convert_all_GRASS_6_vector_maps_to_GRASS_7

(requires current GRASS 7 due to recent bugfixes)

Markus

3

2013/2/14 Markus Neteler <neteler@osgeo.org>

On Mon, Apr 9, 2012 at 1:27 PM, Alexander Muriy <amuriy@gmail.com> wrote:

Hi, Richard.

Is it is possible to set a single SQLite database for the entire GRASS GIS
database or each mapset requires its own sqlite db file?

Use <db.connect> and then <v.db.reconnect.all> to reconnect from DBF.

For my own needs I wrote small shell-script that makes one

…

For the record: there is now this simplified procedure available:

http://grasswiki.osgeo.org/wiki/Convert_all_GRASS_6_vector_maps_to_GRASS_7

(requires current GRASS 7 due to recent bugfixes)

Markus

Markus, thanks for the tip.

4

Richard wrote:

Is it is possible to set a single SQLite database
for the entire GRASS GIS database or each mapset requires
its own sqlite db file?

organize your system as you like, but be sure to ask yourself what
happens to portability with 32bit machines and/or filesystems when the overall DB file gets to be larger than 2gb or 4gb in size.
Even per-mapset sqlite DBs worry me a bit for that, not to mention
the damage-fallout from a bad HD sector or accidental `rm` and
ease of moving stuff to another mapset/ system by hand.

Hamish

5

On Thu, Feb 14, 2013 at 12:50 AM, Hamish <hamish_b@yahoo.com> wrote:

Richard wrote:

Is it is possible to set a single SQLite database
for the entire GRASS GIS database or each mapset requires
its own sqlite db file?

organize your system as you like, but be sure to ask yourself what
happens to portability with 32bit machines and/or filesystems when the overall DB file gets to be larger than 2gb or 4gb in size.

The maximum file size of a SQLite db is 140 TB, independent of the
architecture, i.e. LFS is always there. Usually SQLite will hit the
maximum file size limit of the underlying filesystem or disk hardware
size limit long before it hits its own internal size limit [0].

Markus M

[0] http://www.sqlite.org/fileformat2.html

Even per-mapset sqlite DBs worry me a bit for that, not to mention
the damage-fallout from a bad HD sector or accidental `rm` and
ease of moving stuff to another mapset/ system by hand.

Hamish
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user