SOLAR MARKETTRENDSign in / Sign up
← All blogs

Solar Roof Shade Surveys: Why a Horizon Line Does Not Replace Nearby Obstacles

Share on social media

Check whether a solar shade study includes both the distant horizon and nearby roof obstacles before accepting its energy estimate.

A roof can look open in a photograph while still needing a careful shade study. Before a Pakistani homeowner or factory buyer accepts a solar production estimate, there is a more useful question than “Was shading included?” Ask which obstacles were included, how they were measured, and whether their positions match the proposed panel layout.

A horizon curve and a detailed roof model answer different questions. Buying more powerful panels is not a substitute for documenting either one.

Separate distant and nearby obstructions

PVsyst distinguishes distant shading, represented by a horizon line affecting the array as a whole, from nearby objects that cast shadows across parts of it. Nearby shading needs a three-dimensional description of the system and surroundings. Its documentation also separates lost incoming light from additional electrical mismatch losses. These distinctions explain why a single percentage labelled “shade” needs supporting detail. PVsyst shading documentation

Our recommendation is to ask the designer for an obstacle register with a sketch: water tanks, parapets, stair enclosures, adjoining structures and other relevant obstructions. Mark which are included, which are excluded and why. This is a review checklist, not a claim that every roof contains all these objects.

Check where the horizon information came from

PVsyst accepts horizon measurements as direction and elevation-angle points, including on-site measurements and imported profiles. Its import guidance requires attention to directional conventions and site coordinates. An imported profile therefore needs a named source and an identifiable location; the software accepting the file does not by itself prove that the input describes the intended property. PVsyst horizon import guidance

Ask for the survey date, coordinates, observation position and the profile used in the calculation. Retain the actual file with the proposal rather than just a screenshot. If the designer uses a different reference direction, have them label it clearly so another reviewer can reproduce the study.

Make the layout review practical

For procurement, we suggest requesting two outputs together: the final panel layout and the matching shade scene. Label the panels or roof zones consistently. Ask the designer to identify any planned obstacle removal or relocation on which the estimate depends. Do not count a proposed alteration as completed work.

A useful comparison changes one design choice at a time. For example, ask the supplier to compare the proposed layout with a revised layout that avoids a troublesome roof zone, while keeping weather data and equipment assumptions unchanged. The resulting difference is a design comparison, not a guaranteed saving.

Preserve a record for handover

Keep the agreed model, exclusions and layout revision with the commissioning documents. If roof equipment or neighbouring structures later change, ask for the affected assumptions to be reviewed before blaming the modules. The aim is not the prettiest simulation image. It is a traceable explanation of what the system was expected to see, and which real-world changes could invalidate that expectation.

Sources

  1. PVsyst Shadings
  2. PVsyst Importing Horizon profiles