Hamish:
> use 'g.region rast=tile1,tile2,tile3,tile5' first to
> set the computational region to the outside bounds of all
> the tiles listed.
Nikos:
Something against using g.region's "-a" flag?
If all tiles are from the same source and of the same type it
will not be needed, as bounds will line up exactly. The -a flag
is useful when resampling is not harmful (e.g. before v.to.rast).
But needlessly resampling is to be avoided.
Hamish
Hamish:
> > use 'g.region rast=tile1,tile2,tile3,tile5' first to
> > set the computational region to the outside bounds of all
> > the tiles listed.
Nikos:
> Something against using g.region's "-a" flag?
If all tiles are from the same source and of the same type it
will not be needed, as bounds will line up exactly. The -a flag
is useful when resampling is not harmful (e.g. before v.to.rast).
But needlessly resampling is to be avoided.
Right! I forgot to write that I force resolution to be kept as is with
"res=RESOLUTION".
So "g.region -a res=SomeResolution rast=SomeRaster(s)" is ok or
non-sense?
Nikos