[GRASS-user] MP "tiled" processing?

Hamish hamish_b at yahoo.com
Mon Jan 4 22:24:07 EST 2010

Jonathan wrote:
>    I'm curious if anyone has developed any
> scripts to divide a raster process up *spatially* across
> multiple processors, given a) a tile size and b) an overlap
> size.  We are hoping to run r.sun at 10m across
> California, and would like to break up the full process into
> smaller individual tiles.  Anyone done anything like
> this before and would be willing to share your script? 

be careful with r.sun tiles that you don't crop away shading
mountains just outside of the region. ie you want to include
as much of the "light catchment" basin as possible.

to minimize edge effects I always try to run r.sun with a bit
bigger domain than I am really interested in & allow for some
overlap. when patching two overlapping tiles back together
perhaps 'min' is the method to use? or do you really need to
patch them back together at all?

how many rows x cols is CA @ 10m? at least it is tall & narrow,
which is the optimum for memory use with the raster engine.
staying with the same map projection for the whole thing?

there are a number of tiling scripts around, e.g. r.tileset,
the d.out.gpsdrive man page, one comes with newer gdal-bin,
here is another:

I guess from the "*spatially*" you've seen the r.sun wiki page with its 'poor-man's multi-processing trick' for per-day MP?
r.sun does not use the segment library AFAIR, so parallizing
that wouldn't help.



More information about the grass-user mailing list