it's some months now that I am trying to learn GRASS-GIS and I wonder
1. if one needs to copy some GRASS raster data from his data base in
another computer's GRASS data base (same coordinate system of course),
then how? Where do for example the history files go?
I understand (I think) the need to set-up properly a LOCATION and import
the data. But why isn't there a GRASS portable vector/ raster file
format?
2. the same about vector data
3. Is it really necessaty to export in shapefiles when working with
starspan? If there is "GRASS read-only" support by OGR why is it
necessary to export?
What about OpenEV? If GDAL is built with GRASS support why can't it read
GRASS rasters?
1.. if one needs to copy some GRASS raster data from his data base in
another computer's GRASS data base (same coordinate system of course),
then how? Where do for example the history files go?
See r.pack/r.unpack in the Grass Add-ons. I use these scripts for moving
rasters around from computer to computer:
The r.pack script uses a MatLab format file as an intermediary, and is apparently
a decent universal format for storing rasters in.
I understand (I think) the need to set-up properly a LOCATION and import
the data. But why isn't there a GRASS portable vector/ raster file
format?
I think r.in/out.ascii and v.in/out.ascii are designed for this? Not 100%
sure, but check the man pages for these two commands.
2. the same about vector data
See above.
3. Is it really necessaty to export in shapefiles when working with
starspan? If there is "GRASS read-only" support by OGR why is it
necessary to export?
I can't comment on Starspan; never used it.
What about OpenEV? If GDAL is built with GRASS support why can't it read
GRASS rasters?
On Mon, 2008-03-10 at 14:23 -0400, Patton, Eric wrote:
>1.. if one needs to copy some GRASS raster data from his data base in
>another computer's GRASS data base (same coordinate system of course),
>then how? Where do for example the history files go?
See r.pack/r.unpack in the Grass Add-ons. I use these scripts for moving
rasters around from computer to computer:
The r.pack script uses a MatLab format file as an intermediary, and is apparently
a decent universal format for storing rasters in.
O.K.
>I understand (I think) the need to set-up properly a LOCATION and import
>the data. But why isn't there a GRASS portable vector/ raster file
>format?
I think r.in/out.ascii and v.in/out.ascii are designed for this? Not 100%
sure, but check the man pages for these two commands.
I am checking... It's just that I had the impression that exporting in
ascii is always a bit "dangerous" concerning the metadata this is why I
try to avoid it.
>2. the same about vector data
See above.
>3. Is it really necessaty to export in shapefiles when working with
>starspan? If there is "GRASS read-only" support by OGR why is it
>necessary to export?
I can't comment on Starspan; never used it.
>What about OpenEV? If GDAL is built with GRASS support why can't it read
>GRASS rasters?
> 1.. if one needs to copy some GRASS raster data from his data base
> in another computer's GRASS data base (same coordinate system of
> course), then how? Where do for example the history files go?
The r.pack script uses a MatLab format file as an intermediary, and
is apparently a decent universal format for storing rasters in.
In hindsight exporting to another format will always be problematic and
potentially lossy, it would be better to rewrite r.pack by simply
finding the GRASS files and zipping them up, then have r.unpack
distribute them back around.
> I understand (I think) the need to set-up properly a LOCATION and
> import the data. But why isn't there a GRASS portable vector/
> raster file format?
the easiest way to move grass data is to tarball/zip up the location
directory and copy it across. If you want just one or two select raster
maps use g.copy from a temporary mapset, then zip up the location with
just the temporary and PERMANENT mapsets.
it is hoped for GRASS 7 to move raster maps into a per-map directory
structure like the vector maps instead of having them spread their
parts all over the mapset.
> 2. the same about vector data
vector data is easy, just copy over the data's folder in the
$MAPSET/vector/ directory, and it's database file too. Make sure to
reconnect the database once it arrives at its new home.
