Select to view content in your preferred language

Viewshed and Line-of-Sight Discrepancy

2017
1
01-30-2014 11:02 AM
kg76
by
Regular Contributor
I have a dataset of ~100 archaeological sites (with x, y, and z values) and am trying to figure out which sites are visible from/to other sites.

To do this, I first used the construct sight lines tool to create lines between all site pairs. Then, I used the line of sight tool and a 10-meter resolution DEM to figure out which sites are visible to others. If I understand the line of sight tool correctly, it is the TarIsVis field in the output feature class that indicates whether a target (site) is visible if there is a 1, and not visible if there is a 0.

For a specific site, let's call it Site A, I'm getting the result that there are no sites that are visible from Site A. I know this isn't true because I've stood atop of Site A and could see to Site C, for example. Now I know that it's possible that the spatial accuracy of my coordinates or the resolution of the DEM could be causing this, so I did a viewshed analysis to compare.

What I found doing the viewshed analysis doesn't make sense to me. I used Site A as the input point and the same 10-meter DEM that was used for the line-of-sight tool as the input raster. According to the output raster, the pixel that corresponds with Site C is WITHIN the viewshed of Site A. So why is there no line-of-sight from Site A to Site C according to the line of sight tool? Are they not synonymous?
Tags (1)
0 Kudos
1 Reply
TanjaHumar
Emerging Contributor
Well, unfortunately I can't provide an answer here as I just had the same problem: I was using the line of sight tool to crosscheck my "Observer Points"-Results and they do slighlty differ! Same Offsets, same elevation model and I haven't used the refractivity coefficient either way. Don't understand the difference!
0 Kudos