From SD Card to Client Report: Managing Thermal Drone Data

A thermal inspection earns its fee at the report, not the landing. The difference between a folder of images and a paid deliverable is workflow: shooting radiometric where it counts, naming and backing up in the field, and reporting findings a non-thermographer can act on.

• 1 folderPer site per day
• 2 copiesBefore the card is wiped
• 1 yearCommon retention default
• RadiometricWhat cannot be added later

Capture Decisions You Cannot Undo Later

Record radiometric stills for anything you may need to measure afterwards. Per-pixel temperature data lets you re-analyse with corrected emissivity in post-processing, re-threshold an isotherm, or answer a question the client asks three weeks later. Plain video is fine for context and client walk-throughs and useless for measurement.

Capture a visible-channel frame with every thermal finding. A thermal image alone shows a hot region; paired with a visible photograph it shows a hot component, which is what a maintenance manager can act on. Multi-sensor payloads that shoot both simultaneously halve this workload and guarantee the two frames match — see synchronised capture.

And confirm your payload is a thermometry configuration before any of this matters. Radiometry depends on factory calibration and cannot be added afterwards — radiometric vs non-radiometric covers the one-way decision.

Field Discipline

Three rules, all executed before leaving the vehicle, all cheap compared with what they prevent.

1. One folder per site per day. Not per flight, not per week — the unit that matches how the client thinks about the job.
2. Rename or log card contents before leaving the vehicle, while you still remember which flight was which.
3. Two copies before the card is wiped. One is not a backup; it is a single point of failure with a false sense of security.
4. Tag coordinates from the aircraft log or payload OSD against each image number while memory is fresh.
5. Note the conditions — ambient temperature, wind, sky state, load where relevant — in the same log.

A finding without a location is a reflight, and that is the failure this discipline exists to prevent. On a site with repeating identical bays or panels, an image showing a clear fault at an unknown location is worth almost nothing, and the cost of returning dwarfs the two minutes tagging would have taken. A rangefinder-equipped payload makes this easier — why an LRF belongs on your payload.

The conditions note matters for a subtler reason: it bounds what the survey could see. A roof survey flown in 20 km/h wind or an envelope survey at 6 °C delta had limited diagnostic power, and recording that protects you as much as it informs the client.

Reports That Get You Rehired

Lead with a findings table: location, component, severity, thermal image beside visible image, recommended action. Everything else in the document is supporting material.

Report element	Why it belongs	What happens without it
Findings table up front	The client reads this and may read nothing else	Findings get lost in narrative
Location per finding	Someone has to walk to it	Reflight, or the finding is ignored
Thermal beside visible	Identifies the component, not just the heat	Client cannot tell what is hot
Severity classification	Drives maintenance prioritisation	Client has to grade it themselves
Recommended action	Turns a finding into a work order	Report is information, not a service
Survey conditions	Bounds what the survey could see	Disputes about what was missed
Archived raw radiometric	Settles disputes with data	Disputes settled by memory

Note the conditions because they bound what the survey could see — the honesty also protects you. A report stating the delta-T, wind and sky at time of survey is a report whose limitations are explicit, and that is a much stronger position than one implying complete coverage. What a thermal inspection report should contain covers the full structure, and thermography training covers the grading discipline behind severity.

Archive, and Then Compare

Keep raw radiometric files archived. Disputes are settled by data, not memory, and a client questioning a finding two years later is asking a question only the original file can answer.

The archive also enables the thing that turns inspection into a service: comparison. A finding that is new or growing outranks one that has been stable for three surveys, and only an archive makes that judgement possible. This is what converts a one-off job into a monitoring contract — the complete guide to drone inspections covers the workflow.

Storage is cheap relative to a reflight and trivial relative to a dispute. Radiometric stills are not large by modern standards, and the retention decision should be driven by contract terms rather than by disk cost.

Where Data Workflows Actually Break

Three failures recur, and none of them is technical.

Deferring the naming until the office. By then the flights have blurred together, and the person who flew them is on another job. The two minutes in the vehicle are worth an hour later and produce a better result.

Shooting video where stills were needed. Video is compelling in a walk-through and cannot be measured. Operators default to it because it feels thorough, and the measurement request arrives afterwards.

One copy. Cards fail, laptops are stolen, and the flight cannot be repeated because the conditions have changed. Two copies before the card is wiped is a rule with no exceptions worth making.

Related reading

• Radiometric Temperature Measurement on UAV Payloads
• What a Thermal Inspection Report Should Contain
• Radiometric vs Non-Radiometric Thermal
• Drone Thermography Training and Certification
• Isotherms and Temperature Alarms
• The Complete Guide to Drone Inspections
• PiP, Fusion and Split View
• Thermal Drones, Privacy and Regulation
• MV-2P — 640×512 thermal at 130 g
• OP-90A — zoom, thermal and ranging
• OP-125A — flagship EO/IR pod
• Solar Farm Thermal Inspection

FAQ

How long should raw data be retained?

Contract-dependent, with a year a common default for inspection work and longer where findings feed ongoing maintenance programmes. Two considerations push it longer: disputes tend to surface well after the survey, and comparison across surveys is what turns inspection into a monitoring service. Storage cost is trivial next to a reflight, so let the contract and the trending value set the period rather than disk space.

JPEG or RAW for thermal?

Radiometric JPEG — thermal measurement data embedded in the file — is the practical standard on UAV payloads. Confirm your unit embeds measurement data rather than saving a plain rendered image that merely looks thermal. The distinction is invisible in a file browser and decisive in post-processing: one can be re-analysed with corrected emissivity, the other cannot be measured at all.

What is the single most costly data mistake?

A finding without a location. On a site with repeating bays, panels or spans, a clear thermal image of a fault at an unknown position is close to worthless, and returning to find it costs far more than the two minutes tagging would have taken. Tag coordinates against image numbers before leaving the vehicle, while you still remember which flight was which.

Questions about the technology? Talk to our engineers — we reply within 2 business days.