[GRASS-dev] Re: [GRASS GIS] #1088: r.fillnulls: support other interpolation methods

[GRASS GIS]

#1088: r.fillnulls: support other interpolation methods
-------------------------+--------------------------------------------------
 Reporter:  kyngchaos    |       Owner:  grass-dev@…              
     Type:  enhancement  |      Status:  new                      
 Priority:  normal       |   Milestone:  6.4.3                    
Component:  Raster       |     Version:  svn-develbranch6         
 Keywords:  r.fillnulls  |    Platform:  All                      
      Cpu:  All          |  
-------------------------+--------------------------------------------------

Comment(by hamish):

 none of this gets away from the fact that r.buffer.py is consistently ~
 40x slower than r.buffer2 at all(?) region sizes. For my 8GB workstation
 the extra RAM needed by the classic r.buffer.c would mean I'd have to
 transition to the less ram-hungry r.grow.distance method at a region size
 of 90000x90000 (mem. req. here is 1 byte per region cell), which is, so
 far, still a corner case.  r.buffer.py is an interesting exercise, but I'm
 not convinced that the r.grow.distance method needs to be anything more
 than a full example in the r.buffer help page, wrt alternate steps to take
 if it wants to use more RAM than you've got.


 regards,
 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1088#comment:27>
GRASS GIS <http://grass.osgeo.org>