7 Explanatory Items Without a Comparison Table to Avoid Regretting Your RTK Selection

When choosing RTK equipment and RTK operation services, it is not uncommon for people to be tempted to compare only price and the numbers on the catalog. However, in real-world field situations, even when they are all grouped under the same term "RTK," the most suitable configuration can vary greatly depending on how it will be used, the required accuracy, the communications environment, how correction information is received, ease of operation, maintenance arrangements, and future expandability. Problems such as equipment purchased because it seemed cheap being difficult to get a Fix in the field, operation being difficult and incurring high training costs, correction service contracts being more onerous than expected, and work stopping when a failure occurs often arise because there were insufficient comparison criteria before introduction.

RTK in particular cannot be judged by device performance alone. It only becomes a system that can be used in practice when it includes the satellite receiver, the communication method for receiving correction information, an understanding of coordinate systems, on-site initialization and verification procedures, and post-work data utilization. Therefore, simply following the items in a comparison table that look easy to understand at first glance will not reveal how user-friendly it is on site or how resistant it is to failure.

In this article, without using comparison tables, we organize and explain seven key considerations to help you avoid regrets when selecting RTK. Rather than presenting price lists or spec sheets, we carefully organize the practical, important points—intended use, accuracy, communications, corrections, usability, maintenance, and future expansion—so you can see where to focus to minimize the risk of failure. The content is compiled to be useful not only for managers considering their first RTK deployment, but also for those who already use RTK and are thinking about replacement or expansion.

Table of Contents

• Introduction

• First, confirm whether it is suitable for its intended use.

• Assess the required accuracy according to on-site standards

• Consider whether the configuration can withstand the communication environment

• Compare methods of receiving correction information and their operational burden

• Verify operability and ease of training.

• Considering maintenance systems and uninterrupted operation

• Check whether it can be expanded in the future.

• Summary

Introduction

The most common mistake when selecting RTK is getting the order of comparison wrong. Many people look at price first, but you should actually start by clarifying the intended use, determine the accuracy and operational mode required for that use, and then align conditions such as communication, corrections, usability, and maintenance. In other words, RTK selection is more successful if you think of it as designing field operations rather than simply choosing equipment.

For example, the usability required differs between sites where, in existing-conditions surveys, you want to quickly cover a wide area and construction sites where you want to repeatedly check specific points. In the former, portability and connection speed are important, while in the latter it is important to be able to make reproducible measurements under the same conditions and to make it easy to compare with known points. Furthermore, if the work environment differs — such as in mountainous areas, urban areas, or near structures — the conditions affecting the stability of the Fix also change.

Also, RTK is an area where operational issues tend to become apparent after implementation. Before purchasing, people tend to focus only on the receiver unit itself, but the actual problems are peripheral issues such as communication dropouts, difficulty in receiving corrections, inconsistent understanding of coordinates across the site, mistakes in handling antenna heights, and measurement quality varying by operator. These problems are affected not only by the quality of the equipment itself but also—often significantly—by how extensively operational use was anticipated at the time of selection.

That's precisely why there is value in thinking without a comparison table. Comparison tables are convenient, but they inevitably homogenize items and make it hard to see real usability problems, training costs, and differences in the ability to respond when troubles occur. What on-site staff really want to know is not which product is the cheapest, but which configuration they're least likely to regret for their operations.

Below, we will look at the seven considerations to keep in mind when selecting an RTK, in order. Considering them in this sequence makes it easier to organize issues that are often overlooked before deployment, and consequently makes it easier to avoid making a decision based solely on price.

First, check whether it is suitable for the intended use

The starting point for RTK selection is to clearly define what it will be used for. If you begin choosing equipment while this is ambiguous, you may end up buying a configuration with more features than necessary or, conversely, deploying one that lacks the functions needed on site. Organizing the intended use is unglamorous, but it is the most important step to avoid regret.

