Comparing Network RTK and GCP Operations: 5 Ways to Choose Without Failing on Site

It is not uncommon for field teams to be unsure whether to use network RTK or GCPs, or how to use them in combination. This topic is especially important for practitioners who want to streamline positioning operations without sacrificing stability of accuracy or the reliability of deliverables.

Network RTK is widely recognized as a method for quickly obtaining high-precision positions on site by using correction information from reference stations. On the other hand, GCPs have long been used as references to correctly tie surveying data, photogrammetry data, point clouds, and drawing coordinates to local coordinates. Both are means to ensure accuracy, but their roles are not identical. Therefore, comparing the newer method and the traditional method as a simple either-or choice can lead to incorrect decisions.

In practice, introducing network RTK can lead some teams to think GCPs are no longer necessary, only to encounter coordinate inconsistencies later that require rework. Conversely, believing that installing many GCPs will guarantee safety can result in excessive time spent on installation and management, causing missed opportunities for labor savings. The important point is not to declare one superior across the board, but to choose appropriately based on site conditions, required deliverables, the operational system, and the need for reproducibility.

This article organizes the differences between network RTK and GCP operations and explains five practical ways to choose so you don’t fail on site. Rather than a mere conceptual comparison, it dives into when to emphasize each approach, why that judgment is necessary, and common on-site failures. The content is organized so that those struggling with how to use network RTK and GCPs can apply it directly to measurement planning and operational rules from tomorrow.

Table of contents

• Correctly understand the differences between network RTK and GCP operations

• Preconditions for field operations to confirm before comparing

• Choice 1: Decide from required accuracy and deliverables

• Choice 2: Decide from site environment and reception conditions

• Choice 3: Decide from workload and frequency of repeated tasks

• Choice 4: Decide from personnel structure and operational load

• Choice 5: Decide from the need for verifiability and accountability

• Think in combinations, not just one or the other

• Summary

Correctly understand the differences between network RTK and GCP operations

When comparing network RTK and GCP operations, the first point to clarify is that they are not interchangeable methods with the same purpose. If this remains ambiguous when making an implementation decision, unexpected offsets and rework are more likely to occur on site.

Network RTK is an operation that receives correction information via communications to obtain high-precision coordinates on site. In other words, it excels at immediately determining exactly where a location is at that moment. It is highly effective in situations where coordinates are handled quickly while moving on site, such as collecting survey points, position checks for as-built verification, staking out temporary structures and structural positions, and verifying known points. Especially on sites that want to accelerate initial work, the ability to enter high-precision positioning without heavy setup or preparation is a major advantage.

GCPs, by contrast, are an operation that uses ground-established reference points to reliably tie the entire dataset into a coordinate system. In photogrammetry and point cloud processing, multiple datasets obtained on site must be correctly joined during post-processing. Having GCPs makes it easier to suppress model rotation, scaling, and translation errors and to improve the consistency of deliverables. In other words, GCPs are often more useful as standards to ensure the reliability of the entire dataset than for instantly obtaining a single point’s position on site.

Put practically, network RTK is a means to increase field work mobility, while GCPs are a means to increase the stability and reproducibility of deliverables. Of course, points acquired by network RTK are sometimes treated as control points, and operations that install a few GCPs and complement them with network RTK are common. The two overlap in practice, but understanding that their central roles differ makes decisions easier.

Failures often occur when teams assume that introducing network RTK makes all coordinate management simple. In locations with poor reception or unstable communications, positioning solutions may not be stable. Even if it appears that good values were obtained temporarily on site, another reference may be needed when considering overall data consistency and downstream use. Conversely, assuming that installing many GCPs ensures everything is safe is also risky. If installation locations are poorly chosen, visibility of markers is inadequate, or management is lax, simply having many points will not directly lead to improved accuracy.

The first step in comparison is to understand that network RTK’s strength is handling positions immediately on site, while GCPs’ strength is stabilizing standards for entire deliverables. With that understanding, you need to determine what your site should prioritize.

Preconditions for field operations to confirm before comparing

Before comparing network RTK and GCPs, there are preconditions you should decide on at the site. If these preconditions are unclear, operations will be inconsistent regardless of which you choose.

