Back to Blog
solar technology26 min read

Solar Drone Site Survey: Thermal, LiDAR, Rules

Plan a solar drone site survey with clear sensor choices, accuracy checks, flight rules, and cost assumptions before handing data to designers.

Rainer Neumann

Written by

Rainer Neumann

Editorial contributor · SurgePV

Keyur Rakholiya

Edited by

Keyur Rakholiya

CEO & Co-Founder · SurgePV

Published ·Updated

Answer

A solar drone site survey captures imagery or spatial data to support roof modeling, shading assessment, or inspection. The deciding factor is the quality of the accepted deliverable, not the aircraft specification alone. Define accuracy requirements, verify independent checkpoints, obtain the applicable flight permissions, and check the design-data handoff.

Last updated: November 2026 Consider an illustrative design example: a multi-level industrial roof in Stuttgart, with skylights, ventilation equipment, and parapets at different heights. A drone survey could help document the geometry and surrounding obstructions before the design team decides which roof areas are usable. It would still need a defined accuracy requirement, independent checks, and separate structural and electrical assessment.

This is a planning example, not a documented project or a claim about flight time, measured accuracy, or avoided site visits. The value of drone capture depends on whether the final deliverables answer the designer’s questions.

SurgePV publishes this post and sells solar design software.

TL;DR: Specify the deliverable before choosing a drone. RGB imagery supports photogrammetry, thermal imagery supports investigation of operating arrays, and LiDAR can support geometry or terrain work where justified. Validate the finished model with independent checks. Flight permissions, data processing, and design-software compatibility are separate parts of the job.

Make the survey useful to your design team

Explore the roof modeling and shading workflow your site evidence needs to support.

Book a Demo

Checking cost first? See the SurgePV pricing page.

Latest Updates: Solar Drone Surveys 2026

The important 2026 distinctions are between aircraft positioning and survey accuracy, between mapping and thermal camera variants, and between a commercial purpose and the legal category of a flight. A product name or a paid assignment does not settle those questions.

Equipment and regulation checks

The DJI Mavic 3 Enterprise specifications distinguish the Mavic 3E from the Mavic 3T. The 3E has a 20 MP 4/3 CMOS wide camera with a mechanical shutter. The 3T has a 48 MP 1/2-inch CMOS wide camera and a 640 × 512 thermal camera. Do not combine the 3E’s wide-camera specification with the 3T’s thermal capability in a purchase comparison.

The FAA Remote ID guidance applies to registered drones and drones required to be registered. It describes standard Remote ID aircraft, broadcast modules, and operations within FAA-Recognized Identification Areas under their conditions. The statement that every commercial drone must always broadcast without any exception is too broad.

For Europe, EASA explicitly includes low-risk commercial activities in the Open category. A solar survey is not automatically a Specific-category operation. The aircraft, location, people nearby, and operating plan determine whether the Open requirements can be met.

Issue Checked source Practical implication
Mapping versus thermal model DJI Mavic 3 Enterprise specifications Verify the exact camera variant and accessories
US Remote ID FAA Remote ID guidance Establish the applicable compliance route for the aircraft and operation
EU commercial work EASA Open-category guidance Assess the operation against the category conditions
Final model accuracy PIX4D accuracy documentation Distinguish relative accuracy, absolute accuracy, and positioning specifications
Survey deliverables OpenDroneMap output documentation Specify image, surface, point-cloud, and mesh outputs separately

Sources in this table were opened in November 2026 and are linked here or in the relevant sections below. The table is a set of checks, not an equipment popularity ranking.

What to revisit before the next survey

Review aircraft firmware, registration details, required identification, mission-software support, and the camera configuration. Record changes that could affect capture or processing. An old project template may contain an obsolete device name, coordinate setting, or assumption about available imagery.

Treat beyond-visual-line-of-sight (BVLOS) work as a separate operational question. An aircraft’s advertised transmission range is not permission to fly that distance. Use the regulator’s applicable route and the actual authorization conditions before planning a mission beyond ordinary visual-line-of-sight operation.

Likewise, a cloud processor’s export menu is not proof that your solar design platform can use every output. Ask for a representative dataset and check the full path from capture to a reviewed design. This is more useful than relying on a generic statement that drone data integrates with modern software.

Why Drone Surveys Can Complement Manual Site Assessment

Drone capture can provide an overhead record and a basis for reconstructing geometry, especially where roof form and surrounding obstructions are difficult to document from the ground. It does not remove every reason to visit or inspect a building.

What manual and aerial surveys each contribute

Manual measurements can establish dimensions and control references that are difficult to infer from imagery. Ground-level inspection can record electrical equipment, access routes, customer requirements, and details hidden from an overhead camera. The design team needs these facts even when a drone supplies the roof model.

