Jonathan Greenberg wrote:
Thanks, but I'm more curious in just the generic way GRASS does
tiled processing (say, in mapcalc). I assume there is a low-level
processing layer GRASS uses (or no?).
GRASS' primary raster processing model is row-by-row. Where possible,
the code reads a row,
GRASSers:
I was curious -- how is tiled processing realized in GRASS GIS? Is
there a fixed input tile size (in MB of RAM or # of lines)? Is there
some documentation buried on the GRASS site that describes the
algorithm? I'm trying to replicate an efficient tiled approach in R --
I was
Milton:
Thanks, but I'm more curious in just the generic way GRASS does
tiled processing (say, in mapcalc). I assume there is a low-level
processing layer GRASS uses (or no?). I'm not doing a direct grass-to-R
link, I'm doing the processing completely within R with rgdal, but I'm
Hi Jonathan,
When I need to do tiles processing of grass coupled R, I usually set a list
of bounding boxes on R (a list of x1, x2, y1, y2), and then I put it on a
for() looping. So, I set a new g.region using n= s= e= and w= parameters
using system() function of R (you can do it of other ways).
