[GRASS-dev] r.resamp.stats: nulls along western boundary

Glynn Clements glynn at gclements.plus.com
Mon Oct 13 16:34:19 EDT 2008


Hamish wrote:

> > > While running through this set of commands to resample from 30" to 2':
> > >   http://grass.osgeo.org/wiki/Blue_Marble#Processing
> > > 
> > > I notice that the output of r.resamp.stats has its western-most raster
> > > column set to all NULL. The other 3 borders seem to be ok. As the 30"
> > > data is without NULLs, and the target region is an exact multiple of
> > > the source region, it doesn't seem to be an inherent
> > > exceeding-the-border effect. The propagate nulls flag was not used.
> 
> Glynn:
> > Can you come up with a recipe to reproduce this with the
> > standard example data sets?
> 
> sure:
> 
> # lat/lon location
> g.region n=90N s=90S w=180W e=180E res=0:15
> r.mapcalc fifteen=15
> g.region res=1
> r.resamp.stats in=fifteen out=fifteen.one

Okay, I can reproduce this.

Unfortunately, this looks like it's going to be a pig to fix.

BTW, I consider this a bug:

	> print G_col_to_easting(0, &dst_w)
	$20 = -180
	> print G_easting_to_col(-180, &src_w)
	$21 = 1440
	> print src_w.cols
	$22 = 1440

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


More information about the grass-dev mailing list