Aerial photographs can document roof planes, visible penetrations, adjacent structures, and vegetation from multiple positions. With an appropriate capture and processing workflow, the images can support an orthomosaic, point cloud, or digital surface model. Missing views, reflections, and occlusion remain possible.

An orthomosaic is an image product corrected and assembled for mapping. A point cloud is a collection of spatial points representing reconstructed or measured surfaces. A digital surface model (DSM) represents surface elevations, including visible buildings and vegetation. These are related deliverables, but they are not interchangeable.

Compare complete workflows, not flight time

A fair time comparison includes preparation, travel, permissions, control measurement, capture, upload, processing, quality review, and any return visit. Flight duration alone excludes much of the work required to produce an accepted design input.

Record those stages for your own sites. Separate elapsed processing time from staff time: a machine running overnight may use little labor, while a short flight with a long travel route can still be expensive. Include failed captures and weather postponements in the operational record.

Use the same scope when comparing an outsourced quote with an internal survey. A quotation for images only should not be compared with a service that includes surveyed checkpoints, processed geometry, and a signed accuracy statement. Define what the designer receives and what remains their responsibility.

Safety and access

Drone imagery may reduce roof access needed for some visual observations. It cannot verify concealed roof construction, attachment suitability, internal electrical conditions, or every aspect of roof condition. Plan any remaining inspections under the relevant site safety procedures.

The flight itself introduces a different set of tasks: launch and recovery, people and vehicle management, airspace checks, weather assessment, and emergency planning. Reducing one exposure does not make the whole survey risk-free.

Separate the flight assessment from the building inspection plan. A drone provider may be responsible for collecting imagery while another person determines whether the roof can support the installation. Record that division in the scope so neither party assumes the other has completed a structural assessment.

Accuracy must be demonstrated

The PIX4D explanation of relative and absolute accuracy distinguishes internal model geometry from the model’s position in a reference frame. A roof can look internally consistent and still be shifted relative to other site data.

Real-time kinematic (RTK) and post-processed kinematic (PPK) positioning can improve image geolocation. They do not, by themselves, verify every roof edge, height, or reconstructed obstruction. Capture quality, processing, control, and the reference system still matter.

Specify the acceptable error for the intended task and how it will be checked. A roof-edge clearance decision may need different evidence from a preliminary sales visualization. Do not use one universal centimeter figure for every aircraft, sensor, surface, and output.

Key Takeaway: Positioning is not model acceptance

Ask for independent checks of the dimensions and heights that matter to the design. An RTK status indicator or a detailed-looking mesh is not enough to approve the finished survey.

Types of Drone Data for Solar Projects

Choose the sensor according to the question being answered. A new roof-layout survey and a thermal inspection of an operating array need different capture plans and different acceptance criteria.

RGB photogrammetry

RGB cameras record visible-light images. Photogrammetry uses overlapping views to reconstruct spatial relationships and, where the workflow supports it, produce map imagery and three-dimensional geometry.

For a new solar design, the useful targets include roof boundaries, pitch changes, visible obstructions, neighboring buildings, and tree canopies. Define which features need measurable geometry and which need only photographic documentation. A small pipe may be visible in a photograph yet poorly represented in the surface model.

Require imagery with enough detail and coverage for the chosen processing method. Reflective, transparent, repetitive, or textureless surfaces can make reconstruction difficult. Keep uncertain features marked for another measurement rather than accepting the processor’s interpolated surface as fact.

RGB capture is a reasonable candidate for many roof-geometry tasks. Whether it is sufficient depends on the site and deliverable, not a fixed rule that every residential project needs only one sensor.

Thermal infrared imaging

A radiometric thermal camera records information used to estimate apparent surface temperature under specified settings and conditions. For an operating PV array, thermal patterns can identify areas that need investigation alongside visible imagery and electrical information.

Thermal capture is not a substitute for a roof-geometry survey. It also cannot directly prove every cell defect or the cause of every warm area. Reflections, shading, soiling, operating state, and environmental conditions can affect interpretation.

Keep the original radiometric files where the workflow provides them, not only colorized screenshots. The report should identify the camera, settings, capture conditions, array state, and location of each finding. That allows a qualified reviewer to assess an anomaly and plan follow-up work.

Do not infer thermal measurement accuracy from visible-camera resolution. The two sensors have different optics, pixel counts, and calibration behavior. Verify the specification and operating conditions for the thermal payload actually used.

LiDAR

Light detection and ranging (LiDAR) uses laser returns, combined with positioning and orientation information, to produce spatial measurements. It can support roof geometry, terrain work, and vegetation assessment when the survey method is suitable.

