DefinitionA

Aerial Roof Scan

Assessment of roof geometry and visible features using overhead imagery or remotely acquired data, with stated methods, uncertainty and required project verification.

5 min read
Keyur Rakholiya

Written by

Keyur Rakholiya

CEO & Co-Founder · SurgePV

Rainer Neumann

Edited by

Rainer Neumann

Editorial contributor · SurgePV

Quick answer

Assessment of roof geometry and visible features using overhead imagery or remotely acquired data, with stated methods, uncertainty and required project verification.

What Is an Aerial Roof Scan?

Answer: An aerial roof scan assesses roof geometry and visible features using overhead photographs, photogrammetry or other remotely acquired data. It can support solar screening, preliminary layouts and targeted verification. The result must identify source dates, measurement methods and uncertainties. It is not automatically a verified survey, structural assessment, roof-condition inspection or complete approval to install solar.

Aerial imagery import loads the reference data; the scan interprets it. Keep that distinction clear when commissioning a deliverable or explaining a remote proposal to a customer.

What Each Data Product Can Support

Product Useful information Boundary
Overhead RGB image Visible outlines, obstructions and context Hidden surfaces, height and pitch may remain unresolved
Photogrammetric model Reconstructed geometry from suitable overlapping images Reconstruction and geospatial accuracy need assessment
LiDAR point cloud Sampled 3D surfaces Coverage, classification, datum and accuracy matter
Thermal image Temperature-pattern evidence under recorded conditions A pattern does not independently prove moisture, structural failure or a specific electrical fault

Do not assign a universal accuracy, price or turnaround to “satellite,” “drone” or “LiDAR.” Nor does a particular drone brand or RTK label alone prove a survey-grade result. The PIX4D accuracy documentation distinguishes internal geometric accuracy from absolute geographic position and recommends checkpoint assessment. Point clouds and orthomosaics can have locally less accurate roof edges or reflective surfaces.

Roof Assessment Workflow

  1. Confirm the building and the actual capture date, coverage and data products.
  2. Identify roof planes, visible ridges/eaves and uncertain boundaries. Record how pitch and heights were obtained.
  3. Mark visible vents, skylights, HVAC, parapets and neighboring obstructions; flag occluded zones rather than treating them as empty.
  4. Align image and elevation data using their stated reference systems and verification evidence.
  5. Apply the applicable project setbacks/access requirements and assess shading with the needed geometry and resource data.
  6. Produce a preliminary layout and a verification list, then revise it after required site and engineering checks.

The USGS orthoimagery specification provides a useful reminder that imagery resolution, spatial quality and application requirements are distinct. Its base mapping specification is not approval of a solar roof layout.

Plan Area, Surface Area and Usable Space

A top-down projected area is different from a sloping roof’s surface area. For a hypothetical simple plane with 48 m² horizontal projection and an independently established 30° pitch:

Surface area = 48 ÷ cos(30°) = 55.43 m².

This assumes a planar roof and a valid horizontal projection. It does not obtain pitch from a single image or establish space for a particular panel count. Modules have dimensions, gaps, mounting constraints and access requirements.

Exclusion footprints can overlap. Suppose another hypothetical 100 m² roof-surface polygon has 15 m² obstruction exclusions, 20 m² setback exclusions, and 5 m² shared overlap:

Excluded union = 15 + 20 − 5 = 30 m².

Remaining surface area = 100 − 30 = 70 m², before other requirements. Simply subtracting both full exclusions would produce 65 m² and double-count their overlap. A layout still requires geometric packing; remaining area alone does not give an installable panel count.

Shade is also time-dependent. A shadowed region is not automatically a permanent exclusion of the same area. Use the actual design objective and performance assessment rather than subtracting one aerial shadow from the roof as an annual loss.

Verification Before Release

Retain known dimensions and uncertainty sufficient to test the proposed fit. A simple scale example is 5% of a 40-foot run = 2 feet; treated as a hypothetical discrepancy, it shows why an unverified edge can materially affect layout. It is not a measured scan-error rate.

Independent checks need not be limited to two dimensions for every roof. The verification plan should resolve the particular risks: edge location, pitch, obstacle height, concealed areas, current condition and mounting access. Roof structure and electrical/service capacity require their own qualified assessment.

Recent photographs and property records can supplement the scan but do not prove hidden roof condition. Thermal results need appropriate acquisition conditions and interpretation; they do not automatically identify rot, moisture or a failed bypass diode.

Where new drone acquisition is warranted, specify the deliverables, coverage, reference system, control/checkpoint evidence and permitted use first. For U.S. flights, consult FAA commercial-operator guidance and the actual flight requirements. Do not assume a fixed equipment budget or a certificate permits every operation.

Handoff to Designers, Installers and Customers

Designers should identify which geometry is measured, derived or assumed and carry unresolved items into shading analysis and layout review. Installers should document verification findings and communicate revisions before construction. Sales teams should distinguish an illustrative proposal from a released design and avoid unsupported cost savings, installation accuracy or same-day approval promises.

When evaluating SurgePV, confirm the supported data and workflow for this project. A general platform claim does not establish automatic roof scanning, obstruction detection, structural review or universal imagery coverage.

Common Questions

How accurate is an aerial roof scan?

Review its actual method, control/checkpoint evidence and local uncertainties. Resolution or sensor type alone is insufficient.

Do I still need site verification?

Remote assessment does not establish hidden condition, structure or electrical capacity. Resolve those and any uncertain geometry through the appropriate project checks.

How much does a scan cost?

Obtain a quote for the required acquisition, processing, accuracy evidence and rights. There is no universal site price.

Can a scan diagnose roof defects?

It may reveal visible or thermal indications. Diagnosis and suitability for installation need qualified interpretation and verification.

Which drone should I use?

Define the required outputs, accuracy and flight constraints first. The model name alone does not establish fit for the task.

About the Contributors

Author
Keyur Rakholiya
Keyur Rakholiya

CEO & Co-Founder · SurgePV

Keyur Rakholiya is identified by SurgePV as its CEO and a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, testing claims, media appearances, and speaking engagements are not asserted without retained evidence.

Editor
Rainer Neumann
Rainer Neumann

Editorial contributor · SurgePV

Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.

Explore More Solar Terms

Browse 300+ terms in our complete solar glossary - or see how SurgePV puts these concepts into practice.

No credit card required · Full access · Cancel anytime

Choose which optional technologies SurgePV may use. Essential storage remains active for security and requested features.