Solar Shade Analysis 2026: Tools, Methods and Accuracy

A Phoenix commercial rooftop produced 6,300 MWh in its first year instead of the modeled 8,200 MWh. Solar shade analysis would have caught the neighboring building’s shadow that caused the 23% shortfall. The developer later paid more than $500,000 in PPA penalties and redesign costs. Shade is not a secondary input. It is a primary design variable.

Solar shade analysis is the process of modeling or measuring how obstructions block sunlight from reaching a PV array. It predicts annual energy losses, identifies viable roof areas, and informs equipment choices such as string inverters versus microinverters.

This guide compares the six methods installers and engineers actually use. We look at accuracy claims against real validation data, cost per site, and which method fits residential, commercial, and utility-scale workflows. We also explain how to turn a shade report into a design decision — and which mistakes turn accurate data into bad installations.

In this guide:

• What solar shade analysis measures and why it matters
• Six methods compared by accuracy, cost, time, and program acceptance
• How 3D simulation engines calculate shading hour by hour
• What validation studies say about remote versus on-site accuracy
• A decision framework for choosing the right method for your project
• Common mistakes that ruin shade analysis
• How shade data drives inverter selection and production estimates

What Solar Shade Analysis Actually Measures

Solar shade analysis answers one question: how much of the available solar resource actually reaches the modules? The answer is not just a percentage. It is a set of metrics that each drive different decisions.

Solar Access % measures shade-only loss. It compares irradiance that reaches the array after shading to the irradiance that would reach the same surface with zero shade. A south-facing roof with a tree blocking 10% of the sky might score 90% Solar Access. Orientation does not affect this number — only obstructions do.

Tilt and Orientation Factor (TOF) measures the geometry penalty. It compares actual plane-of-array irradiance at the roof’s real pitch and azimuth to the optimal pitch and azimuth for that latitude. A shallow north-facing roof at mid-latitude might score 75% TOF even with no shade.

Total Solar Resource Fraction (TSRF) combines both: Solar Access × TOF. This is the headline number on most shade reports and the figure incentive programs use. A roof with 92% Solar Access and 96% TOF produces 88.3% TSRF.

Most programs set a TSRF floor. Energy Trust of Oregon requires 75% for on-site tools and 80% for remote analysis. NYSERDA pro-rates incentives below 80%. MassCEC accepts 70% weighted average. Oncor’s Texas program uses Solar Access %, not TSRF, so submitting the wrong metric causes rejection.

Shade analysis also distinguishes between geometric shading — the physical area blocked — and electrical shading loss — the actual energy lost. Because series-connected cells must carry the same current, a 10% geometric shade can cause 30–40% electrical loss in a string inverter system. Good analysis models both.

Why the Metrics Matter in Practice

Imagine two identical houses on the same street. House A has a clear south-facing roof at 30° pitch. House B has the same roof but a mature oak 40 feet to the south. Both might have similar TOF, but House B’s Solar Access drops from 100% to 82%. That 18-point drop reduces TSRF from roughly 96% to 79%.

For a 7 kW system in a market with a $0.15/kWh retail rate, the difference is approximately 1,100 kWh per year. Over 25 years, that is 27,500 kWh, or about $4,100 in lost production value. The shade report is what prevents that loss from being a surprise.

Read more about the physics in our guide on how shading affects solar panels.

Six Methods for Solar Shade Analysis in 2026

There is no single best method. The right choice depends on project scale, budget, risk tolerance, and whether the output must be accepted by a lender or incentive program.

Accuracy figures derived from NREL validation studies, Scanifly 2023, and industry-observed ranges. Costs are approximate as of mid-2026.

Sun path diagrams are the simplest method. A printed chart of solar altitudes and azimuths is overlaid on the visible horizon. The method is fast and free but operator-dependent. It is useful for ruling out obviously poor sites, not for production estimates.

The Solar Pathfinder improves consistency with a reflective dome that shows the entire sky hemisphere on a sun-path chart. It is widely accepted by US incentive programs and costs under $350. The limitation is single-point measurement: it tells you about one spot, not every module location on a complex roof.

Fisheye-lens photography captures the same hemisphere digitally. Software overlays sun paths and calculates shaded hours automatically. It produces a permanent record and moderate accuracy, but it still samples one point at a time.

3D software simulation is the industry default for professional design. Tools like SurgePV, PVsyst, HelioScope, and Aurora Solar build a 3D scene from satellite imagery, LiDAR, or manual input. The engine simulates 8,760 hourly sun positions and calculates shading loss for every module. Accuracy is typically ±2–3% annually when the 3D model is correct.

Satellite/LiDAR remote analysis runs inside these same platforms using aerial data alone. Where LiDAR is available, it is statistically equivalent to on-site measurement. Where only satellite imagery is available, tree canopy height is the main uncertainty.

