7-Item Guide Without Comparison Tables to Avoid Regretting Your RTK Selection

Table of Contents

• Why it's difficult to decide on RTK selection from comparison tables alone

• Not what you want to do, but what you want to leave as a deliverable.

• What matters is not the highest accuracy, but reliably ensuring the required accuracy.

• How the reception of correction information and the communication environment affect operations

• Don't overlook device integration and the ease of app operation.

• Resistance to field conditions is determined by how it is used rather than by the spec sheet.

• The way you choose will change depending on whether it can be used by one person or operated by multiple people.

• Make decisions based not only on initial implementation costs but also on ongoing operational costs.

• Final checks when selecting RTK

• Why it's difficult to choose an RTK solution based on comparison tables alone

When planning to implement RTK, the first things many people want to know are the easily comparable factors: price, accuracy, communication method, compatible devices, and dust/water resistance. Of course those are important. However, regrets in actual field operations typically don't stem from overlooking numbers in comparison tables, but from deciding without anticipating operational conditions that are hard to capture in those tables.

For example, even RTK equipment that looks similar will require very different configurations depending on whether it will be used in mountainous areas or urban environments, and whether it will be used on construction sites every day or only a few times a month. Simply choosing a higher-precision device is not necessarily the right approach, and selecting a cheaper device does not necessarily lead to failure. What matters is whether you can operate it in a way that is consistent, repeatable, and without undue strain for your company's intended use.

Also, RTK is not a tool that works by itself. Practicality is determined only when you include the receiver, correction information, communications environment, terminals, apps, understanding of coordinate systems, field procedures, and verification methods. In other words, selecting an RTK solution is not about choosing equipment but about choosing an operational workflow. If you get this wrong, it may appear to work immediately after deployment, but the moment the number of sites increases, operations are likely to break down.

Comparison tables are not useless. However, while a comparison table can be helpful for the final narrowing down, it is not suited to provide initial direction. What’s needed first is to clarify which items your company should prioritize. In this article, to help you avoid regret when selecting an RTK, I will sequentially explain seven perspectives that make it easy to make a judgment even without laying them out side by side in a table. While highlighting practical differences that are hard to discern from numerical values alone, we will organize the way of thinking for choosing an RTK.

1. Not what you want to do, but what you want to leave as deliverables

When selecting RTK, the first thing to consider is not what you want to do, but what you ultimately want to leave as the final deliverable. If you proceed with selection while leaving this unclear, you are likely to either choose an unnecessarily expensive configuration or, conversely, select a configuration that cannot meet the required conditions.

For example, whether you only want to quickly record single-point positions on site, need to meet certain accuracy standards for as-built or construction management, want to use it for aligning point clouds or photogrammetry, or want to streamline position verification of existing structures will change the role required of RTK. If single-point observations are the main focus, being lightweight, quick to start up, and easy to operate is emphasized. On the other hand, if it is used for continuous surveying work or rigorous as-built verification, operational aspects—including stability during repeated observations, coordinate management, and verification procedures—become important.

A common mistake here is assuming too broad a range of uses. It’s natural to want something that can be used in many different situations in the future, but if you choose from the outset on the assumption that a single unit must perfectly cover every possible use, it can actually become harder to use on site. Having many features does not necessarily translate into ease of use in the field. Rather, there are many situations where what counts more is minimal preparation for the primary everyday use, quick startup, and the ability for anyone to take measurements following the same procedure.

Therefore, in the early stages of selecting an RTK, it is effective to articulate your company's deliverables before comparing equipment. For example, clarifying whether the task is point records for site condition verification, reflecting measurements on drawings, checking construction positions, or georeferencing photos or point clouds makes it easier to see the required accuracy and the necessary workflows. RTK may seem like an all-purpose solution, but in practice its value is determined by whether you can choose the appropriate way to use it for your deliverables.

Furthermore, it is important to ensure there is no misalignment of expectations between field personnel and managers. Field teams tend to prioritize ease of use, while management often demands accuracy and traceability, so selecting a solution that satisfies only one side can lead to regret. The starting point for RTK selection is to determine upfront whether you can reconcile an operation that will continue to be used in the field with the management’s requirements.

2. What is required is not the highest accuracy but reliably maintaining the necessary level of accuracy

When comparing RTK systems, many people are most concerned with accuracy. However, what is truly important in selection is not the peak accuracy listed in the specifications, but whether you can consistently secure the required accuracy under your company’s actual site conditions. If you misunderstand this, a solution that is superior on paper can easily fail to meet expectations in the field.

