[GRASS-user] Use of Postgres/PostGIS with GRASS

GRASS GRASS user
, ,
1

Aren wrote:

Wait, so GRASS can read directly from PostGIS tables? I thought
you had to import all the data into GRASS first?

check out the new v.external module.

http://grass.osgeo.org/grass64/manuals/html64_user/v.external.html
http://grass.osgeo.org/grass64/manuals/html64_user/vectorintro.html

and the v.external.out module in GRASS 7-dev.

note this is about the geometry data, the attribute data could
already be stored in a plain postgres DB since GRASS 5.7.

also there is a new r.external module, combine that with GDAL's
`gdalbuildvrt` Virtual raster maps (eg *.tif) and cut out a whole
slew of middle-steps and disk writes.

don't expect these virtual maps to work as well as native maps
of course, but they shouldn't be buggy either.

Hamish

2

Wow, I don’t know how I missed that. I searched a lot and all I came up with were ways to import PostGIS data into GRASS.

Aren

On Fri, Feb 25, 2011 at 1:31 AM, Hamish <hamish_b@yahoo.com> wrote:

Aren wrote:

Wait, so GRASS can read directly from PostGIS tables? I thought
you had to import all the data into GRASS first?

check out the new v.external module.

http://grass.osgeo.org/grass64/manuals/html64_user/v.external.html
http://grass.osgeo.org/grass64/manuals/html64_user/vectorintro.html

and the v.external.out module in GRASS 7-dev.

note this is about the geometry data, the attribute data could
already be stored in a plain postgres DB since GRASS 5.7.

also there is a new r.external module, combine that with GDAL’s
gdalbuildvrt Virtual raster maps (eg *.tif) and cut out a whole
slew of middle-steps and disk writes.

don’t expect these virtual maps to work as well as native maps
of course, but they shouldn’t be buggy either.

Hamish