7 Reasons Satellite Images Miss Parts of Solar Shading

An overhead image can make a roof feel fully observed. You see the planes, a chimney, a tree canopy, and perhaps a neighboring building. Then the design screen adds panels, and the site begins to look settled.

Shade refuses to stay inside that picture. It moves through the day and year, stretches with height, disappears behind parapets, changes with vegetation, and affects electrical configurations differently. A satellite image is valuable evidence, but it is one observation within a much larger model.

This guide is for solar designers, site assessors, sales engineers, and reviewers deciding how far remote evidence can carry an early layout. It does not prescribe a universal survey method. Project stage, jurisdiction, roof form, available data, and consequence should determine the verification plan.

Results depend on source data, assumptions, equipment models, configuration, and review. Outputs support design and documentation workflows but do not replace approval by the responsible engineer, authority, lender, insurer, or utility.

Treat imagery as a source with a date and purpose

Do not paste an image into the project and let it become timeless. Record the provider, capture or currency information available, resolution or quality notes, viewing limitations, and the decision it supports. If the capture date is unknown, record that absence instead of guessing from roof color or vegetation.

Google’s Solar API overview describes building and solar data products derived from imagery and elevation information. Its data-layer documentation distinguishes imagery, digital surface models, flux data, and building masks. That distinction is useful even if a team uses another provider: the photograph, elevation representation, and modeled solar data are different records with different limits.

Use satellite or aerial imagery to support the question it can answer. “Is there enough visible roof area to justify a closer look?” may be reasonable. “What exact annual shade loss will this installed system experience?” requires more evidence and modeling.

What can satellite imagery establish in a solar shading review?

Satellite imagery can establish a dated overhead observation of visible roof shape, surrounding context, large objects, and capture-time shadows within its resolution and viewing limits. It can support screening and obstruction questions. It cannot by itself verify current conditions, hidden features, heights, roof function, access, annual shade, electrical response, production loss, or suitability for engineering, procurement, construction, or financial commitments.

Treat each image as a record, not a background. The source should remain connected to the roof model, obstruction markers, and every customer graphic derived from it. When the provider offers several data layers, record which layer the project actually used. A photographic image, surface model, building mask, and modeled flux layer carry different information and should not be blended into one “satellite verified” status.

Use this copy-ready imagery evidence card:

1. Project, site, building, roof zone, and current design revision:
2. Imagery or data provider and exact layer used:
3. Capture, currency, retrieval, and processing dates available:
4. Native detail, viewing angle, orientation, crop, and quality limitations:
5. Visible roof edges, planes, large objects, surrounding context, and capture-time shadows:
6. Areas hidden by canopy, parapet, equipment, shadow, cropping, glare, or image artifacts:
7. Geometry or object fields inferred from the image and confidence assigned:
8. Other views, surface data, plans, photographs, customer statements, or measurements compared:
9. Conflicts among sources and the reviewer authorized to resolve them:
10. Permitted use, such as screen, concept, evidence request, or preliminary model:
11. Prohibited reliance and decision-changing field evidence still required:
12. Owner, expiry event, downstream outputs, and review trigger:

Separate visible evidence from inferred geometry. A crisp outline may support object location while leaving height unknown. A shadow may support that an object interrupted light at the capture moment while leaving the object’s exact geometry and annual effect unresolved. A building mask can help isolate a roof and still omit small penetrations or access constraints.

Use status words that name the task. “Suitable for early roof-screening question” is clearer than “good imagery.” “Roof edge unresolved for detailed layout release” is clearer than “low confidence.” The first form tells the next person what they may do and which evidence they need before doing more.

Bind every derived image to the source revision. If a proposal uses a roof rendering produced from a particular overhead image, the caption should identify the preliminary basis and observation limits. Replacing the source without updating the rendering, shade model, or proposal breaks the evidence chain even when the new image looks similar.

Do not upgrade a source because the model adds depth and texture. Three-dimensional rendering can make inferred heights feel measured. The evidence card should remain visible to reviewers so display quality never outranks provenance.

1. The image may predate the condition you are selling

