Is GCP Still Necessary with RTK? Six Steps to Stabilize Survey Accuracy

With the wider availability of RTK-compatible equipment and workflows, more field teams are wondering, "Can we minimize GCPs now?" or "Is RTK alone sufficient without GCPs?" Indeed, RTK is an effective way to greatly improve positioning workflow efficiency and reduce the effort of assigning coordinates. However, being RTK-capable does not automatically mean the final deliverables will have stable accuracy. In real-world sites, multiple factors—such as sky visibility, communication conditions, stability of correction data reception, object geometry, imaging plans, and validation methods—interact and cause accuracy fluctuations. Therefore, RTK compatibility does not unconditionally eliminate the need for GCPs.

Many practitioners searching for "GCP placement RTK" want to cut down on GCPs but also want to avoid poor accuracy or rework. The important point is not to treat the choice of using GCPs as a binary decision, but to determine for each site where, how many, and in what roles GCPs should be retained. RTK provides positions, while GCPs serve as standards to verify accuracy and stabilize the overall result. If you operate without understanding this difference, a workflow may seem to work at the site yet reveal shifts or distortions in later stages.

This article organizes why GCPs remain important even in RTK-enabled workflows and explains six practical steps for stabilizing surveying accuracy. By understanding the difference between the traditional method of placing many GCPs and an RTK-based approach that optimizes GCP usage, you can reduce unnecessary installation work while keeping the required accuracy. The content clarifies common field questions like "How far can we reduce GCPs?", "What verification points are needed?", and "How should deliverables be validated?"

Table of Contents

• Why GCPs are still required even with RTK

• Step 1: Assess site conditions and determine the limits of RTK-only workflows

• Step 2: Define GCP roles based on required accuracy

• Step 3: Plan GCP placement to be minimal and effective

• Step 4: Standardize acquisition and positioning operations to avoid increasing errors

• Step 5: Establish check points and always verify deliverable accuracy

• Step 6: Standardize and improve operations to inform future sites

• Summary: Don’t pit RTK against GCPs—stabilize accuracy

Why GCPs are still required even with RTK

RTK enhances positioning accuracy by using correction data and contributes greatly to field efficiency. RTK is particularly effective when you need to survey large areas quickly or assign coordinates to multiple points. Because you can obtain positional information with less effort than before, RTK is suited to reducing GCP installation. However, RTK’s strengths lie in positioning efficiency and immediacy; it does not automatically eliminate global model distortions or local discrepancies. Misunderstanding this can lead to overlooking final deliverable quality.

GCPs are not merely reference points for coordinates. They provide a benchmark for processing results, allow reassessment of overall consistency, and help confirm the reliability of the final deliverable. Even if RTK provides high-precision coordinates for capture or observation positions, the geometry of the target surface and acquisition conditions can still produce vertical shifts, edge distortions, or local stretching. Without GCPs or check points placed on site, it can be difficult to judge whether processing results are truly correct. In other words, RTK is a means to provide positions, while GCPs function as standards that support the results.

Furthermore, RTK performance cannot be judged by theoretical values alone. Under ideal conditions—open sky, stable communications, little reflection or obstruction—you may be able to dramatically reduce GCPs and still achieve high accuracy. However, in sites with dense trees, closely spaced structures, large elevation differences, or unstable observation conditions such as slopes or watersides, RTK figures may appear stable while the actual deliverable still contains distortions. In such environments, rather than eliminating GCPs entirely, placing a few at key locations can help stabilize overall accuracy.

Even more important is the intended use of the deliverable. For progress checks or general situational awareness, some deviations may be acceptable. But for as-built verification, comparisons with design, volume calculations, deformation monitoring, long-term comparisons, or base data for drawing, absolute accuracy and reproducibility are often critical in addition to relative accuracy. For these uses, even with RTK compatibility, it is safer to appropriately set GCPs and verification points so you can confirm that the required accuracy is met.

Field failures often stem less from the binary choice of RTK or GCPs and more from proceeding without a clear justification for why a given method is sufficient. Decisions to reduce GCPs should be constructed not only from experience but also from site conditions, required accuracy, intended use, and verification methods. Whether GCPs are necessary with RTK is not uniform across all sites, but operations that eliminate GCPs without any verification mechanisms pose high practical risks.

Step 1: Assess site conditions and determine the limits of RTK-only workflows

First, confirm whether RTK can truly be used stably at the site. A wrong judgment here will misalign the entire subsequent GCP plan. Don’t be reassured by the term "RTK-compatible" alone; observe actual site conditions and identify which factors are likely to affect positioning accuracy.

