Bulent Arikan wrote:
> > Cubic interpolation can introduce overshoot, as can other forms of
> > spline interpolation. Linear and nearest-neighbor interpolation don't
> > have this issue.
> >
> > With r.resamp.rst, the problem can be alleviated to a degree by using
> > higher values for the tensio
Thanks Glynn.
That makes sense now. I did not know about the inherent problem of
overshooting in cubic interpolation. ASTER DEMs I have seem to be pretty
consistent in terms of data ranges and representation of values (based on
r.report), so I am not sure about the noise effect in my case. However
Bulent Arikan wrote:
> I am running GRASS 6.5 svn (Snow Leopard). I have several ASTER GDEMs
> (Latlong, 30m res.), which I reprojected into UTM using both 'nearest' and
> 'cubic' methods ('r.proj'). Only in some imagery that are reprojected in
> cubic, I ended up having couple of cells (literall
Hi,
I am running GRASS 6.5 svn (Snow Leopard). I have several ASTER GDEMs
(Latlong, 30m res.), which I reprojected into UTM using both 'nearest' and
'cubic' methods ('r.proj'). Only in some imagery that are reprojected in
cubic, I ended up having couple of cells (literally, 1-2 cells out of 8
mill
