How to Read a Viewshed Map | Certified Energy

A viewshed map shows areas that a model identifies as potentially visible from a nominated observation point, or areas from which a proposed feature may be visible. Reading the map correctly requires more than recognising the coloured areas.

Its meaning depends on the modelled viewpoint or target, the terrain and surface data, the height settings and the assumptions used to calculate visibility. Without that context, a coloured visibility zone can be mistaken for a prediction of what people will actually see on site.

For architects, planners, developers and project teams, careful interpretation helps turn a technical map into useful evidence for design discussions and planning documentation.

A viewshed map identifies modelled potential visibility under stated conditions. It does not, by itself, establish the visual prominence, sensitivity or significance of a development.

Start by checking what the map is modelling: visibility from a viewpoint, visibility of a target, or a combined result from several observation locations.

Read the legend, scale and mapped extent, then confirm what the visible and non-visible classes mean. A coloured area may represent potential intervisibility rather than a verified unobstructed view.

Check the height settings, terrain or surface model, treatment of vegetation and buildings, and any distance or curvature assumptions documented with the output.

Finally, interpret the map alongside site information and, where needed, field verification or separate visual impact assessment. A map is evidence of a modelled condition, not a complete planning conclusion.

Interpretation boundary: A viewshed map can indicate theoretical visibility, but it does not independently assess visual impact, viewer sensitivity, landscape character or the acceptability of a proposal. Those questions may require separate assessment.

Before reading the colours, identify the question the model was designed to answer. A map may test what is visible from one nominated location, which surrounding locations may see a proposed structure, or how visibility changes across several viewpoints.

The distinction matters. A viewpoint-based analysis and a target-based analysis can look similar but answer different questions. The map title, legend or accompanying report should identify the observation and target arrangement.

Confirm whether the result represents an existing condition, a proposed design or a comparison between scenarios. If the purpose is unclear, the map cannot be interpreted confidently.

Visibility maps often use contrasting colours to distinguish cells classified as visible from cells classified as not visible under the selected model assumptions. Some maps show counts, such as the number of viewpoints from which a location is visible.

Colours are not standardised across every GIS workflow. Green does not always mean low impact, and red does not necessarily mean an unacceptable outcome. The legend determines what each class means.

Check whether blank or transparent areas indicate non-visibility, excluded analysis areas, missing data or simply the background map. These are different conditions and should not be treated as interchangeable.

Where graduated classes are used, identify the units or calculation behind them before drawing conclusions.

A viewshed result is tied to the positions used in the model. A viewpoint may represent a road, public lookout, dwelling, site boundary or other selected location, depending on the project.

Check the point markers and labels against the site plan. A map generated from a single observation point should not be read as though it represents every person moving through the surrounding landscape.

If the model uses multiple points or a line of viewpoints, determine whether the map combines their results and how the legend expresses that combination.

For more detail on the method distinction, see the Viewshed Analysis Knowledge Pillar.

A modelled visible cell generally indicates that the calculated line of sight is not blocked by the elevation information and obstructions represented in that model. It is a conditional result, not proof that a feature will be noticeable.

A modelled non-visible cell indicates that the model identifies an obstruction or terrain relationship preventing the tested line of sight under its assumptions. It does not necessarily establish that every part of a large structure would be hidden.

Partial visibility, the amount of a structure exposed, atmospheric conditions and the apparent scale of a feature may not be represented by a simple binary map.

The distinction between potential visibility and visual effect is particularly important when a map supports planning discussions.

Locate the project site and check the geographic extent of the analysis. The study boundary may reflect a nominated distance, an assessment area or a project-specific scope.

Map scale affects how precisely individual visibility boundaries can be read. A small-scale regional map is useful for broad patterns, but it should not be used to infer exact visibility at a single window or property boundary.

Also check the coordinate reference system, north arrow and base mapping where supplied. These help relate the output to the site and other project drawings.

A map should not be treated as more spatially precise than the underlying elevation data and model resolution allow.

Terrain elevation is central to the calculation. Some analyses use a digital terrain model representing ground elevation, while others use a digital surface model that may include buildings, vegetation or other elevated features.

If the map is based on bare-earth terrain, trees and buildings may not block modelled sightlines unless they are incorporated separately. A surface-based model may represent some of those obstructions, subject to data quality and currency.

The legend alone will rarely tell you which model was used. Look for the methodology, source date, cell resolution and any noted limitations.

