How to Choose an RTK-Compatible Surveying App: 5 Ways to Avoid Failure with Accuracy and Usability

Table of Contents

‐ Summary

• Why RTK-compatible surveying apps are attracting attention

• Causes of failure when choosing an RTK-compatible surveying app

• How to choose an RTK-compatible surveying app 1: Can it stably ensure accuracy?

• How to choose an RTK-compatible surveying app 2: Is it intuitive to use on site?

• How to choose an RTK-compatible surveying app 3: Does it support the surveying tasks you need?

• How to choose an RTK-compatible surveying app 4: Is the handling of coordinates and data adequate?

• How to choose an RTK-compatible surveying app 5: Can you foresee post-introduction operations?

• Checkpoints to confirm before introduction

• Frequently asked questions when selecting an RTK-compatible surveying app

• Summary

Why RTK-compatible surveying apps are attracting attention

Traditionally, on-site positioning work has often been planned on the assumption of dedicated equipment and experienced operators, and not only the measurement itself but also surrounding tasks such as recording, transcription, drawing reflection, and sharing took a lot of time. In contrast, RTK-compatible surveying apps leverage highly portable devices to obtain high-precision position information and have strengths in making it easy to carry out the entire workflow on site: point recording and verification, linking with photos, overlaying on drawings or maps, and cloud sharing.

Especially in practical fieldwork, not every task requires the highest-level surveying equipment. There are many situations where substantial efficiency gains can be achieved if centimeter-level (half-inch level) position information can be obtained—for example, checking current conditions, simple as-built confirmation, checking stake positions, on-site matching of boundary candidates, and confirming locations of buried objects or equipment. For that reason, RTK-compatible apps that do not assume heavy equipment and can be started quickly and handled by a single person are receiving attention both for improving site productivity and for addressing labor shortages.

Furthermore, from the perspective of digitizing recording tasks, these apps are also important. It is not enough to simply capture position information: an app that can handle coordinate values, photos, attribute information, notes, and point names together will greatly simplify downstream organization. The need to re-enter data captured on site back at the office is reduced, and sharing or transcription errors are less likely. In other words, the value of RTK-compatible surveying apps lies not only in improving positioning accuracy but in shortening the entire flow from the field to reporting.

Causes of failure when choosing an RTK-compatible surveying app

Many selection failures for RTK-compatible surveying apps come from judging based only on a list of features. Catalogs and descriptions are full of attractive words like RTK support, high accuracy, easy operation, and cloud integration, but the substance matters in practice. For example, even if an app is RTK-compatible, there are differences in the conditions for receiving correction information, dependence on the communication environment, ease of initialization, stability of the Fix state, and behavior in sites with obstructions. If you don’t check these, an app that looks high-performance on paper may not function as expected on site.

Also, placing too much emphasis on accuracy alone causes failure. For field practitioners, it is often more important that the app can be used consistently with the same procedure every time, that anyone can use it without confusion, and that results can be reviewed immediately. Even if accuracy is high, an app whose operation is complicated and whose settings take time each time is likely to be avoided on busy sites. As a result, only a few knowledgeable staff members end up using it and it does not become established across the organization.

Another often overlooked issue is post-acquisition data utilization. Even if coordinates are captured on site, if they are difficult to reflect on drawings, format conversion is cumbersome, sharing methods are limited, or linking with photos is unclear, manual work returns in the end. A surveying app should be judged not only at the moment of measurement but including recording, organizing, sharing, and reuse.

In this way, the causes of selection failure lie in judging only by accuracy figures or the presence of functions without concretely imagining actual operational scenes. From the next chapter, we will look at five selection principles in order to avoid failure.

How to choose an RTK-compatible surveying app 1: Can it stably ensure accuracy?

The first thing to confirm is not a single ideal value but whether accuracy can be stably ensured under field conditions. RTK-compatible surveying apps have the potential to achieve high-precision positioning, but that accuracy is greatly influenced by the surrounding environment, satellite reception conditions, the reception state of correction information, the combination of terminal and receiver, and user procedures. Therefore, before introduction, it is important to determine not how high the accuracy can be, but how reproducibly the accuracy required in practice can be achieved.

