Using GIS to Determine Horizon Belts[2]
Using GIS to Determine Horizon Belts[2]
Using GIS to Determine Horizon Belts[2]
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Create the ridge viewpoints file<br />
The ridgeline data was used <strong>to</strong> indicate what portions of the road viewshed<br />
corresponded <strong>to</strong> ridges. A ridge viewpoint file was created that corresponded <strong>to</strong> the back<br />
edge of the viewshed traversing a ridge (Figure 1). The ridgeline was used only as a<br />
horizontal guide for the location of the ridge. The back edge of the viewshed, and the<br />
corresponding “ridge” viewpoints could have extended beyond or fell short of the actual<br />
ridgeline. At least three ridge viewpoints were selected, two from near the ends of the<br />
ridge and one from a highpoint along the ridge. Additional viewpoints were added for<br />
divides, as indicated by ridgelines. They were also added at viewshed junctions where<br />
the back edge of the viewshed changed direction sharply. These viewshed junctions<br />
represent locations viewed by more than one road viewpoint. The ridge viewpoints were<br />
converted <strong>to</strong> a 3D file, with elevations derived from the TIN model. Both target offsets<br />
and observer offsets (OffsetA) of 35 feet were assigned as attributes <strong>to</strong> all viewpoints.<br />
Create an analysis mask<br />
Analysis masks were used <strong>to</strong> constrain the viewshed analysis from the ridge<br />
viewpoints <strong>to</strong> a limited area (Figure 2). This served two practical purposes. Areas<br />
“behind” the ridge viewpoints were not of concern and eliminating them from<br />
consideration speeds up processing time. Analysis masks also were used <strong>to</strong> segment<br />
concave ridges and create separate horizon belts for each ridge segment.