RTK Surveying App Comparison | 7 Checkpoints to Avoid Regrets on Site

Table of Contents

\- What is an RTK surveying app \- Why comparing RTK surveying apps is important \- Checkpoint 1: Visibility of accuracy display and Fix determination \- Checkpoint 2: Availability of observation functions needed on site \- Checkpoint 3: Scope of supported coordinate systems and correction information \- Checkpoint 4: Usability and suitability for solo work \- Checkpoint 5: Ease of data output and in-house sharing \- Checkpoint 6: Integration with photos, drawings, and AR \- Checkpoint 7: Designed for sustainable operation \- Common mistakes when comparing RTK surveying apps \- How to choose an RTK surveying app by use case \- Summary

What is an RTK surveying app

An RTK surveying app refers to an application that works with a GNSS receiver, uses correction information to obtain high-precision positions, and supports point recording, stakeout, and simple surveying tasks. RTK stands for Real-Time Kinematic, a widely known technique that corrects satellite positioning errors aiming for centimeter-level position accuracy (cm level accuracy (half-inch accuracy)).

However, it is important to note that RTK accuracy itself is not determined by the app alone. Actual accuracy varies depending on multiple factors such as the satellite reception environment, the quality of correction information, receiver performance, antenna setup conditions, communication status, and observation methods. Among these factors, the app plays a role in how usefully the obtained position information is displayed, recorded, verified, and reused on site.

In other words, when comparing RTK surveying apps, simply checking whether they are “high-precision” is insufficient. To turn high-precision positioning into practical results, you need screen designs that make on-the-spot decisions easy, support for required coordinate formats, ease of recording, and operation that avoids confusion on site. Think of the app not as the entry point of positioning but as a tool that determines the efficiency of the entire operation.

Why comparing RTK surveying apps is important

You need to compare RTK surveying apps because even if multiple apps say they support “RTK,” what they can actually do can differ greatly. One app may be strong at point acquisition but weak at drawing review or photo documentation. Another may excel at map display and sharing but make detailed observation management difficult. Even if two apps look similar, their on-site usability can be completely different.

Also, RTK positioning often cannot be treated like a regular map app. For example, day-to-day tasks include confirming the stability of a Fix solution, understanding the connection status of correction information, deciding whether to re-observe in areas with unstable positioning, checking against known points, choosing a coordinate system, and confirming output formats for deliverables. Whether you can perform these checks without stress affects both on-site speed and the rate of rework.

Moreover, even if things look fine at introduction, inconveniences can emerge during operation. For example, you might initially think that being able to capture points is enough, but later need stakeout guidance, as-built verification, photo logs, cloud sharing, or coordinate-annotated drawings. If an app has low extensibility or poor integration, you may need to add other tools or organize records manually.

That is why, when comparing RTK surveying apps, it’s important to choose while considering not only current use but also operation six months or a year later. Below are seven checkpoints to remember to avoid regrets on site.

Checkpoint 1: Visibility of accuracy display and Fix determination

The first thing to check is how clearly the positioning status is displayed. When comparing RTK-capable apps, beginners tend to judge only by whether the app “supports RTK,” but in practice the next step matters. It is essential that information such as whether the current position is Fix, Float, or standalone positioning, whether correction information is being received stably, and what the estimated accuracy is, be displayed intuitively on site.

This is because RTK does not always deliver the same quality of positioning. In locations with poor sky view, near buildings or trees, or with weak communication, maintaining a Fix can become difficult. If the app’s screen is hard to understand, the operator will find it difficult to decide “whether to accept this point now.” As a result, low-accuracy points may be recorded by mistake, or operators may wait unnecessarily even when a point could be taken.

When comparing, check whether accuracy is shown not only numerically but also using colors or icons for easier understanding. On site, decisions often need to be made quickly while wearing gloves, so designs that require opening detailed menus to see status are at a disadvantage. Apps that show the number of satellites, correction connection status, solution type, estimated accuracy, and position update status at a glance on the home or observation screen are more suitable for practical use.

It is also important whether quality can be easily checked before and after observations. For example, if the app can store the observation state for each acquired point, later inspection becomes easier. Even if a point seems fine at the moment it is taken on site, you may feel in the office that “conditions at that point were poor.” If Fix determination and accuracy information are recorded in the history, it is easier to decide whether to re-observe.