Roofs change. Trees are pruned or grow, HVAC equipment moves, skylights appear, neighboring construction rises, and a re-roof can alter edges or penetrations. An undated image invites the team to treat a past condition as the present site.

Look for currency clues, but do not convert clues into a capture date. Compare the image with customer photographs, survey records, permit drawings where appropriate, recent street-level evidence, and the customer’s description of work. Ask directly whether the roof or surrounding site has changed.

Create a change question in intake:

If current evidence is unavailable, keep the output preliminary and name the verification trigger. “Remote concept based on imagery of unconfirmed date” is more useful than a broad note that site conditions may vary.

2. An overhead view compresses height

Shade length and direction depend on the three-dimensional relationship among the sun, receiving surface, and obstruction. A tree crown, parapet, vent, chimney, or adjacent wall may be visible from above while its height remains unknown. Other objects disappear behind taller features or blend into similar roof textures.

Some datasets include elevation information, but the reviewer should know which layer the workflow actually used, its limitations, and whether small roof objects are represented. Do not infer a measured height merely because the rendered model looks three-dimensional.

Check heights against field measurements, suitable survey products, drawings, known building data, or other defensible evidence. Where exact height is not necessary for screening, use a visibly labeled scenario and test whether the conclusion changes across a reasonable project-specific range. Do not publish the range as fact unless its inputs and calculation are validated.

The important distinction is simple: object location and object height are different claims. A sharp image can support the first and remain weak on the second.

3. One view cannot show every roof feature

Image angle, shadows at capture time, roof color, resolution, compression, canopy cover, and occlusion can hide small or low-contrast features. Pipes, vents, drains, wires, antennas, roof hatches, small mechanical units, and temporary objects may not read clearly from an overhead view. Parapet and setback relationships can also be hard to interpret without oblique or field evidence.

Run an obstruction sweep before placing modules:

1. Trace every roof plane and height transition.
2. Mark every visible object without deciding whether it matters yet.
3. Compare other views, photographs, drawings, and notes.
4. Create an unknown-object list with location and affected decision.
5. Route each unknown to evidence, field verification, or an explicit design exclusion.

The missed-obstruction checklist expands that sequence. The key is to inspect the source before admiring the final layout. Once modules fill the plane, reviewers tend to see the design they expect rather than the object the model omitted.

4. The sun moves while the image stays still

A shadow visible in imagery records one solar position and viewing moment. It does not show when the same object shades the array in another season, how rapidly the shadow crosses modules, or which hours carry the most solar resource.

Solar position changes with location, date, and time. The receiving plane’s orientation and slope also change how a shadow intersects the proposed array. A winter shadow may reach much farther than a summer one, while the energy consequence depends on the resource available during the affected periods.

Build a time-aware model using suitable geometry and resource data, then inspect representative dates and hours. The seasonal sun-path discussion explains how to communicate those changes without turning one animation into a production guarantee.

Avoid screenshots labeled “shade-free” unless the label defines the tested time basis and evidence. No visible shadow at noon on one date does not establish annual absence of shade.

5. Vegetation is a living assumption

Trees have height, canopy density, seasonal behavior, growth, pruning history, health, ownership, and management constraints. A satellite image can show a crown at one time. It cannot establish a future maintenance agreement or guarantee that the tree will keep the modeled form.

Separate three scenarios:

• Present observed vegetation
• Approved work supported by a responsible-party commitment
• Speculative trimming or removal discussed only as an option

Only the first two may support a project scenario, and the second needs documented scope, timing, ownership, and permissions appropriate to the site. Never improve the shade result by deleting a tree from the model because someone said it “could probably” be trimmed.

Record canopy assumptions in the same place as the shade output. If future growth is material, define a review or maintenance trigger without inventing a universal growth rate. Site species and conditions differ, and property rights can matter as much as biology.

6. Horizon and neighboring objects may sit outside the crop

Design screens naturally zoom to the roof. That crop can omit a distant tree line, adjacent tower, upper building level, terrain, pole, or neighboring structure that matters at a low solar angle. A clean roof image can therefore produce a cramped mental model of the site’s solar horizon.

