Knowing how to integrate GNSS with CAD is what turns site observations into drawings and design information that crews can use with confidence. The process is not simply a matter of exporting points from a rover and opening them in CAD. The coordinate reference system, datum, height model, coding structure and quality checks must all agree. If they do not, a drawing can look correct while being metres, or even millimetres, wrong on the ground.
For UK survey, construction and infrastructure work, the objective is clear: capture accurate GNSS positions, process them in the correct project coordinate system, and create CAD-ready data for design, verification or setting out. A controlled workflow reduces rework, protects dimensional accuracy and makes information easier to share between survey, engineering and construction teams.
Start with a defined coordinate strategy
Before collecting a single point, establish which coordinate system the project will use. This decision governs every subsequent import, export and field operation.
Many UK projects use British National Grid coordinates with Ordnance Datum Newlyn heights. Others use a local engineering grid, a site calibration, or a client-specific coordinate system based on existing control. GNSS receivers calculate positions in a global reference frame, commonly WGS84 or a closely related realisation. CAD drawings may instead be based on OSGB36, a local grid, or coordinates that have been translated and rotated to suit the scheme.
This difference is fundamental. A raw GNSS coordinate should not be assumed to match the coordinates in a CAD drawing. Confirm the following with the project surveyor, designer or principal contractor before mobilisation:
- the horizontal coordinate reference system and map projection;
- the vertical datum and required height type;
- the geoid model required to convert ellipsoidal heights to orthometric heights;
- the drawing units, typically metres;
- whether a local grid transformation or site calibration applies.
Where supplied control is available, occupy it with the GNSS rover and compare the observed position against the published values. This establishes whether the correction service, receiver configuration and transformation are producing the expected result. It also identifies control that may have been disturbed before it becomes a construction issue.
Configure GNSS for the project, not just the postcode
An RTK rover needs more than satellite reception to deliver construction-grade results. It requires a reliable correction source, correctly selected coordinate settings and a clear understanding of the accuracy required for the task.
Network RTK is often efficient for topographic surveys, asset capture and general setting out where mobile connectivity is dependable. A local base station may be preferable where the project requires independent control, mobile coverage is weak, or work is concentrated around a fixed site. Either method can perform well, provided the correction source and coordinate reference frame are compatible with the design data.
Set the receiver to record the point quality information that matters: fixed or float solution status, horizontal and vertical precision, epoch time, antenna height and correction age. For critical points, establish an acceptance threshold before fieldwork begins. A point that appears in the correct place on screen is not necessarily suitable for concrete works, structural setting out or legal boundary evidence.
Vertical control deserves particular attention. GNSS naturally measures ellipsoidal height, while drawings and levels are normally issued relative to a vertical datum. A correctly selected geoid model converts between them, but an incorrect model can introduce a consistent height error across the whole site. Check a known benchmark or control point rather than relying on a screen setting alone.
Prepare CAD data for field use
CAD data should be clean and intentional before it reaches the rover or field controller. Importing an entire consultant drawing, with title blocks, old revisions, external references and presentation layers, creates unnecessary risk and slows down field operations.
Create a field issue drawing containing only the features needed for the task. For setting out, this may include centre lines, kerb lines, pile positions, grid intersections, formation levels, building corners and nominated offsets. Use clear layer names and distinguish between design geometry, survey control and temporary construction features.
Check the drawing origin, units and coordinate values. A common failure occurs when a drawing is created near a local 0,0 origin but is treated as if it contains National Grid coordinates. Another is a millimetres-versus-metres mismatch. Both can send field data to the wrong location by a factor of 1,000 or more.
Where coordinates are very large, CAD software may show reduced display precision or introduce operational inconvenience. A local drawing origin can be useful, but only if the transformation to and from the GNSS coordinate system is documented and applied consistently. Never allow an undocumented shift to become the project standard simply because it made one drawing easier to handle.
Import GNSS observations into CAD
Most GNSS controllers export points as CSV, TXT, DXF or LandXML files. The best format depends on the CAD platform and the required deliverable. CSV is widely compatible and effective for point records with eastings, northings, levels, codes and descriptions. DXF is useful for basic graphical transfer. LandXML is often more appropriate for surfaces, alignments and civil design data.
For a surveyed feature, the coordinate order must be checked carefully. UK workflows commonly use easting, northing and elevation, but some software expects northing before easting. A swapped coordinate order may place data hundreds of kilometres away while still producing a valid-looking import.
Use feature codes consistently in the field. A code such as KERB, CL, FENCE or MH can be mapped to CAD layers, symbols and linework during processing. This improves productivity, but coding must match the project specification. Automated linework is only as reliable as the observed order, code definitions and surveyor’s judgement around changes in level, breaks in alignment and obscured features.
Once imported, compare the GNSS data with known control and existing surveyed detail. Look for systematic translation, rotation or height differences rather than correcting individual points to make the drawing appear acceptable. Systematic errors usually indicate a coordinate-system, calibration or datum problem that should be resolved at source.
Send CAD design geometry back to GNSS
The reverse workflow is equally valuable. Exporting approved CAD geometry to a GNSS controller allows field teams to set out points and lines without manually transcribing coordinates. This is useful for earthworks, drainage routes, building footprints, access roads, utilities and asset replacement work.
Use simple, unambiguous geometry for field setting out. Where a line has a specified offset, include the offset line in the field issue rather than expecting the operator to interpret a general arrangement drawing. Name key points clearly and avoid duplicate point identifiers across revisions.
Revision control matters. Field staff must know which drawing issue is live, when it was loaded and who authorised it. A sound process removes superseded files from the controller, records the design revision in the survey log and checks a small number of critical points against independent control before production setting out begins.
For complex civil work, consider whether the field software can work directly with alignments, profiles and surfaces rather than isolated points. A surface model can support cut-and-fill checks and formation verification, while alignments support chainage-based setting out. The right format depends on the controller software, project tolerance and the level of construction control needed.
Validate the workflow on site
A GNSS-to-CAD workflow should include checks at the start, during and at the end of each operation. Surveying is not a one-directional data transfer exercise. It is a controlled loop between field measurement, design information and independent verification.
Start by checking into known control. During the survey, re-observe a control point after a significant period, a battery change, a loss of RTK fix or a move to another area of the site. At the end, compare the CAD output against expected geometry, levels and tolerances.
Independent checks are particularly valuable when setting out structural elements, drainage inverts or interfaces between contractors. Use a second instrument, an alternative occupation or a check point not used in the original transformation. If the tolerance is tight, GNSS may not be the sole method required. Total stations, digital levels and conventional control networks remain appropriate where line of sight is available and millimetre-level confidence is needed.
Common integration problems and their causes
When GNSS points do not align with CAD, the cause is usually traceable. A uniform horizontal shift often indicates an incorrect projection, local-grid parameter or transformation. A uniform vertical difference is more likely to be a geoid, benchmark or height-datum issue. A scale error points towards incorrect drawing units or an unsuitable local calibration.
Poorly repeated results may be operational rather than computational. Tree canopy, buildings, cranes, reflective surfaces and restricted sky view can degrade GNSS performance. Network corrections can also be interrupted or unsuitable for the site location. In these conditions, establish reliable control with GNSS where sky visibility permits, then use a total station for detailed work in obstructed areas.
LiDAR Tech UK supports end-to-end workflows covering GNSS hardware, correction services, survey capture, CAD-ready processing and practical implementation advice. That joined-up approach is valuable where a team needs to standardise both the equipment and the data process across multiple sites.
Make coordinate control a project decision
The most dependable GNSS and CAD workflows are agreed before design files reach site and before survey data is issued to others. Define the coordinate system, validate against known control, keep drawings clean, manage revisions and retain a clear record of transformations and checks.
That discipline gives project teams more than faster data transfer. It gives them positions, levels and CAD deliverables they can rely on when decisions are being made on the ground.