First, what you should confirm are the measurement targets and the frequency of the work. RTK can be used in a wide range of ways, such as site condition checks, as-built verification, layout marking, pile-driving assistance, simple positioning, inspection records, and linking positions with photos. Even if the goal is to obtain the same centimeter-level (half-inch-level) position information, the required work time, necessary repeatability, allowable error, and the strictness of the required procedures differ. For example, on sites where many points need to be collected in a short time, fast startup and reconnection and simple operation are advantageous. On the other hand, on sites that place greater emphasis on consistency with reference points, procedures for checking each observation and the ease of keeping records are more important.

Next, it’s also important to consider who will be using it. The optimal equipment changes depending on whether you assume an experienced surveyor will use it or that construction management or inspection staff will use it on a daily basis. People with specialist knowledge can handle devices with numerous configuration options, but if the device will be shared among multiple users and you want anyone to be able to use it with consistent quality, fewer settings and a clearer interface should be prioritized. Even a high-performance system can reduce overall site efficiency if only a limited number of people are able to operate it.

Furthermore, the characteristics of the location of use must also be considered as part of the application. Whether the site is mainly open, predominantly mountainous, close to structures, or in urban areas with limited overhead visibility will make the perceived stability of the same RTK completely different. Even when use is primarily outdoors, conditions vary along roadsides, slopes, development sites, and around equipment, so it is risky to assume it will be fine simply because it will be used outdoors.

When organizing intended uses, it is important to think in the terminology used on-site as much as possible. For example, if you translate questions into the flow of actual work—such as how many points you want to collect per day, whether it will be carried by one person, whether you will verify known points each time, and whether records will be rechecked within the company—the necessary conditions become clear. Before comparing feature names in catalogs, it is effective to trace your on-site tasks in chronological order and identify moments that will be burdensome.

If you select without clearly defining the intended uses, you may end up continuing to pay for features you use less than expected in the field, or discovering that the features you truly needed are lacking. To avoid regretting your RTK selection, it is essential to first specify the intended uses and articulate the requirements needed for them.

Determine Required Accuracy According to On-site Standards

When comparing RTK, many people are most concerned with accuracy. However, it should be noted that accuracy cannot be compared by numbers alone. If you judge solely by the accuracy statements written in catalogs, discrepancies with expectations are likely to arise after implementation. What matters is clarifying how much accuracy is required for your site and how much repeatability and stability you need.

RTK is generally known as a high-precision positioning method, but what matters in practice is not the theoretical best values but whether you can consistently achieve results close to that level in real field conditions. For example, even if a device shows high performance in ideal environments, if it takes a long time to reach Fix at sites with poor communications or limited sky visibility, it can be hard to use in actual work. Conversely, even when the numerical differences are small, a configuration that initializes and reacquires quickly and produces stable results with the same procedure is often more trustworthy in the field.

When considering accuracy, it is important to treat horizontal and vertical (height) separately. On-site, some tasks are acceptable as long as the planar position is correct, while others require proper alignment in the vertical direction. However, users sometimes judge solely by the term "centimeter-level (half-inch-level)" without fully appreciating this distinction. Height often needs to be evaluated more strictly than the plane, and because it is more susceptible to site conditions and procedures, it is necessary to determine the required level of reliability according to the application.

Also, accuracy includes not only the observed values themselves but also operational errors. In practice, human involvement adds error sources such as antenna height input mistakes, insufficient cross-checking with known points, incorrect coordinate system settings, and variations in observation timing. For this reason, in addition to pure reception performance, it is necessary to consider whether the operation/interface is designed to be error-resistant and whether verification procedures can be easily incorporated into field workflows as part of ensuring accuracy.

When selecting, it is important not to be vague about the required accuracy. Rather than using expressions like “I want high accuracy” or “I want to be as precise as possible,” clarify which tasks and what degree of difference will be problematic. For example, acceptable tolerances vary depending on whether the use is for checking against design values, for position recording, or for construction assistance. Thinking in terms of on-site standards makes it easier to avoid spending on performance beyond what is necessary.

In other words, comparing RTK accuracy is not just a numbers game. It’s important to evaluate how stably it can be used under your on-site conditions, how easy it is to maintain accuracy including human error, and whether it meets the required level without excess or shortfall. The more you insist on accuracy, the more you need to think in terms of on-site criteria rather than spec sheets.

Consider whether the configuration can withstand the communication environment

