9 Checks to Make When RTK-Measured Coordinates Don't Match

Table of Contents

• First, check how the deviation manifests at the known points.

• Confirm the coordinate system and geodetic datum settings

• How to select reference points and verify known-point information

• Confirm the inputs for antenna height and instrument height.

• Check the types of correction information and their delivery status

• Check the communication status and the delay of the correction data

• Verify satellite reception status and the stability of the Fix

• Check for multipath and shielding/obstruction caused by the surrounding environment.

• Check for differences between equipment configuration and on-site operations

• Summary

First, check how the deviation manifests at known points

When you feel that the coordinates measured with RTK are not matching, the first thing you should do is not to start guessing the cause and changing settings. First, check known points to determine how the offsets are occurring. If you skip this step, whether the cause is the coordinate system, the antenna height, or communication or satellite reception will get mixed together, making it difficult to isolate the problem.

What I want to check is whether the offsets are always in the same direction and amount, or whether they vary each time. For example, if every point you measure is displaced tens of centimeters (several inches to a few feet) to the east, you should suspect an error in the coordinate system, transformation settings, or the known-point information. On the other hand, if repeated measurements of the same point scatter within a range of a few centimeters to tens of centimeters (about an inch to a few feet), then unstable fixes, communication outages, satellite reception, or the surrounding environment are more likely to be the cause.

In this initial check, if possible we use known points or control points near the site, or reliable existing benchmarks. We take multiple observations there to see whether the horizontal position shifts consistently in the same direction, whether only the height differs significantly, or whether the results change depending on the time of day. If only the height is significantly off, you should suspect an antenna height input error, the handling of geoid height, or confusion between orthometric height and ellipsoidal height. If both the horizontal position and the height shift together by a consistent amount, it is more likely a difference in the coordinate system, the established coordinates of the known points, or the settings of the correction source.

The basic approach to isolating the cause is to first make continuous observations at one known point, and then check whether the same trend appears at another known point. If only one point doesn't match, there may be a problem with that point's measurements themselves. Conversely, if the same trend appears at multiple points, it becomes more likely that the cause lies in the settings or operation on the observation side.

When troubleshooting RTK issues, it's important not to be vague about what and how much has shifted; instead, view it in three parts: the planar (horizontal) direction, the height (vertical) direction, and changes over time. This initial observation will correctly guide the subsequent order of checks.

Confirm the Coordinate System and Geodetic Datum Settings

Once you have determined how the discrepancies appear at known points, the next thing to check is the coordinate system. In RTK situations where coordinates do not match, differences in the coordinate system or geodetic datum settings are often the cause before insufficient equipment performance. In particular, if the horizontal position is stable but consistently offset by a fixed amount, you should prioritize checking this.

Here, the items to check are whether the data use the World Geodetic System or legacy results, whether the zone number of the plane rectangular coordinate system is correct, whether latitude/longitude display and plane coordinate display have been confused, and whether the geoid model and elevation conversion settings are correct. At some sites, the drawings may be in plane rectangular coordinates while the receiver still handles latitude/longitude, or even when using the same plane rectangular coordinate system they may be operating under a different zone number. In this situation, even if the positioning itself is normal, the coordinates will not match.

One common characteristic of such shifts is that planar positions are displaced together by large amounts. The displacement can be several meters (several ft) or more; this should be considered not so much an error in satellite reception as a difference in how the reference is defined. Also, if only the height is consistently offset, the difference between ellipsoidal height and orthometric height, or the presence or absence of geoid correction, may be influencing the results. In the field, there are cases where people feel "the height is always off by tens of centimeters (several in)," but often it is not an equipment malfunction but a confusion between types of height.

To isolate the issue, first clarify which coordinate deliverables should be used on site. Check the coordinate system and the definition of heights adopted in the contract drawings, reference point result tables, known-point report forms, past observation data, etc. Then verify that the settings of the receiver, controller, surveying app, and output files all match. Even if the equipment itself is configured correctly, different settings can be applied when exporting CSV or DXF, so you should verify everything through to the final output.

One thing to be particularly careful about on site is when settings used at another site are left as-is. In practice, it's quite common to have used a coordinate system for a different area yesterday and come to a new site today without switching the system number. Verifying equipment settings is not merely a formality; it is a basic action that must be performed at the start of every site.

How to Choose Control Points and Verify Known Point Information

After the coordinate system, the next thing to check is the reference point itself. With RTK you can achieve high-precision positioning by receiving correction information, but if the information for the reference points or known points used for comparison is incorrect, the results will of course not match. Here, the selection of reference points, verification of the results table, mix-ups of point names, and checking the update history are important.

