What causes RTK correction data to be cut off? 6 communication countermeasures

Table of Contents

• What happens when RTK correction data is lost?

• Main causes of RTK correction data dropouts

• Communication measure 1 Check the signal conditions in advance

• Communication measure 2: Review devices and communication settings

• Communication Measure 3 Adjust operations to suit the on-site environment

• Communication Measure 4: Establish a system to enable rapid reconnection for correction reception.

• Communication measure 5: Standardize observation procedures to reduce human error

• Communication Measure 6: Design equipment configurations that minimize work stoppages even when communications are unstable

• Summary

What happens when RTK correction data is lost?

When using RTK on site, even if positioning itself appears to continue, reception of correction data can stop midway, causing the expected accuracy not to be achieved. What is troublesome for practitioners is not only cases where communication becomes completely impossible. Even when coordinates appear to be obtained, there are cases in which accuracy has unknowingly degraded because corrections are not being received consistently. Especially for tasks that require accurate position information in a short time—such as as-built verification, staking out, site-condition assessment, and temporary works and construction management—the interruption of correction data greatly affects both work efficiency and reliability.

RTK is not a positioning method that relies solely on signals received from satellites; it is a system that achieves high accuracy by using correction information sent from a reference station. Therefore, it assumes that correction data will be continuously received. This is a major difference from typical use of location information. Because the key to improving positioning accuracy depends on communications, any disruption in the communication environment directly leads to degradation in positioning quality.

There is not just one phenomenon that occurs when correction data is lost. Sometimes the fixed solution cannot be maintained and accuracy degrades, while other times reinitialization takes time and disrupts the work tempo on site. Furthermore, if operators continue observations without sufficiently checking the correction reception status, they may later notice coordinate scatter and inconsistencies and need to remeasure. Such rework not only simply wastes time but also affects overall site scheduling and coordination with other trades.

Also, interruptions in correction data do not necessarily occur only in mountainous areas or places with weak signals. Even in urban areas, signal reception can become unstable near buildings or structures, in underground spaces, in locations with heavy movement of construction equipment or vehicles, or when communication devices are poorly configured. In other words, the problem of correction data dropouts is not limited to special sites; it is a practical issue that can occur anywhere RTK is used routinely.

That is why it is important not to view the causes of correction data loss narrowly as a communications-only problem. In reality, radio signal conditions, device settings, observation posture, operational procedures, equipment configuration, and on-site decision-making are all intertwined. In this article, after organizing the typical causes of RTK correction data loss, we explain in detail six communication measures that can be readily implemented on site. By organizing not only the theory but also how to prevent loss in practice and how to recover when it occurs, it becomes easier to achieve stable operations.

Main causes of RTK correction data loss

When trying to understand why correction data drops out, the first thing to note is that the problem does not necessarily originate in a single place. In the field, people often stop after suspecting only the communication line, but in reality instability is frequently caused by a combination of multiple factors. If you address the issue without properly isolating the causes, you will end up repeating the same malfunction over and over.

One common cause is insufficient mobile network signal strength. In mountainous areas, valley-shaped terrain at development sites, near slopes, under bridges, in structures close to the ground, or inside temporary enclosures, communications can be more unstable than they appear. Even if the device's display shows it is connected, reduced data rates or repeated brief dropouts can prevent continuous reception of correction data. Because RTK can be affected by communication interruptions as short as a few seconds, you cannot be certain everything is fine just because general business messaging or map display functions are available.

The second is confusing the satellite reception environment with the communications environment. In locations where the sky is not open, satellite reception conditions worsen, but such locations are often also unfavorable for communications. Under elevated structures or next to buildings, both satellite reception and communications tend to become unstable, making it difficult for operators to determine which is the primary cause. As a result, they may suspect only the antenna when the problem is actually with the correction data, or conversely, only review communication settings when the satellite environment is poor, leading to mismatched countermeasures.

The third is misconfiguration on the device side. If power-saving settings are too aggressive, background communications are restricted, the screen turns off or communication is suppressed after a certain period, or reconnection behavior does not operate properly, correction reception is likely to stop while working in the field. In particular, when a device used for everyday purposes is reused as-is for work, settings that are adequate for general use may be insufficient for RTK operations.

The fourth is the handling of connection endpoint information and authentication. If the connection settings for receiving correction information, login credentials, choice of delivery method, the connection sequence at the start of observations, and so on are unclear, on-site reconnection will take time. In configurations that do not automatically recover after a communication drop, operators must check multiple items on the spot, which lengthens the time to recovery.