RTK accuracy is not determined solely by receiver performance. Satellite reception conditions, sky visibility, obstruction by surrounding structures, effects of reflections, communication stability, the quality of received correction information, observation time, installation method, operator procedures, and many other factors are involved. In other words, even if a catalog states centimeter-level accuracy, it cannot necessarily be reproduced exactly at every site.

What is important here is to specify the required level of accuracy. For example, the points to consider change depending on whether the task can tolerate errors of a few centimeters (a few in), whether positional reproducibility is required in repeated measurements, whether relative positional relationships are important, or whether the reliability of absolute coordinates is important. Rather than simply looking at the minimum error, it is necessary to consider whether results can be reproduced across days, whether a different operator can obtain the same results, and how often situations where measurement is not possible occur.

Also, the more you pursue higher accuracy, the more difficult the operation can become. When installation conditions become more stringent, observation times must be lengthened, or verification tasks increase, it can clash with the pace of on-site work. As a result, even if a high-performance RTK is introduced, it may in practice be used only in a simplified way and end up not realizing its full potential.

When selecting, it is important to consider the level of accuracy your company needs as an operationally achievable standard, not as an ideal value. For example, a configuration that can measure stably in a short time every time may be more valuable than one that occasionally delivers high accuracy but requires time-consuming preparation. The more an RTK is used continuously in the field, the more you should prioritize everyday average ease of use and reproducibility over peak accuracy to avoid later regret.

From this perspective, RTK selection is not about competing for top performance but about building a system that can maintain the level of accuracy that is necessary and sufficient in the field. Before deployment, anticipating which conditions will allow its use and which conditions are likely to cause accuracy to degrade will greatly reduce the risk of making a poor selection.

3. How the Reception of Correction Information and the Communication Environment Affect Operations

Since RTK is a positioning method that operates by receiving correction information, how that correction information is received is a key criterion in selection. However, it's not uncommon for attention to focus solely on the receiver unit’s performance, leaving considerations about how corrections are received and the on-site communications environment for later. This oversight is a point that often leads directly to dissatisfaction after deployment.

There are ways to receive correction information, such as using a network-based service or operating your own reference station. Generally, network-based services are easier to introduce and more convenient to use over a wide area, but they increase reliance on communication links. Operating your own reference station offers greater flexibility, but increases the burden of installation and maintenance. Rather than one being superior to the other, what matters is whether it fits your company’s site conditions and operational setup.

For example, if communications are stable in urban areas and the work location changes daily, network-based operations are reasonable. On the other hand, if operations are mainly in mountainous areas, construction sites, or remote locations where communications are unstable, fluctuations in connection quality themselves become the bottleneck for RTK operations. In this case, even if the receiver unit itself is excellent, it becomes difficult to use in practice if correction information cannot be received stably.

Also, it’s not just whether a connection exists but how stable it is that matters. Situations such as connecting but dropping frequently, quality varying by time of day, or tethering to a device being unstable create significant stress on site. RTK is convenient when it works, but if there are prolonged periods when it doesn’t, it quickly loses trust. Therefore, it is important not to overlook communication conditions during the selection phase.

Additionally, the way correction information is received affects on-site work procedures. Whether you need to log in or configure settings every time, whether reconfiguration is complicated when changing devices, and whether it’s easy to isolate problems during network outages—these points directly affect the operational burden after deployment. In practice, smoother startup from morning power-up to the start of observations can be more important than theoretical usability.

When selecting RTK, it's important not to regard the method of correction information merely as a technical specification, but to judge whether the field team can operate that method smoothly. Not only comparing equipment performance, but also considering whether use will be mainly within communication coverage, involve moving between multiple sites, or require site-by-site operations in the future will improve the accuracy of your selection.

4. Don't overlook device integration and ease of app operation

RTK is often thought to be complete with the receiver alone, but in actual operations, device integration and app usability greatly affect work efficiency. If these are overlooked, you may find that, even though you were satisfied with the accuracy and price when you implemented it, on-site operations become cumbersome and it fails to gain traction.

The usability of RTK in the field can vary greatly depending on what device is used on-site. Whether you primarily use a smartphone, a tablet, or a dedicated controller affects screen readability, ease of input, portability, and the availability of alternatives in case of failure. For example, if you want to handle photos, maps, and location records together in the field, the more compatible the device is with the one you use daily, the smoother the work will be.

In this respect, it is very important to assess compatibility with existing device operations. If every time a new RTK is introduced you have to learn different devices or apps, the burden on site staff increases. Conversely, if it can be configured to integrate naturally into the devices and workflows you already use, training costs decrease and usage tends to increase. An RTK may be high-performance, but it is meaningless if it is not used.