First, clarify why you are taking coordinates. Even with the same type of positioning, the required accuracy and management methods differ depending on whether it is simple status confirmation, as-built management, pre-construction staking out, or georeferencing photos and point clouds. For status surveys you can sometimes prioritize immediacy, but if you need to overlay data strictly with drawings or existing datasets later, stricter standard management is necessary. Using the same method regardless of purpose tends to produce middling results in both efficiency and quality.

Next, unify the coordinate systems used on site. If coordinates obtained by network RTK, existing drawing coordinates, past point clouds, and future additional measurements are not managed using the same conventions, individually plausible datasets will not align in the field. Whether you have agreements on coordinate origins and vertical datums, naming rules for local files, and methods for delivering deliverables will greatly affect the amount of rework downstream.

It is also important to consider how to maintain verification points. While network RTK is highly mobile, relying solely on instantaneous on-site results can make post facto anomalies hard to detect. GCPs, too, are not automatically reliable just because they are installed; you must separately confirm whether each point itself is trustworthy and whether surrounding conditions are suitable. In other words, adopting either method without an independent viewpoint for confirmation is risky.

Another often-overlooked issue is how to absorb differences between field personnel. Experienced operators can judge reception conditions and avoid suspicious values, but to ensure consistent quality regardless of who is responsible, standardization of procedures is essential. For network RTK, decide on pre-measurement checks, how to handle unstable communications, and re-survey criteria. For GCP operations, define installation locations, marking methods, appearance in photos, and maintenance procedures.

Comparisons are not decided by instruments or methods alone. It’s important to consider operational design: how the site will use, verify, and archive data. When these preconditions are in place, the five selection methods explained next become much more practical.

Choice 1: Decide from required accuracy and deliverables

The first axis of decision is how much accuracy is required and what the final deliverable will be. If this is ambiguous when comparing network RTK and GCPs, you may spend unnecessary effort or omit necessary management.

For example, when the purpose is to grasp rough positional relationships on site, quickly record construction progress, or promptly confirm locations of existing features, the immediacy of network RTK is a major asset. Because you can move to the point you want to measure and obtain a high-precision position on the spot, it is suitable for tasks where a small team must cover a wide area. Particularly when you want to accumulate georeferenced records on a site that changes daily, the ability to begin measurements without time-consuming preparation is a big advantage.

Conversely, when it is necessary to integrate measurement data collected over multiple days or to produce results whose consistency is readily verifiable by third parties, GCPs play an important role. In photogrammetry and point cloud generation, even if measurements on site were correct, misalignments can be amplified during post-processing when joining datasets. Without reference points, slight distortions can go unnoticed in the overall model. Properly operated GCPs make it easier to improve positional and shape stability of the deliverable as a whole.

Be aware that point accuracy and model/surface accuracy are not the same. Even if network RTK yields high-precision positions point by point, the consistency of the overall model constructed as a surface may not be sufficient. Conversely, even if GCPs stabilize the overall model, the method may not be suitable for quickly staking out positions on site. Whether to prioritize one or the other depends on whether the final deliverable is point-centric or model/surface-centric.

It is also important to consider future reuse. Even if only simple position records are needed now, it is not uncommon to later want to overlay other design or as-built data or compare time-series data. Considering such extensibility, it may be safer to incorporate the concept of verification points or control points from the start.

In short, if you prioritize quick field response and efficient capture of per-point positional information, lean more on network RTK; if you prioritize reproducibility and stability of the entire dataset, lean more on GCP operations. When discussing accuracy, specify not only numerical targets but also which process, which unit, and which deliverable they apply to — that concreteness helps prevent failures.

Choice 2: Decide from site environment and reception conditions

The second axis is the site environment. Network RTK is very convenient, but it performs best where the sky is open, communications are stable, and radio conditions are relatively good. Conversely, its strengths diminish in locations with poor reception conditions.

For example, sites surrounded by tall trees, near slopes or structures, in mountainous areas, in dense urban settings, or temporary sites with many machines and materials may experience unstable satellite signal reception. Unstable communications affect receipt of correction information. As a result, solving and fixing the positioning solution can take longer, measured values may vary in stability, and operators may unknowingly take measurements under unfavorable conditions.

In such environments, GCP-based operations gain value because you can keep a post-processing or data integration standard without being constantly dependent on communications and reception conditions. Especially when acquiring data from multiple directions for imaging or scanning, stabilizing the whole dataset against local reception-poor areas using control points is effective.