The fifth is the on-site operations themselves. If you do not check communication status while moving, skip pre-observation test connections, fail to set thresholds for reception quality, or have disconnection procedures that vary by person, interruptions in correction data will lead to variability in work quality. Not only differences in equipment performance, but also the presence or absence of operational rules greatly affect stability.

The sixth issue is a mismatch between equipment configuration and work objectives. If you want to continuously observe many points in a short time but adopt a configuration that makes communication recovery time-consuming, require difficult one-handed operation that increases confirmation steps, or involve frequent on-site handovers that lead to neglecting connection monitoring, configurations that do not match the operational workflow will greatly amplify the impact when communication interruptions occur. In other words, the problem of losing correction data should be regarded not only as a matter of weak radio signals but also as an issue of field design.

Communication Measure 1: Check signal conditions in advance

The most fundamental and yet highly effective measure is to verify the expected communications before entering the site. RTK correction data only enables high-precision positioning when it is received reliably. Nevertheless, on site attention often focuses solely on satellite conditions, and checking mobile communications can be put off. This is a very wasteful way to operate.

What is important in the preliminary check is not simply whether there is network coverage in the area, but whether correction signals are likely to be received continuously at the actual work points. Even within the same site, conditions can change dramatically: there may be no problem at the roadside, but reception can be impaired in the shadow of embankments, on the north side of buildings, near steel or material yards, or close to the shoulder of a slope. Rather than making a blanket judgment for the entire site, it is necessary to anticipate differences between individual work points.

In practice, performing a test connection before starting work and simply checking the startup and maintenance of correction reception can be effective. What you want to check here is not whether it connects once, but whether reception remains stable when you move slightly, whether it drops out when stationary for a few minutes, and how long it takes to reconnect. Even a short check makes it easier to identify hazardous locations in advance.

Also, it is important to share on-site the points where correction reception tends to become unstable. If only certain locations are prone to signal loss, you can adjust the observation sequence near those areas or use places where correction reception is more stable as relay points. This reduces the time spent hesitating on-site each time a loss occurs.

At some sites, the time of day when work is performed also has an effect. The operating status of nearby equipment, vehicle movements, the placement of workers and machinery, and the condition of temporary structures around the area can make reception easier in the morning or in the afternoon. Therefore, during the initial operation, don’t be reassured by a single confirmation; understanding differences by time of day and by location will improve stability.

Loss of correction data will halt operations if you only deal with it after it happens. However, if you know in advance where it is likely to occur, you can change the way you design observation plans. This may be unglamorous, but ultimately it is one of the most practically effective communication measures.

Communication Measure 2: Review Devices and Communication Settings

One thing that is easily overlooked on-site is the device settings. Receiving correction data requires continuous communication with external sources, but devices are often designed for general consumer use and will default to power‑saving behavior if nothing is done. While that behavior can be convenient between tasks, it can work against you in RTK operations.

For example, when power-saving functions are strongly active, communication apps and reception processing can be suppressed in the background, and reception may stop after the screen goes off. Because workers are focused on the positioning device, they tend not to notice changes in the device’s behavior, and by the time they notice, the corrections have often been disabled. First, review the settings of the devices used for business and configure them so that continuous communication is less likely to be interrupted.

Notifications, automatic updates, and unnecessary synchronization processes can also affect communication stability. In the field, because you need to continuously receive correction data over limited network conditions, concurrent unrelated communications can cause increased load and delays. During operations, it is desirable to disable unnecessary functions as much as possible and keep the system in a state that prioritizes the communications required for receiving corrections.

Furthermore, how the device is held or positioned cannot be ignored. If it is placed deep in a pocket, covered by a metal case, pressed too closely against equipment, or positioned where it is easily shaded by the body or materials, the communication can become unstable. Even if the device itself is functioning normally, the way it is handled during operation can degrade communication quality. On-site, simply being mindful of ways of holding or mounting the device that make the connection-status display easy to see and that are less likely to obstruct communication can make a difference.

What’s important when reviewing settings is not to treat it as a one-time adjustment. Devices can change behavior after updates or restarts, and settings may be altered when they are shared among multiple users. For that reason, incorporating a check of communication settings into pre-shift inspections makes it easier to reduce the risk of disconnections in the field.

When correction data is interrupted, attention inevitably shifts to the communication area or the distribution side. However, in practice, many cases can be improved simply by optimizing device settings. These are measures you should always keep in mind, since they require little effort yet deliver a significant impact.

Communication Measure 3: Adapt operations to the on-site environment

When people think about communication measures, they tend to imagine only seeking a stronger signal, but in reality changing how you operate on-site can sometimes be more effective. At sites where RTK correction data tends to drop out, rather than continuing the same approach everywhere, it is important to reorganize observation procedures on the assumption of environments where communication is likely to be unstable.

