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.<div><br></div><div>Aren<br><br><div class="gmail_quote">On Fri, Feb 25, 2011 at 1:31 AM, Hamish <span dir="ltr"><<a href="mailto:hamish_b@yahoo.com">hamish_b@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Aren wrote:<br>
> Wait, so GRASS can read directly from PostGIS tables? I thought<br>
> you had to import all the data into GRASS first?<br>
<br>
</div>check out the new v.external module.<br>
<br>
<a href="http://grass.osgeo.org/grass64/manuals/html64_user/v.external.html" target="_blank">http://grass.osgeo.org/grass64/manuals/html64_user/v.external.html</a><br>
<a href="http://grass.osgeo.org/grass64/manuals/html64_user/vectorintro.html" target="_blank">http://grass.osgeo.org/grass64/manuals/html64_user/vectorintro.html</a><br>
<br>
and the v.external.out module in GRASS 7-dev.<br>
<br>
note this is about the geometry data, the attribute data could<br>
already be stored in a plain postgres DB since GRASS 5.7.<br>
<br>
<br>
also there is a new r.external module, combine that with GDAL's<br>
`gdalbuildvrt` Virtual raster maps (eg *.tif) and cut out a whole<br>
slew of middle-steps and disk writes.<br>
<br>
<br>
don't expect these virtual maps to work as well as native maps<br>
of course, but they shouldn't be buggy either.<br>
<font color="#888888"><br>
<br>
Hamish<br>
<br>
<br>
<br>
<br>
</font></blockquote></div><br></div>