Send grass-windows mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.osgeo.org/mailman/listinfo/grass-windows
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of grass-windows digest..."


Today's Topics:

   1. Re: Copying data from location to location (Markus Neteler)


----------------------------------------------------------------------

Message: 1
Date: Mon, 14 Sep 2009 20:24:51 +0200
From: Markus Neteler <[email protected]>
Subject: Re: [GRASS-windows] Copying data from location to location
To: Louis Becker <[email protected]>
Cc: [email protected]
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Sep 14, 2009 at 1:41 PM, Louis Becker
<[email protected]> wrote:
> Hi
>
> I am trying to copy vector data from one location (loc1) to another (loc2).
> Loc1 used to be a copy of loc2, but now exists on another computer. I would
> like for copy a vector set from loc1 into loc2. The only way I can find is
> v.proj, but it takes very long.

In the case that loc1 is a copy of loc2, v.proj isn't ideal because
it is an unnecessary data modification.

> Another way would be to export and import,

Also not ideal...

> but I believe that it will also take very long. Is there another way?

Yes: just copy the files. The structure is very easy in case you
use DBF as backend (or almost also with SQLite).
You need to package the relevant DBF file(s) in the dbf/ directory
and the vector geometry directory. Just extract on the target
computer into the appropriate directories and that's it.

Markus


------------------------------

_______________________________________________
grass-windows mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-windows


End of grass-windows Digest, Vol 37, Issue 4
********************************************

Reply via email to