Returns may reach ground through gaps in vegetation, but the sensor does not see through solid leaves or guarantee a complete bare-earth surface. Ground classification and independent checks remain necessary. Dense canopy, surface reflectance, flight geometry, and the required point distribution influence the result.

The DJI Zenmuse L2 specification lists supported aircraft and conditions attached to range and accuracy figures. Use those conditions when assessing a proposed configuration. A sensor’s ranging specification is not the same as the accuracy of a delivered roof model.

For a complex roof, ask what LiDAR resolves that the planned photogrammetry cannot. For ground-mount work, ask whether the required terrain is visible and how classified ground points will be checked. Choose the method from those questions rather than treating LiDAR as mandatory for every large site.

Multispectral imaging

Multispectral imagery records selected wavelength bands and can support vegetation or agricultural analysis where the sensor and method are appropriate. It is a specialist option for questions such as agrivoltaic crop monitoring, not a routine requirement for placing modules on a roof.

Define the intended vegetation metric, calibration process, and interpretation responsibility before commissioning capture. A colored vegetation map without a repeatable method may be difficult to compare across dates. Where agronomic conclusions matter, involve the relevant specialist.

Sensor selection questions

Survey purpose Candidate data Acceptance question
New roof geometry RGB photogrammetry, with additional measurement where needed Are critical edges, heights, and planes independently checked?
Complex terrain or vegetation LiDAR and visible imagery as appropriate Are ground classification and remaining gaps documented?
Operating-array anomaly screening Radiometric thermal plus visible imagery Are capture conditions and follow-up requirements recorded?
Agrivoltaic vegetation monitoring Suitable multispectral data Is the metric calibrated and comparable across visits?

This is a planning comparison based on the sensor and processing documentation cited in the guide. It is not a ranking of vendors or a promise that a sensor alone meets the acceptance requirement.

Drone Equipment for Solar Surveys

Select the complete capture system rather than the aircraft body alone. The camera, positioning method, software compatibility, batteries, support, and legal operating conditions all affect whether the system can perform the intended job.

Distinguish the actual camera configuration

The Mavic 3E and 3T examples above show why exact product names matter. A camera optimized for visible-image mapping and one that adds thermal capture serve different purposes. More visible-camera megapixels alone do not establish better mapping results.

For a modular aircraft, verify the payload, controller, firmware, mounting, and processing support as a complete combination. DJI’s L2 page lists the Matrice 350 RTK among supported aircraft. That compatibility statement should not be expanded into a claim that the combination is the industry’s most widely used system.

Avoid buying from an old price table. Request a dated quotation that identifies the aircraft, payload, positioning accessories, batteries, charger, software, support, and any required service plan. Check regional availability and contractual restrictions with the supplier before committing to a workflow.

Residential and small commercial work

For smaller roofs, assess portability, image quality, mission planning, and the ability to capture the relevant obstructions. Ask how the operator will document roof edges and verify measurements. The simplest equipment arrangement that meets those requirements may be preferable to a more complex kit.

Use a representative roof in an evaluation. Check difficult features such as shiny metal, a narrow dormer, a roof valley, or a parapet. A demonstration over an open field does not answer the same reconstruction questions as a residential roof.

Include the remaining site visit in the plan. Electrical service details, roof construction, and access requirements may need separate collection. A portable drone does not turn those tasks into aerial observations.

Commercial and utility-scale work

For larger sites, assess capture coverage, operational permissions, launch locations, battery logistics, and processing capacity together. A long advertised endurance does not equal usable mapping time with the chosen payload and reserve requirements.

Fixed-wing, vertical-takeoff, and multirotor aircraft have different operational trade-offs. Consider the site layout, takeoff and recovery space, need to hover, terrain, and the legal operating envelope. Require a mission plan for the actual site instead of assuming any one aircraft maps a fixed acreage per flight.

Where a specialist survey provider already has the necessary equipment and competence, outsourcing may be a useful first step. It can also reveal the deliverables your design team needs before you purchase equipment. Compare that option with the full internal cost rather than the aircraft price alone.

The Solar Drone Survey Workflow

A complete survey moves from an agreed design question to a checked deliverable. The six stages below keep capture, measurement, processing, and design acceptance connected.

Step 1: Pre-flight planning

Define the site boundary, target features, required outputs, coordinate reference system, and acceptance method. Identify the person who will accept the result and the design decisions that depend on it. Include surrounding shade sources where they are relevant and can be captured lawfully.

Check airspace and operating permissions through the appropriate authority. In the US, the FAA describes LAANC as an airspace-authorization service. Approval through that system is not a general waiver of other flight rules or site responsibilities.

Select flight height, image overlap, camera angle, speed, and exposure to meet the chosen processing workflow and site conditions. Keep the distinction between height above the ground and distance from a raised roof surface. A mission configured for flat terrain may produce different image detail over a tall building.

