How dense does drone LiDAR need to be for automated linework?

Search "lidar point density" and you get specs written for terrain mapping. USGS base specifications, ASPRS density guidance, a 2014 blog post on point spacing. All of it answers one question: how many points do I need to build a good ground model?

That is the wrong question for most drone survey work today. Nobody flies a corridor or a site just for a DTM anymore. They fly it to get linework: edge of pavement, curb, striping, crown, poles, signs, building footprints. And the density that makes a fine DTM is nowhere near the density that lets software draft a curb line for you.

This post is the guidance we give customers when they ask "what should I fly at so your automation actually works?" One framing note first. Density is the third of three things that decide how much automation can pull from a dataset. Calibrated imagery aligned to the cloud is first, coverage and overlap second, density third. Density is the one this post is about because it is the one flight planning controls most directly.

For automated feature extraction on Mach9, we recommend a floor of 300 to 400 points per square meter. Above roughly 1,000 points per square meter, small features and edges get noticeably cleaner. Below 300, the platform still processes the data, but you should expect terrain and large features only, with the linework drawn by hand.

Here is how that plays out feature by feature, based on what we see on drone datasets uploaded to the platform:

Two caveats on that table. Anything with a vertical face (sign faces, pole-mounted equipment) comes through at lower density from the air than from the ground no matter how you fly, so plan on oblique passes or ground capture if the deliverable depends on them. And the aerial models are still expanding, so a feature that automates on mobile data today may not be on for aerial yet.

The pattern is simple. Terrain is forgiving because it is big. Linework is not, because a curb is a 6-inch break in a surface and the software needs several points across that break to find it.

These two get mixed up constantly, so it is worth separating them.

Accuracy is how close each point is to where it really is. It comes from your GNSS and IMU, your control, your PPK or RTK workflow, and your calibration. A well-run drone LiDAR flight can be accurate to a few centimeters at 50 points per square meter.

Density is how many of those accurate points land on each square meter of ground. It comes from your altitude, your speed, your sensor's pulse rate, and your overlap.

An accurate but sparse cloud is great for volumes and terrain. It is still a bad input for automated linework, because the algorithm cannot draft an edge it cannot see. Most "the automation missed the curb" complaints we see trace back to density, not accuracy.

Density scales with time over target. Fly lower, fly slower, overlap more. Every sensor has its own numbers, but the direction is always the same.

One customer example. Welch Comer, a civil engineering and surveying firm in Idaho, flies a GeoCue TrueView 540 at 150 to 200 feet above ground and about 5 meters per second on the projects they bring into Mach9. That is deliberately low and slow for a sensor of that class, and it is why their datasets come in dense enough for automated edge of pavement, striping and crown, with the extraction output denser and more consistent than what they drafted by hand.

A few practical notes from their workflow and others like it:

• Plan for the smallest feature you need. If the deliverable includes curb and gutter, fly for the curb. Terrain will take care of itself.
• Cross-flight the corridor and keep overlap. Edges of the swath are the sparsest part of any pass, and a single flight direction biases both the cloud and the ortho. Perpendicular strips fix both. For aerial LiDAR, 30 to 50 percent side overlap is a reasonable baseline.
• Add an oblique pass if you need vertical features. Pure nadir flying puts very few points on sign faces, pole hardware and building walls. A separate oblique mission is the cheapest way to get them.
• Slow down at intersections. Turn arrows, crosswalks and curb ramps are the densest concentration of small features on a roadway job.
• Don't fly high to save battery on a linework job. You will spend the saved flight time, several times over, drawing lines in the office.

Density gets you geometry. It does not tell the software what it is looking at. Object recognition, the part that labels a pole as a pole or reads a sign face, needs imagery.

For drone work, that means an orthophoto. Upload a georeferenced GeoTIFF in the same coordinate system as the LAS or LAZ tiles and the platform can use it for building edges and for paint and pavement boundaries that pure geometry cannot separate from the ground. Mobile mapping gets the same benefit from calibrated panoramic imagery (E57 is the cleanest way to deliver it).

If you have to choose between flying denser and flying with a good camera, the answer depends on the deliverable. Terrain and edges: density. Assets and inventory: imagery.

You do not always control the flight. Sometimes the data comes from a subcontractor, or was flown for a different deliverable, or the terrain forced you high.

Low-density drone data still processes. The cloud gets classified on upload, you can build a TIN and contours from whatever you draft, and building edges come through if you brought an orthophoto. What you lose is most of the automated linework. Plan the office time accordingly, and use the semi-automated tools (the linear extraction tool along a guideline, drape to snap vertices to the cloud, pick surface to land a click on the averaged surface instead of a stray point) rather than drawing every vertex from scratch.

And before you re-fly, ask what the deliverable actually needs. A site plan with terrain and footprints may be fine as flown. A roadway plan with curbs is not.

Drone LiDAR sensors got good faster than the office side did. A crew can fly a corridor in an afternoon that used to take a week on the ground. Then the data goes back to the office and someone spends three days tracing curbs, because the software they have cannot do it.

The tool is the bottleneck, not the team. Flying for density is the cheapest fix there is, because it turns the office work from drafting into checking.

What point density do I need for drone LiDAR feature extraction? For automated linework such as edge of pavement, curbs and striping, plan for at least 300 to 400 points per square meter. Terrain-only deliverables work at much lower densities.

How accurate is drone LiDAR? Survey-grade drone LiDAR with proper control and a PPK or RTK workflow is typically accurate to a few centimeters. Accuracy depends on your positioning workflow, not your point density.

Does flying lower always give better results? Lower and slower gives more points per square meter, which helps automation find small features. The tradeoff is flight time and battery. Fly for the smallest feature in the deliverable.

Can I extract linework from sparse drone data? Yes, manually or with semi-automated tools that snap to the point cloud. Automated linework needs enough points across each edge for the software to detect it.

Upload a drone dataset and see what the automation drafts before you plan the next flight. Book a demo at mach9.ai/get-started.