For example, rather than staying for long periods at a spot prone to disconnections and repeatedly performing detailed checks, it can be more efficient to first establish correction reception at a location where communications are more stable and then move to the target point. This is the idea of separating the location where corrections are stabilized from the location where observations are made. In particular, at sites where obstructions are scattered, moving just a short distance can greatly improve the signal quality.

Also, planning the observation sequence is effective. Rather than leaving the more secluded or unstable areas of a site until later, it is better to handle them first during periods with relatively good communication conditions or when the schedule allows some leeway, as this makes recovery easier if problems occur. Conversely, entering unstable areas near the end of an operation when time is limited increases the likelihood of making rushed, incorrect decisions if corrections are lost.

The operator's standing position is also important. In situations where correction data is prone to drop out, rather than standing so that you only look at the target point, be mindful of an orientation and positional relationship that make communication easier. Avoid locations shadowed by buildings or vehicles, stand a short distance away from structures, and simply being aware of clear sky above and openness around you can sometimes improve matters. Because this also tends to have a positive effect on satellite reception, it is meaningful for both communication and positioning.

Furthermore, at sites where communications are unstable, the way observations are checked should also be changed. Instead of immediately fixing on a single point, by adopting methods such as rechecking after short time intervals, checking consistency with nearby points, and periodically verifying relationships with known or control points, you can detect the effects of correction interruptions earlier. Rather than noticing only after corrections have been lost, you will be able to detect them at the stage of early signs.

The site environment is not the same every day. Temporary layout changes, fluctuations in materials, the positions of heavy equipment, and the progress of surrounding works all alter communication conditions. Therefore, the very stance of changing operations to suit the site is the most practical communications measure. Whether you can choose operating methods suited to the site, rather than leaving everything to machines, is what determines stable operation.

Communication Measure 4: Establish a system to quickly reconnect correction reception

No matter what countermeasures you take, there are situations where it is difficult to completely eliminate disconnections of correction data. That's why it's important not just to aim to prevent them, but to build a system that can quickly recover when they do occur. In practice, this approach clearly shows up as differences in work time.

Many sites where reconnection takes a long time rely on people's memory for procedures. When tasks such as confirming the connection destination, entering authentication credentials, checking communication status, and assessing the positioning status after re-receiving corrections are handled based on on-site experience, recovery times vary by person. Even if an experienced person can restore service quickly, another operator may take longer to get things running, so operational quality is not stable.

To prevent this problem, simplify the reconnection procedure as much as possible and standardize the checklist. For example, specify in a fixed order what to look at first when corrections are lost, how to check the communication display, in what order to reconnect, and what to verify after reconnecting before resuming observations so that anyone can perform the same sequence. This reduces oversights caused by haste and stabilizes positioning quality after recovery.

Also, it is common in the field to resume observations immediately after reconnecting corrections. However, a displayed connection does not mean the system has returned to a stable, high-precision state. If you resume without confirming the reception status, the stability of the solution, and how the coordinates are settling, you risk accepting unstable values immediately after recovery. The verification procedures after reconnection, including these checks, should be standardized.

Additionally, it is important to make sure that the information needed to reconnect is not something people have to search for on site. If connection conditions and items to check exist only in people’s heads, the process becomes vulnerable to staff changes and sudden handovers. Keeping concise procedure documents or checklists with the equipment makes it easier to calmly recover even if an adjustment-related interruption occurs.

Efforts to reduce interruptions to correction data are, of course, necessary. However, in practice, differences in recovery capability can have a major impact on productivity. To make communication measures truly work on-site, it is essential to design the actions to be taken when a disconnection occurs.

Communications Measure 5: Standardize Observation Procedures to Reduce Human Error

The problem of RTK correction data dropouts can be exacerbated not only by communications equipment and radio environments but also by human operation. Omissions in checking settings, overlooking connection status, and mistaken judgments about when to start observations may each seem minor, yet in the field they can lead to significant rework. That is why standardizing observation procedures is so important.

First, it is necessary to clarify the pre-work checklist. If you fix how far to check before starting observations—battery level, device settings, communication status, correction connection, satellite reception, verification at known points, etc.—it becomes easier to maintain consistent quality even when the person in charge changes. Conversely, if you leave it to each individual's judgment, checks tend to be skipped on rushed days, increasing the likelihood of correction loss or coordinate errors.

