[GRASS-user] DB copy for v.db.connect
Markus Neteler
neteler at osgeo.org
Mon Nov 3 09:41:03 EST 2008
On Mon, Nov 3, 2008 at 12:37 PM, Hamish <hamish_b at yahoo.com> wrote:
> Hi,
>
> it is advised to copy DB before running v.db.connect to a second map, as
> if you delete the second map the DB will be removed for the parent map
> too. db.copy seems the obvious way to do that, but db.* only work if the
> source map (ie table) is in the same mapset as the new map. How to copy
> a DB from another mapset to the current one cleanly? Like 'g.copy vect='
> does, but only the DB table.
>
> e.g. attach table from roads at PERMANENT to new map in current mapset.
Could you trick it with
g.mapset
and generate a tmp sqlite file?
Markus
More information about the grass-user
mailing list