Aerial mapping mission report app
A mapping deliverable is only as trustworthy as the mission behind it: the flight height and overlap that set the ground sample distance, the ground control that ties the model down, and the independent checkpoints that prove it. Clients rarely ask for the flight log until a design clash makes them doubt the surface. SurveyThanks records the mission on site and renders a deliverable report that states the accuracy and how it was tested.
Built for mapping firms running teams of roughly 3–50 inspectors.
Sample Mapping deliverable report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Mapping deliverable report
Section 2 — Mission summary and accuracy statement
- Project
- Fictional Ridge subdivision, Stage 3
- Flight date
- 9 February 2026
- Coordinate system
- GDA2020 / MGA Zone 56; heights AHD
| Item | Recorded value | Status |
|---|---|---|
| Flight height / GSD | 90 m AGL / 2.4 cm | Status: Pass |
| Forward / side overlap | 80% / 70% | Status: Pass |
| Ground control points | 8 targets, GNSS observed | Status: Pass |
| Independent checkpoints | 5 points, vertical RMSE 0.031 m | Status: Pass |
| Area under tree canopy (north-east) | Surface interpolated, not observed | Status: Limitation |
Fields captured on site
Your firm builds the form in-app, so these are a starting point rather than a fixed schema. Every field is captured on the device, with or without signal, and lands in the mapping deliverable report where your template puts it.
Mission
- Aircraft and sensor
- Remote pilot and operator details
- Flight height and planned GSD
- Forward and side overlap
- Weather and wind at take-off
Ground control
- GCP and checkpoint IDs (from the mark register)
- Target type and photo
- Observation method
Deliverable
- Products supplied
- Accuracy achieved at checkpoints
- Areas of reduced reliability
Standards the report works to
- CASA Part 101Civil Aviation Safety Regulations 1998 — Part 101, Unmanned aircraft and rockets
- The operating rules the mission is planned and flown under, recorded with the pilot and aircraft details.
- ICSM DEM guidelinesICSM Guidelines for Digital Elevation Data
- A common reference for how vertical accuracy of an elevation product is tested and reported.
Load the standards you hold into your reference library and the drafted prose is written against them rather than against a general model.
How the mapping deliverable report gets built
Capture it once, offline
Your firm builds the aerial mapping mission form in-app — 25 field types, nesting repeatable groups, compound AND/OR visibility rules, reusable modules and calculated fields. Field capture works with no signal: jobs, forms, photos, notes and audio all queue in an idempotent outbox that only clears once the server confirms receipt.
Link it to your marks, stations and monitoring points
Enter marks, stations and monitoring points once, as a register. Every one of your observations, rounds and movement readings then points at a stored row rather than a name somebody typed — and the links survive a disconnected device.
Render your own template
The mapping deliverable report renders into the Word template you already use — your letterhead, your section order, your clause library — with conditionals, loops over repeats, composable sub-templates and photo grids.
Reviewed before it leaves
You write the review framework: a checklist of what a mapping deliverable report must contain, plus the prose standards you would mark a junior against. Link it to a report template and it runs every time that template renders. Each finding comes back graded info, minor or major, quoting the sentence at fault, and a person accepts or dismisses every one.
Because the structured submission behind the report is held too, the review is a comparison rather than a proofread: The movement summary reports 4 mm at PM3; the round’s readings put it at 11 mm.
Checks a surveying framework usually carries
- Control, datum and epoch are stated for every deliverable
- Quoted tolerances match the project specification being reported against
- Every mark named in the text exists in the register
- Assumptions and sources of error are recorded rather than assumed
Questions
- Can checkpoints and control points be kept separate in the report?
- Yes. Each target is a row in the mark register with a role, so the report can list control used in processing apart from the checkpoints used to test it.
- Where do the orthomosaic and surface files go?
- They stay in your processing and delivery workflow. The report states what was supplied and to what accuracy; SurveyThanks does not host or process imagery.
- Can the pilot record the pre-flight details on a tablet in the field?
- Yes, offline. The mission form, target photos and notes queue on the device until it is back in coverage.
What this is not
Worth knowing before you book a demo, so neither of us wastes the half hour.
- Not field-service dispatch. No timesheets, no parts, no inventory. Scheduling exists to get an inspector to a site.
- No signature capture. If your deliverable has to carry a signed sign-off on the artefact itself, this is not the tool yet.
- Field capture is what works offline — jobs, forms, photos, notes and audio. Reports, chat, scheduling and the inbox need a connection.
- No client portal. Reports go out as a file or a password-protected link.
Other surveying work we cover
- Bathymetric survey runsBathymetry report
- Boundary survey field notesSurvey plan evidence
- Construction set-out recordsSet-out verification report
- Contour and detail surveysDetail survey report
- Deformation monitoring roundsMovement monitoring report
- GPR survey recordsGPR survey report
- Laser scan site capturesPoint cloud delivery report
- Mine survey pickupsMine survey report
Other disciplines
Rebuild your mapping deliverable report in SurveyThanks
Bring the Word template you already send clients. If you are coming off another field-forms tool, a filled report can be uploaded, read field by field, and re-rendered into your template.