A drone survey is only useful when the handover helps someone make the next decision. A colourful map, a cloud-viewer link or a folder of images may look complete, but none of those items alone confirms what land was covered, when it was observed, how it was processed or what the team should inspect on the ground.
Before accepting an agricultural drone survey, ask the provider to supply a short, readable delivery record alongside the imagery and maps. The record should allow the grower, farm manager, agronomist or GIS user to answer five questions:
- What area and date does this material represent?
- What files have been supplied, and which ones are intended for use?
- How was the map related to real field locations?
- What processing or interpretation was applied?
- What remains uncertain, and who will follow up?
The appropriate answer will vary with the crop, sensor, contract, software and decision involved. The aim is not to require every possible product from every provider. It is to ensure that the delivered material can be checked, handed on and used without assumptions being lost.
Start with the decision the survey is meant to support
Ask first what question the survey was commissioned to answer. This should shape both the flight plan and the deliverables requested afterwards.
For example, the task may be to:
- identify areas that should be prioritised for crop scouting;
- review apparent differences in crop cover or canopy condition;
- inspect drainage patterns after a weather event;
- compare field appearance between agreed survey dates; or
- provide a current visual record of a block before another operation.
These are different jobs. A general overview image may be adequate for one discussion, while a field team comparing locations with historical boundaries may need a geographically referenced map and compatible spatial files.
The University of Florida IFAS notes that UAS collection settings and post-processing outputs should be matched to the agricultural application and the sensor used. Its guidance describes possible products including orthomosaics, 3D maps and plant-health or stress-status maps such as NDVI maps. That does not mean every survey needs every product. It means the requested output should be stated before delivery is judged complete.
As a practical ACA recommendation, write the intended use into the purchase order, work brief or email confirmation. Include the field or block concerned, the person who will receive the files and the expected next action. A request such as “drone maps for the farm” leaves too much room for different interpretations. “A map for the scouting team to identify zones for inspection, with field boundaries and a printable overview” is more workable.
Confirm coverage, survey date and field identification
The first quality check is simple: can the buyer tell exactly what was surveyed?
Request a delivery note that identifies the surveyed area in a way your team can recognise. This may include farm names, block names, internal field codes, boundary files or a labelled map. The International Rice Research Institute’s Manual for UAV Data Collection treats identification of the study area and its geographical coordinates as part of collection planning. For a service handover, the equivalent need is clear identification of what the results represent.
Ask the provider to record:
| Item to confirm | Why it matters | Practical check |
|---|---|---|
| Field, block or plot identifier | Prevents a file being assigned to the wrong area | Compare with the farm’s own naming system and boundaries |
| Survey date | Establishes the observation period | Check it against field operations and the question being investigated |
| Approximate collection window | Helps interpret conditions where timing matters | Confirm whether all blocks were flown in one period or across multiple passes |
| Covered and excluded areas | Reveals gaps before decisions are made | Look for unflown edges, inaccessible sections or omitted blocks |
| Repeat flights or passes | Avoids treating separate collections as one observation | Ask which files belong to each pass |
| File naming convention | Makes handover and retrieval easier | Ensure names can be understood without relying on the provider’s memory |
A complete-looking image can still omit a corner, a separate block or an area affected by flight conditions. Do not infer full coverage from a viewer thumbnail. Compare the delivered boundary or map footprint against the area originally requested.
Consistent and complete collection records are a central concern in the University of Florida IFAS best-practices guidance for efficient aerial surveying. In practice, consistency also helps when a different member of staff needs to review the survey later. A field code, date and product type in a filename may seem basic, but it reduces avoidable uncertainty during a busy season.
File names and internal farm codes are not universal technical standards. They are operating controls. Agree them with the people who will receive, store and use the material.
Request image and map outputs in usable forms
A survey handover may include several kinds of files. They should not be treated as interchangeable.
Source imagery consists of the individual images captured during the flight. It may be useful for audit, reprocessing or close visual inspection, but it can be numerous and may not align neatly with a farm map.
Processed products may include a stitched map, an orthomosaic, a digital surface model, a colour map or a vegetation-index map. The Texas A&M AgriLife Extension UAS manual describes workflows that can generate orthomosaics and digital surface models, delineate plot boundaries, export plant features in spreadsheets and create colour maps in GIS software.
A summary export might be a PDF, image, spreadsheet or brief report designed for quick review. These are often useful for meetings, but may not replace the underlying spatial data if your team needs to overlay field boundaries, sample points or previous observations.
Ask the provider to include a simple file inventory. For each delivered item, the inventory should state:
- the filename and folder location;
- the product type;
- the field or block it covers;
- whether it is source imagery, a processed product or a summary;
- the software, platform or viewer expected to open it; and
- whether a downloadable copy is available.
Do not prescribe a single file extension unless your receiving system requires one. A format that works for a consultant’s GIS workflow may not be useful for a farm office that needs a simple map, and a cloud viewer may be convenient without being a long-term archive.
If the provider supplies only a web link, ask what happens if the link expires, the account changes or a team member needs to view the material offline. The buyer does not necessarily need every processing file, but should know what is retained, what is downloadable and who controls access.
Ask how the map was located and processed
An aerial image can be visually informative without being suitable for measuring, overlaying or navigating to a field location. This distinction matters when a map will be compared with boundaries, drainage plans, sampling points or another survey.
The Ohio State University fact sheet on remote sensing in precision agriculture explains that aerial images can be geometrically distorted by factors including platform position and topographic relief. Orthorectification is used to improve correspondence between the image and ground locations before interpretation and analysis.
For the buyer, the key request is not a technical promise of accuracy. It is a plain-language processing note. Ask the provider:
- Was the delivered map processed as an orthomosaic or another image product?
- How was it geographically referenced?
- Were field control points, onboard positioning information or another method used?
- Were boundaries supplied by the client, created during processing or only shown as a visual overlay?
- Were any corrections, clipping, resampling or smoothing steps applied?
- Are there known alignment issues, edge effects or areas where the map should not be used for location-specific work?
Texas A&M’s manual distinguishes direct and indirect georeferencing within its agricultural UAS workflow. That is useful context for asking how a map was located, but it does not establish the positional quality of a particular commercial survey.
Avoid accepting phrases such as “high accuracy” or “survey grade” without project-specific records and a clear definition of what those phrases mean. A provider may have sound methods, but the buyer still needs to know whether the delivered output is suitable for visual review, general scouting, boundary comparison or another stated purpose.
Read vegetation and colour maps as screening tools
Vegetation-index and colour maps can be useful for directing attention. They can show patterns worth checking, particularly when a large area would otherwise be difficult to inspect evenly.
However, a visible difference is not a diagnosis. A darker or lighter area may relate to plant cover, soil background, moisture, crop stage, shadows, sensor settings, processing choices or other factors. It does not by itself prove nutrient deficiency, disease, pest damage, water stress or a need for a particular input.
IFAS guidance includes plant-health and stress-status maps, including NDVI, among the possible outputs from UAV data processing. The Wheat CAP workflow also notes that multispectral work may involve radiometric calibration when pixel values are used to estimate spectral reflectance and vegetation indices. These references explain why processing details matter; they do not turn every colour gradient into an agronomic conclusion.
ACA’s practical approach is to treat a flagged zone as a scouting question. The handover should identify what the map is intended to show and what field observation is needed next.
For example:
“Area B has a different index pattern from surrounding crop. Inspect plant stand, soil condition, water movement, visible symptoms and recent field operations before assigning a cause.”
This wording preserves the map’s value while keeping responsibility for agronomic interpretation where it belongs: with field observations, relevant records and qualified local advice where needed.
Document limitations and assign the follow-up
A useful handover includes what did not work, not only the finished images. Ask the provider to note known gaps and constraints, such as excluded areas, incomplete overlap, image-quality issues, weather or visibility conditions where recorded, processing failures or portions that could not be converted into the planned output.
The IRRI manual discusses site and risk assessment as part of UAV collection planning. The details in that manual are not a China-specific operating rule, but the underlying handover lesson is broadly useful: collection conditions and site constraints can affect what a dataset can represent.
Use a short close-out checklist before the survey is accepted:
- Surveyed fields and excluded areas are identified.
- Survey date and collection window are recorded.
- Files are listed, understandable and accessible to the intended recipients.
- Source imagery, processed maps and summary outputs are distinguished.
- The provider has described georeferencing and processing in plain language.
- Known gaps, limitations and interpretation cautions are recorded.
- A named person is responsible for field checking any flagged areas.
- A review date is set for comparing scouting findings with the survey output.
Ownership and follow-up are often more valuable than another map layer. Without an assigned person and a deadline, a potentially useful observation can remain in a folder until the operating window has passed.
The international materials cited here support general concepts of collection planning, processing and repeatable delivery. They do not establish Chinese aviation requirements, mapping standards, data rules or crop-management instructions. If a survey will be used for regulated activity, land records, contractual measurement or a high-consequence agronomic decision, obtain the relevant local and project-specific guidance separately.
Frequently asked questions
Should I ask for the original drone images as well as the finished map?
Usually, ask what source imagery exists, whether it will be retained and whether you can obtain it if reprocessing is needed. You may not need to receive every original image if the finished products meet the agreed use and your team has limited storage or software. But the contract should make clear whether the provider keeps the source files, for how long and under what access arrangement.
What is an orthomosaic, and when does a grower need one?
An orthomosaic is a processed image product assembled from multiple images and corrected to improve its relationship to ground location. It is generally more useful than a set of separate photos when the team needs to view a whole field, compare patterns with boundaries or direct scouting to a mapped area. A simple overview image may be sufficient when the task is only general visual discussion.
Can a vegetation-index map tell me what is causing crop stress?
No. It can help identify patterns or zones that deserve attention, but it does not establish the cause by itself. Check the area in the field and compare it with crop stage, soil conditions, irrigation or drainage records, recent operations and other relevant observations.
What should I do if part of a field is missing from the drone survey?
Record the missing area before accepting the survey as complete. Ask why it was omitted, whether another flight or processing step is possible and whether the gap affects the intended decision. If it cannot be recovered, label the limitation clearly so that no one assumes the map represents the full field.
A bounded next step is to create a one-page acceptance form for your farm or procurement team. Use it on the next drone-survey handover, then revise it after the first review meeting. The form should reflect your own field names, receiving software, archive location and scouting responsibilities rather than copying a generic technical checklist.
Source and further reading
ACA’s practical examples and working checklists are independent editorial analysis. The linked source provides the underlying reference; it does not endorse this article.