Also, for app operation, simply showing the location is not enough. It is important that the app supports the required coordinate storage formats, can record entries together with photos and notes, makes it easy for multiple people to share data, and makes it easy to verify the same point on revisits—features that align with practical fieldwork. These aspects are hard to see in comparison tables and only become apparent when you actually imagine operating the app.

Connection stability should not be overlooked. Issues such as the connection between the device and the RTK receiver frequently dropping, reconnections being cumbersome, or the app becoming unstable when running in the background are difficult to quantify, but they directly affect on-site satisfaction. The accumulation of minor hassles ultimately becomes a reason for people to stop using it.

Recently, RTK configurations that enhance compatibility with smartphones have become more common, and more companies are considering field operations that assume the use of iPhones. For example, iPhone-mounted GNSS high-precision positioning devices such as LRTK are one of the easier-to-envision options when you want to incorporate high-precision positioning while leveraging a device you use every day. The important point is not that a particular method is always the correct one, but whether it can be adopted without disrupting your company’s device operations.

To avoid regretting your RTK selection, you need to think concretely not only about receiver performance but also about who will use which device, which app they will use, and how the data will be recorded. The more seamless the device integration, the more RTK will become established not as a special piece of equipment but as an everyday operational tool.

5. Durability in the field is determined by how it is used rather than by the spec sheet

When selecting an RTK, attention often focuses on dust and water resistance and overall durability, but resistance to field conditions is not determined solely by a high protection-rating number. The durability you actually need depends on the type of site, who will use it, how often, and how it will be held or carried.

For example, paving and earthwork sites are easily affected by dust, while in forests and development sites the risk of falls and impacts increases. At sites where many observations are made in rainy weather, water resistance is important, and in hot summer environments heat management for the terminal cannot be ignored. Even if the receiver itself is rugged, if the connected terminal becomes unstable due to heat, the RTK system as a whole becomes difficult to use. In other words, you need to assess whether the entire RTK system can withstand the conditions on site.

Also, for outdoor use, ease of carrying and storage is also important. Issues such as being too heavy, having many protruding parts, or being cumbersome to take in and out of its case may not appear on the spec sheet, but they have a major impact on daily operation. In particular, when shared among multiple people, you should consider whether the operation will remain viable under somewhat rough handling, rather than assuming it will always be treated carefully.

Furthermore, robustness to field environments isn’t just about being unlikely to fail. It also includes how easy it is to isolate the cause when a failure occurs, how easy it is to operate with a spare unit, and how easy it is to replace parts or peripheral equipment. In practice, there are situations where the ability to recover quickly after a stoppage is more important than simply not breaking. Especially during busy periods or continuous on-site operations, unexpected stoppages have a greater impact on work.

If you only look at the comparison table here, you tend to think that a higher dust and water resistance rating is safer, but in reality, everyday handling—such as case use, storage methods, charging management, and rules for taking equipment out—often has a significant impact on failure rates. In other words, the robustness of RTK equipment is not determined by the product alone but is decided together with the site’s operational design.

Therefore, when selecting equipment, it is useful to carefully identify the conditions at the worksite. Will there be frequent work in rain, a lot of dust, frequent vehicle movement, frequent walking, use in confined spaces, or a need for one-handed operation? Once these conditions are clear, the required durability, form factor, and accessory choices also become apparent. If you want to continue using RTK for a long time, it is important to choose not just based on numerical strength but assuming operations that can withstand the roughness of the site.

6. Your choice depends on whether it can be used alone or operated by multiple people

When choosing an RTK, it's easy to focus on the device's capabilities, but what actually determines the success or failure of implementation is who will be using it. Whether only a specific person will use it or multiple people across the site will use it greatly changes the optimal choice. If this perspective is missing, the system may work initially but become unusable the moment personnel change.

If a single experienced operator is assumed, the operation may be feasible even if there are many settings or fine adjustments are required. However, the situation changes when the system is shared among multiple people. If the startup procedure is complicated, if it cannot be used without understanding the quirks of the connections, or if important cautions during observations become tacit knowledge, operational quality will vary greatly depending on the person in charge. This is a very common problem when introducing RTK.

What's important in multi-person operations is that procedures be easy to explain and easy to reproduce. It's crucial that the workflow—from powering up the equipment in the morning, receiving correction information, verifying coordinates, conducting observations, to saving records—can be easily standardized into a manual. Even excellent RTK equipment will be difficult to operate continuously if operating procedures vary between personnel.

Also, the training burden is one of the selection criteria. Whether it can be started with just an initial briefing, requires a few sessions of accompaniment, or presumes understanding of coordinate systems and correction information will affect how easily it can be deployed internally. On-site, because workers must learn new tools amid busy schedules, configurations that can be used intuitively are more readily accepted.

