So assuming that we have duplicated the projection info from one
filesystem to the next (the case I'm dealing with is running out of
space on one filesystem, and we needed to continue work on another but
using the same projection info) -- if I create mapset on one of the
two filesystems, and then symlink it within the identical location on
the other filesystem, would this work to allow me to g.copy (or,
indeed, allow me to reference the files using @ from both
filesystems?)

--j

On Fri, May 14, 2010 at 11:05 AM, Glynn Clements
<[email protected]> wrote:
>
> Jonathan Greenberg wrote:
>
>> I have some rasters in a grass data directory on a different mounted
>> drive in unix that i want to copy into a different data directory +
>> mapset -- i can't seem to figure out how to do this with g.copy, which
>> AFAIK only copies from mapsets within a given data directory.
>
> Indeed, g.copy only works on maps within the same location. For good
> reason: maps in different locations typically have different
> projections, so you can't simply copy the data.
>
> The only supported ways of "copying" a map in a different location
> are:
>
> 1. Use r.proj or v.proj, which will re-project the data based upon the
> projections of the source location and the current location.
>
> 2. Use e.g. r.out.gdal/v.out.ogr to export the data and
> r.in.gdal/v.in.ogr to re-import it. The latter will check that the
> projection is correct.
>
> --
> Glynn Clements <[email protected]>
>
_______________________________________________
grass-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-user

Reply via email to