The first thing to check is sky visibility. Stable reception of satellite signals underpins RTK operations. Sites surrounded by tall trees, located in valleys, or enclosed by buildings or retaining walls tend to have variable signal reception. Even if part of the site is fine, edges or low areas may become unstable. Therefore, it is important not to view the site as uniform but to anticipate where conditions may deteriorate.

Next, examine the communication environment. If correction data cannot be received stably, RTK cannot perform as expected. Even if signals are briefly received, frequent interruptions during work will undermine the reliability of observations. This is especially true when moving while covering a wide area—conditions can change point to point, so desk-based assumptions before site entry are insufficient. Anticipate where along work routes reception will remain stable and, if necessary, conservatively leave GCPs or check points.

Don’t overlook object geometry and ground-surface conditions. Flat, feature-rich targets may yield good processing consistency. Conversely, homogeneous surfaces, heavily vegetated areas, near-water surfaces, slopes, shoulder zones, and elongated structures tend to produce more unstable models than they appear. Even with RTK-attached coordinates, if processing constraints are weak, the whole model may twist slightly or show vertical bias. In these areas, a few GCPs can have a large impact.

Pay attention to the site’s spatial layout. A compact, near-square site and an elongated site such as a road or river require different accuracy-management strategies. Elongated sites are prone to edge errors and cumulative shifts; while RTK alone might seem adequate locally, issues can arise in end-to-end consistency. For such sites, placing references at ends and intermediate points matters, and a zero-GCP decision should be made cautiously.

The key question is not simply "Can RTK be used?" but "Can RTK alone manage quality control until the end?" Obtaining positioning values and producing stable deliverables are different. During the site-assessment phase, envision which locations are risky, which directions distortions might occur, and at what stages checks will be needed—this makes subsequent steps much easier to plan. Thorough pre-checks are the starting point for operations that reduce GCPs without failing.

Step 2: Define GCP roles based on required accuracy

The next step is to clearly define the accuracy required for the deliverable and determine what role GCPs must play to ensure that accuracy. If this is vague, decisions about whether to place many GCPs or reduce them will be subjective. In practice, start by working backward from the intended use to define the requirements.

For example, for 3D visualizations used for situational awareness or publicity, visual consistency matters more than strict absolute coordinate accuracy. Conversely, when deliverables are used for comparisons with design, as-built evaluation, dimensional checks across sections and profiles, displacement monitoring, or comparisons across years, planimetric and vertical consistency become important. Even if something is labeled "high accuracy," what matters might be horizontal accuracy, vertical accuracy, within-site relative accuracy, or reproducibility across different times—each requires a different approach.

It helps to think of GCP roles in three categories. First, GCPs act as references to consistently align processing results with the coordinate system. Second, they serve as constraints to suppress global model distortions and local offsets. Third, they function as check references to verify final deliverable accuracy. If RTK coverage is strong, the first role can be partly substituted, but the second and third roles remain important depending on site conditions and intended use. Understanding these differences alone clarifies how cautious you must be about adopting a zero-GCP approach.

In practice, not all GCPs need to serve the same purpose. You can place the minimum number of control points required for processing and keep the rest as check points. This approach reduces GCP-installation work while maintaining a verification framework. Rather than omitting all control points because RTK is available, consciously separate points used for constraint from points used for evaluation—this helps balance efficiency and deliverable quality.

When considering required accuracy, also confirm that the achievable accuracy at the site is compatible with reporting or contractual accuracy requirements. Chasing ideal accuracy can lead to excessive GCP placement, while prioritizing labor savings excessively can make deliverables hard to justify. What practitioners must be able to do is explain why a chosen method is sufficient for the final deliverable. That rationale comes from defining the required accuracy and clarifying GCP roles.

For the question of whether GCPs are necessary with RTK, the most practical answer is: "The number and roles of required GCPs depend on the intended use and required accuracy." Not every site needs many GCPs, but very few sites will be safe to declare all roles unnecessary. Therefore, start by defining the required accuracy and be explicit about why any remaining GCPs are being kept—this is essential to stabilize accuracy.

Step 3: Plan GCP placement to be minimal and effective

Once you decide to use GCPs, placement matters more than number. Placing many points indiscriminately is less effective than strategically locating fewer points in positions that suppress overall distortions. On RTK-enabled sites you may be able to reduce GCP counts compared to traditional practice, but that reduction hinges on careful placement planning.