Because RTK is a method that enhances accuracy using correction information, it cannot be selected without considering communications. In fact, the most common post-deployment complaints are less about accuracy itself and more about communication-related issues such as unstable corrections, time-consuming reconnections, and significant differences in ease of use depending on location. When selecting RTK, you need to evaluate from a field perspective not only the receiver’s performance but also whether the configuration can withstand the communication environment.

What you should consider first is the communication conditions at the work site. Even in urban areas, places near underground sections, under elevated structures, or in the canyons between buildings can experience unstable communications, and in rural or mountainous areas there are inherently differences in line quality. If you judge there is no problem just because your smartphone usually works, you may find that continuous correction reception is surprisingly unstable. With RTK, what matters is not whether it connects for a moment, but whether it remains connected throughout the work.

Next, the communication setup is important. Whether the receiver itself has communication functionality, whether it goes through an external terminal, and which terminal is used to connect for corrections can greatly change how easy it is to handle on site. The more complex the configuration, the greater the chance of setup mistakes or connection failures. While a specialist can deal with this if always present, if multiple team members use the system daily, a configuration that requires less connection effort will be easier to operate reliably.

When evaluating a communication environment, you should not overlook how easy it is to recover when a connection is lost. In the field, an ideal communication state cannot always be maintained, so the issue is not only whether connections stay up, but also how quickly they can be restored after a drop. If reconnection requires many steps or users have difficulty identifying where the break occurred, not only does work efficiency suffer, but the psychological burden on the personnel in charge also increases.

In addition, it is important to note that unstable communication often manifests as concerns about accuracy. On site, poor communication can appear as failure to achieve Fix, not returning from Float, or unstable results, so from the user’s perspective it becomes difficult to determine whether the device or the communication is at fault. Therefore, when selecting equipment, whether the status is easy to understand during communication troubles, whether it is clear what to check, and whether judgments can be made easily from logs and displays are also important comparison points.

To avoid regrets about communications, it is important to anticipate the typical patterns of your company’s job sites. Don’t just consider open sites—envision locations where signals may be weak, sites with a lot of movement, and situations requiring long continuous use, and assess whether the configuration will be feasible in those cases. Recognizing that RTK is, before being a high-precision instrument, also a field device that involves communications will help reduce failures.

Compare methods of receiving correction information and operational burden

The usability of RTK depends greatly on which correction information is received and how. However, when introducing it, the discussion often focuses only on the receiver hardware, and the correction-information contract type, connection method, and the burden of daily operation are not always adequately compared. As a result, even when the equipment itself is fine, the correction operation can be burdensome and the system may stop being used in the field.

The first thing to consider regarding correction information is what kind of operation you will assume. Whether you always use a network-based correction service, plan to operate your own base stations, or use both depending on the application, the knowledge required and the management burden will differ. Network-based systems are easy to introduce but depend on contracts and communication environments. On the other hand, running your own system offers flexibility but increases responsibility for installation and management. Rather than deciding which is superior, it is important to judge whether it fits your company’s setup.

Next, what I want to look at is how naturally on-site personnel can handle corrective connections. If aspects of daily operations—such as choosing the connection target, managing credentials, procedures for reconnecting, and the ease of checking status—are complicated, the burden increases the more frequently they are used. Even if it’s fine when only a small number of experienced people use it, if you want to roll it out across multiple sites or teams, these kinds of hassles will make a big difference later.

When selecting correction information, area compatibility is also important. You should evaluate whether it is easy to use in the target area, whether it can accommodate sites that move frequently, and whether managing contracts and connections is practical. Unlike the equipment itself, correction information is something you will continue to deal with after deployment. Therefore, you need to consider not only the initial ease of implementation but also the ease of monthly operations, responsiveness to inquiries, and how easily it can be handed over within the organization.

How correction information is received also affects troubleshooting capability. When a fix cannot be obtained, it is important that operations make it easy to determine whether the problem stems from device settings, the correction service, or communications. Because causes on site are often multiple, systems that make connection and correction status easy to view and that facilitate standardization of verification procedures are easier to operate.

