[GRASS-dev] Re: [GRASS GIS] #1088: r.fillnulls: support other
interpolation methods
GRASS GIS
trac at osgeo.org
Thu Feb 16 03:47:41 EST 2012
#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 mmetz):
Replying to [comment:22 hamish]:
> Replying to [comment:21 mmetz]:
> > r.fillnulls should do just that, filling nulls, and not do
> > resampling.
>
> I am not convinced (not even a little). No exceptions to the standard
map creation conventions unless it is absolutely fundamental to what the
module does. If this was a edit-in-place module like r.null maybe I could
buy the argument, but it isn't. Either deal with all of the input map's
native bounds, or use the current region, not half and half. Using the
current region settings gives the user the choice of which one they want.
In theory I would agree, but not everybody knows that for a 3 arcsec SRTM
g.region -a res=00:00:03 is wrong and only g.region align=SRTM properly
aligns the region to the raster map.
If you want to respect the current region, you would need to remove the
align=input option from g.region in r.fullnulls when you zoom to the
holes. You could zoom to the raster buffer instead which has been created
using the current region.
Markus M
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/1088#comment:25>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list