The basics of placement are to consider perimeter areas, edges, locations with elevation changes, and points where the shape changes. Model distortions often appear not only at the center but at peripheral and edge areas, so placing references near corners and at the edges of the area is effective. For elongated sites, intentionally placing points not only at the start and end but also at intermediate locations helps detect cumulative shifts.

If vertical stability is important, simply spreading points horizontally is insufficient. On terrain with elevation differences, placing points at both low and high locations makes vertical bias patterns easier to identify. A visually even horizontal distribution can still miss height-error tendencies if elevation differences are ignored. This viewpoint is especially important where height control is critical.

Do not choose GCP locations solely based on ease of observation. Locations that are convenient for workers are not always effective for model constraint. For example, clustering points near easy access points can weaken outer and edge control. While you should balance placement practicality and effectiveness, recognize when effect should take precedence.

Also consider keeping some points unused for processing and reserved for verification. This allows independent accuracy checks after processing. If you use all points in processing, results may appear consistent internally but provide little evidence of external accuracy. On RTK-enabled sites, how you assign roles to a few points often determines the outcome.

In practice, discussions often center on "how many points to place," but the real question is "why place them there?" If you plan placement based on site shape, intended use, required accuracy, and expected error patterns, you can often limit GCP count while maintaining stable results. Conversely, reducing counts without a clear placement plan undermines RTK benefits and increases rework. Optimizing GCPs is not simply cutting numbers; it means increasing placement effectiveness.

Step 4: Standardize acquisition and positioning operations to avoid increasing errors

No matter how you design RTK and GCPs, accuracy will not be stable if acquisition operations are inconsistent. A common field failure is that even with correct reference concepts, variability in imaging and observation operations increases errors. To stabilize accuracy, you need to improve the reproducibility of data acquisition itself.

First, before work begins, check the positioning status and start acquisition only when the system is stable. Even if the system appears fixed numerically, if reception was unstable until recently or the environment changes suddenly, observations can vary. Although field teams often want to hurry, skipping the initial stability check typically results in unexplained shifts appearing later in processing.

Next, be aware of changing conditions during data collection. When working while moving, sky visibility and communications are not constant. In sites where conditions vary significantly point to point, some sections may degrade in quality. Prevent this by identifying problematic segments beforehand and, if necessary, performing supplementary captures or additional checks. Don’t proceed with a uniform procedure just because the site is RTK-capable; adapt acquisition density and check frequency to field conditions.

Imaging-plan consistency also greatly affects accuracy. Variability in capture altitude, travel direction, overlap, and viewing angle to the target weakens tie points during processing, and RTK-attached position data will not prevent local distortions. For complex 3D structures, slopes, walls, or stepped surfaces, don’t assume overhead captures alone suffice. If you don’t capture data from necessary angles, coordinates may align while shape reproduction remains insufficient.

On the ground-control side, consistency in installation and observation is essential. If markers are hard to identify because of poor visibility, unstable mounting surfaces, or insufficient discernibility, even properly placed GCPs may not be effective. GCPs only matter when they can be reliably identified and treated as stable positions. Meticulous record-keeping and management of installation locations are as important as the sites you choose.

Also consider weather and time-of-day effects. Strong sunlight, moving shadows, wind-induced motion, and changes in surface conditions affect visibility and observation stability. RTK compatibility can breed complacency, but these basic conditions remain important for stabilizing accuracy. Final quality depends not only on advanced features but on how carefully acquisition conditions are controlled.

In short, with RTK you still need operations that don’t disrupt overall data acquisition. Reading site conditions, confirming positioning state, and improving the reproducibility of imaging and observation are the basics for avoiding added errors. The more you reduce GCPs, the more these operational details determine outcomes—don’t forget that.

Step 5: Establish check points and always verify deliverable accuracy

If you want to stabilize surveying accuracy, the most important step is the final verification. Even if you’ve used RTK, placed the minimum necessary GCPs, and performed careful acquisition, you cannot guarantee quality without checking the final deliverable. The difference in practice often comes down to whether this verification is habitual.

The purpose of check points is to evaluate processing results from an external perspective. If you only look at points used in processing, the results may appear favorable, but that only shows internal consistency under processing conditions and not necessarily real independent accuracy. By intentionally leaving out some points from processing and comparing their positions and elevations with the final deliverable, you can conduct a more practical accuracy assessment.

This check should not only consider mean offsets. You must read where errors are large, whether bias is horizontal or vertical, whether differences occur between edges and the center, and whether elevation-related biases appear. Even if the mean is small, large shifts under specific conditions may render the deliverable insufficient for certain uses. Don’t be satisfied with a single number—inspect error distribution and tendencies.