What you need to check first is whether the known point you're using is actually the one that should be adopted at that site. Even if old stakes or pins remain, they are not necessarily valid as the current control standard. They may have been physically moved due to pavement renewal or construction, and there may be multiple points with similar names within the same site that are easily confused. If you trust only the coordinate values on the paperwork and start surveying without checking the physical condition of the point, you'll end up with major rework later.

Typical misalignments include patterns where only some points are significantly off, or where the site as a whole aligns reasonably but specific points deviate abnormally. In such cases, the problem may not be with the receiver but with the physical known points or their result information. There can also be cases where only the elevation results of the known points are outdated, or where the horizontal results are correct but only the height results have not been updated.

An effective method for isolating the cause is to verify against at least two known points. If you make a judgment based on only one point, you are likely to mistake an anomaly of that point itself for an observation error. The basic idea is that if the same trend appears across multiple points, suspect the observations; if only one point is anomalous, suspect the reference point. Also, when the values in the results table are entered manually, you should check for digit shifts and sign errors. Because planar coordinates are long strings of numbers, even a single-digit input error can produce a large displacement.

Furthermore, if you are using localization or site coordinate transformations, you should also review whether the selection of the known points that form their basis is appropriate. If you perform the transformation using only points with biased positional relationships, it may fit locally but the misalignment can grow elsewhere. Information about the reference points is the foundation for determining whether the receiver is measuring correctly. If that foundation is unclear, no matter how high-performance the RTK is, it cannot be evaluated properly.

Verify the antenna height and instrument height inputs

When coordinates don't agree in RTK, a common but easily overlooked cause in practice is an input error in the antenna height. This check is essential, especially when a vertical offset appears as a consistent amount. Beginners tend to suspect satellites or communications, but in reality basic issues such as how the instrument is held, the pole height, or differences in input units are often the cause.

What I want to confirm here is from which point to which point the antenna height is being entered, whether it is slant height or vertical height, whether the pole height is re-entered after being changed, and whether the receiver's antenna phase center is correctly configured on the device. Even if a pole looks like the same 2 m (6.6 ft) pole, if the measured value and the entered value do not match, the height result will be off.

A common characteristic of such offsets is that the height is shifted by an almost constant amount. For example, if the height is 5 cm (2.0 in), 10 cm (3.9 in), or higher or lower by the amount of the pole extension no matter where you measure, that strongly suggests an issue with the antenna height. When the planar position is relatively correct but only the height is off, this is the first place to check. Also, if you were observing with the pole tilted, the position itself can be displaced. Even equipment with a tilt-compensation function can show errors if the compensation is not enabled, the calibration is off, or the operating conditions fall outside the supported range.

To isolate the cause, first take consecutive measurements on a known point without changing the antenna height, then deliberately change only the input value and observe the response — this makes the cause easier to see. If the measured height changes by the same amount as the change in the input value, you can tell that the antenna height setting is directly affecting the results. Also, if another operator measures the same point with the same equipment and gets different results, there may be differences in the input values or in how the pole is handled.

On site, operational mistakes also occur, such as working with a 2 m (6.6 ft) pole in the morning and extending it in the afternoon without changing the input. Alternatively, when the receiver model is changed and the antenna reference position shifts, operators may still enter data with the same assumptions as before. Antenna height may appear to be a simple item, but it is a very real cause of coordinate discrepancies. If you are troubled by height inconsistencies, this is the first thing you should check.

Confirm the types of correction information and their distribution status

RTK's high precision is only realized when correction information is available. Therefore, if the type or delivery status of the correction information is not as expected, even when a "Fix" indication is shown the results may be unstable or may not reach the accuracy anticipated in the field. When coordinates do not match, you must always verify which correction information you are currently receiving.

Points to verify include whether you are using network-based corrections or a single-reference-station correction, whether you can connect to the intended mount point, whether the correction data format is compatible with the device, and whether the correction information is up to date and being received continuously. Even if it appears to be connected, it may actually be set to a different streaming configuration or the correction data updates may have stopped.

A characteristic of deviations that tend to occur is that their reproducibility varies with the time of day and location. If measurements agree at one time but shift at another, are unstable immediately after work begins, or lose accuracy toward the edges of the site, suspect the quality or consistency of the correction data. Also, if the type of correction is not appropriate for site conditions, the vertical (height) component can be more unstable than the horizontal (planar) component.

In troubleshooting, first check the reception status of correction information on the controller screen and in the logs. A display that simply says "connected" is not sufficient; examine the correction update interval, the data age, the time to Fix, and the stability of the solution. Next, if possible, switch to another correction service or a different communication method and observe the same point to compare whether the results improve. If the results improve, it becomes more likely that the cause lies in the correction path rather than in the receiver unit itself.

