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

[GRASS GIS]

#465: r.proj.seg thins along null areas and raster bounds for bilinear and cubic
methods
------------------------+---------------------------------------------------
  Reporter:  kyngchaos  |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect     |      Status:  new                      
  Priority:  major      |   Milestone:                           
 Component:  Raster     |     Version:  svn-develbranch6         
Resolution:             |    Keywords:                           
  Platform:  All        |         Cpu:  All                      
------------------------+---------------------------------------------------
Comment (by glynn):

 Replying to [ticket:465 kyngchaos]:

 > For now, the surrounding cells are filled with the "nearest" input cell
 to the interpolated cell, like the original r.proj did.  This works for
 the bilinear interp, but could cause odd interpolation in the cubic
 method, so the cubic null filling needs some work.

 The existing behaviour regarding actual nulls is correct, and will be
 preserved. If you want nulls filled, use e.g. r.fillnulls. Don't go
 stuffing ad-hoc fudges into r.proj.

 The issue with lat/lon wrapping is valid, although personally I think that
 this is a fundamental defect with GRASS. GRASS only supports lat/lon to
 the extent that every single module deals with it by itself.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/465#comment:3>
GRASS GIS <http://grass.osgeo.org>