Drone photogrammetry produces centimeter-accurate 3D models from overlapping aerial images. It is the most defensible method for complex sites and is increasingly accepted by programs like MassCEC and Rhode Island REF.

How 3D Software Simulation Works

3D simulation is the method most readers will actually use. Understanding how it works helps you spot when a model is trustworthy and when it is garbage.

The process has four stages:

1. Scene reconstruction. The software builds a 3D model of the site. Data can come from satellite imagery, LiDAR point clouds, drone photos, or manual measurements. SurgePV’s solar shadow analysis software ingests multiple sources and lets designers add trees, buildings, and mechanical equipment manually when aerial data is incomplete.

2. Sun position calculation. For every hour of the year, the engine calculates the sun’s altitude and azimuth using the project’s latitude and longitude. This produces 8,760 sun positions.

3. Ray-tracing or viewshed analysis. The engine casts rays from each module location toward the sun. If an obstruction blocks the ray, that hour is flagged as shaded. Advanced engines also calculate diffuse irradiance reduction based on the visible sky dome.

4. Energy yield integration. Shading results are combined with hourly weather data — typically from NREL’s NSRDB or an equivalent TMY dataset — to produce annual production. The output includes monthly and annual Solar Access, TSRF, and energy loss maps.

The quality of the output depends almost entirely on the quality of the 3D scene. A model with the wrong tree height or a missing parapet will produce wrong numbers even if the ray-tracing math is perfect. That is why the best workflows include a manual review step, especially for tree-heavy sites.

Diffuse Irradiance and the Sky Dome

Direct beam irradiance is either blocked or not. Diffuse irradiance is more complex. It arrives from the entire sky dome, not just the sun’s disk. A panel behind a parapet still receives diffuse light from the visible portion of the sky.

High-latitude locations like Germany, the UK, and the northern US receive 50–60% of their annual GHI as diffuse irradiance. In those markets, a horizon profile that blocks part of the sky dome matters, but the loss is smaller than the geometric shadow suggests. In desert sun-belt locations, direct beam dominates. The same obstruction creates a larger production drop because there is less diffuse light to fill in the shaded hours.

Good simulation engines model this with view factors. They calculate how much of the sky dome is visible from each module point and weight irradiance accordingly. Engines that only model direct beam shading systematically underestimate losses in diffuse-rich climates and overestimate them in clear-sky climates.

Weather Files and Temporal Resolution

Most shade engines use Typical Meteorological Year (TMY) data. In the US, the standard source is the National Solar Radiation Database from NREL. The TMY file provides hourly irradiance, temperature, and wind data representative of a multi-year average.

Temporal resolution matters. An engine that simulates shading once per day at solar noon will miss morning and afternoon obstructions. Hourly simulation is the minimum acceptable standard. Sub-hourly simulation adds accuracy for fast-moving cloud shading, though that is usually handled by a separate weather variability model rather than the shade engine itself.

Shade Analysis and Inverter Topology: A Worked Example

Shade data is only useful if it changes the design. The most important design decision it drives is inverter topology.

Consider a 10 kW residential system with a chimney that shades one panel for four hours each winter afternoon. The analysis shows 8% annual shading loss geometrically, but the electrical loss depends on the inverter choice.

Values assume 14,000 kWh/year unshaded production and a $0.16/kWh blended retail rate. Actual results vary by module, climate, and shade pattern.

The optimizer premium for this system might be $800–$1,200. The recovered energy value is $3,500–$7,000 over 25 years. Even with moderate shading, module-level power electronics pay for themselves quickly.

This is why the shade report should never live in a separate PDF from the electrical design. When shading data flows directly into the BOM, the designer sees the financial impact of each topology choice before the proposal leaves the desk. SurgePV connects shadow analysis to the electrical design and financial model so the topology decision is based on numbers, not habit.

The Accuracy Question: What Validation Studies Really Show

Accuracy claims are easy to make. Validation studies are harder. Three data points matter most.

NREL Aurora validation: The National Renewable Energy Laboratory compared Aurora Solar’s remote shade analysis to on-site Solmetric SunEye measurements in Los Angeles and Denver. Annual Solar Access Values were within ±5 SAV of SunEye overall. Where LiDAR data was available, accuracy improved to ±3 SAV. The study established that remote analysis can match on-site measurement when high-quality elevation data exists.

Scanifly drone comparison (2023): Scanifly reported virtual solar viewshed calculations within 1% of SunEye readings at the same site, and up to 30% more accurate than satellite-plus-LiDAR alone on complex roofs. This confirms that drone surveys add the most value where obstructions are complex or close to the array.