For example, an app may work well in open areas but show differences in accuracy or Fix maintenance near buildings, around trees, in terrain with elevation differences, or in sites with unstable communications. What matters here is whether the app can display positioning status clearly: whether it is Fix, what the estimated accuracy is, and whether anomalies are easy to notice. Even if points appear to be captured visually, if the status display is insufficient, users may adopt data with large errors as is.

It is also important to have mechanisms that support accuracy assurance, such as averaging, re-observation, adjustment of observation time, and quality checks for each measured point. Because fieldwork is a race against time, simply claiming high accuracy is not enough. The difference in practical operation lies in whether the app supports how to judge, how to correct, and how to reacquire data in situations prone to errors.

Moreover, it is essential to consider required accuracy by task. The strictness of accuracy required differs for current condition surveys, construction records, simple position checks, on-site boundary matching, and as-built confirmation. If you apply the same accuracy standard to all tasks, you may demand excessive features and sacrifice usability, or conversely choose an app that cannot meet the necessary accuracy. First divide your company’s tasks and clarify how much reproducibility is needed for each task, and evaluate whether the app meets those requirements.

In short, when evaluating the accuracy of RTK-compatible surveying apps, you should prioritize stability, reproducibility, visible state indicators, and ease of quality checks rather than peak performance. If this is left vague at introduction, the difference between when it works and when it doesn’t on site will be large, and the app will eventually fall out of use.

How to choose an RTK-compatible surveying app 2: Is it intuitive to use on site?

The next priority is whether the app is intuitive to use on site. Surveying apps differ from office software that is used carefully indoors: they are used outdoors, while moving, and under time pressure. Users may operate with gloves on, struggle to see the screen in sunlight, or work in locations with unstable communications. Under these conditions, being able to operate without hesitation is more important than having many functions.

There are several common traits among easy-to-use RTK-compatible surveying apps. First, the steps to start work are short. It is crucial that the flow—from device connection, checking reception of correction information, confirming positioning status, to recording points—is easy to understand so that even a first-time user can start within a few minutes. Apps that hide settings in deep menus or spread status checks across multiple screens impose burdens on the field.

Next is clarity of screen display. It should be structured so that at a glance users can understand what state they are in, whether it is Fix, whether communications are stable, whether a point has been recorded, which coordinate system is in use, and whether photos and attributes have been attached. Especially when multiple people use it, reducing operational mistakes due to experience differences depends heavily on screen design.

Also important are ease of point registration, photo attachment, and attribute input. If each input takes time on site, omissions or postponements occur. Apps that make it easy to implement point naming rules, clearly link photos to points, provide simple note entry, and support continuous observations reduce daily operational load and are more likely to be adopted.

When evaluating operability, it is important not only that the person responsible for procurement tests it, but that the actual field personnel can try it in a short time. An app highly rated in selection meetings will not deliver results if the people using it in the field find it difficult. Because usability from the field perspective is hard to see from the specifications alone, it is necessary to verify it along the workflow.

An RTK-compatible surveying app’s practical value lies not in having high-precision features alone but in being usable repeatedly in the field without strain. Apps that anyone can handle at the same level are best suited for organizational adoption.

How to choose an RTK-compatible surveying app 3: Does it support the surveying tasks you need?

The term RTK-compatible alone does not determine which tasks an app is suited for. The third selection point is to confirm whether it supports your company’s necessary surveying tasks. “Support” here means more than simply being able to record points: it means being able to handle the required information seamlessly in the workflow of that task.

On-site use of surveying apps spans many tasks: current condition surveys, layout setting, stake-driving guidance, as-built confirmation, boundary checks, photo records, recording equipment locations, and simple earthwork volume checks. For example, on sites where layout setting is a priority, important considerations are whether guidance to target points is easy to see, whether direction of travel and remaining distance are intuitive, and whether multiple points can be followed in sequence. If current-condition surveys are the focus, it is important whether points can be captured continuously, whether line and area management is easy, and whether attribute information can be grouped. If the aim is construction records, emphasis is placed on whether photos can be strongly linked with coordinates, and whether point names and notes are easy to review afterward.