The distinction between terrain and surface datasets is developed separately in our technical Viewshed Analysis content; this article focuses on interpreting the map supplied.

Visibility can change when the height of an observer or target changes. A map tested from an assumed eye level is not equivalent to one tested from a roof, elevated platform or other height.

Likewise, the visibility of a proposed building may depend on whether the target represents ground level, the roofline, a nominated structure height or multiple points on the proposal.

Check whether heights are expressed above ground level or as absolute elevations, and whether the methodology applies them consistently.

If height assumptions are absent from the map or accompanying report, request clarification before comparing its result with another design option.

A typical viewshed map does not describe the quality of a view, the cultural or scenic value of a landscape, or how strongly a visible proposal may attract attention.

It also may not capture temporary screening, seasonal foliage, atmospheric haze, fine-scale local obstructions or the detailed appearance of a development, depending on the model and available data.

A visible area should therefore not be labelled a significant impact area without separate supporting analysis. Equally, a non-visible result should be read in light of model limitations and the relevant project scale.

Where visual effects are the planning question, see Visual Impact Assessment for the distinct assessment context.

Viewshed maps can be used to compare design options, but a meaningful comparison requires consistent methods. Different terrain datasets, observer heights, target definitions or analysis extents can produce differences unrelated to the design itself.

When reviewing two maps, confirm that their legends and visibility classifications are equivalent. A change in colour palette is not a change in visibility.

If the purpose is to compare proposed heights or locations, identify which input changed and which assumptions remained fixed.

A short methodology note accompanying each map can make the comparison much more defensible.

Once the map has been interpreted, record the main visibility pattern and the assumptions that materially influence it. The useful conclusion is often where further review may be warranted, not a blanket statement about impact.

For example, the map may identify potentially visible locations that justify more detailed viewpoint selection, site inspection or visual documentation. Those next steps depend on the project and planning context.

Where a project requires a professional visibility study, the Viewshed Analysis service can help establish an appropriate assessment scope and reporting approach.

The final interpretation should be proportionate to the data quality, project stage and decisions the map is intended to inform.

A map without its methodology may still show a useful spatial pattern, but it is difficult to judge how much confidence to place in the result.

Ask for the purpose of the analysis, observation and target locations, input heights, elevation dataset, resolution and treatment of obstructions.

Where a map has been supplied as part of a planning package, check whether the report explains how visibility classes were calculated and what limitations apply.

Do not assume that an unlabelled white area means a feature is invisible. It may fall outside the study boundary or lack usable input data.

If the information cannot be established, describe the uncertainty explicitly rather than presenting the map as conclusive evidence.

Consider a proposed building on an elevated site. A project team receives a viewshed map showing coloured areas across nearby roads and residential land.

The team first confirms that the map tests potential visibility of a nominated point at the proposed building height, rather than views from the building itself.

The legend identifies modelled visible and non-visible cells. The methodology states that the calculation uses a bare-earth terrain model and does not explicitly include existing tree cover or buildings as screening.

The team therefore understands that some coloured areas may be screened in practice, while the result remains useful for identifying locations that could warrant closer review.

Before comparing a lower building option, the team checks that the same terrain data, viewpoint assumptions and study boundary are used for both models.

This is an illustrative scenario, not a project finding. It demonstrates why map interpretation depends on the modelling inputs as much as the displayed colours.

What do the colours on a viewshed map mean?

The legend defines the colours. In a simple map they may distinguish modelled visible and non-visible areas; in other outputs they may show the number of observation points with potential visibility. Colour alone does not indicate visual impact.

Does a visible area mean a development will be clearly seen?

No. It means the model indicates potential line of sight under its stated assumptions. The degree of visibility, apparent scale, screening and visual effect require further context.

Why might a viewshed map show an area as visible when trees block the view?

The model may use bare-earth terrain data or may not include the relevant vegetation. Check the input dataset and whether trees or buildings were represented.

Can a viewshed map show whether a proposed building will affect views?

It can help identify locations with potential visibility of a modelled part of the building. It does not independently assess the significance of any change to views or amenity.

Can two viewshed maps be compared directly?

Only where their methods and inputs are sufficiently consistent. Differences in elevation data, target heights, observation points or map classes may make a direct comparison misleading.

What should I ask for if I receive a viewshed map without a report?

Request the map purpose, legend, observation and target locations, modelled heights, terrain or surface data, analysis extent and key limitations. These details are needed for reliable interpretation.