[GRASS-dev] [GRASS GIS] #3080: Add flag to ignore NULL values in r.cross

GRASS GIS trac at osgeo.org
Mon Jun 27 06:43:02 PDT 2016

#3080: Add flag to ignore NULL values in r.cross
  Reporter:  pvanbosgeo   |      Owner:  grass-dev@…
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Milestone:  7.0.5
 Component:  Default      |    Version:  unspecified
Resolution:               |   Keywords:
       CPU:  Unspecified  |   Platform:  Unspecified

Comment (by pvanbosgeo):

 Replying to [comment:1 annakrat]:
 > Is this duplicate of #1674?

 I think the problem in ticket #1674 was a bug, which I think has been
 resolved since?

 This ticket is more an enhancement request. The current behaviour of
 r.cross seems to be that NULL values are treated as a category. If that is
 indeed the correct behaviour, I would suggest to add a flag similar to the
 -z flag, but for NULL instead of 0 (zero) values. So, the description of
 this flag (let's use the -n flag)

 ''With the -n flag NULL values are not crossed. This means that if a NULL
 value occurs in any input data layer, the combination is NULL (no
 category) in the resulting map layer, even if other data layers contain
 non-NULL data.

 I would in fact have expected the above (an output layer is NULL where one
 or more layers have a NULL value) to be the default / more logical

Ticket URL: <https://trac.osgeo.org/grass/ticket/3080#comment:2>
GRASS GIS <https://grass.osgeo.org>

More information about the grass-dev mailing list