[GRASS-dev] [GRASS GIS] #2032: r.mapcalc does not always respect MASK

GRASS GIS trac at osgeo.org
Tue Jul 16 11:26:55 PDT 2013


#2032: r.mapcalc does not always respect MASK
-------------------------+--------------------------------------------------
  Reporter:  pvanbosgeo  |       Owner:  grass-dev@…              
      Type:  defect      |      Status:  closed                   
  Priority:  normal      |   Milestone:  7.0.0                    
 Component:  Raster      |     Version:  unspecified              
Resolution:  invalid     |    Keywords:  r.mapcalc                
  Platform:  Linux       |         Cpu:  Unspecified              
-------------------------+--------------------------------------------------

Comment(by glynn):

 Replying to [comment:2 pvanbosgeo]:
 > OK, thanks, I didn't know that / hadn't read that part of the manual
 carefully enough. Perhaps not something that the user will encounter
 often, but nonetheless, it is something I can see others might overlook as
 well when using r.mapcalc. Perhaps a short note of this can be added to
 the r.mapcalc help file (which is where I looked to see where my
 expectations of the behavior of r.mapcalc were wrong)?

 The behaviour isn't specific to r.mapcalc. Except for a few special cases,
 the MASK behaviour isn't implemented by the individual modules, but by the
 raster I/O library. You can observe the same behaviour with e.g.
 r.neighbors.

 The correct place to document this behaviour is wherever the MASK
 behaviour is described, e.g. the rasterintro manual page and the r.mask
 manual page. FWIW, the first sentence of the DESCRIPTION section of the
 r.mask manual page (after the summary) is:
 {{{
 The MASK is only applied when reading an existing GRASS raster map,
 for example when used in a module as an input map.
 }}}

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



More information about the grass-dev mailing list