Thus, even among RTK-compatible apps, strengths differ by task. An app with many functions may be hard to use on site if it does not fit essential workflows. Conversely, an app that excels in a narrow set of necessary tasks tends to yield higher on-site satisfaction.

Whether an app supports tasks also affects output. How it organizes and exports point information, photos, simple sketches, and attribute data—not point clouds—greatly influences downstream efficiency. Apps that organize measured data in forms that drawing personnel or managers can readily use contribute to overall optimization.

During selection, it is effective to enumerate the actual tasks that occur on site and confirm for each task how the app enables completion. Rather than vaguely asking if it can be used for surveying, evaluate per unit: can it be used for current-condition checks, layout setting, as-built confirmation, or photo recording? This approach improves selection accuracy.

How to choose an RTK-compatible surveying app 4: Is the handling of coordinates and data adequate?

When introducing an RTK-compatible surveying app on site, the handling of coordinates and data is extremely important. If you overlook this, the app may be convenient on site but increase office workload afterward. In surveying work, the outcome is determined more by how data is organized, utilized, and shared after capturing points than by the instant of capture. Therefore, choose an app with the data outputs in mind.

First, check coordinate handling. In practical use, you often want to confirm coordinates not only in latitude/longitude but also in more convenient coordinate systems such as plane rectangular coordinates. If the app is inflexible here, you will need conversion work after acquisition, which introduces not only effort but potential errors. Ensure that coordinates can be handled in a way that aligns with site drawings, existing data, and management ledgers.

Next, consider data output and ease of sharing. Can point information, photos, attributes, and notes be exported together? Can you confirm them in an organized list? Are they easy to share with others? These aspects directly affect daily efficiency. If output formats are limited or the linkage between photos and coordinates is unclear, manual work will be necessary for report creation and drawing updates. Introducing an app to save time on site but losing time downstream defeats the purpose.

The approach to cloud sharing and history management is also important. Apps that make it easy to trace who captured which points, when, and where are suitable for multi-user operations. In construction management and maintenance, it is common to want to recheck the same location later. Being able to quickly call up past data and easily re-verify on site is highly valuable.

Moreover, functions for overlaying photos or drawings and in-field visualization expand an app’s role from a simple coordinate recorder to a site support tool. The ability to transform captured position information into formats easily understood by stakeholders enhances practical utility.

In short, the ease of handling coordinates and data is fundamental to app convenience. Confirm whether the flow from measuring to storing, reviewing, sharing, and reusing is seamless to avoid selection mistakes.

How to choose an RTK-compatible surveying app 5: Can you foresee post-introduction operations?

The fifth point is whether you can foresee post-introduction operations. App selection often stops at the function comparison stage, but whether you obtain results depends on post-introduction adoption. No matter how good an app is, it is meaningless if it fails to permeate the field.

First consider training burden. If only one knowledgeable person understands the app at introduction, operations will stop when personnel change. Whether the app is intuitive enough to be used without a manual, whether field staff can start using it after a short explanation, and whether routine inquiries are few all greatly affect continued use.

Next, consider adaptability to field conditions. Outdoor work brings challenges such as unstable communications, power management needs, device heating and visibility issues, and desires to simplify procedures. It is important to consider whether the app remains easy to use under these constraints. Especially when handling high-precision positioning, the stability of connections between terminals and receivers and clarity of status confirmation directly impact operational quality.

Also check whether the app fits into internal workflows. How will data captured by field staff be connected to managers, designers, subcontractors, and client presentations? An app that fits such flows functions not merely as a field tool but as a business platform. Conversely, an app that is convenient on site but hard to roll out to other departments will have limited impact.

Additionally, consider potential for future expansion. What starts as simple surveying or construction recording may later evolve into as-built management, AR display, cloud sharing, or integration with maintenance ledgers. Apps with room for such expansion tend to offer higher return on investment.

Selecting with post-introduction operations in mind means thinking not only about current issues but how you want to use the app six months or a year from now. RTK-compatible surveying apps should be chosen as an entry point to field digitalization rather than as a standalone tool.