However, do not view GCPs as a panacea. Poorly chosen GCP locations can reduce visibility and become error sources. Installing points where they are easily hidden by mud or dust, obscured by reflections or shadows, or frequently trampled along work paths increases management effort without improving quality. In other words, the more severe the site conditions, the more important it is to design how to compensate for reception-poor areas rather than to treat network RTK vs GCP as a simple binary choice.

Also note that site conditions change over the day. A clear view in the morning can become impeded in the afternoon by vehicle or material placement. Temporary fencing or scaffolding can completely change the environment. If you base your operation on network RTK, you must decide how to accommodate such changes operationally. Don’t assume constant conditions; define recheck timing and alternative methods in practice.

From the site-environment perspective, if the sky is open, communications are stable, and you need to cover many points in a short time, network RTK is highly effective. If reception conditions vary and you need to ensure overall stability through post-processing, give greater weight to GCPs. Making this decision without inspecting the site, only from a desk, increases the likelihood of failure.

Choice 3: Decide from workload and frequency of repeated tasks

The third axis is the scope and frequency of repeated tasks. Even on the same site, optimal operations differ depending on whether measurements are one-off or performed daily or weekly.

A major strength of network RTK is fast startup and mobility. On sites where installing many GCPs each time would be time-consuming, network RTK allows you to quickly move between required points and record them. For repetitive tasks such as construction progress checks, temporary position records, daily as-built checks, and monitoring changes in managed items, this efficiency advantage accumulates significantly. Particularly on sites suffering from labor shortages, the ability to operate with a small team at high frequency is critical.

Conversely, when data accumulated from repeated measurements will be integrated and used later, the value of GCPs and known-point management increases because small offsets accumulate into problems as the number of passes grows. Although it may appear that each session was measured locally correctly, if comparison standards drift over months or years, evaluating changes or overlaying past data becomes difficult.

A common failure is doing thorough baseline measurements only on the first run and omitting them thereafter. Even with high initial quality, ambiguous ongoing rules lead to datasets that cannot be compared over time. On the other hand, attempting to manage GCPs at the same density every time imposes an operational burden too heavy to sustain. The key is to design which checks to perform each time and where simplifications are acceptable for repeated operations.

Thus, network RTK shows clear advantages for tasks that require quickly covering wide areas or repetitive short-time multi-point operations. However, if time-series comparison or long-term operation is expected, you must at least maintain reference points or verification methods, or the data will become unusable. Efficiency is not merely reducing effort but reducing effort while maintaining quality that remains usable over time. Therefore, always consider workload and repetition frequency together.

Choice 4: Decide from personnel structure and operational load

The fourth axis is personnel structure. No matter how theoretically superior an operation is, it will fail to continue if it does not match the number of people, skills, and time constraints on site. Which to emphasize between network RTK and GCPs is closely tied to your site’s staffing.

Network RTK pairs well with small teams. You can move nimbly, check coordinates on the spot, and measure only the necessary locations efficiently. This is a big advantage when construction supervisors perform site checks themselves or when a dedicated surveyor is not always present. Being able to perform necessary checks on the spot without stopping work improves overall site flow.

However, because network RTK can look easy to use, vague operational rules can create variability among operators. If one person carefully checks reception before measuring while another simply records numbers at face value, quality will vary even with the same method. Thus, while it suits small teams, standardizing check points is essential.

GCP operations require planning and management, so they work well when roles can be divided on site. If you can distribute tasks for installation, recording, maintenance, and post-processing, data quality can be stabilized. In reality, many sites cannot allocate that many people, and GCP installation and checks become a burden that leads to ritualized, ineffective practices. Problems such as inadequate recording of installed points, failure to notice relocations, or inability to match points across datasets are common when operational load is too high.

The important thing is to balance ideal accuracy management with operations the site can sustain. High-density management is not always necessary. Deciding for each site who makes which decisions, how to re-check in abnormal situations, and in what format data are stored can greatly reduce quality variability.

If your site lacks personnel experienced in positioning and coordinate management, anchoring the operation on network RTK while clarifying verification points may be easier to implement than imposing complex GCP procedures. Conversely, if you have a dedicated structure for ongoing data management, incorporating GCPs to improve deliverable reproducibility becomes an easier choice. Ultimately, operations only make sense if they fit the site. Ignoring personnel when comparing methods is a typical cause of on-site failure.

