Opened 9 years ago
Closed 8 years ago
#2664 closed defect (fixed)
The r.watershed module documentation has the wrong value for cells that do not get included in a complete watershed.
| Reported by: | swendel621 | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.0.5 |
| Component: | Docs | Version: | 7.0.0 |
| Keywords: | r.watershed, basin, doc | Cc: | |
| CPU: | All | Platform: | All |
Description
In the current online r.watershed module's help documentation, there is a conflicting statement to the output generated for the basin parameter.
http://grass.osgeo.org/grass71/manuals/r.watershed.html
In the text it says, "0 values indicate that the cell is not part of a complete watershed basin in the current geographic region."
If I run r.watershed on the Elevation sample data and set the threshold to 10000, the output basin will have areas on the edges that do not generate a basin. The values of these areas are null instead of 0 like the documentation makes it sounds like it should get. It makes sense for the values to be null instead of 0 so the documentation needs to be updated.
Change History (9)
comment:1 by , 9 years ago
| Milestone: | 7.0.1 → 7.0.2 |
|---|
comment:5 by , 8 years ago
Replying to swendel621:
In the current online r.watershed module's help documentation, there is a conflicting statement to the output generated for the basin parameter.
http://grass.osgeo.org/grass71/manuals/r.watershed.html
In the text it says, "0 values indicate that the cell is not part of a complete watershed basin in the current geographic region."
If I run r.watershed on the Elevation sample data and set the threshold to 10000, the output basin will have areas on the edges that do not generate a basin. The values of these areas are null instead of 0 like the documentation makes it sounds like it should get. It makes sense for the values to be null instead of 0 so the documentation needs to be updated.
Manual updated in trunk r67920.
comment:6 by , 8 years ago
| Milestone: | 7.0.4 → 7.0.5 |
|---|
Ticket retargeted after 7.0.1 milestone closed