When comparing correction services, it's dangerous to decide based on price alone. Certainly, running costs are important, but even if something is cheap, if the connection is complicated or on-site recovery takes time, the real cost becomes higher. What matters when choosing an RTK solution is not whether you can receive corrections, but whether you can continue to use them reliably. From that viewpoint, it is essential to compare options including the post-installation effort.

Verify operability and ease of training

When selecting RTK equipment, performance and accuracy tend to be discussed first, but in fact usability greatly affects day-to-day satisfaction. No matter how high-performing a device is, if it takes time to boot up, has an unclear screen, makes it hard to intuitively grasp status, or has complicated operating procedures, it is likely to be judged as difficult to use in the field. Especially when shared among multiple people, differences in usability directly translate into differences in training costs and error rates.

What you should check is not the initial setup, but the workflow during everyday use. You should evaluate whether there are few points where users might get confused in the series of steps—turning the power on, connecting to corrections, checking the status, taking measurements, saving the results, and, if necessary, verifying with known points. Even if the specification sheet lists many features, if it is difficult to reach the required operations, it will become a burden in the field.

Clarity of status indicators is also important. In RTK, users operate while checking multiple status items — for example, whether it is Fix or Float, whether communications are active, whether corrections are being applied, and what the satellite status is. Whether the display enables users with limited expertise to make the necessary judgments affects the stability of operations in the field. With equipment whose status is hard to see, operators tend to become anxious when problems occur, and as a result the equipment may end up being underused.

Ease of training is directly linked to wider adoption. Even if only a subset of staff are expected to use it at first, if it’s convenient people will want to broaden its use. At that point, whether training materials are easy to create, procedures are easy to standardize, and explanations for beginners are straightforward is extremely important. Even if there are many configuration options, another evaluation point is whether settings that can be hidden during daily use can actually be hidden, and whether frequently used operations are simplified.

Furthermore, usability also encompasses physical ease of use. Aspects such as how easy a device is to carry, how simple it is to set up, whether the screen is easy to read on-site, whether it can be operated while wearing gloves, and whether coordination between devices is not cumbersome are often overlooked in desk-based evaluations, but they directly affect satisfaction in the field. Because these are items carried every day, small annoyances can accumulate into major frustrations.

To use RTK reliably over the long term, equipment that an average operator can use to deliver consistent quality is often more suitable than equipment that only skilled users can handle well. When selecting equipment, it is important to regard operability not merely as ease of use but as ease of training, resistance to errors, and ease of internal deployment.

Considering Maintenance Structure and Uninterrupted Operations

Because RTK is equipment used in the field, you must assume that failures and malfunctions can occur. However, when they are introduced, attention often focuses only on performance and price, and maintenance arrangements and procedures for handling problems are sometimes neglected. In practice, what matters more than preventing every failure is how quickly you can restore on-site operations without bringing work to a halt when a problem occurs.

The first thing to check is how easy it is to make inquiries and obtain support. When a problem occurs, is it clear whom to contact? Can you receive concrete guidance for issues that commonly arise on-site, and can you consult about setup and operation? These factors greatly affect users’ sense of security. Whether the support system only handles equipment malfunctions or is also easy to consult about issues such as correction, connectivity, and configuration directly affects ease of use after deployment.

What we should consider next is the approach to spare units and alternative measures. If RTK is operated with a single unit, there is a risk that the entire operation will halt the moment that unit stops. If you use it every day, it becomes even more important to plan for alternative operation in case of failure and to define a minimum backup configuration. This is more a matter of site downtime costs than maintenance expenses. Even if the device itself is inexpensive, if the loss when it stops is large, it cannot be considered a cheap choice overall.

Maintenance includes not only physical failures but also the upkeep of settings and operational rules. For long-term operation, factors such as how easy it is to retrain personnel when staff change, whether settings are unlikely to become tied to a single person, and whether the company can easily follow up on updates and changes internally are also important. If only a particular person can handle something, operations are more likely to come to a halt simply because that person is absent.

You should also check how easy consumables and peripheral equipment are to handle. If peripheral elements such as batteries, cables, fasteners, storage, and charging operations are complicated, they can cause on-site downtime even without a malfunction. Especially when the equipment is used outdoors frequently, practical handling of things other than the device itself—such as drops, exposure to water, and shocks during transport—is important.

