ControlPoint Manual — versioned with the code; every worked example below is a REAL corpus job and its numbers are pinned by the test suite.
TapeDrop: importing a GSI
What it does
TapeDrop's Import button now reads Leica GSI16 level files directly — the REAL staff readings and sight distances come straight into the fieldbook (unlike a .dat import, which only has reduced legs and synthesises readings). Readings longer than any staff (>5.5 m) are flagged as tape-drop candidates: flag the row and attach the calibrated tape to apply the corrections the raw file never had.
Worked example — the 2HPX shaft book
M_16032023.GSI books the drop as a 6.25 m "staff" reading on TAPE1. Import brings in D2's backsight 1.14880, TAPE1's 6.25320 (flagged), and reduces D2→TAPE1 = −5.10440 m, TAPE1→BM6 = +1.54314 m — leg-for-leg identical to the network importer's reduction (the suite cross-checks every corpus GSI against both parsers).
Theory in one paragraph
A digital level books backsight/foresight events in time order; a change point is simply a foresight and a backsight on the same point. The import reconstructs the paper book from that stream — and because two independently written parsers must produce identical legs on every real file before anything ships, a booking quirk (like two consecutive foresights) becomes a caught case, not a silent error.