Expand the review area before finalizing shade objects. Inspect multiple scales and directions. For complex sites, use field horizon measurements, suitable elevation data, or survey methods proportionate to the decision. Document which surrounding features were modeled, excluded, or could not be resolved.

The Department of Energy’s public photovoltaic design overview notes the importance of solar resource and site conditions in system design. It is educational context, not a substitute for a local obstruction survey.

When a nearby object is outside the property, also separate physical modeling from commercial control. The team can model an existing tree without implying that the customer can remove or maintain it.

7. Physical shade and electrical response are different layers

A shadow map describes where modeled direct light is obstructed. Energy effect also depends on when the event occurs, the irradiance components and resource, module behavior, bypass paths, array configuration, power electronics, and the performance model. Two layouts with similar shaded area can therefore produce different modeled outcomes.

Sandia’s PV Performance Modeling Collaborative places shading, soiling, and reflection losses within a larger modeling chain. Reviewers should preserve that chain. Do not convert a colored roof overlay directly into an annual loss statement without the intermediate assumptions and calculation.

Inspect module placement and electrical grouping together. Confirm that the equipment model and configuration match the current design revision. If a shade mitigation feature is claimed, support it with current manufacturer documentation and a model appropriate to the actual configuration. Avoid generic promises that electronics “eliminate” shade losses.

The shading analysis design workflow provides a broader handoff method. The satellite-image boundary is only the first control.

Build an evidence ladder for shading decisions

Not every project needs the same evidence, and no single method answers every question. Use an evidence ladder tied to the release stage.

Progress upward when the lower level cannot resolve a decision-changing uncertainty. Do not demand a full field exercise for a harmless exploratory question, and do not let an attractive remote model carry a construction or financial claim beyond its evidence.

Review the model before the energy number

When a proposed annual-energy value looks plausible, reviewers may stop asking how shade entered the model. Reverse that order.

First check project location, imagery and surface-data basis, roof geometry, receiving planes, modeled obstructions, vegetation treatment, horizon coverage, array placement, and electrical configuration. Then inspect resource data, diffuse and reflected components where relevant, shade calculation method, other losses, and the current equipment set. Only after those checks should the team interpret annual or monthly energy.

The open System Advisor Model libraries contain performance calculation modules, while the System Advisor Model application repository supports inspection of a more detailed modeling environment. These resources do not establish a universal “correct” result for another platform. They show why reviewers need to identify the model and inputs before comparing outputs.

If two tools differ, do not choose the preferred result. Normalize inputs where possible, document method differences, and decide which model is fit for the project purpose.

Communicate shade without turning uncertainty into fear

Customers do not need a lecture on every solar-position calculation. They need to know what was observed, what was modeled, what remains unverified, and how the uncertainty affects the choice.

Use a shade communication card:

Avoid the phrases “no shade” and “fully optimized” unless the evidence and defined scope support them. A more accurate statement often gives the buyer more control: “The preliminary model avoids the major objects visible in the current remote evidence; field verification remains required for roof features and surrounding heights.”

Reopen every dependent output when shade evidence changes

A new tree height or obstruction does not belong only in the shade tab. It may change module placement, system capacity, stringing, energy, materials, price, savings, and customer images. Record which outputs depend on the changed evidence and rerun or reconcile them.

Use a change sequence:

1. Add the new evidence with source and date.
2. Identify the model object or assumption it replaces.
3. Update geometry and array placement where affected.
4. Review electrical configuration.
5. Rerun energy and downstream financial scenarios.
6. Reconcile bill of materials and proposal outputs.
7. Expire the prior review and issue a controlled revision.

This sequence prevents a familiar failure: the roof image is corrected, but the annual-energy chart and proposal headline remain tied to the old layout.

How should teams reconcile satellite imagery with new site evidence?

When site evidence supersedes satellite imagery, preserve both records, identify the changed roof, object, height, access, or vegetation field, and map every dependent geometry, layout, shade, electrical, energy, material, price, savings, proposal, and field output. Route the evidence decision to the authorized reviewer, rerun affected models, issue a controlled revision, explain material changes, and withdraw artifacts tied to the source.

