Opened 5 years ago
Last modified 5 years ago
#3888 new defect
r.buffer dropping zone
Reported by: | dnewcomb | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 7.6.2 |
Component: | Raster | Version: | svn-releasebranch76 |
Keywords: | r.buffer | Cc: | |
CPU: | Unspecified | Platform: | MSWindows |
Description
I have a raster with 5 ft resolution cells. When I specify distances= 5,10,15,20 and units=feet, the first zone is value 1, distances calculated from these locations. The second zone is value 3 5-10 feet The third zone is value 4 10-15 feet the fourth zone is value 5 15-20 feet
Should there not be a value 2, 0-5 feet?
This is version 7.6.1 on Windows 10 64 bit
Change History (2)
comment:1 by , 5 years ago
comment:2 by , 5 years ago
Replying to dnewcomb:
I have a raster with 5 ft resolution cells. When I specify distances= 5,10,15,20 and units=feet, the first zone is value 1, distances calculated from these locations. The second zone is value 3 5-10 feet The third zone is value 4 10-15 feet the fourth zone is value 5 15-20 feet
Should there not be a value 2, 0-5 feet?
In theory yes, but with a resolution of 5 feet, there are no NULL cells closer than 5 feet to non-NULL cells, thus there are no cells with value 2, 0-5 feet.
I wonder if it's just some kind of rounding issue (feet - meters conversion). If you increase the distances slightly, does it help (e.g. 5.001)?