IEA-PVPS Task 13: The IEA Photovoltaic Power Systems Programme reports that shading losses for well-sited systems typically range from 1–5% annually, but can reach 20–30% for urban rooftop and facade installations. The magnitude of loss is highly site-specific, which is why generic derate factors are risky.

These studies reveal a counterintuitive point: remote analysis is not inherently less accurate than on-site measurement. The deciding factor is data quality, not proximity. A drone survey or LiDAR-based remote model often outperforms a handheld Pathfinder because it samples the entire roof, not one point.

The exception is satellite-only analysis without LiDAR. On tree-heavy sites, canopy height errors can push a borderline 77% TSRF above an 80% incentive threshold on paper while the real system underperforms. For those sites, add a drone survey or physical measurement.

Bankability: Which Reports Programs Actually Accept

A shade report is only useful if the program reviewing it trusts the method. Bankability is program-specific, not universal. A report accepted by NYSERDA may still need supplemental verification for a private lender or a different state fund.

Most US incentive programs maintain an approved-tool list. The lists change, so always pull the current version before submitting. As of mid-2026, the major programs generally accept the following methods:

Oncor’s Texas program is the important exception. It does not use TSRF at all. The program manual requires Solar Access %, stated as the annual unshaded percentage. Submitting TSRF instead of Solar Access causes the interconnection agreement to be returned for correction.

NYSERDA also handles thresholds differently from most programs. A system at 72% TSRF still qualifies, but the incentive is pro-rated. A rebate that would be $5,000 at 80%+ becomes roughly $4,500 at 72%. The project moves forward, but the homeowner must understand the reduced number before signing.

For commercial and utility-scale projects, bankability is about lender confidence, not just program rules. Lenders typically want:

• A recognized simulation platform with documented validation
• Hourly TMY weather data from an accepted source
• A 3D model traceable to survey data, LiDAR, or drone photogrammetry
• Clear assumptions for soiling, mismatch, wiring, and availability losses
• P50/P90 energy estimates when debt or tax equity is involved

The cost of upgrading from a standard 3D simulation to a drone-verified bankable report is usually $500–$2,000 per site. On a commercial project, that cost is recovered if it prevents even a 1% production shortfall on a multi-hundred-kilowatt array.

Choosing the Right Method for Your Project

Use this framework to match method to project.

For most residential and small commercial projects, 3D software simulation is the right starting point. It is fast enough for same-day proposals, accurate enough for standard incentives, and integrates directly with energy yield and financial modeling.

Add a drone survey when any of these apply:

• The roof has heavy tree cover within 50 feet.
• The project needs sub-2% production uncertainty for financing.
• Satellite/LiDAR data is outdated or low resolution.
• There are nearby buildings or parapets that aerial data may misrepresent.

For utility-scale or PPA-backed projects, treat shade analysis as a due-diligence item. An independent review of the 3D model and assumptions is standard practice. The cost is small compared to the value of production guarantees.

The regional climate also shapes the choice. In northern Europe, where diffuse irradiance dominates, a rough horizon profile may be sufficient for concept-level screening because direct beam losses are smaller. In the US sun belt, where direct beam irradiance dominates, accurate obstruction modeling is critical — a small shadow at the wrong hour creates a large annual loss.

Common Mistakes That Ruin Shade Analysis

Even good tools produce bad results when misused. These are the most common failures.

Using a single measurement point for a multi-plane roof. A Pathfinder or fisheye photo measures one location. If that point is on the south plane but modules also go on the east plane, the measurement is irrelevant for half the array. 3D simulation samples every module location.

Ignoring tree growth. A system designed for year-one canopy height will be shadier in year fifteen. Some platforms now model vegetation growth using LiDAR-derived canopy data. On long-term contracts, this is not optional.

Confusing geometric and electrical loss. A roof plan showing 8% shaded area does not mean 8% energy loss. In string inverter systems, partial shading creates bypass-diode losses that multiply the real impact. Always model electrical behavior, not just shadow area.

Submitting satellite-only reports on tree-heavy sites. Incentive programs and lenders know this risk. Energy Trust of Oregon requires 80% TSRF for remote analysis versus 75% for on-site tools — a direct acknowledgement that remote methods carry higher uncertainty where trees are involved.

Forgetting seasonal variation. Annual TSRF can hide severe winter shading. A system with 85% annual TSRF but 60% Solar Access in December may still qualify for incentives while disappointing the homeowner in January. Always review the monthly chart.

Not updating the model after mitigation. Tree trimming changes the shade report. Lenders require the as-installed report, not the pre-mitigation version. Re-run analysis after any physical change to the site.

Using default obstruction heights. A software platform may auto-generate a tree or building at a default height if the data source lacks the real value. A 25-foot default tree when the real tree is 45 feet will understate shading by a wide margin. Always verify auto-detected obstructions against aerial imagery or a site photo.