Also, at some sites, correction settings from previous work may remain, causing the receiver to connect to an unintended base station. Workers may overlook this if they assume "it's fine because it shows Fix," but in RTK the Fix indicator alone does not guarantee quality. Only by checking the contents and stability of the corrections can you judge the reliability of the positioning results.

Check communication status and correction data delay

Even if the correction information itself has no problems, if the communication receiving it is unstable, the coordinates will be difficult to match. In RTK, communication quality may appear to be an inconspicuous backstage factor, but in reality it is an important element that affects the stability of the solution. Especially in network RTK, poor communication conditions can interrupt the correction data, causing the solution to drop from Fix to Float or to repeatedly reinitialize.

What we want to check here are the mobile network signal conditions, whether there are communication dropouts, the latency of correction data, the stability of Bluetooth or cable connections, and device-side power-saving settings or background restrictions. In the field, the communication condition of the smartphone or tablet is often worse than that of the receiver itself, and correction data may only be received intermittently.

Typical deviations include phenomena such as the measured value changing slightly each time the same point is measured, sudden large jumps, inability to maintain a Fix, and instability for a while after reconnecting. If communication outages occur repeatedly even for short periods, operators may continue observations in an unstable state without noticing. As a result, although measurements may appear to have been taken correctly, the coordinates do not match when compared later.

To isolate the problem, first check the communication status display and see whether correction data updates are continuing. Next, while staying in the same location, change only the communication path—swap the communication terminal, change the SIM, try an external antenna or a different line—and compare. Also, if you are using a Bluetooth connection, suspect the distance to the device, interference from other equipment, and instability caused by continuous use. If the wireless connection is unstable, both the correction data and observation control tend to be interrupted.

In practice, communication quality can suddenly drop in the shadows of buildings in urban areas, in mountainous regions, below slope faces, or near tunnels. Even if there are no problems in the morning, moving the work position even slightly can change the connection status. When coordinates don't align, it is important to check communications as carefully as you check the satellites, because RTK is a system in which positioning and communications are integrated.

Confirm satellite reception status and Fix stability

After communications, the next thing to check is satellite reception itself. RTK is a high-precision method, but it will not be stable without a sufficient number of satellites and good reception conditions. When coordinates do not match, judging solely by whether the Fix indicator is displayed is dangerous. Even if it shows a Fix, if that Fix is not stable, the results will vary.

What to check includes the number of satellites in use, the placement of each satellite, the strength of received signals, the frequency of switching between Fix and Float, the initialization time, and positioning quality indicators. It is important not only to have a sufficient number of satellites but also how they are distributed across the sky. Even if there are many satellites, a biased distribution can worsen the geometric conditions of the solution and reduce accuracy.

A common characteristic of offsets that occur easily is that they vary rather than occur in a consistent direction. If the same point shifts slightly even when measured again shortly afterward, or if it shows "Fix" but moves by several centimeters (a few inches) to a dozen or so centimeters (about 4–8 in) upon re-observation, there may be a problem with the stability of satellite reception. Also, if conditions are good in the morning but poor in the afternoon, or if only a corner of the site is unstable, the satellite visibility conditions may be a factor.

In isolation testing, start by continuously observing at a known point for a set period to check how stable the solution is. Then move to an open-sky location and compare. If there is a clear improvement in the open area, you can conclude that reception conditions or the surrounding environment are having a strong effect. Also, if simultaneous observations with a different receiver model show differences, that will reveal differences in device performance or antenna conditions.

A common mistake beginners make is treating the "Fix" indication as absolute. In RTK, whether it is fixed is important, but that alone is not sufficient. You need to consider the time it takes to reach Fix, the Fix maintenance rate, any jumps in the solution during observation, and the frequency of reinitializations — only then can you tell whether the quality is suitable for field use. When coordinates don't match, you need to look at the overall stability of the observations, not just a single character on the display.

Check for multipath and obstructions caused by the surrounding environment

Unstable satellite reception can often be strongly influenced by the surrounding environment at the site. In RTK, even when you think the sky is visible, buildings, trees, guardrails, slopes, heavy machinery, metal fences, water surfaces, and the like can disrupt reception and cause coordinates to be off. Beginners in particular tend to worry only about visible obstructions, but multipath from reflections is hard to detect visually and can be troublesome.

What you need to check is not only how open the sky is overhead, but also whether there are nearby reflective surfaces, whether there are metal objects close to the receiver, and whether heavy equipment or vehicles are moving and changing the reception environment. For example, next to buildings, satellite signals from certain directions can be blocked, and reflections off walls can further disturb the signal. In this condition, measurements taken at the same point will not be stable.

Common offsets include phenomena such as becoming unstable only at certain locations on the site, values changing depending on the time of day or the presence of nearby vehicles, and gradual drift in both horizontal position and height. If it matched at a known point but suddenly stops matching as soon as you move near a structure, you should strongly suspect the influence of the surrounding environment. Also, under trees the reception conditions can change with the condition and moisture of the leaves, and seasonal or weather differences can affect the results.

