A drone flight can finish without obvious problems and still leave the office with unanswered questions. Which coordinates were used for the base? Was the antenna height measured to the correct reference point? Were the points labeled as checkpoints kept out of the adjustment?
Those questions belong in the field plan. RTK and PPK help establish the position of the capture system. Ground control helps constrain the mapping solution. Independent checkpoints help evaluate the resulting deliverable. Each has a different job, and the crew needs to know which records support each one.
Use the following checklist to connect project requirements, field setup, and the office handoff. It is a planning framework; the responsible surveyor should adapt it to the site, equipment, contract, and applicable requirements.
Start with what the client will accept: an orthomosaic, a point cloud, a topographic surface, quantities, or some combination. Identify the required coverage, coordinate reference system, horizontal and vertical units, datum, and accuracy assessment method. Record any required reference epoch and geoid model.
The verification plan must fit that deliverable. A visible image target and a suitable surface for checking LiDAR elevations serve different purposes. Decide what will be checked, how the reference observations will be established, and who will review the results.
This discussion also matters when using a drone mapping service. Agree on the control, checking, and delivery responsibilities before anyone mobilizes.
RTK applies positioning corrections during the operation. Its field setup needs a suitable correction source and a working communications path. Confirm what the equipment records about correction status and interruptions; do not treat a fixed indicator as an accuracy certificate for the completed map or surface.
PPK processes recorded positioning observations afterward. As PIX4D's RTK and PPK guidance explains, the workflow depends on the required rover and reference data. Verify the actual raw observations, timing or exposure-event records, and reference coverage your equipment and processing method require. A plan to use PPK cannot replace data that were never recorded.
A ground control point is used to constrain or adjust the mapping solution. A checkpoint is withheld from that process so it can provide an independent comparison. The distinction follows how the point is used, rather than what the target looks like. Make those roles explicit in both the field list and the processing instructions.
For a local base, document the occupied point, coordinate source, reference system, and antenna setup. Record the receiver and antenna identification, antenna reference point, height measurement method, units, and observation times. Keep a photograph or clear setup note when it helps another person reconstruct the occupation.
An error in the reference position or antenna information can affect the work tied to it. NGS's OPUS guidance warns that selecting the wrong antenna or entering an incorrect antenna reference point height can produce errors the service may not detect. Check those entries against the actual setup before the work progresses.
When using CORS observations, confirm the station identity, required observation interval, and overlap with the mission. Obtain the coordinate information appropriate to the project and processing method. The NGS CORS data page cautions that coordinates in RINEX headers and station logs are approximate and directs users to published coordinate and velocity information. Save the coordinate source and the frame and epoch information needed to interpret it.
If the reference is uncertain, resolve it or document a defensible recovery plan with the responsible surveyor. Do not leave the processor to infer which coordinates were intended.
Create one point list with unique IDs, descriptions, surveyed coordinates, units, observation records, and a clear role for every point. Distinguish existing control, ground control used in the solution, and independent checkpoints. Keep any points that were rejected or reobserved traceable.
For imagery, choose stable locations where a target's center can be identified in both the ground observation and the planned images. PIX4D's ground control guidance emphasizes visibility and distribution. Consider the full project extent, elevation changes, obstructions, and the image coverage each target will receive. Avoid a layout that checks only the easiest corner of the site.
For LiDAR, plan check locations and surface conditions that suit the intended assessment. The USGS Lidar Base Specification separates calibration or control from independent accuracy testing. Its specific requirements apply within its own scope; use the project's governing specification rather than importing a universal checkpoint count into every job.
If a point is later used to improve the solution, update its role. It no longer serves as an independent test of that adjustment. Keep additional independent checks available where the assessment requires them.
Build the packing and setup list around the selected workflow. Alongside the aircraft and sensor, account for the base or correction service, rover, targets, power, storage, and required logging. The broader drone survey equipment checklist provides useful inventory context; the project plan determines what this crew needs.
Before production capture, confirm that the required observation files are being written, the reference recording period will cover the mission, and the planned targets or check areas remain usable. Check equipment time settings and the timing records required by the processing workflow.
Agree on the response to a correction outage, logging failure, moved target, or inaccessible checkpoint. The decision might involve collecting additional observations, repeating an affected portion, or changing the plan. Record what happened and where; an unexplained status change is poor handoff information.
Do a field completeness check while recovery is still practical. Confirm the required mission files exist, the base or reference observations cover the work, point IDs match the field list, and setup notes identify the reference and antenna information. Review coverage and target visibility where the available field tools allow it.
Confirm file sizes and recording periods rather than relying only on a successful-flight message. Preserve the original observations and a verified backup. Separate completeness review from final accuracy acceptance: the presence of all expected files does not prove that the finished deliverable meets its requirements.
If something remains unresolved, identify the affected area or data and the next action before the crew disperses. Clear exceptions are easier to investigate than a folder that simply says final.
Deliver the mission and reference observations with the point list, coordinate documentation, antenna records, and a short exceptions log. State which points may constrain the solution and which must remain independent. Preserve those distinctions through any processing revisions.
The workflow may pass through GNSS or mapping software before reaching a receiving CAD or GIS environment. The important handoff is the documented relationship between the observations, reference system, processing decisions, and delivered files. Include that relationship when comparing data management workflows.
For imagery, continue the review with the orthomosaic acceptance and CAD/GIS handoff checklist. Ground setup records and final deliverable checks should tell a consistent story.
A clear checklist helps the crew and office agree on what is complete and what still needs a decision. Talk with SmartDrone about your next survey project, including its control plan, required outputs, and field-to-office responsibilities.