8 Reasons RTK and DXF Don't Match | How to Deal with Coordinate System and Elevation Offsets
By LRTK Team (Lefixea Inc.)
Table of Contents
• 1. Coordinate system mismatch – the same point doesn't match on drawings
• 2. Differences in geodetic reference (datum) – shifts caused by old and new standards
• 3. Differences in unit systems – confusion over numerical scales
• 4. Coordinate transformation errors/omissions – data overlaid without converting between different references
• 5. Localization not performed – insufficient alignment to local coordinates
• 6. Axis tilt and scale differences – discrepancies that increase with distance
• 7. Errors due to misconfiguration – e.g., incorrect input of control point coordinates
• 8. Differences in vertical datum – elevation values do not match
• Summary
Have you ever had the problem of coordinates obtained by high-precision GNSS positioning (RTK) not lining up when overlaid on CAD drawings (DXF files)? You are not alone; many people have experienced this. Even if you survey with centimeter-level accuracy, if coordinate shifts cause points to be displayed in the wrong place on the drawing, it can lead to serious mistakes and rework.
In recent years, not only dedicated surveying equipment but also mobile RTK systems that combine smartphones with compact GNSS receivers have made high-precision positioning easily accessible to anyone.
However, no matter how high the positioning accuracy is, it is meaningless if the coordinates obtained with RTK do not match the coordinates in the design drawings (DXF). To prevent such "coordinate troubles", it is important to correctly understand the differences between the coordinate system of RTK positioning results and that of the design drawings, and to take appropriate measures.
In this article, we identify eight common causes why RTK and DXF coordinates do not match and explain how to address each one. With various RTK use cases in mind—from GNSS surveying equipment to smartphone-based systems—we cover practical issues you are likely to encounter, such as coordinate system and elevation discrepancies, configuration errors, and data conversion mistakes. The key points are organized clearly so that those involved in surveying and design can exchange data with confidence.
1. Coordinate system mismatch – the same point does not align with the drawing
The coordinates obtained by RTK positioning are, in principle, absolute coordinates based on a global geodetic reference system. In Japan, many RTK services output results as latitude/longitude and plane rectangular coordinates of the Japanese Geodetic Datum 2011 (JGD2011), but depending on the settings they can also be WGS84 geodetic coordinates (global coordinates). On the other hand, civil engineering and construction design drawings (DXF data) do not necessarily use a global geodetic reference. It is common to use a local coordinate system (a custom coordinate) that sets an arbitrary origin for each site, and the values on the drawings can be completely different from earth-scale coordinates. In other words, if the absolute coordinates provided by RTK and the coordinate system adopted by the drawings do not match, the numbers will not agree even for the same point, and the data will not align when overlaid.
For example, if an arbitrary coordinate origin that is valid only within a particular site is set to (0,0) on the drawing, comparing it with global coordinates obtained by RTK will result in a dramatically larger discrepancy. Also, in Japan’s plane rectangular coordinate system used for public surveying there is a zone number called the "◯-kei" for each region; if the zone number on the drawing differs from the one used by RTK, the reference origin will be shifted and offsets on the order of several hundred kilometers can occur.
Countermeasure: The most basic solution is to unify the coordinate system. Before starting surveying, check the coordinate system used by the project's drawings, and, if possible, configure the RTK receiver and positioning app to output in the same system. For example, if the drawings adopt the "JGD2011 plane rectangular coordinate system, zone ◯", set the RTK to measure and output coordinates in that same zone. If the drawings were created in a proprietary local coordinate system, you will need to convert the RTK results later into that local system (this is handled by the localization process described below). In any case, by ensuring that both the RTK and the drawings produce values based on a common coordinate reference, the planar positional offset when overlaying them can be eliminated.
2. Differences in Geodetic Reference (Datum) – Discrepancies Arising Between New and Old Standards
Large positional discrepancies can also occur between design data and RTK positioning results when there are differences in the geodetic datum (datum). In Japan, in 2002 the official geodetic datum was switched from the former "Old Japanese Geodetic System (Tokyo Datum)" to the "World Geodetic System (JGD2000/2011)". Therefore, old drawings and cadastral maps produced before that may use the old datum. Because there is a persistent regional offset on the order of hundreds of meters (hundreds of ft) between the old datum and the current world geodetic system, for example if a drawing uses coordinates in the old datum while the RTK outputs coordinates in JGD2011, the same point can be displaced by hundreds of meters (hundreds of ft).
This is not limited to Japan; coordinate shifts caused by differences in geodetic datums also occur overseas. For example, if older North American data are recorded relative to NAD27 or NAD83 while GPS positioning is processed in WGS84, forgetting to convert will cause positions on the map to not align.
Countermeasure: It is necessary to unify the geodetic datum being used or to convert it appropriately. When handling drawings based on an older datum, confirm the reference system with the creator and apply transformation parameters to convert the coordinates to the new datum (the world geodetic system). In Japan, the Geospatial Information Authority of Japan publishes transformation formulas and parameters for old geodetic datum ⇔ the world geodetic datum, so you can use those to convert coordinates in old drawings to JGD2011. Conversely, if an RTK receiver requires the old geodetic datum, enable the corresponding transformation in the positioning software settings. In short, if the data and drawings are aligned to the same geodetic datum, large coordinate discrepancies caused by datum differences will be resolved.
3. Differences in Unit Systems – Misunderstanding of Numerical Scales
Mismatch of unit systems is another point that must not be overlooked. If the units of coordinate values on CAD drawings are millimeters (mm (in)) rather than meters (m (ft)), the surveying values obtained by RTK (usually in meters (m (ft))) will not align and will be interpreted as a value off by a factor of 1000. For example, if a coordinate on a CAD drawing appears as "(12000, 5000)" and it is recorded in millimeters, the actual position is "(12.000 m (39.370 ft), 5.000 m (16.404 ft))". However, if you fail to notice the unit difference and treat them as meters, you will end up plotting the point at a completely wrong location on the drawing.
Overseas, there are scale errors caused by confusing feet (ft) and meters (m (ft)), but in Japanese design sites confusion between m (ft) and mm (in) is particularly likely.
Countermeasure: It is important to check the units of drawing data in advance and convert them as necessary. When exporting or sharing CAD data as DXF or similar, make sure you know what unit system the coordinate values are in. If the units differ, convert them to match the survey data (for example: mm (in)→m (ft), reduce the numerical values by a factor of 1/1000) before comparing. Some CAD or GIS software allow you to specify the units on import or to scale the entire drawing, so use those functions to make the unit systems consistent.
4. Coordinate transformation mistakes and omissions – Data overlaid with different reference frames
Data mismatches also frequently occur because coordinate system transformations are forgotten or done incorrectly. Ideally, if coordinates obtained by RTK are recorded in a particular reference system, you should convert them to the coordinate system of the design drawings before using them. However, if that conversion is neglected and data from a different reference are simply overlaid, the positions naturally will not match. For example, if RTK positioning results remain in WGS84 latitude/longitude but the drawings are in a local coordinate system, forgetting to convert and plotting them will appear as a discrepancy of tens of meters or more (tens to hundreds of feet or more).
This "forgotten coordinate transformation" can also occur due to misconfiguration between software. For example, when overlaying data in GIS software, there are cases where alignment becomes offset because the spatial reference (coordinate system information) of each dataset was not specified correctly. CAD drawings (DXF) basically do not contain metadata about the coordinate system, so when importing into a GIS the user must specify which coordinate system the geometry’s values are in. If the drawing coordinates are mistakenly read as latitude/longitude data, they will be displayed in a completely different location in the GIS, and if layers are overlaid while the projection (map projection) differs, subtle errors in angle and scale will arise.
Countermeasure: It is essential not to omit the coordinate transformation process. When exchanging data, both parties should confirm the reference coordinate system, and if they differ, always perform the appropriate transformation before overlaying. In GIS, correctly set the coordinate reference system (CRS) for each layer, and when overlaying layers with different coordinate systems, use the software's coordinate transformation tools to unify them. When placing a CAD drawing with arbitrary coordinates onto geographic coordinates, you can also fit it by performing translation, rotation, and scale adjustment (affine transformation) based on known points. In short, if you find that coordinate systems differ between datasets, make it a strict habit to always carry out the prescribed coordinate transformation processing before integrating them.
5. Localization Not Implemented – Insufficient Alignment to Local Coordinates
If drawings are created in a site-specific local coordinate system, simply applying RTK positioning’s absolute coordinates will not produce correct positions. If you use GNSS-derived coordinates without any correction for a coordinate system based on the site’s own origin and orientation, points measured may be plotted on the drawing tens to hundreds of meters (tens to hundreds of ft) away from their actual locations. To prevent this, a process called localization (coordinate alignment) must be performed to fit GNSS coordinates to the local coordinate system. If coordinate transformation based on known control points is not carried out (i.e., localization is neglected), that omission will cause coordinate misalignment.
Localization uses points on site whose exact coordinate values are known, such as known control points and boundary stakes. At least two known points (ideally three or more) are observed with RTK, and by comparing the coordinates obtained with GNSS to the coordinates on the drawings, the planar offset amounts in the east–west and north–south directions (displacements in X and Y), the rotation angle, and, if necessary, differences in scale are calculated. By applying those corrections to the RTK positioning results, all measured points can be matched to the drawings’ local coordinates. This procedure is called localization (also known as site calibration), and it is an indispensable process for surveying in a local coordinate system.
Countermeasure: Ensure that localization using known points is performed reliably. In projects that use a local coordinate system, measuring multiple known points at the start of surveying and using them for coordinate alignment will allow all subsequent observation points to be recorded in the correct coordinate system. Even if there are few known points, align with at least two points and, if possible, correct for subtle axis misalignments and scale differences (this correction is increasingly important on larger sites). After localization, it is also effective to measure a separate control point to verify that the data matches the drawings. By rigorously following these steps, RTK positioning data can be overlaid precisely onto drawings even in a local coordinate system.
6. Axis tilt and scale differences – deviations that increase with distance
Even if you align the coordinates at only one point, if there are differences in the rotation of the coordinate axes or in scale, the discrepancy grows with distance. For example, if the drawing's X and Y axes are set tilted by a few degrees from true north, aligning RTK coordinates at a single point will cause the east-west and north-south directions at other locations to be slightly twisted and not match. Also, on sites where the terrain extends over a wide area, differences in the projection scale of the plane rectangular coordinate system and scale errors due to elevation can produce slight differences between the drawing and the actual site even for the same distance. If these rotation and scale differences are ignored, positional misalignment becomes more pronounced farther away, causing problems such as the ends of the drawing not matching.
Countermeasure: By aligning coordinates at multiple points, you can also correct differences in axis orientation and scale. In the localization work mentioned in Cause 5, use two or more known points to calculate rotation angles and scale factors and apply them to the data. This will enable high-precision alignment across the entire site. Especially on large sites, aligning to only one point is insufficient, so even if it requires extra effort, perform adjustments using multiple control points.
7. Errors Caused by Configuration Mistakes – Such as Incorrect Entry of Reference Point Coordinates
Even when using advanced surveying equipment, coordinate shifts can occur due to human input errors. A typical case is entering the base station (reference point) coordinates for RTK surveying incorrectly. The base station should be set with an accurate known coordinate, but if that value is registered incorrectly, all positioning results calculated for the rover (mobile station) based on it will have a consistent offset. For example, if you reverse the sign of the longitude (east/west), mistype a digit, or swap latitude and longitude at the reference point, positioning can be performed with erroneous coordinates off by tens of meters. Because the positioning will appear to operate normally immediately after setting up the base station, you may continue working without noticing the mistake, and later, when plotting into CAD, you might turn pale thinking, "All the measured points are shifted!" — such a situation can occur.
There are also cases where errors in the receiver or software output settings cause discrepancies. For example, the output may have been in a different coordinate system than intended, the reference height may have been set incorrectly, or known point coordinates may have been registered incorrectly; a single configuration mistake can shift both the horizontal position and the elevation.
Countermeasure: Checking settings and double-checking before surveying is essential. When entering known-point coordinates into the base station, recheck with the documentation to ensure you have transcribed the digits and signs accurately. If possible, after configuration, try a test measurement on another known point or a reference mark to verify it matches the drawings. Also check in advance setting items such as the GNSS receiver’s output coordinate system and height reference, and confirm they conform to the standards required by the project. These settings may seem trivial, but neglecting them can cause large errors in the results, so exercise the utmost care.
8. Differences in vertical datums – Elevation values do not match
Differences in the reference for height (elevation), not just in planar position, can also cause RTK values and the values on drawings to disagree. The height that GNSS (RTK) directly measures is usually the height from the Earth’s ellipsoid (ellipsoidal height). On the other hand, the elevations used in civil and architectural design drawings are often heights above mean sea level (orthometric height), based on a reference surface corresponding to the sea surface called the geoid. There is a regional difference of tens of meters (tens of ft) between ellipsoidal height and orthometric height (the geoid height). Therefore, it is natural that directly comparing the height given by RTK with the elevation on the drawings will not match.
For example, in Japan the elevation system that uses the Tokyo Bay mean sea level as the reference (the so-called Tokyo Bay Mean Sea Level = TP) is used, but the ellipsoidal height obtained by RTK can differ by about 20-40 m (65.6-131.2 ft) depending on the region. If this is not corrected, a large discrepancy will occur between the heights on drawings and the heights measured in the field.
Countermeasure: To align height references, use known benchmarks or apply corrections using a geoid model. If there is a benchmark on site with a known elevation, measure it with RTK and calculate the difference from the ellipsoidal height obtained. By adding or subtracting this difference (the regional geoid height) to the heights of other observation points, you can match all points’ heights to the elevation datum used in the drawings. Also, recent GNSS receivers and positioning apps have a geoid model covering all of Japan built in and include a function that automatically converts ellipsoidal height to elevation (height above sea level). Actively using such functions allows you to obtain on-site height data that uses the same reference as the drawings immediately, reducing the effort required for post-processing.
Summary
Coordinate discrepancies between RTK surveying and CAD drawings (DXF) can arise from various factors such as differences in coordinate systems or datums and setup errors. However, by implementing the countermeasures outlined in this article, many troubles can be prevented. Before surveying, confirm the coordinate system, units, and vertical datum, and on site ensure consistency between positioning data and design drawings by performing coordinate alignment and verification using known points. If you do not neglect careful preparation and checks, occurrences of “I measured with RTK but the positions don't match!” can be steadily reduced.
In recent years, solutions that can greatly reduce the effort of such coordinate alignment have emerged. One of these is LRTK, a high‑precision GNSS device that can be attached to and used with an iPhone. By using LRTK, you can simply pre‑enter known local point coordinates into the app and perform localization (conversion to the local coordinate system) with a single tap. Without having to think about complex coordinate calculations, the points collected on site are recorded from the start in the same coordinate and elevation systems as the design drawings, so there is little need to convert or correct coordinates afterward. Even without being an experienced surveyor, by utilizing these new tools you can now smoothly overlay high‑precision RTK positioning data onto design CAD drawings. For daily operational efficiency and mistake prevention, be sure to incorporate the latest technologies.
Next Steps:
Explore LRTK Products & Workflows
LRTK helps professionals capture absolute coordinates, create georeferenced point clouds, and streamline surveying and construction workflows. Explore the products below, or contact us for a demo, pricing, or implementation support.
LRTK supercharges field accuracy and efficiency
The LRTK series delivers high-precision GNSS positioning for construction, civil engineering, and surveying, enabling significant reductions in work time and major gains in productivity. It makes it easy to handle everything from design surveys and point-cloud scanning to AR, 3D construction, as-built management, and infrastructure inspection.