The basic method for isolating the cause is to slightly change the observation position and compare. Move a few meters (a few ft) and re-observe from an open spot to see whether the readings stabilize. If it improves, you can conclude that it's likely caused by the environment rather than equipment settings. Also, keeping photos of the surroundings and notes during observation makes it easier to review the causes of any deviations later.

In practice, it's important not to try to push through site conditions using RTK alone. At locations where signal obstruction is severe, it is safer to use surveying instruments that rely on different methods or to supplement with auxiliary observations. RTK is convenient, but it is not a cure-all. Understanding how the surrounding environment affects positioning accuracy is the quickest way to reduce coordinate discrepancies.

Confirm the differences between equipment settings and on-site operations

Up to this point, we have checked, in order, the coordinate system, reference point, antenna height, correction information, communications, satellite reception, and the surrounding environment. If the coordinates still don't agree, the last thing to review intensively is differences in device settings and field operations. Even when using the same receiver, if results vary between operators or from day to day, the cause is often hidden in this area.

There are many items to check. For example, differences in receiver firmware versions, differences in controller app settings, differences in positioning modes, whether tilt compensation is enabled or disabled, settings for averaged observations, log storage formats, the application status of localization, initialization procedures before starting observations, whether matching to known points is performed, methods for verifying pole verticality, the duration of observations, and so on. Even if the equipment itself is functioning normally, if settings and operations are not standardized, the results will not be consistent.

Common characteristics of discrepancies that tend to occur are differences depending on the operator, mismatches with data from other crews, and changes in procedures between morning and afternoon even at the same site. For example, if one operator begins the main observation after checking known points while another starts working immediately upon arriving on site, there will be differences in initialization stability. Likewise, if one person adopts observations averaged over several seconds while the other records instantaneous values, the way the results vary will differ.

To isolate the issue, it is effective to lay out the observation procedures in writing and visualize who is doing what and where. Coordinate mismatches may not be resolved by looking only at the equipment. In reality, there are many cases where people think they are using the same device, but the settings screens or work procedures differ between individuals. If you standardize and compare procedures—pre-observation checks, known-point checks, communication checks, Fix stability checks, observation time, and re-observation conditions—the differences will become apparent.

Also, in field operations, rushed work generates errors. Actions such as taking measurements immediately after obtaining a fix, being lax about checking pole leveling/centering, omitting verification against known points, or proceeding despite communication failures—all of these cause coordinate discrepancies. RTK is convenient in real time, but it is also a tool that makes it easy to rush decisions. That is why standardizing procedures is important.

Whether the coordinates ultimately match is not determined solely by the receiver’s performance. It is necessary to choose the correct coordinate system, verify using the correct reference points, enter the antenna height correctly, stabilize corrections and communications, and operate using the same procedures while monitoring the satellites and the surrounding environment. In other words, RTK accuracy is produced by both the equipment and the operation.

Summary

When coordinates measured with RTK don't match, rather than chasing causes at random, it's important to isolate the problem by following the sequence of checks to be performed on site. First, observe how the measurements deviate at known points to determine whether the offset is a consistent amount or whether the errors are scattered. Then check the coordinate system, reference points, and antenna height to see if there is an error in the reference itself. Next, inspect correction data, communications, and satellite reception to confirm that a stable RTK solution is being obtained. Finally, assess the influence of the surrounding environment and identify any differences in equipment settings or field procedures.

The reason this order is important is that skipping the checks in earlier steps will make later judgments inconsistent. For example, improving only the communications won’t solve the root cause if the coordinate system is different, and looking only at the number of satellites won’t reconcile the height if the antenna height is incorrect. Conversely, by verifying each step in sequence, you can narrow down the cause with a high probability.

RTK coordinate discrepancies are not necessarily due only to difficult theoretical problems. In the field they often result from a combination of basic factors—leftover settings, mixed-up point names, input errors, unstable communications, and variations in observation procedures—so it is important not to hastily assume a single cause but to methodically work through and eliminate each item to be checked one by one.

When you're a beginner, it's easy to be confused when a 'Fix' indication appears but the coordinates don't match; in RTK, behind an apparently normal display there can be discrepancies in the coordinate system, corrections, communications, environment, or operation. By making it a habit to check known points, standardizing pre-observation setup checks, and establishing a routine to review anomalous values after work, you can greatly reduce troubles caused by coordinate mismatches.

To use RTK stably, more important than choosing high-performance equipment is following the proper order of checks. Especially when coordinates don’t match, the most reliable solution is not to hastily keep changing settings, but to verify things in order starting from the reference.