Centimetre-level positioning is only useful when every part of the workflow is working together. For organisations asking what equipment is needed for RTK surveying, the short answer is a capable GNSS receiver, a correction source and a practical way to collect, check and export field data. The right specification depends on whether the job is setting out, topographic survey, machine control, utility work or rapid site capture.
RTK, or Real-Time Kinematic positioning, uses carrier-phase GNSS measurements and live corrections to reduce the errors that affect standalone satellite positioning. When the solution is fixed and site conditions are suitable, an RTK system can deliver repeatable centimetre-level results in real time. That performance is not automatic: sky visibility, mobile signal, correction quality, datum control and operator procedure all matter.
The core equipment needed for RTK surveying
A professional RTK survey setup has four functional elements: a rover that measures position, a correction source that supplies reference data, a controller or application that manages the survey, and field accessories that keep the system stable and operational. In many cases, the rover and controller form a compact, connected package. The correction source may be a local base station or a network RTK service.
1. A multi-constellation GNSS RTK rover
The rover is the primary field instrument. Mounted on a survey pole, it receives signals from satellite constellations such as GPS, Galileo, GLONASS and BeiDou, then applies real-time corrections to calculate its position. For professional work, choose a receiver designed for multi-constellation and multi-frequency operation. More tracked signals improve the opportunity to maintain a fixed solution where visibility is restricted by buildings, trees or plant.
Receiver specification should be judged against the environments your teams actually work in. Key considerations include stated RTK horizontal and vertical accuracy, time to fix, tilt compensation, ingress protection, operating temperature, battery endurance and the quality of the internal radio and cellular modem. A receiver with IMU-based tilt compensation can speed up collection around walls, fences and obstructions because the pole does not need to be held perfectly plumb. It does not remove the need for sound checking procedures, particularly on control or setting-out work.
For UK survey workflows, it is also sensible to confirm support for the coordinate reference systems, transformations and grid settings required by your client or project. A precise receiver using the wrong coordinate system will still produce the wrong answer.
2. A correction source: network RTK or a base station
An RTK rover needs correction data from a reference receiver with a known position. The most common option is a network RTK correction service delivered over the mobile internet. The rover connects through a SIM card or paired controller, receives corrections via NTRIP and applies them while observations are taken. This is usually the most efficient choice for teams working across multiple sites, provided dependable mobile coverage is available.
A local base station is the alternative. It is another GNSS receiver placed over a known control point, or over a point established through an appropriate localisation procedure. The base transmits corrections to the rover by UHF radio or, in some configurations, through the internet. A base-and-rover kit is valuable on remote sites with weak mobile coverage, for isolated work areas, or when a contractor needs direct control of the correction source.
The trade-off is operational responsibility. A base must be set up correctly, protected from disturbance, powered throughout the survey and referenced properly. If its assumed coordinates are incorrect, every rover point will inherit that error. Network corrections reduce the field setup burden but introduce reliance on a subscription, mobile data and the network’s availability.
3. A field controller and survey software
The controller is where field measurements become usable survey information. This may be a rugged handheld data collector, a tablet or, for lighter duties, a mobile device running compatible software. Professional survey applications allow the operator to select coordinate systems, connect to corrections, monitor solution status, code features, stake out coordinates, navigate to lines and surfaces, and export results in the required format.
For topographic work, feature coding and linework collection can substantially reduce office processing. For setting out, the controller should support CAD or design data, clear cut-and-fill guidance and tolerances suited to the construction task. For asset capture, configurable forms can standardise attributes such as asset type, condition, material, photographs and inspection notes.
Do not select a controller purely on screen size. It needs a daylight-readable display, a responsive touch interface that works with gloves where required, sufficient battery capacity, stable connectivity and an operating system supported by the GNSS manufacturer’s software. The field workflow should also integrate cleanly with the office software used for CAD, GIS, design models or reporting.
4. Survey pole, mounting hardware and accessories
The pole may look secondary, but it is part of the measurement system. Use a rigid, calibrated carbon-fibre or aluminium survey pole with a clear height mark and a suitable bipod for static observations or repeatable control checks. The antenna height entered in the software must match the actual setup. A loose clamp, damaged pole tip or unverified pole length can undermine otherwise excellent GNSS results.
A practical field kit should include:
- spare batteries and charging equipment sized for a full shift;
- a protective case, cleaning materials and weather-appropriate covers;
- a SIM card and data plan when using network corrections;
- a radio antenna and cables when operating a local UHF base; and
- a tape measure, marker materials and basic control-point documentation.
For long days, high-output charging in the vehicle can prevent downtime. Battery planning is especially relevant in cold weather, where capacity can fall and tablet screens can become less responsive.
Choosing between a rover-only and base-and-rover RTK system
A rover-only system connected to a correction network is often the best commercial starting point. It is quick to deploy, reduces equipment carried to site and supports flexible working across a broad area. It suits routine topographic surveys, site verification, volume checks, utility mapping and many construction tasks.
A base-and-rover system gives greater independence and can be the better option for remote infrastructure, forestry, large rural estates and locations where mobile data is unreliable. It is also useful where a project has an established control network and the survey team needs a dedicated local reference. However, it requires more training, more setup time and disciplined control management.
Some organisations need both. A rover can use network corrections on accessible sites and switch to a local base where coverage or project requirements demand it. This approach is often more resilient than treating one correction method as suitable for every job.
Accuracy depends on more than the hardware
Published RTK accuracy figures are achieved under stated conditions, usually with a fixed solution, good satellite geometry and suitable correction data. A receiver may display a highly precise position while still being affected by multipath, where signals reflect from buildings, vehicles, metal fencing or water. Dense canopy and narrow urban corridors can also interrupt satellite tracking.
Operators should confirm that the receiver has achieved a fixed RTK solution before accepting critical points. Check measured control points at the beginning and end of the session, observe important positions more than once and investigate any discrepancy rather than averaging it away. For work tied to legal boundaries, engineering tolerances or third-party design control, establish the required verification procedure before mobilisation.
Vertical results deserve particular attention. GNSS measures height relative to an ellipsoid, while UK projects may require orthometric levels related to a recognised vertical datum. The correct geoid model, transformation and project settings must be applied consistently from field collection to final deliverables.
Equipment decisions by application
For construction setting out, prioritise fast fixed solutions, tilt compensation, reliable CAD stake-out tools and clear control verification. A rugged controller and strong support for design-file import will often have more value than adding unnecessary survey modes.
For land and topographic survey, feature coding, linework collection, repeatable pole setup and direct export to CAD or GIS are central. A rover with network RTK can provide an efficient daily workflow where mobile coverage is sound.
For forestry, utilities and asset inspections, select a receiver that performs well under partial canopy and pair it with data-collection forms that capture attributes consistently. GNSS may need to be supplemented by total station, mobile mapping or LiDAR where satellite visibility is poor or detailed geometry is required.
For drone ground control, the requirement is not simply an RTK rover. The team also needs a defined control strategy, stable targets where appropriate, coordinate-system discipline and independent check points. An RTK drone can reduce the amount of ground control required, but it does not remove the need to validate the final mapping output.
Build the workflow, not just the kit list
The best RTK purchase is one that supports the full route from control to deliverable. That means confirming correction coverage, coordinate reference requirements, controller software, export formats, staff training and a support route before equipment reaches site. LiDAR Tech UK can help organisations match GNSS hardware, correction workflows and survey software to the accuracy, environment and output requirements of their projects.
Before committing to a system, test it against a representative site and a real deliverable. A short field demonstration that proves fix reliability, coding speed and office compatibility will tell you far more than a specification sheet alone.