What is static surveying? A 5-minute explanation of the differences from RTK and when to use each

Even if you know the term static surveying, many field personnel find RTK more familiar and are unsure which to choose in practice. Especially when installing control points, establishing the basis for as-built verification, fixing coordinates before construction, or observing in areas with unstable communications, not only speed but also the reliability of results and ease of later verification are important. This article organizes, from a practical perspective, the basics of static surveying, its differences from RTK, how to use each in the field, and common points where judgments go wrong. By the time you finish reading, you should be better able to decide not which method is superior, but which method to apply to which task.

Table of Contents

• What static surveying is

• What RTK is

• Differences between static surveying and RTK

• Situations suited to static surveying

• Situations suited to RTK

• Decision criteria when unsure which to use

• Common failure points in static surveying

• Summary

What static surveying is

Static surveying is a method in which receivers are fixed at multiple observation points to receive satellite signals simultaneously, and the positional relationships between observation points are determined later by post-processing those observation data. In other words, it's not a surveying method that produces an immediate answer on site, but a concept of carefully collecting data for a certain period and analyzing it afterward to determine coordinates. Since the instruments remain in place during observation, it’s easy to understand it as a static observation method, as the name implies.

In practice, static surveying is often chosen when you want to establish control points by linking known points and new points, when you want to refine results while checking analysis conditions later, or when you want to proceed without relying on a communications environment. The measured values are not fixed at the moment of observation, but because you can secure observation time and analyze the relationships among multiple points, it is well suited to the work of creating control frameworks. This concept is also easy to understand from the fact that public surveying standards organize the static method in the context of control point surveying and present operations involving observation diagrams, session planning, repeat observations, and inspections.

Public surveying standards require a reasonably long observation time for the static method depending on conditions. As a typical guideline, observations of 60 minutes or more are standard for baselines under 10 km, and 120 minutes or more for baselines of 10 km or more; this approach differs from the idea of quickly picking up one point at a time in a short period. In other words, static surveying is easier to view as a method for building the reliability of control points by spending a set amount of time, rather than a method to quickly increase the number of points.

Static surveying is not simply a matter of observing for a long time. What points to observe simultaneously, which known points to fix, the order in which to build the network, and how to include repeat observations and loop-closure checks all affect how easy the results are to handle. It’s important to understand that quality is largely determined during the work planning stage, not just by placing equipment in the field and waiting.

What RTK is

RTK is a method in which a base station and a rover receive satellite signals simultaneously, and the base station’s information is sent to the rover so that positions can be determined immediately on site. Because the surveyor can check coordinates in the field and then move to the next point, the main feature is that per-point observation results can be used immediately on site. The Geospatial Information Authority of Japan also describes RTK as a method that uses base station data to determine positions in real time and can be expected to achieve centimeter-level accuracy.

In current practice, networked operations that distribute correction information using multiple reference stations or continuously-operating reference stations are widely used, not just simple corrections from a nearby base station. This approach reduces the long-baseline issues that traditional RTK struggled with and aims to achieve accuracy comparable to short-baseline RTK. From the field operator’s perspective, it is easy to think of RTK as a surveying method that obtains a reference and produces an immediate answer while continuing to move.

However, while obtaining a real-time solution is a strength of RTK, that immediacy also brings caveats. When satellite signal masking, communication interruptions, reacquisition of correction information, or reinitialization occur, the observation flow can stop or additional work may be required to confirm solution quality. Fast does not mean万能; it is important to understand that RTK is a very powerful method when environmental conditions are favorable.

Furthermore, because RTK provides usable results on site, surveying operations often tie directly to construction or inspection decisions. It is easy to determine on site how far the current location deviates from the design position, where to move next, or whether the planned area has been completed, so RTK is also useful for information sharing with construction personnel. The immediacy of RTK makes it a common choice when you want to speed up field operations.

Differences between static surveying and RTK

The biggest difference between static surveying and RTK is when the results are finalized. Static surveying determines coordinates by post-processing after observing on site for a certain period. RTK obtains a solution on the spot using a base station or correction information. In other words, static surveying is post-processing based, while RTK is real-time based. This difference greatly affects work speed, required preparation, suitable applications, and how risks manifest in the field.

