ControlPoint Manual — versioned with the code; every worked example below is a REAL corpus job and its numbers are pinned by the test suite.
1 — Import
What it does
Drop the instrument's job in — a DBX folder/zip (total station), GSI16 or LandXML (level), a .dat, or a native .obs. The importer converts it to observations, names sideshots, pulls any control stored in the job, and records a SHA-256 of every input so the report can prove what went in. Nothing is renamed silently; anything odd lands in a report file next to the conversion, flagged.
Worked example — 260722-2HR19
The 2HR19 DBX drops in as 8 setups. Three of them were rushed in the field (the instrument kept the previous setup's station name and height) — the importer spots that the typed HI matches no height-capture event and marks the setups for trig heighting in step 2. Control stored in the job (class 150 coordinate records) is decoded and offered in step 3.
Theory in one paragraph
The converter is a faithful transcriber: it never guesses. Interpretation (point identity, renames, control matching) happens at import, where you can see it and veto it. That split is what makes the audit trail trustworthy — the raw record of what the instrument stored is never touched.