Review weather, emergency actions, people and vehicles, launch and landing areas, battery condition, and manufacturer operating limits. Establish what conditions will postpone or stop capture. The pilot should not be expected to improvise those decisions under pressure to finish a booked survey.

Step 2: Control and independent checkpoints

A ground control point (GCP) is a surveyed point used to constrain the reconstruction. An independent checkpoint is withheld from that adjustment so its reconstructed position can be compared with a reference measurement.

Plan the distribution and measurement method around the site geometry and required accuracy. Avoid placing all references on one accessible corner while relying on the model for distant or elevated features. The survey professional should determine the arrangement and document the reference-system accuracy.

RTK capture does not make independent checks unnecessary. Record positioning status, correction source, base information where applicable, and any periods of degraded positioning. Keep control and checkpoints identified separately in the processing report.

A checkpoint on the ground does not automatically validate every roof surface. Include checks that are relevant to the dimensions or heights that will drive the design, using a suitable and safe measurement method.

Step 3: Data capture

Capture the planned overlapping imagery, then inspect representative files before leaving. Check focus, exposure, motion blur, coverage, and whether difficult features are visible from enough positions. Flight completion in the controller is not proof that useful data was recorded.

Nadir images look downward; oblique images look at an angle. Where the reconstruction method calls for oblique coverage, use it to improve visibility of roof edges, vertical faces, and obstructions. Plan those views within the approved operating envelope.

Keep detail photographs and field notes linked to the project. If a roof feature cannot be reconstructed reliably, a clear photograph and a separate measurement can prevent the office team from guessing. Record any departure from the planned mission.

For thermal inspection, coordinate with the asset operator so the array’s operating state is known. Capture the environmental and electrical context required by the inspection method. Do not infer irradiance from inverter power alone, since curtailed or faulty equipment can change output.

Step 4: Photogrammetry processing

Archive the raw imagery and metadata before processing. Record software version, camera model, coordinate system, control, and settings. If the processing is repeated, retain the relationship between the new result and the original inputs.

The reconstruction typically involves matching image features, estimating camera relationships, generating spatial information, and producing selected surfaces or imagery. The exact pipeline and available outputs vary by software and settings. A successful process log still needs a quality review.

Choose processing software using representative data, output requirements, privacy needs, support, and total cost. Do not rely on a universal processing-time table: image count, resolution, hardware, settings, and cloud queues can change turnaround.

The OpenDroneMap output documentation lists georeferenced point clouds, textured meshes, orthophotos, and optional terrain or surface models. It shows why the requested output must be specified instead of assuming every processing job produces every deliverable.

Step 5: Quality check and deliverable generation

Compare independent checkpoints with their reference coordinates and report the method, distribution, and errors. Review local geometry as well as a project-wide summary. A small average error can conceal a problem in the particular roof section used for module placement.

Inspect seams, roof edges, glass, reflective metal, shaded areas, and vegetation. Mark holes or interpolated regions. Do not silently fill a missing roof corner and then present it as a measured feature.

Deliver the agreed files with a concise quality record: capture date, equipment, processing version, coordinate reference, control and checkpoint information, limitations, and any supplementary measurements. State which outputs are suitable for which decisions.

Step 6: Import and design acceptance

Verify supported formats and coordinate handling in the destination software before relying on the export. Import a sample and check known dimensions, elevations, orientation, and alignment between imagery and geometry.

Use the accepted survey as evidence for roof modeling and obstruction placement. The designer still needs the applicable setbacks, structural findings, electrical information, and equipment constraints. A measured roof edge does not itself supply the fire-access rule.

For a dedicated vendor example, Scanifly describes field upload of drone photographs and other site data as part of its workflow. Evaluate any platform against the exact deliverables and project needs rather than assuming equivalent functions across vendors.

Cost Analysis: Drone Survey vs. Traditional Methods

The financial case depends on the complete cost per accepted deliverable and the number of suitable jobs. There is no universal survey price or project-volume threshold that makes an internal program profitable.

Equipment and operating costs

Build a budget using dated supplier and service quotations. Include aircraft, payloads, positioning equipment, batteries, maintenance, software, computing or cloud processing, training, insurance, travel, and staff time. State how replacement and depreciation are treated.

Keep fixed annual costs separate from variable costs per site. Some subscriptions have limits that change the cost at higher volume. A software tier adequate for a few small roofs may not cover a large commercial dataset or every required export.

Allow for weather postponement, inaccessible sites, processing failures, and recapture. These should be visible in your operational assumptions rather than hidden inside an optimistic annual survey count. Use accepted projects as the denominator when calculating actual cost per deliverable.

Illustrative volume calculation

