What to Look for When Reviewing Aerial Mapping Deliverables

Why a Deliverables Checklist Matters

Every project that relies on drone-captured data ends with a handover: the team receives a set of files, reports and visualisations that are supposed to answer the questions the survey was meant to solve. The gap between what was asked for and what is delivered can cost time, rework and missed deadlines. A simple checklist keeps the review process systematic, so nothing slips through.

This article focuses on the things project teams should inspect when they receive aerial mapping outputs. Whether you work in construction, environmental monitoring, agriculture or infrastructure inspection, the same core checks apply. The list below is built around the reality that a modern project team often uses a point cloud viewer to examine the data before accepting it. The viewer itself is a tool; what matters is what you look for inside it.

Check the Point Cloud Density and Coverage

The first thing to verify is whether the point cloud actually covers the area of interest. It sounds obvious, but gaps happen. A flight plan might have missed a corner of the site, or tree canopy and buildings may have created shadow areas where the ground is poorly represented.

Open the data in your point cloud viewer and pan across the full extent. Look for empty patches or areas where points are sparse. For most survey-grade work, you want a minimum density that matches the required ground sampling distance. If the deliverable includes a separate quality report, compare the reported point density against what was specified in the project scope. If no report is included, measure a few sample areas yourself using the viewer's statistics tool.

Also check for uniformity. A dense cloud in one part of the site and a thin one elsewhere suggests inconsistent flight speed or altitude. That can affect the accuracy of later measurements and models.

Verify Georeferencing and Coordinate System

A point cloud that looks correct in isolation may be useless if it is misaligned with the real world. Confirm that the data uses the coordinate system and datum that was agreed in the project plan. The point cloud viewer should display this information in its metadata panel.

Even if the coordinate system is correct, check the actual positional accuracy. Place a few known control points or visible features - a road intersection, a building corner, a survey marker - and compare their coordinates in the cloud to a trusted reference. Common tolerances are within a few centimetres for engineering surveys and within half a metre for less demanding applications. If the data came from a nationwide capture service, the provider should supply a validation report showing root-mean-square error figures. National Drone Services, for example, typically includes such documentation with its deliverables.

Inspect the Classification and Noise Level

Raw point clouds contain everything the sensor saw: ground, vegetation, buildings, vehicles, power lines, birds, and sometimes noise from atmospheric scatter or sensor artefacts. A well-processed deliverable separates these classes so you can work with the surfaces that matter.

In your point cloud viewer, toggle the classification layer if it exists. Check whether ground points have been correctly identified under trees and near building edges. Look for stray points that should have been filtered out, such as low-flying birds or dust particles that registered as returns. Excessive noise can distort volume calculations and make it hard to see fine ground detail.

If the deliverable includes a digital terrain model (DTM) and a digital surface model (DSM), overlay them in the viewer. The DTM should show only the bare ground, while the DSM includes everything above it. Any vegetation or structures visible in the DTM suggest the filtering was too aggressive or that the classification missed those features.

Check the Colourisation and Image Alignment

Many point cloud viewers support colourised clouds, where each point carries an RGB value from the drone's camera. This helps with visual interpretation but introduces its own failure modes. Look for colour seams along flight strip boundaries, where the lighting or white balance changed between passes. A good deliverable blends the strips so the colour transition is smooth.

Also verify that the colour values align with the geometry. A point that belongs to a red roof should show a red colour, not green or blue. Misalignment usually means the camera calibration was off or the timing between the laser pulse and the image capture was not synchronised properly. Zoom into a few high-contrast edges - a building roofline against a lawn, for instance - and check that the colour boundary matches the geometric edge.

Assess the Deliverable Format and File Structure

Project teams often receive data in multiple formats: LAS/LAZ for point clouds, GeoTIFF for orthophotos, and DXF or SHP for vector features. The deliverable should include a readme or metadata file that lists every file, its format, its coordinate reference system, and the software version used to generate it.

Open a few files in your point cloud viewer and in the other tools your team uses. If a file fails to load or displays incorrectly, the problem may be a corrupt file or an unsupported format. Check that the file sizes match what you would expect for the stated point count and area. A file that is suspiciously small may have been cropped or subsampled without notice.

Also confirm that the delivered dataset includes any ancillary files you need: the flight log, the processing report, the calibration certificate for the sensor, and the ground control point coordinates. Without those, you cannot independently verify the quality of the data. If you ordered capture through a platform like nationaldroneservices.net, those supporting files are usually included in the download package.

Test the Data in Your Own Workflow

The ultimate check is whether the deliverable works for its intended purpose. Load the point cloud into your project's software stack and run a few sample tasks. If the goal is a volume calculation, compute the volume of a known stockpile or excavation and compare it against a manual measurement or a previous survey. If the deliverable is for a building model, extract a cross-section at a critical location and check the dimensions.

This step often reveals issues that were invisible during a visual inspection. A point cloud that looks clean may still have systematic errors in the z-axis that only show up when you try to calculate a slope or a cut-and-fill quantity. The point cloud viewer can help here too, by letting you measure distances, angles, and elevations directly in the 3D space.

Document and Communicate Findings

Once your team has gone through the checklist, write a brief review report. List what passed, what failed, and what needs clarification. Send it to the data provider or the capture service while the project timeline still allows corrections. A structured checklist makes this conversation factual rather than subjective.

If you are working with a provider like National Drone Services, the review process is usually part of the service agreement. Their deliverables are designed to meet common industry standards, but every project has unique requirements. A clear, documented review helps both sides close the loop quickly.

The point cloud viewer is a powerful tool, but it is only as useful as the data it displays. By running through these checks systematically, project teams can avoid the costly surprise of discovering a data problem halfway through a design or analysis phase. A few minutes of inspection at the start saves hours of rework later.

National Drone Services on social media Facebook