Supersession does not mean the older image was useless. It means a newer or more suitable record now controls a particular decision. Preserve the image, its permitted use, and the outputs produced from it so the team can explain why a preliminary scenario changed. Do not overwrite the only evidence of what the customer previously saw.

Use a source-reconciliation workflow:

1. Freeze the current project, model run, proposal, and customer-facing shade artifacts.
2. Add the new survey, photograph, drawing, measurement, or responsible-party record with source and date.
3. Compare it with the image layer and list each field that agrees, changes, conflicts, or remains unresolved.
4. Assign the controlling evidence decision to the reviewer authorized for that release.
5. Update the roof, object, height, vegetation, access, horizon, or status field without erasing provenance.
6. Map every dependent layout, shade model, electrical configuration, energy result, materials record, price, financial scenario, proposal image, and field instruction.
7. Rerun affected models and calculations through their approved methods, keeping unchanged inputs visible.
8. Obtain the required technical, commercial, customer, utility, authority, safety, or other review.
9. Issue a new controlled revision with the changed source, outputs, limitations, and next event stated.
10. Mark the prior artifacts superseded and confirm distribution withdrawal or receipt where required.

Do not attribute every output change to imagery. A site survey may arrive alongside new equipment, customer load data, tariff information, scope, or other inputs. The comparison record should list which fields remained fixed and which changed. Otherwise a different annual-energy result can be blamed on roof geometry when the model basis moved in several places.

Separate physical and financial dependencies. A changed obstruction can affect shade and energy. Financial impact still depends on current consumption, tariff, export, ownership, financing, and other inputs. Route the energy revision into the financial model rather than turning the physical observation directly into a currency claim.

Explain the revision plainly. “Current field evidence identified a roof feature not visible in the remote source; the array and dependent modeled outputs were revised” gives the buyer a cause. Add the controlling revision, which decisions changed, and what remains open. Avoid saying the new output is universally accurate or final when later reviews still apply.

Check derivative images. A corrected roof model may coexist with an old sales screenshot, presentation, email, portal thumbnail, work order, or partner copy. Register those uses when they are created. Source control is incomplete until the team can find and withdraw the customer-facing artifacts that preserve an older condition.

Set remote-review stop conditions

Remote work becomes safer when reviewers know when to stop. Define stop conditions before a deadline makes every uncertainty look minor.

Examples include unresolved roof edges that affect usable area, hidden or ambiguous objects within the proposed array, unknown parapet or tree heights with material shade implications, evidence of recent site change, disagreement among imagery and drawings, complex horizon conditions, or a release that others may build or contract against without suitable field verification.

A stop condition does not necessarily reject the project. It changes the next output. The team may request photographs, schedule a site visit, build a bounded scenario, reduce the preliminary array, or route a specialist question.

The DOE homeowner solar guide describes site assessment within a broader customer process. Professional teams should define the actual assessment and approval requirements for their project and market rather than treating a general guide as local authority.

When should remote shading review stop and request field evidence?

A remote shading review should stop when decision-changing geometry, height, vegetation, roof access, horizon, image currency, or object identity remains unresolved; when imagery conflicts with drawings or photographs; or when another person may rely on the output for engineering, procurement, contract, construction, or consequential financial decisions without adequate field evidence. The stop changes the next output, not the project’s viability.

Define stop conditions before the project deadline. Otherwise every unresolved object starts to look small when the team wants to release a proposal. A stop can apply to one roof area, one claim, one model, or the whole package. The responsible reviewer should state the scope rather than letting a general warning freeze unrelated work or permit unsafe inference.

Use a remote-review disposition table:

Write the stop as an action. “Verify on site” is too vague when another team needs to know whether it can continue. Name the zone, unresolved field, affected output, evidence required, responsible owner, and event that reopens review. If a reduced preliminary layout avoids the unresolved area, state whether that is a temporary screening choice or the accepted project scope.

Do not use the stop rule to manufacture urgency. A site visit may be appropriate, or another current source may answer the question. The required evidence follows the decision and project procedure. The article cannot prescribe one universal survey method for every roof, market, risk, and release.