The following calculation shows how survey volume changes the allocation of a hypothetical fixed budget. Assume fixed annual costs of USD 7,816. This is not a supplier quotation, market average, or recommended equipment package. It excludes variable labor, travel, processing charges, and any other costs not included in that assumed fixed amount.

Accepted surveys per year Assumed annual fixed cost Fixed cost allocated per accepted survey
100 USD 7,816 USD 78.16
200 USD 7,816 USD 39.08
400 USD 7,816 USD 19.54
Fixed cost per survey: illustrative volume example (USD fixed cost per accepted survey)
  • 100 surveys/year$78.16
  • 200 surveys/year$39.08
  • 400 surveys/year$19.54

Source: Illustrative example, not market data: assumed USD 7,816 annual fixed cost divided by accepted surveys; variable costs excluded, checked November 2026.

The calculation shows the effect of spreading a fixed cost over more accepted work. It does not demonstrate that the team can complete that volume or that each additional job has no incremental cost.

Break-even analysis

For a simplified comparison, let F be the additional annual fixed cost of the internal program and S be the saving per accepted survey after variable costs. Then break-even volume = F / S, rounded up to whole surveys where appropriate.

Using the hypothetical F of USD 7,816 and an assumed S of USD 50 gives approximately 157 surveys. At an assumed USD 100 saving, the result is 79 surveys. These are arithmetic scenarios, not evidence of available savings or a prediction of payback.

Check whether the comparison uses an outsourced equivalent scope, an existing manual process, or a new service that was not previously offered. Each produces a different saving definition. Do not count the same staff saving both in variable costs and again as a separate benefit.

Potential reductions in rework should be measured from your project records. Avoid assuming that drone-derived visuals improve close rates or that every new model makes the yield forecast more accurate. Record the specific error avoided and the resulting cost before adding it to the business case.

Requesting comparable outsourced quotes

Send providers the same site boundary, intended use, deliverable formats, accuracy requirements, and deadline. Ask who establishes control, who checks the result, and how limitations are reported. Include any requirement for raw data and future access.

Clarify travel, weather rescheduling, recapture, processing revisions, and data-retention terms. A low flight-only price can become expensive if the output needs substantial office reconstruction. Compare the price of the accepted result, not merely the time spent in the air.

Plan the handoff before commissioning a flight

Discuss your survey deliverables and the supported SurgePV design workflow with the product team.

Book a Demo

Checking cost first? See the SurgePV pricing page.

Photogrammetry for Solar: From Images to 3D Models

Photogrammetry depends on observations of the same features from different viewpoints. Good imagery, suitable geometry, control, and processing must work together before the result can support measurements.

Structure from motion and image quality

Structure from motion estimates spatial relationships from matched image features and camera information. Subsequent processing can generate denser geometry and image products. A textured model can look convincing even where its underlying geometry is weak.

The PIX4D acquisition guidance emphasizes overlap, exposure, camera characteristics, and the acquisition plan. Follow guidance appropriate to the actual scene and software rather than treating one overlap percentage as sufficient for every roof.

Ground sampling distance (GSD) describes the spacing represented by image pixels at the observed surface. It is a resolution measure, not a guaranteed positional accuracy. Height, focal length, sensor characteristics, and the local surface affect it.

Check image detail at the roof, not only the terrain beneath the building. Slopes and height changes can alter overlap and resolution. If the smallest feature matters to the design, confirm that it is visible and reconstructed adequately rather than inferring suitability from the average GSD.

Common reconstruction failures

Observed problem Possible cause Review action
Missing surface patches Occlusion, weak texture, insufficient useful views Inspect source images and plan additional capture or measurement
Bent or shifted geometry Control, positioning, calibration, or reference-system issue Examine checkpoints and processing assumptions
Blurred imagery Motion, focus, or exposure problem Reject unsuitable frames and assess whether recapture is needed
Weak roof edges Poor viewing geometry or reconstruction artifacts Compare oblique images and independent dimensions
Noise on glass or shiny metal Reflections or ambiguous matches Mark uncertainty and obtain another measurement where necessary
Misaligned exports Different reference systems or processing origins Verify coordinate metadata and known reference features

These are diagnostic possibilities, not automatic diagnoses. Inspect the evidence before changing a processing setting. A larger output file or higher-quality preset cannot create a feature that the camera never observed.

DSM versus terrain and mesh

A DSM represents surface elevations, including buildings and vegetation. A digital terrain model (DTM) aims to represent ground after the relevant classification or processing. Using a terrain model where a roof surface is needed can remove precisely the objects that cast shade.

A textured mesh adds a visual surface representation. It may be useful for inspection and communication, but its appearance should not replace a measurement check. Keep the survey’s uncertainty information with any simplified model exported to another application.

