Check Points FAQ

Check Points are surveyed points with known coordinates that are excluded from SLAM correction and georeferencing correction. They are used to validate accuracy after processing by comparing the surveyed positions with the processed dataset. In Aura, these comparisons are reported as residual errors in the accuracy report.

• Meet surveying and geospatial standards that recommend or require independent accuracy checks.

• Provide documented proof that the scan meets project tolerances (for example, ±20 mm).

• Ensure validation is independent of the control points that influence georeferencing.

• Avoid the need for third-party software or additional workflows to validate accuracy.

Yes. Both control points and Check Points can be included in the same CSV file. Mark points as Check Points during assignment.

A minimum of 3 to 5 well-distributed Check Points is recommended for reliable validation. More may be required for large or complex projects.

No. Check Points are excluded from the correction process and contribute only to validation and reporting.

Using every surveyed point for georeferencing removes the independent dataset needed for validation. Keeping some points as Check Points maintains an unbiased measure of accuracy rather than letting all points influence the correction.

The Before GCP correction rigid alignment error is reported after survey points are assigned but before SLAM correction is applied. It shows the initial fit between the SLAM trajectory and the survey data, and may appear large in complex or extended scans.