Topographic Survey, Field to CAD: How a Job Runs End-to-End

What a topographic survey actually delivers

A topographic survey answers one question with measurable certainty: where is everything, and how high is it? Not roughly — to a stated accuracy, in a stated coordinate frame, layered cleanly enough that a road designer, a drainage engineer, or an architect can build straight on top of it. The romantic image is a surveyor with a telescope. The real work is a disciplined chain: set the frame, capture the ground, then turn raw observations into a contoured CAD surface that holds up under scrutiny. Below is how our crews run that chain, end to end, on a real site.

Step 1 — Control comes first, always

Before anyone shoots a ground point, we build the frame everything else hangs from: a small control network of marked, permanent-enough points whose coordinates we know to high confidence and that are tied to the national grid. This is the unglamorous part that decides whether the whole survey is worth anything. Get it right and every RTK shot and every total-station observation lands in one consistent datum and projection; get it wrong and you produce a thousand points that each look fine and don't agree with each other.

We declare the datum and projection up front — the EPSG code is part of the deliverable, not an afterthought — so the client's GIS or design team isn't guessing what frame the numbers live in. On most jobs the control itself is a hybrid: a GNSS static or fast-static session to fix a couple of base points hard to the grid, then those carried through the site so the rest of the day's work inherits them.

Step 2 — Capture the ground: RTK in the open, total station in the shadows

With control set, capture is a division of labour by line-of-sight. Out in the open — fields, car parks, bare terrain — GNSS-RTK is fast: walk the detail, tag each point with a feature code, and the position drops straight onto the grid. But RTK needs sky, and real sites have canopy, walls, narrow alleys, and the inside of buildings. There the total station takes over, traversing in from known control and measuring angles and distances to a prism with a precision satellites can't reach under cover. Same frame, two instruments, no seams. The discipline that makes the office work possible is coding: top vs toe of bank, edge of pavement, kerb line, the breaklines that tell the software where the ground changes slope. Points without codes are just confetti.

Step 3 — Processing: from observations to a DWG that holds up

Back in the office the points become a surface. We import the raw observations, apply the declared coordinate frame, and clean: throw out the obvious blunders, re-check any shot that disagrees with a known control point, and confirm the density is enough to describe the ground honestly. Then the codes earn their keep — the software triangulates the points with the breaklines, so contours bend along the top of a bank or the edge of a road instead of smearing across them. Contours generated without breaklines are the classic giveaway of a survey done in a hurry.

The output is not 'the points'. It's a layered DWG: surveyed points on their layer, planimetric detail on theirs, breaklines and contours on theirs, all on the stated datum and EPSG projection, with the point list alongside. Where the project needs it we also issue the surface model itself. The test we hold it to is simple — can a designer open this and start work without re-surveying anything? If yes, the job is done.