[GRASS-dev] Re: [GRASS GIS] #465: r.proj.seg thins along null areas and raster bounds for bilinear and cubic methods

[Glynn Clements]

[Replying here as Trac is not responding at this time.]

GRASS GIS wrote:

>  > There is no need to modify the existing functions; just check whether
>  > the calculated value is null.
> 
>  Checking if the output is null doesn't tell us if it's null because the
>  nearest input cell is null or because it interpolated to null from nulls
>  in the matrix. 

Try nearest first; if that returns null, then you know that bilinear
and bicubic will also return null, so you can just abort at that
point. Otherwise, try bicubic then bilinear.

-- 
Glynn Clements <glynn at gclements.plus.com>