Mobile LiDAR vs static LiDAR — which to choose
Mobile and static LiDAR scanners produce very different results at very different speeds. Here is how to decide which is right for your project based on accuracy requirements, site size, and programme.
LiDAR is often treated as a single technology, but the way the scanner is deployed makes a real difference to the result. The broad split is between static scanning, where the instrument is set up on a tripod and records from fixed positions, and mobile scanning, where the scanner moves through the site as it captures. They produce different accuracies at very different speeds, and choosing the wrong one wastes either money or precision. This post explains the difference and how to decide.
How static LiDAR works
A static, or terrestrial, LiDAR scanner is mounted on a tripod, levelled, and left to scan from a fixed position. It sweeps the laser through a full sphere and records a dense, highly accurate point cloud from that one location. The instrument is then moved to the next position and the process repeats. Afterwards the individual scans are registered together — aligned into one coordinated cloud — using overlapping detail or targets.
The strength of static scanning is accuracy and density. Because the instrument is stationary and levelled, each scan is captured under controlled conditions, and the result is the highest-precision point cloud LiDAR can produce. The cost is time: every position is a separate set-up, and a large or compartmented building needs a great many of them.
How mobile LiDAR works
A mobile LiDAR system captures while moving. The scanner is carried, pushed, or vehicle-mounted, and it records continuously as it travels through the site. To make sense of a moving dataset, the system constantly tracks its own position — typically using a technique that builds a map of the surroundings while simultaneously locating the scanner within it, often supported by other positioning sensors.
The strength of mobile scanning is speed and coverage. An operator can walk a building, a site, or a length of corridor and capture it in a fraction of the time a static survey of the same area would take. Continuous capture also handles long, linear spaces and complex routes well, because there is no penalty for the many set-ups that would slow a static survey.
The trade-off is accuracy. Because position is being tracked on the move, a mobile cloud is generally less precise than a static one, and small positional uncertainty can accumulate over a long capture. For many purposes that accuracy is entirely sufficient; for the most demanding ones it is not.
Choosing between them
The decision comes down to three questions, weighed together rather than in isolation.
- How accurate does the result need to be? If the survey feeds precise engineering work — tight-tolerance fit-out, structural analysis, clash detection against new steelwork — static scanning’s higher precision is usually the right call. If the survey supports space planning, asset records, visualisation, or general measured-survey purposes, mobile accuracy is normally well within tolerance.
- How large is the site? A small, accuracy-critical area suits static scanning: the number of set-ups is manageable and the precision is worth having. A large building, an extensive site, or long linear infrastructure favours mobile, where static set-up times would make the survey slow and costly.
- What does the programme allow? Mobile capture is dramatically faster on site, which matters where access is limited, where a building is occupied and disruption must be kept short, or where the survey sits on a tight programme. Static scanning needs more time on site for the same extent.
In practice these pull in the same direction more often than not. A small, precision-critical job points clearly to static; a large site on a short programme with moderate accuracy needs points clearly to mobile. The harder cases are in the middle, and they are worth a conversation with the surveyor rather than a default choice.
When a combined approach makes sense
The two methods are not mutually exclusive. A common and effective approach on a larger project is to use mobile LiDAR to capture the bulk of the site quickly, then use static scanning in the specific areas where higher accuracy is genuinely needed — a plant room, a structural connection zone, an area due for tight-tolerance work. This puts the precision where it earns its keep and the speed everywhere else, and it usually delivers a better result for the budget than forcing one method across the whole job.
The practical recommendation
There is no single best LiDAR method; there is the method that fits the job. Define what the point cloud will actually be used for, and the accuracy requirement follows from that. Match that requirement against the size of the site and the time available. A short, accuracy-critical survey leans static; a large survey on a tight programme with moderate accuracy needs leans mobile; many real projects are best served by a sensible mix.
The mistake to avoid is specifying by habit. Commissioning static scanning for a large, low-tolerance site burns money on precision nobody will use; commissioning mobile for a small, high-tolerance job risks an answer that is not accurate enough. Decide from the use, the size, and the programme — in that order.