What this step is for: get the field job into the page, whole. Nothing is filtered or computed on the way in.
Drop a DBX job folder here, or pick it. A .cpt working file, the instrument's .xml export or a saved job .json is accepted too.
Runs entirely in this browser — nothing leaves the device.
What this step is for: read the inventory before deciding anything — every setup, pointing, point, round, task, file and note the instrument recorded. Click any row for every field.
What this step is for: connect every setup into one frame using the vectors between points, before any control is involved. Names are only a hint; the geometry decides. You accept, reject or rename each identity — nothing is written back to the job.
What this step is for: bring in the known marks — a list (name E N H), or any document that holds the coordinate table (PDF technical note, Excel, Word): the page sniffs the table out, you pick the name column, the grid and whether the marks are good for plan, level or both — then match them to the assembled network by name and by vectors, look at the residuals, and decide which marks to hold and how tightly.
Per mark and axis: fixed, weighted with a standard deviation in millimetres, or free. This is the same hold list the Select & order step shows — one source of truth, keyed by point name.
What this step is for: decide which setups, rounds and pointings enter the adjustment, and in what order. Nothing is deleted — excluded records stay in the job with use = no.
Points with coordinates. For each axis: blank = free, 0 or ! = fixed, a number = weighted with that standard deviation in millimetres. Holds are keyed by point name and travel with the job into the working file and the adjustment; the Control step edits the same list.
What this step is for: correct what the crew got wrong — target heights, prism constants, instrument heights, a target shot under the wrong name, a use flag — every field of every observation, in the table or in the text. The as-imported value stays beside the edit and every change is logged.
What this step is for: run the least-squares adjustment with the holds, identities and observations you settled above, then read the verdict, the residuals and the coordinates — worst first.
What this step is for: see the network as a picture — which points are control, which are stations, which are single-ray sideshots, how many observations tie each pair, and the error ellipses after adjustment. Zoom (wheel or pinch), pan (drag), fit (double-click or double-tap), click a point for its derivation; everything else is under Settings.
What this step is for: one document that shows everything — settings, datum, identities, control fit, observations with the weights applied, statistics, ranked residuals, coordinates with ellipses, and your edit log. The executive summary is below; the full report is one click away, and its ticks decide what the download and the print contain.