The next difference is the purpose of the work. Static surveying is well suited to establishing control points and creating a foundation for observations that require high reproducibility. This is because multiple points are observed simultaneously and it is easy to check accuracy as a network including sessions, loop closures, and repeat observations. On the other hand, RTK is well suited to staking out positions, acquiring as-built points, verifying construction accuracy, and construction support that involves guidance—tasks where you want to observe many points in the field and use them immediately. While the latter is not explicitly enumerated in public documents, this practical categorization follows from RTK being a method of obtaining positions in real time while moving.

A third difference is how time is considered. RTK allows quick per-point decisions and thus may capture many points within the same working time. Static surveying, however, invests observation time not for a single point but to stably determine the relationships among multiple control points. It is important not to compare required time simply. For example, if you collect many points quickly with RTK while the control is ambiguous, you may need to rework the entire dataset later. Conversely, establishing control with static surveying first and then expanding with RTK often improves overall productivity.

A fourth difference is how resilience to field conditions appears. Static surveying is also affected by sky visibility and satellite geometry, but by observing for a set period you can secure more usable data for analysis. RTK assumes an immediate solution, so obstructions or communication outages more directly disrupt observations, potentially requiring reinitialization or re-observation. Therefore, even within GNSS surveying, it is practical to understand that the operational philosophies differ between a method that prioritizes speed and a method that prioritizes accumulated reliability of results.

Additionally, the handling after observation differs. Static surveying makes it easy to organize analysis results, baseline vectors, inspection results, and the rationale for adoption, so the reasons for adopting coordinates are easier to trace later. RTK, while convenient to use as part of on-site decision-making, requires careful attention to how the validity of the on-the-spot adopted values was verified. In other words, static surveying pairs well with record-keeping and verification, whereas RTK pairs well with operational speed.

Situations suited to static surveying

Static surveying is first suited to work that creates the overall control for a site. Points that serve as the starting points for construction, points used later for as-built or design comparisons, and control points that span multiple days—if the initial placement of coordinates wavers, it affects all subsequent surveying results. In such situations, being able to secure observation time and check accuracy by post-processing makes static surveying a safer choice.

It is also suited to places with unstable communications. In mountainous areas, near slopes, around structures, or on sites with many temporary setups, the communications or correction acquisition required for RTK may be unstable. Of course static surveying also relies on sky visibility, but because it does not assume continually receiving corrections to maintain a real-time solution, it offers more flexibility in operational planning. Rather than using static surveying only as an alternative when RTK cannot be used due to poor radio conditions, considering it from the start as a means to secure control simplifies site planning.

Moreover, static surveying is effective for tasks that require later accountability. Examples include connecting to public coordinates, checking consistency with known points, inspections using multiple sessions, and verifying baseline analysis results—static surveying easily preserves the process leading to the result. On site, it can be more important to be able to explain why a coordinate was adopted than merely whether it was measured. Static surveying readily provides material for such explanations.

Another overlooked advantage is when the surveying control is intended to be used for a long period. If the work finishes in one day, the day’s efficiency may take priority. However, on projects spanning multiple stages—land development, structure construction, as-built management, and maintenance documentation—the quality of the initial control affects later processes’ efficiency. Static surveying should be seen as an up-front investment to reduce rework in later stages, rather than a method to boost point counts in the short term.

Situations suited to RTK

RTK shines when you want to make quick, on-the-spot decisions in the field. For example, staking out positions, checking existing conditions, spot-checking as-built measurements, and daily construction management all benefit from seeing results immediately and moving on, rather than waiting for post-processing. For tasks that handle many points while moving, RTK’s immediacy can greatly improve the work rhythm.

RTK is also convenient when a single surveyor covers a wide area. You can check the solution status on the device screen in the field, re-observe as needed, and then move to the next point, making it easier to work with a small crew than setting up multiple units and waiting like in static surveying. While it is not a method for rapidly increasing point density like a point cloud, RTK is excellent for efficiently acquiring required points.

RTK is also useful when you want to immediately check against design values in the field. Being able to confirm the current position and its relation to design or known points on site improves communication among workers. The ability to share results immediately with construction and inspection personnel is a major practical value of RTK.