Checkpoints to confirm before introduction

So far we have explained five selection principles; concretizing what to check in actual selection makes decision-making easier. First, clarify your company’s main intended use. Depending on whether it is current-condition surveys, layout setting, as-built confirmation, or construction records, the functions to prioritize change. If intended use is unclear, comparison criteria become vague, and you may end up choosing something that merely looks convenient.

Next, list the expected field conditions. Whether you often work in open sites, near buildings, in mountainous or tree-covered areas, or in regions with unstable communications will change the required positioning stability and confirmation procedures. Usability requirements differ for urban renovation sites and suburban land development sites.

Also think specifically about who will use it. Whether users are primarily surveyors, construction managers using it as a secondary duty, or whether you want common operation across multiple locations affects acceptable usability and training burdens. An app optimized for experienced users may be difficult for non-specialists.

Confirm the data destination in advance as well. If you know where the captured coordinates and photos will be used, who will check them, and how they will be reflected in drawings and reports, you can identify the required output formats and sharing methods. If you introduce an app without deciding this, you will have to create operational rules after starting use, leading to confusion.

In short, before comparing apps, organize your company’s purpose, field conditions, users, and data destinations—these four items are the shortcut to successful selection. Then evaluate candidates using the five perspectives explained above to greatly reduce the chance of failure.

Frequently asked questions when selecting an RTK-compatible surveying app

One common question from practitioners is whether a dedicated receiver is required. In short, to stably use high-precision RTK positioning in practice, it is generally necessary to combine the app with a receiver that supports high-precision positioning and to utilize correction information. The app is primarily a window for operation and recording, and positioning quality heavily depends on the surrounding configuration. Therefore, consider the positioning setup to be used at the same time as selecting the app.

Another frequent question is whether users with little field experience can use it. This depends on the app. Apps with clear status displays and organized workflows are easier to start using after a short explanation. Conversely, apps with overly detailed settings or those that leave positioning-quality judgments to the user are difficult for inexperienced staff. If you plan organizational adoption, prioritize an app that standard staff can use without confusion rather than one that only advanced users can master.

People also ask whether an RTK-compatible app can replace all surveying tasks. It is important to segment uses appropriately. While many tasks can be made much more efficient with apps, work that requires strict accuracy control or advanced observations may still require specialized methods or equipment. The key is not what to replace but identifying which tasks will benefit most from introduction.

Additionally, questions arise about what is needed for stable operation. For that, consider not only app selection but also the combination of positioning equipment, the environment for receiving correction information, power management, terminal operation rules, data naming rules, and re-observation criteria—i.e., operational design as a whole. To achieve results on site, organizing operational rules is as important as selecting tools.

Summary

What really matters when choosing an RTK-compatible surveying app is not the term RTK-compatible itself. The five perspectives that lead to a failure-free choice are: whether it can stably ensure the accuracy required in practice; whether it is intuitive to use on site; whether it fits your company’s tasks; whether coordinates and data are easy to handle; and whether it can be adopted smoothly after introduction.

Especially in surveying apps, deciding based only on accuracy comparisons tends to lead to failure. High accuracy that is hard to use will not be used on site, and a feature-rich app that does not match workflows increases work. On the other hand, an app that can reproducibly provide the required accuracy under field conditions, is usable by anyone in the same way, and whose acquired data can be applied directly to downstream tasks can dramatically change site productivity.

If you are considering introduction, first clarify which tasks you want to streamline, and evaluate candidates against the five perspectives for those tasks. By doing so, you can make a choice that contributes to field-wide digitalization rather than merely selecting an app.

If you want to set up a positioning environment that is more closely tied to practice with higher accuracy while utilizing a smartphone, configurations such as LRTK—a high-precision GNSS positioning device that mounts on an iPhone—are also strong options. If you want to enable single-person simple surveying, layout setting, photo recording, and coordinate capture on site, consider evaluating not only standalone apps but operations that integrate high-precision positioning devices, which will make the benefits of RTK more tangible.