Opened 5 years ago
Closed 5 years ago
#3926 closed enhancement (fixed)
allow limit viewshed computation by angle
Reported by: | annakrat | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 8.0.0 |
Component: | Raster | Version: | unspecified |
Keywords: | r.viewshed, viewshed | Cc: | |
CPU: | All | Platform: | All |
Description
r.viewshed should allow to restrict the computation to range of angles, e.g. to simulate human field of view.
Change History (4)
follow-up: 2 comment:1 by , 5 years ago
comment:2 by , 5 years ago
Replying to annakrat:
For the record, this is my attempt with hardcoded values, which fails with angle 1 to 270 (the viewshed is written but incorrect). Interestingly, it works with angle 0 to 270.
Your PR #180 works for me. I tested in the NC dataset with
g.region -p rast=elev_state_500m r.viewshed in=elev_state_500m out=viewshed coord=637942.9512846764,188095.68718268772 obs=100 direction_range=0,270 r.viewshed in=elev_state_500m out=viewshed coord=637942.9512846764,188095.68718268772 obs=100 direction_range=1,270 r.viewshed in=elev_state_500m out=viewshed coord=637942.9512846764,188095.68718268772 obs=100 direction_range=270,0 r.viewshed in=elev_state_500m out=viewshed coord=637942.9512846764,188095.68718268772 obs=100 direction_range=270,1
and the results seem to be correct.
Can you provide an example where your PR does not work?
comment:4 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
For the record, this is my attempt with hardcoded values, which fails with angle 1 to 270 (the viewshed is written but incorrect). Interestingly, it works with angle 0 to 270.