Opened 15 years ago
Closed 15 years ago
#711 closed defect (fixed)
r.horizon crashes
Reported by: | eblizza | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 6.4.0 |
Component: | Raster | Version: | 6.4.0 RCs |
Keywords: | r.horizon, wingrass | Cc: | |
CPU: | x86-32 | Platform: | MSWindows XP |
Description
Hello,
r.horizon terminates after going through a series of matching files past kernel32.dll that ends with </DATABASE>.
I realize that you are busy, but could you consider fixing this as a change of pace? I spoke with an ESRI user at MORAP (www.cerc.usgs.gov/morap/) who needs similar output. If r.horizon worked, then they might expand to become GRASS users as well.
Alternatively, would you please tell me how to get horizon angles for a point using ARCMap?
Thank you,
Elizabeth
Attachments (1)
Change History (7)
by , 15 years ago
Attachment: | r.horizon_da8a_appcompat.txt added |
---|
comment:1 by , 15 years ago
CPU: | Unspecified → x86-32 |
---|
Please specify in which projection you used r.horizon and with which parameters. We need to be able to reproduce the problem...
Markus
comment:2 by , 15 years ago
Component: | default → Raster |
---|---|
Keywords: | wingrass added |
Priority: | blocker → normal |
follow-up: 4 comment:3 by , 15 years ago
n.b. like #736, r.horizon uses pj_*() functions. maybe a clue there.
Hamish
follow-up: 5 comment:4 by , 15 years ago
comment:5 by , 15 years ago
Replying to neteler:
Replying to hamish:
n.b. like #736, r.horizon uses pj_*() functions. maybe a clue there.
Since #736 has been fixed, is r.horizon now working on winGRASS? The manual page contains a test example. Can this be closed?
Markus
tested with a self compiled actual Grass64 on WinVista32:
r.horizon elevin=dtm@PERMANENT direction=15 horizonstep=30 bufferzone=200 maxdistance=200 horizon=horangle [...] (Sun Mar 07 21:35:07 2010) Command finished (196 sec) - while r.sunmask is working in the background
Helmut
comment:6 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
As it is working now, I am closing. Feel free to reopen if the problem persists.
Microsoft error log