Illustrative workflow example, not a customer result: Remote sources disagree about a low roof extension beside the proposed array. The reviewer marks the geometry conflict, prevents the layout and annual shade statement from advancing, and issues a request for suitable measurements and photographs. The rest of the screening record remains available, but no one may treat the conflicted zone as confirmed roof.

Record refusals and limitations. If access is unavailable or the customer declines further evidence, do not fill the gap. Change the output, restrict the claim, exclude the area where appropriate, defer the decision, or stop. The project record should show which course the authorized owner chose and why.

Inspect image artifacts before interpreting objects

Stitched imagery can contain seams, displaced edges, inconsistent viewing dates, or textures that resemble roof features. Tree crowns and roof lines may lean because of viewing geometry. Bright surfaces can lose detail, while deep capture-time shadows can hide the object that cast them. These are interpretation problems before they become shading problems.

Compare multiple source layers and views where available. Zooming farther into one raster does not create new evidence after the native detail is exhausted. If the roof boundary moves between layers, record the disagreement and choose a verification action rather than averaging it by eye.

Ask reviewers to mark the source feature that supports each modeled obstruction. An object with no visible or documented basis may be an erroneous addition. A visible feature with no model object may be an omission. This one-to-one trace is especially useful on crowded commercial roofs where equipment, vents, curbs, and parapets overlap in an overhead image.

Distinguish shade avoidance from project optimization

The lowest-shade roof area is not automatically the best project location. Array decisions may also depend on usable area, structural zones, access, drainage, fire and maintenance requirements, electrical routes, inverter placement, construction sequence, roof warranty, customer scope, and consumption or export objectives.

A designer should therefore explain why the selected layout balances the documented constraints. Do not let a shade heat map become the only decision surface. Compare viable layouts on a consistent project basis and show the tradeoff that actually changes the choice.

The solar designing page describes connected roof and layout work. Any selected arrangement remains preliminary until the required site evidence and responsible reviews support its release. Shade analysis narrows choices; it does not grant permission to ignore other disciplines.

When a customer asks why a slightly shaded plane was used, answer from the controlled decision record. “Because the software chose it” is not a project rationale.

Frequently Asked Questions

Can satellite imagery be used for a preliminary solar layout?

Yes, when the imagery is suitable and the output is clearly labeled as preliminary. Record the imagery source and observation limits, identify features that remain uncertain, and state what field evidence is required before later release. Imagery can support screening, but it does not verify every roof dimension, height, obstruction, or access condition.

Why does an overhead image fail to show object height?

An overhead image records reflected light from one viewing geometry. Visible outlines may suggest location, but height and three-dimensional relationships require additional data, stereo or elevation methods, known measurements, or field evidence. Shade duration and reach depend on those vertical relationships as well as the changing position of the sun.

How should trees be handled in a shading review?

Record the observation date, species or growth behavior where known, current height and canopy evidence, ownership or management constraints, and the scenario being modeled. Separate present conditions from proposed trimming or removal. Do not assume that vegetation will remain fixed or that future maintenance can occur without the responsible party’s agreement.

Does visible roof shade equal annual energy loss?

No. A visible shadow is an observation at a particular time. Annual energy effect depends on solar resource, timing, duration, geometry, array placement, equipment configuration, bypass behavior, and the model used. Review the physical shade evidence and the electrical and energy model rather than translating one image directly into an annual percentage.

When is a site visit needed for shading analysis?

Use a site visit or other suitable field method when hidden geometry, current vegetation, object heights, roof access, structural or electrical conditions, or the consequence of error cannot be resolved remotely. The required evidence depends on the project stage and decision, so define the release purpose before setting the verification level.

An image begins the question

Satellite imagery gives solar teams a fast way to see a site and decide whether deeper work is justified. Its value is strongest when its boundaries stay visible.

Record the image as a dated source. Add suitable surface data, multiple views, current photographs, field measurements, and qualified review as the decision requires. Then connect physical shade to time, resource, array placement, equipment, and the energy model. The complete story is a chain of evidence, not a single overhead frame.