LiDAR Point Density and Flight Line Spacing

Point density is the pulse rate divided by the ground area the sensor sweeps per second.

Run the calculator

Example

You enter

You get

Details, formula, and sources

Point density is the pulse rate divided by the ground area the sensor sweeps per second, and that area is the swath width times the ground speed. The swath is twice the flight height times the tangent of half the scan angle, so ALL THREE FLIGHT PARAMETERS ENTER, and the two the pilot can change trade very differently. HALVING THE SPEED DOUBLES THE DENSITY AND DOUBLES THE FLIGHT TIME -- a linear trade, and often the cheap one. HALVING THE HEIGHT ALSO DOUBLES THE DENSITY, because the swath halves, but it doubles the number of flight lines needed to cover the same ground at the same time, so the total flight time doubles too AND the line count doubles with it. Altitude is the expensive lever, and knowing which one to pull before quoting a density is most of the planning. DENSITY IS SAMPLING AND IT IS NOT ACCURACY, which is the same distinction that governs photogrammetry. How many points land per square metre says nothing about where those points are: accuracy comes from the sensor's own ranging precision, from the inertial and satellite trajectory that positions every shot, and from the boresight calibration that relates the scanner to the navigation frame. A dense cloud from a poorly calibrated system is densely wrong, and the check is overlapping flight lines that should agree with each other. Multiple returns are the other thing a density figure hides. A pulse over vegetation can produce several returns, so the FIRST return density and the GROUND return density are very different numbers, and a specification written for one and delivered against the other is a common dispute. Ground density under canopy can be a small fraction of the nominal figure, and it is the ground density that a terrain model needs. Side overlap is the last term, and fifteen to thirty percent is normal, because the swath edges are where the scan geometry is worst -- the beam is most oblique, the footprint is most elongated, and the accuracy is lowest. Nominal density for a linear scanner at constant height and speed over level ground. It assumes uniform coverage across the swath, which an oscillating mirror does not give -- density is higher at the swath edges where the mirror slows and reverses -- and it does not model terrain relief, which changes the swath width continuously beneath the aircraft. It does not address atmospheric attenuation, the maximum range at a given reflectance, eye safety, or the pulse repetition limits that come with multiple pulses in air. The sensor manufacturer's specifications, the project's accuracy and density specification, and the surveyor of record govern.

swath width = 2 x flight height x tan(half the total scan angle); point density = pulse rate / (swath width x ground speed); point spacing = 1 / sqrt(density); line spacing = swath width x (1 - side overlap).

The airborne LiDAR density relations by name, with fifteen to thirty percent side overlap normal because the swath edges are where the scan geometry is worst. DENSITY IS SAMPLING, NOT ACCURACY: accuracy comes from the sensor's ranging precision, the inertial and satellite trajectory, and the boresight calibration. Nominal density for a linear scanner over level ground; an oscillating mirror gives higher density at the swath edges. The sensor manufacturer's specifications, the project's accuracy and density specification, and the surveyor of record govern.

One tangent and one division on numbers off a sensor spec sheet; no manufacturer data is reproduced.

Estimate. AHJ and licensed professional govern.

Field names used by the API: pulse_rate_khz, scan_angle_deg, flight_height_m, ground_speed_ms, side_overlap_pct, area_acres, swath_width_m, point_density_per_m2, point_spacing_m, line_spacing_m, half_speed_density, half_height_density, half_height_swath_m

Related tools