Also, validation results become input for future site decisions. Accumulate knowledge about which conditions allowed reduced GCPs, where additional points proved necessary, and which terrain or targets required vertical verification. Over time, this creates operational standards for your team or company so you won’t have to reconsider the RTK vs. GCP question from scratch each time; you can make reproducible, site-appropriate decisions.

Neglecting the verification step makes problems more likely to surface during downstream processes. If you discover a shift just before submission, you’ll need re-acquisition or re-processing and the site burden increases. By preparing check points from the start, you can detect issues immediately after acquisition or processing and make faster correction decisions. This is not mere caution but a practical method that increases overall efficiency.

In the field there is a tendency to expect that "RTK coverage means accuracy," but accuracy is not guaranteed by expectations—it must be validated. No matter how far you reduce GCPs, eliminating check points weakens your quality-control basis. If you want stable surveying accuracy, review whether you have a validation framework before debating the number of GCPs. Check points are needed not to doubt accuracy but to be able to explain it.

Step 6: Standardize and improve operations to inform future sites

The final step is to incorporate the current results into standard operations for future sites. Because site conditions vary widely, you cannot optimize GCPs with generalities alone. That’s why documenting what worked at your sites and standardizing it is important.

First, record the relationship between site conditions and results. Briefly note sky visibility, communication stability, type of target, terrain conditions, site layout, GCP placement, and validation results. Such notes make it easier to judge similar sites in the future. For example, knowing that a few GCPs sufficed on open flat ground, that intermediate check points were effective on elongated sites, or that vertical verification was important on sites with elevation differences will greatly help future planning.

Next, avoid leaving judgment rules as vague experience. If each field lead has different practices, the number of GCPs and verification methods will vary even for similar projects, reducing reproducibility. Define basic rules for when to proceed mainly with RTK, when to add GCPs, and how to secure check points. This is not excessive bureaucracy but the minimum common language to normalize quality.

If fieldwork and post-processing are handled by different teams, improve information flow between them. Points that seemed adequate on site may reveal weaknesses during processing. Conversely, leaving one check point that the post-processing team needs can make accuracy evaluation much easier. To truly leverage RTK efficiency, don’t separate data acquisition and deliverable evaluation—treat them as a continuous quality-control chain.

When standardizing, don’t make "reducing GCPs" the goal. The objective is to reliably secure the required accuracy while cutting unnecessary work. Chasing zero GCPs and weakening checks defeats the purpose. The ideal state is being able to discern where reductions are acceptable and where points must be retained.

By improving operations this way, site decisions become faster and accountability improves. It’s easier to explain to clients and stakeholders why a given method was chosen and how accuracy was verified. Rather than leaving the RTK vs. GCP debate to intuition, formalizing your company’s standards makes balancing quality and efficiency realistic.

Summary: Don’t pit RTK against GCPs—stabilize accuracy

RTK compatibility has certainly made field positioning workflows more efficient. Revisiting time-consuming control-point tasks and handling coordinates with fewer steps is significant progress. However, RTK capability does not equate to consistently stable deliverable accuracy. The practical point is not to choose RTK or GCPs adversarially, but to understand each role and combine them optimally.

GCPs are not merely a relic of older methods. They serve as processing benchmarks, suppress distortions, and verify final deliverables. Where RTK conditions are sufficient, you can drastically reduce GCPs. Conversely, in places with poor sky visibility or unstable communications, elongated sites, large elevation differences, or where deliverable accuracy is tightly required, retaining even a small number of GCPs or check points is valuable. The appropriate approach depends on site conditions and required accuracy, not a single universal answer.

The six steps presented here form a workflow: first check site conditions, then determine GCP roles from required accuracy, plan placement, align acquisition conditions, verify results with check points, and finally standardize improvements for future sites. Following this flow makes it less likely that reducing GCPs will degrade quality. Conversely, leaving any step vague risks failing to realize RTK benefits and invites later shifts or rework.

Going forward, it will be important not just to adopt high-performance positioning but to embed it in operations that are reproducible by anyone. If you want to balance mobility and verification in the field and make judgment faster and more reliable, choose methods that make coordinate checking easy and streamline the capture-to-verification flow—such as smartphone-mounted high-precision GNSS positioning devices like LRTK. Rather than aiming for zero GCPs, focus on retaining the necessary points while making overall accuracy management more efficient—that is the practical priority for future fieldwork.