For roof modeling and array layout, verify ridge lines, plane boundaries, and the height of shading objects. If the design tool simplifies the incoming surface, review that simplified geometry too. An accurate source file can be misinterpreted during conversion or tracing.

The accuracy of a shade result is not a simple one-to-one function of DSM accuracy. Sun position, weather, obstruction representation, electrical mapping, and model assumptions also affect the output. Treat the survey as an important input to site-specific shading analysis, with the remaining assumptions still visible.

Thermal Imaging for Existing Solar Installations

Thermal inspection identifies temperature patterns that can guide investigation of an operating array. It complements visible inspection and electrical diagnostics; it does not automatically determine the cause or severity of every anomaly.

What thermal imagery can reveal

FLIR’s 2019 guide, Using Thermal Imaging Drones for Solar Field / PV Inspections, describes the value of pairing visible and thermal data and the effects of resolution, operating conditions, and environmental factors. Its discussion supports careful interpretation, not a universal defect-detection rate.

A warm cell-sized area, a repeated substring pattern, or a group of warmer modules may justify follow-up. The report should identify the observation first and distinguish it from a confirmed electrical diagnosis. Visible soiling, shade, reflections, or disconnected equipment can change the interpretation.

Do not state that a functioning cell converts most incident sunlight into electricity. Commercial PV conversion leaves substantial energy outside electrical output, and temperature depends on several heat-transfer and operating factors. A simple hot-equals-defective rule is inadequate.

Capture conditions and camera settings

Choose the flight plan for the inspection’s required detail and the camera’s thermal resolution. A visible image sharp enough to identify a module does not guarantee thermal pixels sufficient to identify a smaller feature.

Record irradiance where required by the procedure, weather, wind, array loading, camera angle, emissivity assumptions, and reflected-temperature treatment. Use the applicable inspection standard and equipment guidance for numeric limits. This guide does not supply a universal flight altitude, temperature-difference threshold, or irradiance cutoff.

Moving cloud shadows, reflections, and changing operating conditions can make images difficult to compare. If conditions change, record the affected area and determine whether it needs another capture. A color palette can exaggerate a small temperature range, so preserve quantitative context where available.

From anomaly to maintenance action

Assign each finding a location that the maintenance team can identify on the ground. Include the visible image, thermal image, relevant conditions, interpretation confidence, and recommended follow-up. Link the record to the module or string identifier where those records exist.

A qualified technician may need electrical measurements or a closer inspection before deciding on repair or replacement. Avoid assigning a universal replacement action to a temperature difference without the inspection method and equipment context.

For repeated inspections, keep identifiers stable and record repairs between visits. Otherwise an apparent improvement may be a change in labeling, capture conditions, or palette rather than a resolved defect.

Scaling an inspection program

Plan flight, processing, interpretation, and follow-up capacity together. The number of megawatts captured per hour is not a complete measure of inspection productivity. An anomaly report that nobody can act on adds little operational value.

If automated classification is used, ask for its scope, error definitions, validation conditions, and human-review process. Do not borrow a generic accuracy percentage from unrelated defect categories. Keep uncertain findings separate from confirmed faults and track the outcome of follow-up work.

Regulatory Requirements for Solar Drone Surveys

Legal requirements depend on the jurisdiction and the actual operation. Use the regulator’s guidance for the aircraft, site, people nearby, and intended flight, with local restrictions checked before launch.

United States: FAA Part 107

The FAA commercial-operator guidance identifies Part 107 as a route for work or business operations with small drones weighing less than 55 pounds. Some operations require a different authorization or a waiver, so define the mission before assuming the standard route is sufficient.

The FAA remote-pilot page states that first-time applicants must be at least 16, meet the eligibility conditions, and pass the initial aeronautical knowledge exam. Certificate holders complete online recurrent training every 24 calendar months to maintain knowledge recency. This is not a requirement to retake the initial exam on that schedule.

Keep pilot qualification, aircraft registration, Remote ID compliance, airspace authorization, and operating restrictions as separate checks. Permission from the property owner does not replace airspace authorization, and an airspace authorization does not remove the other rules.

The FAA permits qualifying night and operations-over-people flights under defined conditions; a blanket daylight-only summary is inaccurate. For any proposed departure from ordinary Part 107 conditions, consult the FAA waiver guidance and the issued authorization. Do not promise a fixed approval time or treat a parachute standard as a BVLOS permission.

European Union: EASA categories

EASA’s Open category can include low-risk commercial flights. Determine whether the aircraft class and proposed operation meet the relevant subcategory conditions, including proximity to people and the operating environment. Do not classify every urban solar assignment as Specific without that assessment.

Where the operation falls into the Specific category, EASA describes several authorization routes. An eligible standard scenario can use a declaration with the required confirmation and conditions; other operations may require an operational authorization based on the applicable assessment route.