Choice 5: Decide from the need for verifiability and accountability

The fifth axis is whether you can explain and verify later. This is often overlooked on site but is extremely important. Measurements may end on site, but deliverables and coordinates are sometimes reviewed later by others. When people who did not attend the measurement—such as other internal departments, clients, subcontractors, or future personnel—use the data, you must be able to explain why those values are trustworthy.

Network RTK provides high-precision values on site, but if operational records are vague, it can be hard to explain them later. For example, if there is no record of the time, conditions, or state of the positioning solution when measurements were taken, or how they aligned with verification points, verbal justification is insufficient to support the values’ reliability. Using network RTK effectively requires not only measuring but also keeping the necessary records.

GCP operations have an advantage in this explainability. When reference points exist and the workflow of integrating data based on those points is clear, traceability is easier. Of course, GCPs are meaningless if installation and management are inadequate, but at least having visible standards that underpin the dataset is a major benefit. High verifiability is particularly important for work involving multiple parties or when the deliverable’s validity is likely to be examined later.

The point here is that high accuracy and the ability to explain it are not the same. Even apparently high-accuracy values are hard to guarantee later without proper records. Conversely, even if procedures take extra effort, organized use of control and verification points tends to preserve the data’s value longer.

Therefore, consider not only short-term on-site decisions but also future checks and handovers: whichever method you use, ensure a system that enables verification. Even in network RTK-centric operations, leaving verification points, checking key locations against control, and standardizing record formats improve explainability. In GCP-centric operations, vague records of installation locations and management status also defeat accountability. The key is not to assume results are correct, but to confirm they are correct and present them in a way others can understand.

Think in combinations, not just one or the other

Looking across the five choice axes, it becomes clear that network RTK and GCPs are not competing options but tools with different roles. Operations that are less likely to fail in practice combine them as needed rather than leaning extremely toward one side.

For example, use network RTK for daily position checks, quick as-built checks, and coordinate logging during site巡回, and use GCPs or verification points at key milestones or when data integration is required to ensure overall consistency. This approach is practical: you avoid heavy operations every time while reducing the risk of generating unusable data.

Another effective approach is to emphasize GCPs and known points early to establish coordinate standards, then use network RTK for subsequent fine-grained additional measurements and position checks. This allows daily operations to be streamlined once the standard is set. Conversely, you might first capture the current state quickly with network RTK, then validate important locations against control points later.

In short, choosing does not mean discarding the other option. What really matters on site is clearly defining what will be done with network RTK and where GCPs or verification points will support it. If that delineation exists, you can reduce unnecessary installation and excessive checks while maintaining required quality.

This idea is especially important on sites pursuing construction DX. Chasing efficiency alone destabilizes quality, while focusing only on quality makes operations too heavy to sustain. That is why how you combine network RTK’s mobility and GCP operations’ stability determines site maturity. The conclusion of comparison is not which is superior, but how to use each to minimize failures.

Summary

When comparing network RTK and GCP operations, don’t decide based solely on apparent convenience or traditional habits. Network RTK’s strength is handling high-precision positions on site instantly and suits tasks that require small, mobile teams. GCPs strengthen overall deliverable consistency and reproducibility and are suited to workflows that consider post-processing and long-term use. Each has a clear role, and the appropriate balance depends on site conditions and objectives.

To avoid failure, organize your decision around five perspectives: required accuracy and deliverables, site environment, workload and repetition frequency, personnel structure, and verifiability/accountability. Considering these five points helps you move beyond vague decisions like “network RTK looks convenient so use it” or “we’ve always used many GCPs so keep doing that.”

Going forward, it will be more important to record coordinates in a way that a small team can maintain necessary quality and produce usable records later, rather than merely being able to take coordinates. In that sense, network RTK and GCPs are not opposing concepts but combinable options to move the site forward. Determine whether your site needs immediacy, overall stability, or both, and design your operations accordingly.

If you want to speed up coordinate checks, staking out, and simple surveying on site, options like LRTK—an iPhone-mounted GNSS high-precision positioning device—can also be effective. They leverage network RTK’s mobility while making it easier to verify local coordinates and streamline routine positioning work, leading to operational approaches that are usable in construction management and surveying practice. If you want to appropriately identify where to use GCPs while reducing daily operational load, consider practical operations that incorporate LRTK.