Point Cloud Survey Cost: What Affects the Price?

The main pricing factors are:

• Coverage and geometry: floor area, levels, façades, roofs, plant, external areas and line-of-sight constraints.
• Capture method: terrestrial laser scanning, mobile mapping, photogrammetry or a combined workflow selected for the required use.
• Access: occupation, inductions, security, working hours, restricted spaces and repeat mobilisation risk.
• Survey control: local registration, project grid, datum, GNSS or OS relationship and independent checks.
• Registration and QA: aligning scan positions, checking residuals, reviewing coverage and documenting limitations.
• Data treatment: cleaning, clipping, segmentation, colourisation, decimation and naming structure.
• Delivery: E57, RCP/RCS, LAS/LAZ or other formats, coordinate information, hosting and transfer requirements.

A price cannot be assessed reliably from area alone because data quality, access and handover requirements can change the workload substantially.

“Point cloud” can describe several very different outputs:

• Raw scan data: instrument-native observations that may still require registration and specialist software.
• Registered point cloud: scan positions aligned into a coherent dataset and exported in an agreed format.
• Controlled point cloud: registration related to an agreed survey-control network, grid and datum with appropriate checks.
• Processed project dataset: registered information cleaned, divided, named or optimised for a defined design workflow.
• Derived outputs: CAD drawings, orthographic imagery, meshes or BIM models produced from the point cloud.

The quotation should name the exact handover condition. If the team needs data for design coordination, specifying only “point cloud” is rarely enough.

Registration joins individual scans into one dataset. For compact internal work, an appropriate local coordinate system may be sufficient. Larger, multi-level, external or multidisciplinary projects may need a formal control network, grid and datum relationship.

Control requirements affect field time, processing and checking, but they also make the dataset easier to coordinate with topographical surveys, design models and later project phases. The right level should be agreed from the intended use rather than added automatically.

For the technical background, see Point Cloud Accuracy & Registration and Terrestrial Laser Scanning Accuracy.

• Colour: panoramic imagery and colourised points can support interpretation but require suitable capture conditions and processing.
• Density: unnecessarily dense delivery increases file size and handling without always improving the intended output.
• Cleaning: removing transient people, vehicles or noise can be useful, but extensive manual cleaning adds time.
• Segmentation: dividing data by floor, zone or discipline improves usability and requires an agreed structure.
• Coordinate transformation: project, national-grid or shared-coordinate requirements should be known before capture.
• Formats: each export must preserve the attributes and coordinate precision needed by the receiving software.
• Online viewing: browser-based access, hosting duration and user permissions may be a separate deliverable.

The Point Cloud File Formats Guide explains E57, RCP/RCS, LAS/LAZ and common handover considerations.

Provide the following information where available:

• site address, approximate area, number of levels and marked coverage;
• the intended use and receiving design or asset-management software;
• required accuracy, control, grid and datum;
• whether colour, imagery, cleaning or segmentation is needed;
• file formats, maximum practical file sizes and naming requirements;
• access, occupation, security and working-hour restrictions;
• required site and delivery dates;
• any CAD, BIM, orthophoto, mesh or hosted-viewer outputs.

This lets suppliers price the same data product. For broader building-survey pricing, see How Much Does a Measured Building Survey Cost?.