Purpose-led terrestrial, mobile or hybrid LiDAR surveying for professional teams commissioning registered point clouds, measured information and specialist spatial datasets.
LiDAR measures the distance between the sensor and visible surfaces using laser light. A survey normally combines many measured observations into a registered three-dimensional point cloud.
Clients often use “LiDAR scanning” and 3D laser scanning interchangeably. We therefore start with the required outcome. If the requirement is a registered spatial dataset, this page is the right route. If the requirement is floor plans, elevations or sections, the appropriate commission is usually a measured building survey, even when LiDAR is the principal capture method.
The point cloud can be delivered as the final product or prepared for a defined downstream workflow. Geo Scan does not assume that every client needs the same density, colour, coordinate system, cleaning, segmentation or file type. Those decisions affect usability, processing time and cost.
LiDAR records surfaces visible from the survey positions. Dense point data does not remove line-of-sight limitations, so occluded, enclosed, covered or inaccessible geometry is not inferred unless another agreed method records it.
Accuracy depends on the instrument, range, surfaces, network geometry, registration, control, mobile trajectory where used, and the completed workflow. The specification should match the decisions the data must support. A real-time visualisation dataset may also require a lighter derivative than the controlled survey master.
LiDAR data provides geometry. It does not by itself complete sightline analysis, creative projection design, virtual-tour production, game optimisation or engineering interpretation unless those services are expressly included.
Dependable survey information is supported by auditable quality-control processes, with capture method, coverage, control, registration, checks and stated limitations aligned to the intended use.
The workflow begins with the receiving software and decisions the data must support—not with a default scanner setting.
We confirm the survey extent, required decisions, receiving software, coordinate system, units, formats, colour, density and programme.
We select terrestrial, mobile or hybrid capture, establish suitable control and plan viewpoints around access, occlusion and the required geometry.
The observations are registered and reviewed for network quality, coverage, control agreement and visible gaps relevant to the brief.
We export, structure and where agreed crop, clean, decimate or transform the dataset for the receiving team, with delivery notes explaining scale, origin and limitations.
In building surveying the terms often overlap. LiDAR describes laser-based distance measurement, while 3D laser scanning commonly describes the survey workflow and terrestrial equipment. Geo Scan scopes the method around the required deliverable rather than relying on terminology alone.
Choose a LiDAR or point-cloud survey when the registered 3D dataset is the required deliverable. Choose a measured building survey when you need interpreted plans, elevations, sections, schedules or another defined drawing package. LiDAR may still be the principal capture method.
Yes, where the required format, scale, origin, colour, density and receiving workflow are agreed. Epic currently documents support for E57, LAS, LAZ, XYZ, PTS and TXT through its LiDAR Point Cloud plugin. The client should confirm the Unreal version, plugin and performance requirements before issue.
A LiDAR survey can provide the measured venue or building geometry used for sightline work. The analysis still needs defined viewer positions, targets, obstructions and acceptance criteria and may be undertaken by the production, design or specialist consultant team.
No. A point cloud provides three-dimensional geometry and may include colour. A polished virtual tour may also require panoramic imagery, a mesh or splat, texturing, navigation, hosting and interface production.
Send the site, survey extent, intended use, receiving software and version, required formats, units, coordinate or origin requirements, colour or imagery needs, target density or performance constraints, access conditions and programme. If drawings, BIM, meshes or visual outputs are also required, identify them separately.