Preparing the published article.
Aerial Survey Briefings: What to Agree Before the Flight
A pre-flight checklist for agreeing survey area, altitude, overlap, flight lines, and deliverable formats with a survey operator.
Agree the Area, the Resolution and the Boundaries in Writing
An aerial survey begins at the desk, not at the take-off point. Before the flight, hold one short briefing with the operator and leave it with a written scope covering the survey area, the desired resolution, the overlap, the number of flight lines, the environmental limits, and the deliverable format. Every number that stays vague at this stage becomes a dispute after the images are processed, and reprocessing rarely recovers detail the flight did not capture.
- Deliver a boundary file, not a verbal description: draw the survey area as a polygon in a geographic format and confirm the coordinate reference system.
- Decide the treatment of the buffer zone and of neighbouring properties, including whether the boundary follows a fence line, a road, or a crop edge.
- State the ground sample distance you need and the crop or asset you need it to resolve.
- Name the flight altitude in metres above ground, and the acceptable deviation, so that a re-flight is judged against an agreed figure.
- Write down the environmental limits: maximum wind speed, minimum visibility, cloud shadow tolerance, and the latest time of day that still gives usable illumination for the intended product.
Altitude determines the ground sample distance, so it belongs in the scope as a figure rather than in a sentence such as high resolution. Ask for the planned altitude and the resulting resolution per pixel, and record who measured the take-off elevation, because pressure altitude and height above ground are not the same quantity.
Fix Overlap, Flight Lines and Metadata Before Wheels Up
Overlap is the part of the plan that most affects whether the imagery can be processed at all. Ask for the forward overlap and the side overlap as percentages, and ask what happens to the effective overlap over sloping ground, because relief changes it. If the operator cannot give both figures, ask what software settings govern the flight and record those settings.
- Flight-line spacing and the total line length to be flown.
- Expected image count, and the planned ground speed for each line.
- Battery and endurance per sortie, with the intended landing point, so the area per sortie and the number of sorties are known before the day.
- Whether ground control points are placed, and, if not, how positional accuracy will be described in the deliverable.
- Which correction or positioning service the aircraft uses, recorded without assuming a stated accuracy level.
One distinction belongs in the scope: overlap for a visual map and for photogrammetric measurement are different requirements, so ask which is planned. Second, imagery may be flown across multiple days, so record the date, start and end time, and conditions of every sortie and ask for delivery per sortie rather than merged without notice.
Name the Deliverable, Its Format and Its Acceptance Checks
Specify what arrives and in what form: each file type, its coordinate reference system, and whether georeferencing is embedded or delivered separately. Decide whether you want raw images, a stitched map, a point cloud, or a derived index layer, and say which of them you can open and use in your own software. An unopenable deliverable is not a deliverable.
| Item to specify | Question to ask the operator |
|---|---|
| File formats and coordinate system | Which projection and unit will be used, and does the file carry georeferencing? |
| Stated resolution | What ground sample distance will the final product have, measured how? |
| Positional accuracy | What accuracy statement will accompany the file, and how was it derived? |
| Coverage gaps | How will unflown or unusable areas be marked in the delivery? |
| Delivery method and timing | Where will the files be placed, and how soon after the flight? |
Then plan the acceptance check. Count the images against the flight report, open the map at full resolution over three known features, and confirm the stated resolution against the file's metadata. Ask what the deliverable cannot support, because the operator usually knows its useful limits in advance. Note that aircraft operation is regulated, so confirm the operator's arrangements with the applicable aviation authority, permissions for the specific site, and site access rules in the same written scope. Finally, write the decision rule: a map is not a finding until someone states which measurement it supports, on which block, and what evidence would contradict it.
Photo credits: the images in this article are licensed reference photographs of the relevant robot class, credited with author and licence in each caption; they are not photographs of the specific equipment discussed. Licence and author details are recorded with each image.