[GRASS-dev] [GRASS GIS] #369: r.mapcalc not correctly determining null space around r.external data set

GRASS GIS trac at osgeo.org
Tue Nov 18 13:44:55 EST 2008


#369: r.mapcalc not correctly determining null space around r.external data set
---------------------+------------------------------------------------------
 Reporter:  dickeya  |       Owner:  grass-dev at lists.osgeo.org
     Type:  defect   |      Status:  new                      
 Priority:  major    |   Milestone:  6.4.0                    
Component:  Raster   |     Version:  svn-develbranch6         
 Keywords:           |    Platform:  Linux                    
      Cpu:  x86-64   |  
---------------------+------------------------------------------------------
 Here's what I'm seeing:

 I have a geotiff file that I link to using r.external (output=test_ras). I
 set the region to have 1px of null space around the input raster, and then
 run:
 {{{
 r.mapcalc "out_ras = if(isnull(test_ras),0,null())"
 }}}

 I expect out_rast to have all nulls set to 0, including the 1px buffer.
 The north and south borders are correctly detected as null and set to 0,
 but the east and west borders are still null in the output.

 If I import the same geotiff using r.in.gdal and run the same routine,
 everything works as expected and I have a ring of 0s around my new data
 set.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/369>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list