Opened 12 years ago
Closed 8 years ago
#1708 closed defect (fixed)
r.fill.dir leaves unresolved areas
| Reported by: | marchesinivan | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.0.3 |
| Component: | Raster | Version: | svn-trunk |
| Keywords: | r.fill.dir | Cc: | |
| CPU: | x86-64 | Platform: | Linux |
Description
We have run r.fill.dir on a grid layer of 16 milions cells. Using grass70 the procedure stops leaving a lot of unresolved areas. Using grass64 the procedure works regularly.
Change History (6)
follow-up: 2 comment:1 by , 12 years ago
comment:2 by , 12 years ago
Replying to marchesinivan:
Moreover, iterating the command in grass grass70 do not decrease the unresolved areas as instead happen using grass64
This seems to be different bugs in different branches related to the -f flag, "Find unresolved areas only".
For grass64, problem areas are resolved if the flag is not given, whereas for grass7, problem areas are resolved if the flag is given. Fixed for trunk in r52872.
BTW, if you want to prepare a dem for hydrological analysis, r.fill.dir is not really appropriate because it uses a method based on questionable assumptions (sink filling). In this case maybe you could give r.hydrodem from addons a try (impact reduction approach).
Markus M
comment:3 by , 9 years ago
| Keywords: | r.fill.dir added |
|---|---|
| Milestone: | 7.0.0 → 7.0.2 |
comment:6 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
The fix was backported, so I am closing it.
Moreover, iterating the command in grass grass70 do not decrease the unresolved areas as instead happen using grass64