Treating annual TSRF as the only number. Annual TSRF gets the project through incentive review. Monthly Solar Access explains customer complaints. A system that qualifies on annual figures can still disappoint in December. Review both before signing the design.

From Shade Data to Design Decisions

Shade analysis is not the end of design. It is the input to four downstream decisions.

Panel placement. Remove modules from locations that receive more than two hours of daily shade during the primary production season. A panel saved from a bad location produces more than a panel squeezed into it. On multi-plane roofs, place the highest-wattage modules on the highest-TSRF planes first.

String routing and inverter topology. Group modules with similar Solar Access % on the same MPPT channel. Never mix a 98% Solar Access module with an 82% module on the same string. For partially shaded strings, specify power optimizers or microinverters. The typical recovery is 20–30% of the energy a string inverter would lose under moderate shading.

Production and financial modeling. Feed shade-adjusted irradiance into the energy yield model. SurgePV’s generation and financial tool applies the shading loss, inverter topology, and local weather data to produce payback and 25-year savings. A proposal built without this integration overstates production.

Customer communication. A shade report should travel with the proposal. When a homeowner can see the 3D model showing why panel 7 is an optimizer, the conversation shifts from trust to evidence. Static PDFs with three numbers do not create that shift. SurgePV’s solar proposal software embeds the live 3D shade visualization directly in the customer-facing document, so the homeowner sees the same model the designer used.

For a deeper walkthrough of the metrics, read our guide on how to read a solar shade report. For platform-specific comparisons, see our post on solar shading analysis tools.

Frequently Asked Questions

What is solar shade analysis?

Solar shade analysis is the process of modeling or measuring how obstructions block sunlight from reaching a PV array. It predicts annual energy losses, identifies viable roof areas, and informs equipment choices such as string inverters versus microinverters.

How accurate is solar shade analysis?

Validated 3D software simulation typically achieves ±2–3% annual accuracy against metered production. Remote LiDAR-based analysis is within ±3–5 SAV of on-site SunEye readings. Hand tools like the Solar Pathfinder have ±10–15% variance. Satellite-only analysis without LiDAR can exceed ±10% on tree-heavy sites.

What are the main methods of solar shade analysis?

The six main methods are sun path diagrams, Solar Pathfinder, fisheye-lens horizon photography, 3D software simulation, satellite/LiDAR remote analysis, and drone photogrammetry. Each differs in accuracy, cost, time, and whether it is accepted by incentive programs.

Is remote shade analysis as accurate as on-site measurement?

Yes, when LiDAR is available. NREL validation found Aurora Solar’s remote analysis within ±5 SAV of SunEye in Los Angeles and Denver, improving to ±3 SAV where LiDAR data existed. Drone photogrammetry has reported accuracy within 1% of SunEye.

What is a good TSRF for solar?

A TSRF above 85% is excellent. Most incentive programs require a minimum of 75–80% TSRF. MassCEC accepts 70% weighted average. Below 70%, designers usually recommend mitigation such as tree trimming, panel relocation, or module-level power electronics.

Which shade analysis method should I use for a residential project?

For most residential projects, 3D software simulation using satellite and LiDAR data is the best balance of accuracy, speed, and cost. Add a drone survey only for complex roofs with heavy tree cover or for projects where bankability requirements demand sub-2% uncertainty.

What software is used for solar shade analysis?

Common platforms include SurgePV, PVsyst, HelioScope, Aurora Solar, OpenSolar, and PVGIS. These tools use horizon profiles, 3D ray-tracing, and hourly irradiance data to quantify shading losses and optimize panel placement.

How does shade analysis affect inverter choice?

Shade analysis reveals which modules or strings are affected. For systems with moderate to heavy shading, microinverters or DC optimizers isolate losses to shaded panels. String inverters are acceptable when annual shading loss is under 5% and exposure is uniform.

Conclusion

Solar shade analysis is the difference between a system that performs as modeled and one that becomes a dispute. The method you choose should match the project’s risk, scale, and financing requirements.

Three actions to take next:

1. Audit your current workflow. If you are still using single-point manual tools for final designs, move to 3D simulation. The accuracy gain pays for itself on the first avoided underperformance claim.
2. Match the method to the financing. Residential incentives accept 3D simulation. Commercial lenders may require drone verification. Know the threshold before you start the survey.
3. Review every shade report monthly, not just annually. Winter shading determines customer satisfaction and inverter start-up behavior. The annual TSRF is a gate; the monthly chart is the story.

Start with SurgePV’s solar design software for same-day shade simulation. Run the shadow analysis, feed the result into the generation and financial tool, and send a proposal that shows the customer exactly why each module goes where it does.