Read and share the QA report

The project's quality report — check-shot residuals, the receiver's own estimates, correction health, 3D captures and an exceptions list — as PDF or HTML.

On this page

The QA report describes the quality of a project's measurements. It opens with the one figure a receiver can't give you: how far your measurements landed from coordinates you already knew. Below that comes a list of everything a reviewer should know before trusting the data. Share it as a PDF for the job file.

Open the report

  1. Go to Tools → QA report. The row shows the horizontal RMS of your check shots, for example RMS 0.014 m, or Not verified if there are none yet.
  2. Scroll through the sections below.
  3. To share, tap the share button at the top and choose Share PDF or Share HTML. The files are named <project>-qa-report.pdf and .html.

All figures in the report are in metres, whatever your display units.

What the report contains

The headline

  • With check shots: Measured against known coordinates, with the horizontal RMS over all check shots and how many were outside tolerance.
  • Without: Not verified, because nothing has been checked against a known coordinate and every accuracy figure is the receiver's own estimate.

To get a measured figure, see Check a known point.

Exceptions

Findings a reviewer needs to see, most serious first. Each one says what happened, what it affects and what to do. With nothing to report, it reads No exceptions raised. See What raises an exception.

Coordinate system

The horizontal system, EPSG code and units; the note that NAD83 is treated as WGS 84 with no epoch; the project's declared vertical datum; and a note on how geoid separation was recorded.

Observations

Counts of Measured positions, Imported design positions, Averaged occupations and Single-epoch shots, and a count for each fix type.

Estimated accuracy

Horizontal, Vertical and Occupation spread, each shown as best / median / worst. These are the receiver's estimates of its own solution, not measured accuracy.

Corrections and solution health

How many positions were measured With corrections and Without; the correction Source; and best / median / worst for Correction age, Baseline (distance to the base), Satellites and PDOP. A position with no recorded measurement data counts as uncorrected.

Observed accuracy — check shots

Every check shot, listed by the target it was taken on, with its horizontal residual and ΔN, ΔE and ΔU. Each also shows its kind, whether it was differenced in the grid or on a tangent plane, and the tolerance. Deltas are measured minus known. The footer gives the vertical RMS when there is one.

Site localization

This section appears if a localization has been solved. It shows horizontal and vertical RMS, rotation, scale, control held and redundancy. The localization is fitted and reported, not applied: no coordinate in the report has been put through it.

3D captures

This section appears if the project has scans. For each one it shows the payload type, the accuracy of the scan's origin, the heading source and accuracy, and the fit.

Identity

Project, operator (from Settings → Surveyor), device, software version and when the report was generated. The report describes measurement quality only. It isn't a certification, and it's no substitute for a licensed surveyor's judgement.

What raises an exception

Critical

Exception Raised when
Check shots outside tolerance A check shot disagreed with its known coordinate by more than its tolerance.
Measured under a different coordinate system The project's zone changed after these positions were collected.
Pole height may be applied twice The receiver was tilt-compensating while a pole height was also set in the app.
Compared against a coordinate that has since changed A check shot's target was edited after the check was taken.
Localization solved in a different coordinate system The saved localization is on a different zone from the project's.

Warning

Exception Raised when
Nothing was checked against a known coordinate There are measured positions and no check shots.
No positioning pedigree Positions have no recorded measurement data (DOP, satellites, correction age, antenna height), for example positions placed by hand.
Receiver observation with no antenna height A receiver position was saved with a pole height of zero.
Stale corrections Corrections were more than 30 s old at the fix.
Saved above the accuracy threshold Positions were kept past an accuracy gate warning.
Below the project's fix floor Positions were saved on a weaker solution than the gate's fix type requires.
Geoid mismatch or undeclared vertical datum Heights use different geoids, don't match the declared geoid, or the project has no stated vertical datum.
Buried utility filed without unrecoverable evidence An open-trench record was missing a depth, its datum or a trench photo.
Check shots recorded after the localization was solved New control isn't in the saved solution.
Coordinates entered by hand Positions were typed rather than measured.
Capture oriented by compass A scan's heading came from the magnetometer.
Capture with no recorded position A scan was captured without a fix.
Capture tracked poorly, or sparsely covered Tracking was degraded for much of a scan, or much of its surface has too few points.

Warnings from the site localization solve also appear here.

Note

Exception Raised when
Heights are phone-GPS grade Vertical accuracy worse than 3 m.
Positions measured again Positions were re-observed; the earlier ones are kept on the asset.
Imported design features never checked Design features have no check shot against them.
Residuals differenced on a tangent plane Check shots were taken with no projected zone set.
Captures started with preflight warnings A scan was started despite preflight warnings.