Next, it's important to decide which items to monitor during observation. In RTK, simply looking at the positioning results is insufficient. You need to check at regular intervals whether correction reception is being maintained, what the solution status is, and whether there are any sudden changes in behavior. If you set checkpoints for verification—such as after moving, when resuming, or immediately after an environmental change—you can detect anomalies early.

It is also important not to leave the criteria for judging what to do when a correction is lost ambiguous. If it is not decided which conditions warrant temporarily pausing, which conditions warrant prioritizing reconnection, and which conditions warrant switching to re-observation, responses will vary depending on the person in charge. As a result, data acquisition quality can become inconsistent even at the same site. The purpose of standardization is not to make operations mechanical, but to reduce variability in decision-making.

Furthermore, the way observation results are recorded is also important. Briefly noting where corrections were unstable, how long reconnections took, and at which points re-observations were made will help improve operations in future runs. At sites without a history of trouble reports, the same problems tend to recur at the same locations each time. Keeping records may seem tedious, but it is indispensable for turning communication countermeasures into an accumulated body of know-how.

Human error cannot be prevented by individual vigilance alone. The busier the field, the more important it is to create workflows that make mistakes less likely. Standardizing observation procedures makes it easier to respond calmly when correction data is interrupted, and as a result improves the overall stability of RTK operations.

Communication Measure 6: Consider device configurations that make it difficult to stop work even when communications are unstable

Finally, what you should review is the equipment configuration you bring to the site. The problem of RTK correction data being lost depends not only on the communication conditions themselves but also on how prone the configuration is to causing on-site work to stop when a connection is lost. In other words, even under the same communication conditions, the practical impact varies depending on the equipment configuration and operational workflows.

For example, in a configuration where the screen needed for checks is hard to see, it takes many operations to determine the connection status, it is difficult to handle safely with one hand, or monitoring of the connection state is interrupted every time the device is handed over, the impact of correction interruptions becomes large. Conversely, if the connection status can be checked immediately, it is easy to judge recovery after reconnection, and carrying and operating on site are simple, the same communication interruption is less likely to halt the overall work.

In practice, it is important not only to compare equipment performance but also to consider who will use it, in what posture, and within what workflow. Whether position checks are carried out while walking, observations are made by stopping and measuring one point at a time, or construction management and positioning are performed simultaneously will determine the appropriate configuration. The simpler the operation and the easier it is to verify, the more valuable it becomes on sites with unstable communications.

Whether the equipment integrates naturally into on-site operations is also important. Even if the high-precision positioning mechanism is excellent, if it is difficult to handle in the field, checks and recovery will be postponed when communications become unreliable. As a result, it may take longer to notice that corrections have been lost. The equipment configuration should be considered not only for its ability to perform positioning but also for its ability to sustain stable operation.

What deserves attention here is the concept of combining everyday familiar devices with high-precision positioning to improve usability in the field. By making it easier to integrate screen checks, monitoring of communication status, and the use of location information, it becomes easier to detect anomalies and recover even when correction data is unstable. In practice, configurations that are easy to operate and that reduce the training burden after deployment tend to lead to more stable operation.

Equipment configuration is often left until later, but it is critically important for making communication measures actually work on-site. Since you cannot completely control communication quality, choosing a configuration that keeps work from stopping even when assuming instability makes a big difference in practice.

Summary

The causes of RTK correction data loss cannot be dismissed simply as a weak communication link. In reality, the site’s terrain and structures, the satellite reception environment, receiver settings, survey procedures, and equipment configuration all interact to produce the effect. That is why, to reduce correction dropouts, it is necessary to review the entire field operation, not just the radio signal.

The six communication measures introduced here are not a cure-all on their own. It is important to identify risky locations by checking radio conditions in advance, configure device settings, adapt operating methods to the field environment, standardize reconnection procedures for disconnections, reduce variability in observation procedures, and consider equipment configurations that are less likely to interrupt work. By combining these measures, you can reduce the impact when correction data is lost and move closer to stable RTK operation.

Especially for practitioners searching for information about RTK, it is important not only to understand the theory but also to be able to reproduce it in the field. Interruptions in correction data, if unnoticed, lead to degraded accuracy, and even if noticed, if recovery takes time they lead to delays in the workflow. In other words, communication measures are not only a positioning issue but also a matter of on-site productivity and quality control.

If you want to make high-precision positioning easier to handle on site and operate it in a way that makes communication conditions and position verification more practical, configurations that combine everyday-easy devices with high-precision positioning—such as LRTK (iPhone-mounted GNSS high-precision positioning device)—are also a promising option. By reassessing systems with attention to the stable reception of correction data and including the ease of on-site verification and operation, RTK becomes not just a means of high-precision positioning but a more usable tool for advancing practical work.