When comparing RTK surveying apps, focusing on how accuracy is presented rather than accuracy alone will reduce failures. Apps that provide clear decision-making information on site help stabilize work quality.

Checkpoint 2: Availability of observation functions needed on site

Next, confirm whether the app includes the observation functions actually needed for on-site work. Even if an app is labeled RTK-capable, some offer only “current location display” and “point saving.” On the other hand, apps that are truly useful on site include not only point recording but also continuous observation, attribute entry, line and area capture, stakeout, known-point verification, photo attachment, and other functions aligned with workflow.

It is important to picture the tasks you will perform. Whether your work focuses on boundary confirmation and site condition surveys, requires stakeout guidance for stake driving, is used as support for construction quality control, or aims to perform simple volume estimation and drawing verification will change which functions you should prioritize. For example, if you only need single-point observation, extensive functionality is unnecessary, but if you frequently perform stakeout, direction and distance to the target should be displayed clearly.

Attribute entry at the time of recording is another often-overlooked point. Whether you can link point name, type, notes, photos, and management number on site greatly affects how easy later processing is. While it is possible to supplement with a paper field notebook or another app, the more input steps you require, the higher the risk of missed records or transcription errors. Apps that let you save required information together at the time of observation lead to improved on-site quality.

Also check how easy it is to re-observe or edit points. On site, you may review a point taken previously and measure it again. The ease of finding the target from the point list, overwriting or managing history, and whether the original record is preserved directly affects operational convenience.

Beginners often think more features are better, but what really matters is whether necessary functions are included in a form that can be used without confusion on site. During comparison, imagine operating along your workflow rather than judging by the number of features on the spec sheet.

Checkpoint 3: Scope of supported coordinate systems and correction information

A particularly important item in RTK surveying app comparison is support for coordinate systems and correction information. Overlooking this can lead to a situation where positioning can be performed but the deliverables cannot be used. On site, more cases require handling plane rectangular coordinate systems, local coordinates, or site-specific reference systems than cases that only need latitude and longitude. Therefore, you must check before introduction which coordinate systems the app can handle and how.

For example, for public surveying or sites involving comparison with design data, apps with ambiguous coordinate handling are unsuitable. Even if they can display coordinates, if output formats are limited or conversion flexibility is low, you will end up doing corrections or reorganization in separate software. That negates the efficiency gains you expected on site and increases office work.

Support for correction information is equally important. Using RTK in practice requires reliably receiving network-based correction information or correction data from a base station. What to check here is not just whether a connection can be made. Operational aspects such as whether connection settings are easy to understand, whether reconnecting is simple, whether it’s easy to understand the state when communication is interrupted on site, and whether switching connection sources is flexible are important.

Some sites have constrained communication environments. In mountain areas, reclaimed land, or around high-rise buildings in urban areas, receiving correction information may be unstable. In such locations, whether the app clearly indicates state changes and whether you can smoothly resume observations after recovery makes a significant difference in practice.

Coordinate systems and correction information may feel somewhat difficult for beginners, but neglecting them affects areas that are hard to correct later. When choosing an app, check this item carefully as a foundation that correctly links on-site data and deliverables, not only facial usability.

Checkpoint 4: Usability and suitability for solo work

When using an RTK surveying app on site, usability is as important as accuracy. In recent years, demand has grown for operators to handle positioning, recording, verification, and photo capture while moving around the site alone. Therefore, apps with simple screen layouts that make it easy to know what to do next perform better in daily operation.

For example, apps that require navigating through many screens to start an observation may seem fine initially, but become a growing burden when taking dozens of points on site. In environments with strong sunlight, rain, glove use, or moving while checking, a high number of operations leads to mistakes. Problems like thinking a point was saved when it wasn’t, skipping attribute entry, or delaying correction state checks are more likely with complex screen designs.

When comparing, pay attention to button size, readability, one-handed operation, and quick access to frequently used functions during observation. An app that looks high-functioning on a desktop may feel like “necessary information is scattered” or “there are too many settings to choose from” on site. Conversely, apps with commonly used flows organized are easier for new users to adopt quickly.