Additionally, when multiple people are involved, data management is also important. If it’s unclear who measured which points, how they are named when saved, and where they are shared, then even high-precision data obtained with RTK cannot be used in downstream processes. It is the establishment of operating rules—not the equipment itself—that determines the outcome.

With this in mind, RTK selection can be said to be an act of choosing an operational design that fits the on-site organization, rather than comparing equipment performance. Whether a small number of people will use it frequently or it will be shared among many, whether most users are beginners or experienced surveyors make the optimal configuration different. To avoid regret, it is important to judge not by the most experienced person but by whether an average user can use it without difficulty.

7. Consider ongoing operating costs, not just upfront installation costs

When selecting RTK, the initial acquisition price inevitably draws attention. Indeed, upfront costs are important, but judging solely on that often leads to regret. RTK is not a device you buy and forget; its value emerges through continued use. Therefore, what you should evaluate is not the purchase price but the overall burden, including ongoing operational costs.

Recurring operational costs include fees for correction information services, communication charges, device update/replacement costs, management of batteries and accessories, responses to failures, training time, and the effort required to organize data. Each of these may seem small on its own, but when accumulated over years they cannot be ignored. In particular, as the number of sites increases, the time required for setup and training also becomes a cost.

Also, even if you think you chose a low-cost configuration, poor connections or operational complexity can increase working time and make it effectively more expensive. For example, situations such as each startup taking a long time, frequent redoing of observations or data saves, or having only a limited number of people in charge so that personnel coordination becomes necessary, all increase hidden costs. RTK is often introduced to save time, so if operation requires extra time, that defeats the purpose.

Conversely, even if the upfront implementation cost appears somewhat high, if it is easy for anyone to use, integrates smoothly with existing devices, and can be naturally incorporated into daily operations, it may prove more cost-effective in the long run. In particular, if it can be expected to reduce on-site labor, speed up verification tasks, and cut down on re-measurements, it is risky to judge solely by simple price differences.

What matters here is to evaluate costs not just for the equipment itself but in terms of overall operational improvement. You need to assess the implementation's on-site impact in non-monetary terms—how many minutes it can save, how the number of people required to perform tasks will change, how the quality of records will improve, and whether it will lead to reductions in outsourcing or revisits.

Furthermore, you should consider future scalability. Even if it will be used by only one department at first, if it proves effective you may want to expand it to other departments or sites. At that point, whether it can be rolled out under the same operational rules, whether adding devices or accounts is easy, and whether the training burden won’t grow too large are important considerations. RTK is an area where differences tend to appear more when scaling up than at the moment of introduction.

To avoid regretting your RTK selection, it's essential not only to compare prices but also to determine whether it will make things easier when you continue using it. Rather than opting for the cheapest option, the ability to continue using it without strain will ultimately provide greater value.

Final things to confirm when selecting RTK

So far, we have looked at seven perspectives to avoid regretting your RTK selection. In retrospect, choosing an RTK is not a simple equipment comparison but a comprehensive decision that includes deliverables, required accuracy, correction information, device integration, field conditions, users, and ongoing costs. Comparison tables become useful after you have organized these priorities. If you try to decide by looking at a table from the start, you are likely to overlook the conditions you should actually prioritize.

A practical approach that is unlikely to fail is to choose one representative site within your company and concretely map out how the system will be used at that site. By thinking through the workflow—who will carry it out, where correction information will be received, what will be recorded, how much accuracy is required, and in what format the results will be delivered—you will see the conditions that are truly necessary. If you can configure the system so that this workflow can be depicted, RTK implementation is more likely to succeed.

Conversely, if you choose a device solely because it is inexpensive, appears highly accurate, or has many functions, it may turn out after deployment that the procedures are complicated, the communication conditions are incompatible, or on-site personnel do not adopt it, resulting in equipment that goes unused. For RTK, the value lies not in being highly accurate per se but in being able to be used without hesitation in the situations where it is needed.

Especially if you are planning to incorporate RTK into daily operations, it’s important to consider not only positioning performance but also integrated operation with devices and apps. If you want to balance convenience and practical utility centered on a smartphone, you may find it easier to consider a configuration that’s straightforward to picture operating as an iPhone-mounted GNSS high-precision positioning device, such as LRTK. What matters is not the product name itself but whether it fits naturally into your company’s field operations.

To avoid regretting your RTK selection, the shortcut is to think in terms of the on-site vertical workflow rather than a side-by-side comparison table. What you should check before implementation is less the differences in performance than the differences in the conditions that allow continued use. With that perspective, RTK is more likely to function not just as a high-precision instrument but as a practical tool that boosts the quality of on-site decision-making and recordkeeping.