01
Export your marks
Whatever your rover or total station writes out. One row per point, with a name, coordinates and an elevation.
Guide
Ground Control Points,Start to Finish
Upload the points you measured on the ground, see how far your cloud sits from them before you process anything, correct it if correcting helps, and hand your client an accuracy statement their own surveyor will recognize.
Checking is free on every plan • only a correction uses credits
Free to check
Every plan, every project
Every plan, every project
Any export
CSV, TXT, ASC or PTS
CSV, TXT, ASC or PTS
Correct if it helps
Never worse than doing nothing
Never worse than doing nothing
In your report
ASPRS 2023 statement
ASPRS 2023 statement
The whole flow
From your rover to your report
Six moments. Only one of them is a decision, and you make it with the error already on screen.
02
Upload them with the project
In the Create a project panel, tick Add ground control points and pick the file. The point cloud itself is not modified by the import.
03
Confirm what was read
Lidarvisor states how many points it read and which column it took as ID, X, Y and Z, so a wrong axis order never rides silently into a figure.
04
Read the preliminary check
It runs on its own shortly after your upload finishes, against the raw cloud, before any processing has happened.
05
Choose a correction, or none
Four options, each showing the accuracy it would leave you and what it would do to your data. The default changes nothing inside your cloud.
06
Collect the accuracy statement
After processing, the figure is measured again against classified ground and written into the project report.
Walkthrough
What each screen is telling you
The four places you will actually spend time.
Importing
Send the file your instrument exports
No reformatting, no template to fill in.
The importer handles what survey software actually writes. Names help when they are there, but the deciding test is your point cloud itself: a candidate reading either drops the points inside the cloud footprint or it does not. That one test catches transposed axes, a wrong coordinate system and wrong units at the same time.
- Comma, semicolon, tab, pipe or aligned columns, with a decimal point or a decimal comma
- Header row, no header row, or a header hidden behind a comment marker
- Any column order, including the headerless Northing before Easting file
- Feet against a metric cloud, or the reverse, detected and converted
- Quality columns such as sigma or Accuracy_Z recognized, never mistaken for coordinates
The preliminary check
See the error before you press Process
The point of checking early is that it is still a choice.
No classification exists yet at that moment, so the ground around each mark is estimated from the raw cloud and read at the exact position of your point. By the time you reach the processing options, Align to control points is already ticked and already tells you what it is working with: how many points, how far the cloud sits from them, and exactly what the run will try. This early figure is always labelled as preliminary, and the figure measured after processing is labelled separately. They differ by centimetres and are never presented as the same number.
- Runs automatically, shortly after the upload finishes
- Tells you whether aligning is worth paying for, before you commit
- Nothing else runs unless you pick it, and the option can simply be unticked
The panel
One sentence, then every number behind it
It docks along the bottom, so the map stays visible.
The panel leads with how far your cloud sits from your survey, the range that figure can be known to, and how many points it rests on. The figure is measured honestly: every point is predicted by a correction computed without it, so no point ever marks its own homework. Open Correction options and each rung is priced the same way, including the one that says outright it would probably leave your data worse. Underneath, one row per control point gives you the surveyed elevation, the cloud elevation, the difference and the status, and every column sorts.
- Difference is your elevation minus the cloud elevation, so positive means the cloud sits low
- Use or exclude any measurable point yourself, for a mark you know is wrong
- Export every residual as a CSV, with the stage and the sign convention in the header
Verify it yourself
Look at the ground under any mark
You should not have to take a number on trust.
The table says a point is out by some amount, or that the ground there could not be measured. Click the ground icon on any row and Lidarvisor cuts two cross sections straight through that mark, one north to south and one east to west, using the same profile tool you use everywhere else. Your surveyed point is drawn on the section at its surveyed elevation, so you can see whether it sits above the ground, below it, or on a kerb the estimator refused.
Honest exclusions
When a point is set aside
A point that cannot be measured fairly is excluded on its own, with its reason in the status column. It never fails the whole set, and the report lists every exclusion.
Outside the data
The mark falls outside the point cloud, or outside the area you asked to process.
Too few ground points nearby
Not enough ground around the mark to measure against. Common under dense canopy.
The ground is not flat enough
The surface there is too uneven to give a reading you could rely on.
A kerb or edge is in reach
A break in the surface, such as a curb, step or bank, would bias any elevation read at that spot.
Sitting on something
The cloud is well above your mark: probably a roof, a vehicle or canopy rather than ground.
Metres from your own survey
A mark the other marks rule out. A target that moved, or a transcription error. Shown, and kept out of every figure.
The decision
Four corrections, and what each one costs you
Expand Correction options in the panel to see them measured against your own survey.
| Option | What it does to your data | When it fits |
|---|---|---|
| Leave it alone | Your cloud is delivered exactly as it was measured. | The differences are already small, or their shape says no correction is the right fix. |
| Shift Default | Moves the whole cloud up or down. Nothing inside it changes. | A common offset across the site. It can be fitted from a single point. |
| Shift and tilt | Also corrects a lean. Distances and angles are preserved, but slopes and drainage directions change. | The differences grow across the site. Needs at least seven usable points. |
| Match every control point | Warps the cloud locally. Nearby features move by different amounts and internal geometry is not preserved. | Local distortion the other options cannot reach. Needs at least seven usable points. |
Every row carries its expected accuracy and a 95% range, measured the same held-out way as the headline. An option that would probably leave your cloud worse than doing nothing says so on its own row, and options your number of points cannot support are greyed out with the reason.
When you press Process
What actually runs
Align to control points sits with the other processing options, and comes pre-ticked when your project has control points. Two things then decide everything: that checkbox, and the correction selected in the panel.
- Ticked, and you touched nothing else. Lidarvisor tries the default shift. If it measurably improves the cloud it is kept, otherwise your cloud is delivered exactly as measured.
- Ticked, and you picked a correction. Your pick is applied, subject to the same safety rule.
- Unticked. The cloud is never moved. The check still runs and the report still carries the figures.
The one rule: no correction ever ships that measures worse than doing nothing. Before your cloud is touched, the chosen correction is measured again on classified ground, each point predicted by a fit that did not use it. If it fails that test, even when you picked it explicitly, it is dropped, the cloud is delivered uncorrected, and the report says a correction was fitted and rejected. On a scattered survey that is the honest outcome, and ticking the option correctly does nothing.
The correction is applied inside the processing pipeline, before anything is derived from the cloud, so your terrain models, contours, breaklines, vectors, tiles and reports all come from the corrected cloud natively. There is no second cloud to reconcile and no re-tiling. Your raw uploaded file is never modified, and changing the decision later means reprocessing the project.
One thing to check first. A shift of a metre or more is almost always a vertical datum mismatch rather than a data problem. Confirm the vertical datum of your file and of your cloud before aligning, or the mistake gets baked in.
The deliverable
The part your client keeps
Project report
An accuracy statement, not a claim
Written the way a reviewing surveyor expects to read it.
When control points could be compared, the report gains an Absolute accuracy section following the ASPRS Positional Accuracy Standards for Digital Geospatial Data, 2nd Edition. It reports the measured vertical accuracy, names the number of checkpoints, and where the classification allows it reports non-vegetated and vegetated terrain separately. When there are no control points the section is simply absent, never a placeholder and never an invented value.
- Honest wording about independence: points used to correct a cloud cannot also be a fully independent check of it, and the report says how the figure was measured instead
- The full statistics, with the RMS labelled indicative when it rests on few points
- A per-point table, so a reader can see which mark drove the figure and take it to the field
- Every excluded point with its reason, because comparing 18 of 22 points and reporting 22 would misstate the test
- What was done to the cloud in plain terms, including a correction that was fitted and then rejected
Questions
Frequently asked questions
Does checking my control points cost credits?
No. Importing them and checking against them is free, on every plan, and your own survey data is never treated as a paid deliverable. Only a correction uses processing credits, and only when you ask for one.
Which file formats can I upload?
One delimited text file: CSV, TXT, ASC or PTS. Instrument-native binary formats such as Leica GSI or Trimble JOB are not read. Every instrument can export delimited text, so export that instead.
Do my points have to be in the same coordinate system as the cloud?
Yes, the same system you declared when you uploaded the cloud. If the file lands somewhere else, you get a message naming how far off the points fall rather than a generic parse error. A coordinate system written on the first comment line of the export, as several packages do, is read.
What happens with vertical datums?
They are declared, never transformed silently. Lidarvisor does not apply geoid corrections behind your back. When your file states its vertical datum, a common offset between survey and cloud can be attributed with confidence. When neither the cloud nor the points declare one, the check still measures the spread of the differences but refuses to call a common offset an error, because it may be a datum difference, and the report says so.
How many control points do I need?
A vertical shift can be fitted from a single point. The tilt and the local warp need at least seven usable points. Options your survey cannot support are greyed out with the reason rather than offered and then failing.
Can I change my mind after processing?
Control points freeze once they have been used to align a cloud. The panel then shows what was applied and the measured result, and the toggles lock. Changing the decision means reprocessing the project.
Go deeper
Read on
The reference documentation covers every status, column and figure. The article covers the standards themselves.
Put a number on your next deliverable
Upload your cloud with the points you measured on the ground, and see how far apart they are before you decide anything.
Create free accountThe accuracy check is free on every plan. Questions? Contact our team or see pricing