#3358 closed defect (fixed)
t.rast.what: null_value is insensitive to passed strings
Reported by: | veroandreo | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.4.2 |
Component: | Temporal | Version: | svn-trunk |
Keywords: | t.rast.what | Cc: | |
CPU: | x86-64 | Platform: | Linux |
Description
G7:t.rast.what has currently a parameter null_value
that allows to change the string representing NULL value (default is *). However, no matter which string or number I use, with or without quotes, it only outputs asteriks (*) where there are NULL values. It seems insensitive to any string one passes.
Change History (9)
follow-up: 2 comment:1 by , 8 years ago
comment:2 by , 8 years ago
Replying to veroandreo:
r71175 fixed the reported bug in G7:t.rast.what null_value option in trunk. Thanks Soeren!
I leave the ticket open in case it needs to be backported
I guess that this would require the backport of r71105 (t.rast.what: added new r.what v flag; added test cases)
comment:5 by , 7 years ago
Milestone: | → 7.2.4 |
---|
comment:6 by , 6 years ago
comment:7 by , 6 years ago
Milestone was 7.2 originally, but maybe it does not make sense at this point. The fix is already in 74 and 76 relbranch
comment:8 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
closing... reopen if you consider it should be backported
comment:9 by , 6 years ago
Milestone: | 7.2.4 → 7.4.2 |
---|
r71175 fixed the reported bug in G7:t.rast.what null_value option in trunk. Thanks Soeren!
I leave the ticket open in case it needs to be backported