I generated a "total viewshed" of a DEM using a series of random observer points. The resulting viewshed attribute table lists the values as the number of observer observer points visible from a count of pixels with that value. So, if you click on a cell, it will show you how many observer points can see the pixel. However, the attribute table, of course, summarizes this, so every row with a value of, say, 6 is listed with the number of pixels with that value (see 400).
This is fine, but I see a weird issue I can't figure out how to fix, especially when I use a lot of observer points. I see that there are multiple rows with the same count but different numbers of observer points in the value column. In other words, rather than one row in which 500 pixels can be seen from 1 observer location, it will have a series of rows in which, say, 500 pixels can be seen by 1, 501 can be seen by 1, 503 seen by 1, and so on. I assume this is happening because given the large number of points distributed across the landscape these are separate individual cells that can be seen by separate groups of observer points. So the 500 pixels that can be seen by 1 are different pixels than the 501 that can be seen by 1.
My confusion is trying to understand the organization of the data to use in other applications. For example, for larger count values I can easily say something like "20,000 pixels are viewable by x number of sites" since there is only one row. But if I want to say the same thing for 1 site, I have several options. I find this is a challenge also in talking about any cumulative frequencies
