Opened 8 years ago
Last modified 6 years ago
#3080 new enhancement
Add flag to ignore NULL values in r.cross
Reported by: | pvanbosgeo | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.6.2 |
Component: | Default | Version: | unspecified |
Keywords: | Cc: | ||
CPU: | Unspecified | Platform: | Unspecified |
Description
Feature request: an option in r.cross to ignore raster cells where one or more input maps have NULL (no-data) value.
Change History (9)
follow-up: 2 comment:1 by , 8 years ago
comment:2 by , 8 years ago
Replying to 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 behaviour.
comment:3 by , 8 years ago
Milestone: | 7.0.5 → 7.3.0 |
---|
comment:6 by , 6 years ago
Milestone: | 7.4.1 → 7.4.2 |
---|
comment:7 by , 6 years ago
Milestone: | 7.4.2 → 7.6.0 |
---|
All enhancement tickets should be assigned to 7.6 milestone.
Is this duplicate of #1674?