If you underestimate the maintenance setup, the operational burden after deployment will be greater than you expect. Conversely, if the configuration makes support easy to access and responses to problems easy to organize, then even if the initial cost is somewhat higher, the entire site can continue to use it with confidence. RTK selection should be considered not only up to the point of purchase but also including ongoing use; in that sense, maintenance should be a central criterion for comparison.

Check whether it can be extended in the future.

When choosing an RTK, selecting the minimal configuration that fits only the immediate use may seem reasonable at first. However, after deployment the ways it’s used often expand as on-site personnel become familiar with it; what was originally intended just for position checks can come to require more advanced record-keeping, deployment to other tasks, use across multiple sites, and integration with external data. Therefore, if you choose without any consideration for future expandability, the configuration can become restrictive at an early stage.

One of the first things to consider for future expansion is the scope of use. Whether it is dedicated to a single person, could be expanded to multiple departments, or will be used not only for surveying-focused tasks but also for construction management, inspection, and maintenance will change the required specifications. Even if only simple observations are made at the time of introduction, if sharing and reuse increase later, how data is handled and the ease of integration become important.

What to check next is whether the equipment and operational practices are too closed. Even if they are sufficient at a given point in time, long-term usability can change dramatically depending on whether they can flexibly respond when peripheral devices, apps, calibration contracts, or internal operating rules change. Future expandability does not necessarily mean high functionality. It is important to have some leeway that makes it easy to accommodate changes.

Also, scalability is related to the scaling of training. Even if you start with a limited number of team members, there are often situations where you want to standardize across the company. At that point, it becomes important whether it is easy to increase the number of devices, whether the same procedures can be rolled out easily, and whether configuration and management do not become overly complicated. If you choose with only the first device in mind, management can suddenly become difficult with the second and third devices.

Also, you should take into account how easy future replacements and upgrades will be. Field equipment cannot remain in the same configuration indefinitely, and may need to be reviewed every few years. At that time, it is important whether you can carry over as much of the existing operation as possible and whether operations, procedures, or ways of thinking will not be disrupted. Even if it can be introduced cheaply now, a configuration that requires full retraining at the time of upgrade will become a significant burden in the long run.

When considering future expansion, the important thing is not to overinvest from the start. Rather, choose a configuration that is sufficient for current needs while not preventing the next step. In practice, needs often only become clear after actually using a system on site, so selecting options that can easily accommodate those changes will ultimately lead to fewer regrets.

Summary

To avoid regrets when selecting an RTK, it is important not to judge solely by price lists and specification sheets. Comparison tables are useful as a starting point, but what really matters in the field is whether it matches the intended use, can consistently deliver the required accuracy, can withstand the communication environment, whether the operation of correction information can run smoothly, whether it is easy to operate and train on, whether the maintenance/support structure is realistic, and whether it can accommodate future expansion.

The seven items introduced here may appear to be independent, but in reality they are deeply interconnected. Once the intended application is determined, the way you think about required accuracy changes; to stabilize accuracy, the operation of communications and corrections becomes important; and to keep daily operations running, usability and maintenance frameworks are indispensable. Moreover, considering that usage may expand after deployment, future scalability cannot be ignored. In other words, RTK selection should be considered not as a comparison of individual devices but as a site-wide operational design.

If you're unsure which option to choose, start by picturing your own worksite concretely. Clarifying who will use it, where, for what purpose, and how often will naturally narrow the comparison points you need to consider. Then, rather than judging solely by high performance, use as a criterion whether it can be used reliably and consistently on site—this will greatly reduce dissatisfaction after deployment.

RTK, when chosen correctly, is an effective means of significantly improving on-site efficiency and repeatability. Conversely, if your selection criteria are off, you may be unable to use it effectively, fail to leverage it as much as you expected, and face increased operational burdens. To make a choice you won’t regret, it’s important to review the seven items introduced today in order and determine what is truly important for your site. Even without a comparison table, if your perspectives for comparison are clear, the quality of your decisions can be greatly improved.