How to Use a GPS Rover for Construction Stakeout

Applies to: Trimble R10, Topcon HiPer HR, Leica GS18

GPS rover stakeout has replaced optical total station stakeout for most horizontal layout work on construction sites — it's faster, requires fewer crew members, and covers large sites without instrument moves. But it depends entirely on getting the RTK link right. A rover that isn't achieving RTK fixed solution is giving you sub-meter positions while showing a display that looks like good data. This guide covers every step of a proper GPS stakeout setup and the checks that prevent expensive layout errors.

Base Station Setup: The Foundation of Everything

Your GPS rover is only as accurate as its base station. The base receiver sits on a known point and transmits correction data to the rover — if the base is set up wrong, every single point the rover stakes is wrong by the same amount. Base setup is the step operators rush most and the step where most GPS errors originate.

Set the base over a control point with known coordinates in your project coordinate system. Use a tribrach and optical plummet to center accurately over the point — errors in base centering transfer directly to rover positions. After centering, measure the antenna height carefully: use the proper measurement method for your antenna type (slant height to ARP on most Trimble antennas, direct height on some Topcon setups — check your antenna's documentation). A 10mm error in antenna height means every point the rover stakes is 10mm off in elevation.

Enter the base point coordinates into the survey controller, matching the project coordinate system and datum. For state plane work, confirm you're in the correct state plane zone and the correct datum (NAD83 vs WGS84 vs local datum). Coordinate system mismatches are the most common cause of GPS positions that are consistently off by a fixed distance in a consistent direction.

RTK Link Verification Before Stakeout

Before staking any points, verify the RTK link is working and achieving a fixed solution — not just initialized. In Trimble Access, look for 'Fixed' in the solution status display. On Topcon controllers, the fixed solution indicator should show before any stakeout begins. 'Float' solutions are not accurate enough for construction stakeout and should never be used for layout.

Verify the RTK baseline (distance from base to rover). Most radio-based RTK systems maintain accuracy within 10-15 km; beyond that, the correction quality degrades. Network RTK (VRS, NTRIP) typically maintains accuracy across larger areas but depends on cellular connectivity and correction service quality.

Check horizontal and vertical precision indicators in your controller software — these are not accuracy guarantees but are real-time quality indicators. Horizontal precision below 0.02m and vertical below 0.03m is good for most construction work. Precisions above 0.05m indicate poor satellite geometry or correction quality — wait for improvement before staking.

Localization: Matching GPS to Project Coordinates

GPS receivers compute positions in WGS84 geographic coordinates. Your construction project uses state plane coordinates (or local grid coordinates) in NAD83. These are different, and the transformation between them — called localization or site calibration — must be properly set up before stakeout begins.

A proper localization uses 3+ control points distributed across the project site, each observed with the rover and compared to their known coordinates. The software computes a transformation that minimizes residuals across all control points. Residuals above 0.03m on any control point indicate either a bad control point or a systematic error in your coordinate system setup.

Perform localization at the start of every project and re-verify with a check shot on a control point at the start of every shift. Equipment moves, battery swaps, and base station restarts can all affect localization validity — a quick check shot costs 2 minutes and confirms everything is still right.

Stakeout Workflow

Load or import your design points into the survey controller before arriving on site. Working from a printout or reading coordinates off a plan sheet in the field is slow and error-prone. Most construction stakeout is done from a DXF/CAD file or a coordinate list — both import cleanly into Trimble Access, Topcon Pocket-3D, and Leica Captivate.

Navigate to each stakeout point: the controller shows direction and distance to the target point. Approach the point until the arrow-to-point distance shows under 0.10m, then slow down and fine-position. When you're over the point within your tolerance, the controller will indicate on-point — tap to accept and record. Set the hub with a nail or chiseled mark at that position.

Always record the as-staked position alongside the design position — the delta (difference) between design and as-staked is quality documentation. Differences over 0.05m should be investigated before continuing.

Common GPS Stakeout Errors and How to Prevent Them

Stakeout in float solution: Float solutions can appear 0.1-0.5m off from true position while showing on the controller display as normal. Always confirm 'Fixed' before staking any point. If the solution drops from Fixed to Float in the field, stop staking and let the receiver re-initialize.

Forgetting to re-check localization after base restart: If the base station restarts during the day (power outage, battery swap, accidental shutdown), the base may have initialized to a slightly different position. Always shoot a check shot on a control point after any base restart.

Tilt compensation at steep angles: Tilt-compensated rovers like the Trimble R10 and R12 allow staking without plumbing the pole, but at steep angles (over 10-12 degrees) accuracy degrades. When precise vertical work is needed, plumb the pole.