However, when choosing RTK, distinguish between being fast and being stable. If the sky is open, communications are stable, and corrections are reliably received, RTK is extremely powerful. Conversely, in locations with poor satellite visibility or where reinitialization is likely during movement, the amount of confirmation work can increase beyond the apparent speed advantage. RTK is the fastest when conditions are met, but its performance degrades in ways that directly affect the field tempo when conditions fail.

Decision criteria when unsure which to use

When you’re unsure in practice, first consider whether the point in question is a control point or an operational point. Control points serve as the foundation for many subsequent tasks. Operational points are those you want to check for the day’s work or construction decisions. If it’s a foundation point, use static surveying; if it’s a point for daily decisions, use RTK. Using this as a basic rule reduces selection errors.

Next, consider when you need the results. If you need immediate decisions on site, RTK is appropriate. If post-processing is acceptable and you want to carefully preserve the rationale for adoption, choose static surveying. This perspective is simple but very effective—many field confusions arise when static surveying is used for work that requires immediacy, or when RTK alone is used for work that requires verifiability.

Third, consider field conditions. Check whether sky visibility is sufficient, whether communications are stable, whether you can observe at the same location for a set time, and whether multiple units can be deployed. For example, if sky visibility is relatively good but communications are unstable, it is realistic to establish control via static surveying and then deploy RTK on another day using that control. Conversely, if you are working on an open development site and need daily staking, an RTK-centered operation fits.

Fourth, consider the cost of rework. If the cost of incorrectly recorded coordinates is high, the value of stabilizing control with static surveying increases. If the work can be fixed with modest re-observation, you can prioritize RTK’s mobility. Field teams often compare only observation time, but the real comparison should be the losses incurred if coordinates are misrecorded. With that perspective, you are less likely to rush unnecessarily and more likely to spend time where it is needed.

Common failure points in static surveying

A common misunderstanding with static surveying is believing that simply observing longer automatically ensures reliability. In reality, quality is determined not only by observation time but also by sky visibility, satellite geometry, measurement of antenna height, how known points are tied in, session planning, and inspection via loop closures and repeat observations. What may look like placing a receiver and waiting is actually a method where preplanning and consistency in post-processing determine the results.

Particularly easy to overlook are management of antenna height and observation conditions. Public manuals indicate that antenna heights are treated at the millimeter level (in), and recommend minimum elevation angles, numbers of satellites used, and avoiding skewed satellite geometry. In other words, although static surveying appears calm, if basic condition management is lax, long observation times may still fail to deliver the expected quality. Observing for a long time quietly is less important than whether you are observing under correct conditions.

Conversely, a common misunderstanding about RTK is thinking that displaying coordinates on the device is sufficient. In RTK, when signal cuts or communication failures occur and reinitialization is required, the initialization stage can be significantly affected by noise and multipath. In the field, it is important not to equate the mere display of numbers with being able to safely adopt those numbers. For critical points, simply confirming at different times of day or checking against known points can significantly improve confidence.

Another important point is not to view static surveying and RTK as adversaries. Trying to cover all stages with only one method will cause problems. Dividing roles—static surveying for control creation and RTK for daily deployment and checks—stabilizes the overall work. In practice, the difference in results comes more from the ability to design which method to assign to which process than from the inherent superiority of one method over the other.

Summary

Static surveying is a static GNSS surveying method in which multiple observation points receive satellite signals simultaneously and positional relationships are determined by post-processing. RTK, in contrast, determines positions immediately on site using base stations or correction information. Therefore, if you emphasize establishing control points and later verification, choose static surveying; if you emphasize speed for staking-out and as-built acquisition, choose RTK.

What really matters on site is not arguing which is better. Separate the process of reliably creating control from the process of quickly surveying the site, and combine both as needed. Understanding the concepts of static surveying makes it easier to interpret RTK results, and understanding RTK’s strengths helps you identify when to use static surveying.

If you handle high-precision positioning regularly on site, it’s also important to choose equipment that is easy to operate based on these differences in surveying methods. Using LRTK, an iPhone-mounted GNSS high-precision positioning device, can make high-precision position checks on site more accessible. By understanding the control concepts to secure with static surveying and the mobility RTK can provide, you should be able to organize the flow from surveying to construction and as-built verification without strain.