What is point cloud georeferencing?
A raw point cloud from a LiDAR scanner or photogrammetry processing contains X, Y, Z coordinates — but those coordinates only make sense if you know which coordinate system they belong to.
Georeferencing means anchoring the point cloud in a real, official geographic reference frame — a coordinate system identified by an EPSG code — so it can be used in a GIS, overlaid with other geographic data, or delivered to a client according to project specifications.
Without proper georeferencing, a point cloud cannot be correctly positioned in QGIS, AutoCAD Civil 3D, or any geomatics software.
Two georeferencing methods
EPSG transformation
The point cloud is already in a known CRS (e.g. WGS84 / EPSG:4326) and needs to be reprojected to another (e.g. UTM zone 32N / EPSG:32632). This is a purely mathematical coordinate transformation.
GCP-based georeferencing
The point cloud is in a local frame (arbitrary coordinates without a CRS). Ground control points (GCP) with known real-world coordinates are used to register the cloud into the correct reference system.
Method 1 — EPSG transformation
If your point cloud is already in a known coordinate system — for example, exported from Pix4D in WGS84, or from a LiDAR scanner calibrated in UTM — you only need to reproject the coordinates to the target system.
GeoRef Cloud uses the PROJ library to perform these transformations accurately, including official transformation grids where applicable.
Common transformation examples
| Source CRS | Target CRS | Use case |
|---|---|---|
| EPSG:4326 WGS84 | EPSG:2154 Lambert 93 | GPS drone → French national deliverable |
| EPSG:32631 UTM 31N | EPSG:2154 Lambert 93 | Pix4D UTM output → national GIS |
| EPSG:32632 UTM 32N | EPSG:2056 CH1903+ LV95 | Cross-border project → Swiss system |
| EPSG:4326 WGS84 | EPSG:3948 RGF93 CC48 | Drone → French conformal conic zone 8 |
| EPSG:2154 Lambert 93 | EPSG:4326 WGS84 | Export for Google Earth or web platform |
Method 2 — GCP-based georeferencing
When a point cloud is produced without an onboard GNSS receiver — or with low-accuracy positioning — it ends up in a local coordinate frame: X, Y, Z values are internally consistent, but don't correspond to any real position on Earth.
To georeference it, you use Ground Control Points (GCPs): points whose real-world coordinates are measured with an RTK GPS or total station, and which can be identified in the point cloud. GeoRef Cloud then computes the transformation (translation, rotation, scale) that aligns the cloud with the real-world reference frame.
How many GCPs are needed?
- 3 GCPs minimum for a rigid transformation (translation + rotation) without scale correction
- 4 or more GCPs for a full transformation with scale correction and residual checking
- 6 to 10 GCPs recommended for large projects or areas with potential deformation
Additional GCPs act as check points to verify georeferencing quality.
Step-by-step: georeference a point cloud with GeoRef Cloud
- Upload your LAS or LAZ file to GeoRef Cloud
- Choose your method: EPSG transformation only, or GCP-based georeferencing
- If EPSG transformation: select the source and target coordinate systems by EPSG code or name
- If GCP: import your ground control points (CSV with real-world X, Y, Z columns) and identify them in the point cloud
- Run the transformation — GeoRef Cloud applies the registration and reprojects the coordinates
- Check the residuals and georeferencing quality
- Download the georeferenced LAS or LAZ file, with the correct CRS written into the header
Why the CRS in the LAS header matters
The LAS format supports embedding the coordinate reference system directly in the file header (VLR — Variable Length Record field). When this field is correctly set, QGIS, CloudCompare, AutoCAD, and all LAS-compatible software automatically recognize the file's CRS and display it in the right position.
GeoRef Cloud automatically writes the target EPSG code into the output file header — preventing positioning errors when importing into a GIS.
Frequently asked questions
My point cloud is in WGS84 — is it already georeferenced?
Technically yes — WGS84 (EPSG:4326) is a valid geographic coordinate system. But for most professional use cases, you'll need to reproject it to a projected CRS (UTM, Lambert 93, national grid) for correct metric measurements, SIG compliance, and client deliverable specifications.
What is the difference between georeferencing and reprojection?
Reprojection transforms coordinates from one known CRS to another — it's a purely mathematical operation. Georeferencing is broader: it includes reprojection, but also the registration of a local-frame point cloud onto a real-world reference system using GCPs. GeoRef Cloud handles both cases.
My GCP coordinates are in Lambert 93 — can I use them directly?
Yes. GeoRef Cloud accepts GCP coordinates in any EPSG system. You specify the EPSG code of your field-measured GCPs, and the application handles the correspondence with the target reference frame.
Does georeferencing affect point density or cloud quality?
No. The coordinate transformation does not change the number of points, their intensity, classification, or RGB color. Only the X, Y, Z values are recalculated.
What GCP file formats are accepted?
GeoRef Cloud accepts CSV files with real-world coordinate columns (X, Y, Z) and corresponding point cloud coordinates (x, y, z). The exact format is detailed in the application documentation.
Can I georeference a point cloud that spans multiple UTM zones?
Yes. If your acquisition covers two UTM zones, you can reproject both sections to a single common CRS (e.g. a national projection) after georeferencing. GeoRef Cloud supports all valid EPSG transformations via the PROJ library.
Georeference your point cloud online
EPSG transformation or GCP-based registration — upload your LAS or LAZ file and get a correctly positioned point cloud.
Try GeoRef Cloud for free