Check operator registration, pilot competence, geographical zones, identification requirements, insurance, and national conditions with the responsible authority. A commercial label alone does not determine all of these requirements. Nor does a standard-scenario declaration permit a mission outside that scenario’s limits.

For Germany, France, Italy, or Spain, use the national aviation authority’s applicable information alongside the EASA framework. Keep the actual permission or documented operating basis with the mission record rather than relying on a generic country checklist copied between jobs.

United Kingdom: CAA requirements

The CAA guidance on flying drones for work bases requirements on the operation’s risk and category. Its table includes commercial work under Open-category conditions and requires an Operational Authorisation for the Specific category. Paid work is not automatically Specific-category work.

Check the applicable operator registration, remote-pilot competence, identification, and authorization requirements for the exact aircraft and flight. The same CAA page requires at least third-party insurance when flying for a reason other than recreation, sport, or a hobby.

Keep the operator identity, insurance, and any authorization aligned. If an external provider conducts the flight, the contract should identify that operator and the deliverables. Hiring a pilot does not remove the need to define who is responsible for each part of the survey.

Pro Tip: Keep the operating basis with the survey

Store the flight authorization or applicable category assessment, pilot and aircraft records, capture conditions, and deliverable quality report together. A later reviewer should be able to distinguish flight permission from measurement acceptance.

When to Use Drone Surveys vs. Satellite Imagery

Choose imagery based on coverage, recency, resolution, geometry, and the decision being made. Satellite imagery, crewed aerial imagery, and drone imagery are different sources; none is automatically best for every roof.

Compare the evidence available

Existing imagery can support an initial assessment when the roof and surrounding features are visible and recent enough. Check the capture date and data product rather than assuming coverage is current everywhere. A map background can contain imagery from different dates.

A dedicated drone survey can document the site at the survey date and target views missing from existing imagery. It still needs legal access, suitable weather, processing, and quality checks. A new image is not necessarily an accurate model.

Decision factor Existing imagery Dedicated drone capture
Recency Check acquisition date and later site changes Record the actual flight date and conditions
Geometry Assess the supplied model and measurement evidence Specify reconstruction and independent checks
Hidden or obstructed details May require another view or site measurement Can still remain occluded or poorly reconstructed
Turnaround Depends on coverage and product access Includes planning, capture, processing, and review
Cost Depends on licensing and data product Depends on scope, permissions, travel, and deliverables

This is a decision framework, not a set of measured market averages. Ask the data supplier for evidence about the product you will actually use.

A staged survey approach

Use available imagery to identify unanswered questions during preliminary assessment. Send the site team a focused list: an uncertain roof plane, a tree height, an extension missing from the image, or an unclear obstruction. That makes the next survey purposeful.

Commission drone capture where it can answer those questions efficiently and legally. Retain manual or specialist inspection for information that aerial data cannot provide. Keep the preliminary layout distinct from the design that incorporates the accepted survey.

When the new survey changes usable area or shading, revise the design and explain the change to the customer. Do not leave the original capacity or savings claim in the proposal simply because the sales conversation began with an earlier image.

Integrating Drone Data with Solar Design Software

Integration succeeds when the destination workflow preserves the information needed for design. A supported file extension alone does not guarantee correct scale, position, elevation, or interpretation.

File format reference

Deliverable Example documented format Intended role
Orthophoto GeoTIFF Georeferenced image reference
Surface or terrain model GeoTIFF Elevation data, with DSM and DTM kept distinct
Point cloud LAZ, PLY, or CSV in OpenDroneMap outputs Spatial points for compatible downstream workflows
Textured mesh OBJ and associated texture files Surface visualization and compatible modeling workflows

These examples come from the OpenDroneMap output documentation linked above. Other processors and solar platforms have their own supported formats, settings, and limits. Verify both ends of the transfer.

Verify the handoff

Record horizontal and vertical reference systems, units, origin, scale, and any transformation. Check a known dimension and a known elevation after import. Confirm that the imagery and geometry occupy the same location.

Inspect roof planes, ridges, parapets, and shade sources in the destination tool. If the workflow requires tracing or simplifying the model, record which dimensions were measured and which were interpreted. Preserve uncertainty instead of smoothing it away without explanation.

Run the layout and shade analysis only after the geometry is accepted for that purpose. Add the applicable setbacks and installation constraints from their own sources. A map-derived boundary and a regulatory exclusion are different inputs.

Use energy and financial modeling with documented weather, equipment, and tariff assumptions. Better geometry can resolve one source of uncertainty while the other inputs still need review.

Evaluating a software workflow