If you expect solo work, check whether the sequence from target guidance to checking current position against drawings, photo recording, and reconfirmation from the point list is smooth. Especially for stakeout and position checks, you often look at the screen while walking, so displays that intuitively convey direction and distance are important. Visual guidance as well as numeric values helps less experienced operators handle tasks.

Training cost is also non-negligible. If only a few specialists can use the app at deployment, it won’t spread through the organization. Apps with good usability are easier to learn on site without long explanations and help prevent reliance on specific individuals. In RTK surveying app comparison, this practical aspect, which is hard to see from spec sheets, should be reviewed carefully from the field perspective.

Checkpoint 5: Ease of data output and in-house sharing

Capturing points on site is rarely the end of the story. The purpose of introducing an RTK surveying app is not only to obtain position information but to share results in-house and utilize them in drawings, photos, reports, and construction records. Therefore, ease of data output and sharing is an important comparison criterion.

For example, whether point data can be exported in common formats, whether coordinates and attribute information can be output together, and whether photos remain linked to location data affect office work efficiency. Even if an app is convenient on site, low flexibility in output forces additional processing when transferring data to spreadsheets, CAD, or cloud systems. That increases work and raises the risk of conversion errors or misidentification.

Ease of sharing directly affects coordination between field and office. Whether observation results can be uploaded to the cloud immediately, sent by email or shareable link, or remain confined to the device determines daily workflow speed. Especially when multiple people handle the same site, ambiguity about who captured which point, which dataset is the latest, or where photos are stored causes extra verification time.

Ease of reusing past data is also important. It is common to reference previously captured points or lines at the next site visit. If data are easy to search and review on the map or in a list, the app becomes a tool for accumulating site assets rather than just a recording app. Conversely, if output is possible but in-app organization is weak, accumulated data become harder to find.

When comparing RTK surveying apps, do not focus only on observation functions; consider how data flow from the field to in-house systems. Apps that make output and sharing easy demonstrate clearer operational improvement after introduction and are easier for teams to use.

Checkpoint 6: Integration with photos, drawings, and AR

Modern RTK surveying apps increasingly offer integration beyond mere position acquisition, including photos, drawings, background maps, and AR displays. This is not mandatory, but if you want to streamline on-site verification and information sharing, it is highly valuable. Especially when beginners or non-survey professionals use the app, systems that convey spatial relationships visually as well as numerically make operation easier.

First, photo integration alone provides considerable advantages if photos can be saved with location data. If you can keep photos of boundary markers, existing structures, pre- and post-construction records, or obstacle positions tied to point data, later review becomes much clearer. When notes and photos are separated into paper or different folders, associations become ambiguous over time. Whether the app naturally links points and photos is very important in practice.

Drawing integration is also a comparison point. Being able to overlay design drawings or simple plans for position checking speeds up decision-making on site. Instead of verifying points in the office after capture, you can confirm on site whether “the measured position deviates from the expected position” or “where additional points should be taken.” Overlay functions reduce rework, especially for as-built checks and stakeout support.

Further, apps with AR integration make on-site understanding more intuitive. For example, if you can overlay target points, boundary lines, or design positions onto real space, the burden of interpreting numbers is reduced. AR is not perfect and is affected by device pose estimation and the environment, so use according to purpose is necessary. However, for stakeout or consensus-building moments, AR can aid site understanding beyond drawings alone.

When comparing, determine whether these visual integrations are mere showpieces or genuinely useful for practical work. Photo, drawing, and AR integration benefits not only survey specialists but also construction managers, site supervisors, and clients, so the broader the intended use, the more weight you might give this feature.

Checkpoint 7: Designed for sustainable operation

The final checkpoint is whether the app is designed to be easy to operate over the long term. An RTK surveying app may look good in an initial demo or short trial, but small inconveniences can accumulate over months of use. Therefore, when comparing, focus not only on isolated functions but also on long-term stability and manageability.

First, check compatibility with devices. Field devices vary in brightness, battery life, communication performance, and operability. If an app is only stable on certain device environments, operational inconsistencies will arise by site. Stability aspects—whether connections to external receivers drop frequently, whether reconnecting is easy, and whether temporary communication instabilities recover smoothly—are not visible in catalogs but are critical.

Next, don’t overlook data and project management. Can you organize data by project, prevent mixing between operators, easily reference past projects, and resist accidental deletion or overwriting? These points matter more as operations scale. While the first few projects can be handled manually, as the number of projects grows, a design that facilitates organization will greatly affect efficiency.

Ease of training is also part of sustainable operation. If an app can only be used by a few knowledgeable people, it won’t spread across the organization. Consider whether new staff can learn it quickly, whether screens and terminology are clear, and whether a standard workflow can be established—these factors matter for long-term use.

Finally, consider whether the app can accommodate future usage. Even if you start focused on point observation, you may later expand to photo management, AR display, cloud sharing, or as-built verification. If the app’s design is extensible, you can continue using it without difficulty as site needs evolve. In RTK surveying app comparison, prefer solutions that are not optimized only for current tasks but can follow operational growth.

Common mistakes when comparing RTK surveying apps

We have explained seven checkpoints, but similar mistakes are repeatedly made in real deployments. The most common is relying solely on the word RTK. People assume that if an app is RTK-capable, high-precision surveying will be easy, and they introduce it without thoroughly checking app design or data workflows; as a result, the expected operational improvements may not materialize.

Another frequent mistake is choosing based only on initial use cases. For example, you might introduce an app believing that capturing a few site points is sufficient, only to later need stakeout, photo logging, or drawing comparison, revealing functional shortcomings. Since on-site usage tends to expand after introduction, it is essential to choose with an eye to near-future operations.

Undervaluing the readability of accuracy displays is another pitfall. While attention often falls on receiver performance, if Fix status or error estimates are hard to see in the app, on-site judgment becomes ambiguous. This can lead to recording points with insufficient accuracy and requiring re-survey later.

Also, some neglect the data output destination. Being satisfied that points can be captured on site is insufficient if it’s difficult to convert to in-house formats or to preserve links between photos and attributes, increasing office workload. Compare not only site efficiency but also record organization.

To avoid these failures, do not judge based only on app screenshots or short descriptions. Map your company workflow—observation, verification, recording, sharing, and reuse—as a sequence to reveal the comparison axes that truly matter.

How to choose an RTK surveying app by use case

Rather than asking which RTK surveying app is absolutely superior, choose based on the intended use. For sites focused on site condition surveys, quickly acquiring points and recording them with photos is important. Stability and speed of observation matter more than complex settings.

For sites prioritizing stakeout or stake driving support, clear guidance to the target point is essential. Designs that let operators sense direction and distance intuitively and move while viewing the screen improve efficiency. In such cases, guidance-screen clarity and ease of reconfirmation matter more than the number of observation functions.

If you plan to integrate with as-built verification or construction management, features beyond point data—photos, notes, drawing overlay, and sharing—become important. If you want to use site records directly for reports and reviews, focus not only on positioning functions but on information organization.

When integrity of coordinates is critical, such as boundary confirmation or cadastral work, handling coordinate systems and output accuracy is especially important. Latitude/longitude display alone is not enough; plane coordinates, verification with known points, and flexible data formats are required. In this field, emphasize solid basic coordinate processing over superficial readability.

Thus, in comparing RTK surveying apps, clarifying use cases is the first step. Define which sites, who will use it, how often, what will be recorded, and how the results will be used; then the necessary and unnecessary features become clear.

Summary

When comparing RTK surveying apps, don’t just check whether they support RTK; evaluate them from a practical perspective to avoid regrets on site. The seven checkpoints introduced here were visibility of accuracy display and Fix determination, necessary observation functions, support for coordinate systems and correction information, usability and solo-work suitability, data output and sharing, integration with photos/drawings/AR, and design for sustainable operation.

All of these directly affect usability after introduction. These aspects are easy to miss by relying on spec sheets or product pages, but in practice they affect site efficiency, rework frequency, record quality, and in-house rollout. To truly leverage RTK high precision on site, choose an app that supports the full flow from observation to recording and sharing, not just positioning itself.

If you are starting high-precision positioning with a smartphone, consider introducing it as a system that supports entire on-site workflows rather than as mere position display. If you want to pursue centimeter-level position checks, on-site records, and stakeout centered on a smartphone, options such as LRTK—a smartphone-mounted GNSS high-precision positioning device that combines smartphone operation with high-precision positioning—are worth considering. Having the perspective to compare RTK surveying apps will help you build an operation that fits your sites and maximize satisfaction after introduction.