Ask for a demonstration with a representative dataset and the actual output your team needs. Check file-size limits, processing responsibility, exports, reference-system handling, and what happens when an imported feature is wrong. Include the cost and time of corrections in the evaluation.

SurgePV supports 3D roof modeling, array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. Its published scope should not be expanded into an unverified promise of direct GeoTIFF, LAS, or DSM import. Establish the proposed data handoff during a product discussion.

Keep the survey quality record with the project, even when the customer-facing proposal shows a simplified visual. The designer and installation team need access to the evidence behind the model after the original survey provider has finished the job.

Common Mistakes in Solar Drone Surveys

The following are practical review points, not a claimed ranking from an undocumented project sample. Each concerns the connection between the capture plan and the design decision.

Insufficient useful overlap

Check whether critical features appear clearly from multiple suitable views. Increasing a nominal overlap setting is not a cure for blur, occlusion, or weak texture. Review representative images before leaving the site and plan supplementary capture where needed.

Uncontrolled lighting and exposure

Deep shadow, glare, and inconsistent exposure can obscure detail. Choose conditions and camera settings that suit the scene and processing method. Record limitations where the surface remains difficult rather than assuming a particular time of day always resolves them.

Missing views of vertical features

A downward-only flight can leave roof-edge and obstruction geometry uncertain. Include suitable additional views where the method and operating permissions allow. Use supplementary measurements for features that remain poorly observed.

Treating RTK as an accuracy certificate

RTK supports positioning; it does not prove every reconstructed dimension. Retain positioning-status records and independent checks. If the reference system or control is wrong, a precise-looking coordinate can still be unsuitable for the design.

Accepting processing completion as quality approval

Review checkpoints, local geometry, missing areas, and export alignment. Assign a person to accept the deliverable against the stated criteria. Keep a rejected or provisional model visibly separate from approved design inputs.

Thermal capture without operating context

Record environmental conditions and array state so anomalies can be interpreted. Pair thermal observations with visible evidence and qualified follow-up. Do not turn every warm area into a confirmed equipment failure.

Permissions checked after scheduling

Resolve the operating basis before promising a flight date. Leave time for permissions, site coordination, and weather changes. Keep the customer informed about the deliverable schedule rather than treating launch time as the only milestone.

Buying more equipment than the scope requires

Choose sensors and software from recurring project needs. A more expensive payload can add training, processing, and maintenance work without improving the required deliverable. Compare an outsourced specialist service when demand is uncertain.

Conclusion

A useful solar drone survey produces evidence the designer can rely on: dated imagery, appropriate geometry, independent checks, and clearly stated limitations. Its value comes from answering site questions and carrying the accepted result into design, installation planning, or maintenance.

Start with a representative project and define the required result. Measure the complete workflow, resolve permissions and data handoffs, and compare cost per accepted deliverable before scaling an internal program.

To discuss how the survey will support a project, bring a sample dataset and your design requirements to a SurgePV demo. Establish the supported workflow and review responsibilities before making it part of your standard survey process.

Frequently Asked Questions

How are drones used for solar site surveys?

Drones capture visible imagery, thermal data, or LiDAR measurements for defined survey tasks. Processed outputs can support roof geometry, shading inputs, or inspection, but their suitability depends on the capture method, quality checks, and destination workflow.

What drone is best for a solar site survey?

The best choice depends on the deliverable, site conditions, and legal operating requirements. Compare the exact camera and positioning configuration, processing support, and total cost using a representative site rather than choosing from an unsupported popularity ranking.

How accurate are drone roof measurements?

Accuracy must be demonstrated for the finished survey rather than inferred from the drone specification. Define the required tolerance and assess independent checkpoints and critical roof dimensions; distinguish image resolution, relative geometry, and absolute positioning.

Do solar drone surveys need Specific-category authorization in Europe?

Not automatically, because low-risk commercial flights can fall within the EASA Open category. Assess the actual aircraft and operation; where Specific-category rules apply, use the appropriate declaration or authorization route and its conditions.

How much does a drone solar site survey cost?

The cost depends on site scope, permissions, travel, capture, processing, and the required quality record. Compare dated quotations for equivalent deliverables, or calculate internal fixed and variable costs per accepted survey instead of using a universal price range.

Can drone data be used in solar design software?

Drone data can support solar design when the destination workflow accepts the required inputs correctly. Verify formats, reference systems, scale, elevations, and alignment with a sample dataset before committing to a specific integration.

Where this fits

This article is part of SurgePV's Solar Technology hub, which works through the topic from first principles to the decisions a project team actually has to make.

About the Contributors

Author
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.

Editor
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.

Get Solar Design Tips in Your Inbox

Join 2,000+ solar professionals. One email per week - no spam.

No spam · Unsubscribe anytime

Book Free Demo

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