How to Do the Static Method in 7 Steps｜Key Points to Avoid Failing Baseline Analysis

Table of Contents

‐ What the static method is ‐ Situations suited to the static method ‐ Step 1 Decide the purpose and required accuracy ‐ Step 2 Select control points and observation points ‐ Step 3 Standardize equipment settings and observation conditions ‐ Step 4 Thoroughly manage antenna setup and antenna height ‐ Step 5 Perform continuous observation for the required duration ‐ Step 6 Organize observation data and perform baseline analysis ‐ Step 7 Ensure consistency with network averaging and result checks ‐ Key points to avoid failures in baseline analysis ‐ Differences between the static method and other GNSS positioning methods ‐ Frequently asked questions about the static method ‐ Summary

What the static method is

The static method is a technique in which multiple GNSS receivers are fixed at known or unknown points and observed continuously for a set period, after which the recorded data are post-processed to determine coordinates. Because it is a premise of this method that the receivers are not moved during observation, it is called the static method—surveying while stationary.

At the core of this method is baseline analysis. A baseline is the vector that connects two observation points, and GNSS observations are used to determine the relative positions between points with high accuracy. Rather than reading latitude and longitude from a single receiver, comparisons among multiple observations help cancel out errors, making it easier to achieve stable accuracy.

The static method is often used for establishing control points, reinforcing control points, cadastral and boundary surveys, and preparing reference points for construction. Because observations are post-processed, the method is better suited to applications that prioritize the reliability of results over immediate on-site answers.

What beginners should first understand is that the static method is not simply a matter of observing for a long time. Observation time is important, but just as important are the choice of control points, ensuring open sky conditions, managing antenna height, achieving simultaneous observations, and designing the baseline network. In practice, it is not an exaggeration to say that preparations made before observations determine the achievable accuracy.

Situations suited to the static method

The static method is suited to situations where accuracy and repeatability are required. For example, when establishing a point that will serve as a reference for future surveys or construction, a single real-time observation may be insufficient. In such cases, the static method—recording observations over a period so that baseline analysis and inspections can be performed later—is highly appropriate.

Another practical advantage is that observation results are easier to explain. You can evaluate results by checking observation duration, satellites used, baseline lengths, fix status, residuals, and closure, making it easier to justify why a given coordinate was adopted. In sites where quality control is emphasized, this traceability is highly valuable.

On the other hand, if you need to move around the site and measure many points on the spot, the static method can be inefficient. Because each observation point requires a period of stationary observation, this method is more effective for tasks that prioritize reliability over speed.

Step 1 Decide the purpose and required accuracy

The first thing to do when using the static method is to clarify why you are measuring. If you go to the site with unclear objectives, observation times, baseline lengths, and point selection tend to be half-baked, making baseline analysis more confusing.

For example, whether you intend to establish a new point from a known point, verify an existing point, or use a point as a construction reference will change the required accuracy and the strictness of necessary checks. Different objectives require different observation durations and decisions about re-observation.

It is important to distinguish whether absolute coordinates are required or whether accurate relative positions are sufficient. If you will tie into known points and publish coordinates in a public system, the reliability of those known points will affect your results. Preparations differ between cases where only the relative positions among unknown points matter and cases where you need to firmly tie into a coordinate system.

Beginners tend to focus on receiver performance and observation time, but in practice the first things to decide are the observation purpose and accuracy requirements. Clarifying these reduces uncertainty on site.

Step 2 Select control points and observation points

Next, select control points and observation points. In the static method, control point selection directly affects result reliability. When using known points, verify the provenance and condition of their coordinates and check whether the monument is stable and whether surrounding sightlines are clear.

When choosing observation points, having a wide-open sky is fundamental. If satellites in the sky are not adequately visible, observation quality will deteriorate. Tree canopies, building eaves, metal roofs, and nearby fences can block or reflect satellite signals and increase multipath risk. Although the static method relies on post-processing, poor field conditions impose limits.

Also pay attention to ground and installation stability. Soft ground for tripods, locations prone to wind-induced sway, or areas with risk of being bumped by passersby or operations can impede continuous observation. Since the receiver must not be moved during observation, even slight shifts can affect later analysis.

In practice, consider not only the pairings of control and new points but also the overall baseline network that will form. Rather than determining coordinates from a single baseline, constraining points with multiple baselines makes it easier to check consistency later. At the point-selection stage, envisioning an analysis-friendly network is important.

Step 3 Standardize equipment settings and observation conditions

Once observation points are set, check receiver and antenna settings. Because simultaneous observations are essential in the static method, you need to standardize observation intervals, logging formats, and observation start and end time management. Small discrepancies in settings on site can lead to significant rework later.

A particular item to confirm is that recording has actually started. It is not uncommon to assume that power-on equals logging when in fact no log was saved. Always check that logging has started before observations and confirm proper shutdown and file saving afterward.

Checking satellite reception conditions is also essential. Satellite geometry may be unstable immediately after starting observations, and reception conditions may differ by observation point. Even if sky openness looks similar, one direction may be obstructed. Checking sky visibility before observations can reduce unnecessary re-observations.

If using multiple receivers, organize in advance how to handle different models, antenna types, and settings. Antenna information and observation-condition consistency are important in post-processing, so sloppy field notes cause trouble during analysis. Because the static method assumes post-processing, it is critical to record comprehensive information on site.

Step 4 Thoroughly manage antenna setup and antenna height

A common oversight by beginners in the static method is how antenna height is handled. Even the best baseline analysis software cannot compensate for incorrect antenna height recorded in the field—the results will be offset. This kind of error is hard to spot by inspection alone and is therefore particularly troublesome.

First, carefully perform centering and leveling. Confirm that the antenna center is directly over the survey point, that the pole or tripod is stable, and that there is no tilt. If the antenna is not directly above the point, horizontal position errors will arise; if antenna-height measurement is improper, elevations will be affected.

Next, standardize how antenna height is measured. Confusion between vertical height and slant height can lead to incorrect values being entered in post-processing. In field records, it is safer to document not only the numeric value but also the method used and exactly from where to where the measurement was taken. Writing the measurement method in the observation log greatly reduces the chance of mistakes during analysis.

Also take measures to prevent tripods or poles from moving during the observation, paying attention to site safety. On windy days or in locations near people or vehicles, ensure post-installation stability. In the static method, even if the setup was correct at the start, a slight shift by the end makes observations meaningless. Although setup is momentary, its impact on results is large.

Step 5 Perform continuous observation for the required duration

After set-up, observe continuously for the required period. In the static method, setting observation duration is important. However, do not think that longer is always better; consider baseline length, required accuracy, satellite geometry, and observation environment.

On short baselines in good conditions, stable analysis may be possible with relatively short observation times. Conversely, for long baselines, obstructed surroundings, or stringent accuracy requirements, longer observations are needed. Beginners often try to finish quickly and lose margin for analysis, so when in doubt it is safer to allow some extra observation time.

Do not stop observations inadvertently. Data gaps caused by battery depletion, logging stoppage, or equipment malfunction degrade baseline analysis quality and may necessitate re-observation. Check power and storage capacity before starting and monitor equipment state during observations as needed.

Also be mindful of overlapping simultaneous observation time. For baseline analysis, it is necessary that the control side and observation side have data for the same time period. If one side ends early or starts late, the analyzable overlap is reduced. On site, pay attention not only to the scheduled end time but to how much effective simultaneous time was actually secured.

Step 6 Organize observation data and perform baseline analysis

After observations, organize the recorded data and proceed to baseline analysis. It is important not merely to import files but first to verify which file corresponds to which point, observation times, antenna heights, and known-point information. If field records and data filenames do not match, confusion often arises at this stage.

In baseline analysis, calculate relative positions between observation points and check which baselines resolve stably. Analysis screens typically display fix status, residuals, baseline length, satellites used, and observation time; use these collectively to decide acceptance. Do not adopt coordinates merely because values are produced—evaluate how trustworthy they are.

A common misconception among beginners is to assume that a fixed solution is necessarily correct. In practice, even fixed solutions can fail to meet expected quality if observation conditions or input values are poor. Conversely, if conditions are harsh and some baselines are unstable, you may still make informed decisions by checking consistency with other baselines.

Therefore, do not treat baseline analysis as final based on each individual baseline; proceed on the premise of checking network consistency. Identify which baselines are stable and which are suspicious, and compare with field conditions to infer causes. While software automates analysis, humans must make acceptance decisions.

Step 7 Ensure consistency with network averaging and result checks

Baseline analysis completion is not the end. Before adopting coordinates as final results, check overall consistency through network averaging and closure checks. This final verification is very important in the static method.

For example, when observing a network that includes multiple known and new points, individual baselines may look fine while small inconsistencies appear when viewing the whole network. Such discrepancies often only become apparent when calculated as a network. Avoid basing decisions on a single baseline to improve result reliability.

When tying to known points, also verify consistency among those known points. If there is an issue on the known-point side, no amount of careful new-point observation will yield stable results. Consider re-observation or adding alternative constraints as necessary.

When checking results, compare not only numeric values but also the observation log and site conditions. Information such as strong winds, nearby machinery operation, re-measurement of antenna height, or delayed observation start times helps interpret analysis results. In the static method, it is important to view field observations and analysis together as a single process.

Key points to avoid failures in baseline analysis

Baseline analysis determines the success of the static method. Here are failure-prevention points that beginners should particularly keep in mind.

The first point is ensuring sufficient simultaneous observation time. Even if you can import files into analysis software, baseline analysis will not be stable unless control and observation data overlap sufficiently. Always check observation start and end times and confirm there is enough valid overlap. On site, you may think you observed long enough when in fact overlap was too short.

The next point is to suspect antenna-height input errors. When baseline analysis yields irreconcilable results, before blaming satellite conditions or equipment faults, recheck the antenna-height records and how they were entered. Confusing vertical and slant heights, unit mistakes, and measuring from different reference points are typical causes of error.

Also do not overlook the effects of multipath and obstructions. If analysis results vary, recall the sky visibility at the site. Nearby walls or metal surfaces or one-sided tree cover will affect observation quality. Consider field conditions as potential causes as well as software numbers.

Do not be reassured by a single baseline result. In the static method, checking the consistency of multiple baselines and residuals after network averaging yields more reliable judgments. A single seemingly good baseline may appear inconsistent when combined with others; conversely, some baselines with slight issues may be acceptable if the overall network is stable.

Another important point is confirming repeatability. For critical points, re-observing at different times or adding constraints via other baselines increases confidence in results. While this requires more time and effort, it makes it easier to justify results later. Think of the static method not merely as a way to produce coordinates but as a way to build reliable results.

Differences between the static method and other GNSS positioning methods

Understanding the static method is aided by knowing how it differs from other GNSS positioning techniques. The major difference is whether results are obtained on site in real time or derived later by post-processing.

Real-time positioning allows immediate on-site coordinate confirmation, which is efficient. It is advantageous when measuring many points sequentially. However, it can be affected by communication conditions and instantaneous reception, and result verification must be handled differently.

By contrast, the static method emphasizes post-processing for accuracy verification and repeatability rather than on-site immediacy. Because observation data are recorded, you can redo baseline analysis or check network consistency later. This is why the method is suited to control point setup and situations requiring high reliability.

Compared with kinematic or short-observation methods, the static method devotes more time at a single point, so preparation and management directly affect results. Choose between efficiency and verifiability depending on the task.

Frequently asked questions about the static method

A common question for newcomers is how long to observe. This depends on baseline length, required accuracy, reception environment, and satellite geometry, so it is dangerous to fix a single duration. Even on short baselines in good environments, it is safer to allow extra time for important points. Conversely, lengthening observation time in a poor environment does not always yield the expected improvement.

Another frequent question is which result to adopt when baseline analysis produces multiple solutions. In this case, do not choose simply the most aesthetically pleasing number; make decisions based on observation conditions, fix status, residuals, and consistency with other baselines. Results must be considered within the overall observation network.

Is one known point sufficient? Theoretically, you can derive a new point from a single known point, but in practice multiple constraints make verification easier and improve result reliability. When establishing an important control point, provide means for later verification.

Beginners often think the static method is difficult, but once you understand the workflow, the procedure becomes quite orderly. The difficulty stems from linking observations, recording, analysis, and result verification. Knowing what to check and when greatly reduces the chance of failure.

Summary

The static method is an effective GNSS surveying technique when you need to reliably determine control points. The workflow is to decide purpose and accuracy, select control and observation points, standardize equipment settings, correctly set the antenna, perform continuous observations for the necessary duration, and after observation perform baseline analysis and network averaging to check consistency. Although the steps may seem complex, careful preparation and meticulous record-keeping determine result quality.

To avoid failure in baseline analysis especially, ensure simultaneous observation time, manage antenna height, confirm sky visibility, and check consistency across multiple baselines. The static method does not provide immediate on-site answers but makes post-checks easier and yields more reliable results. It remains a foundational approach for control-point surveying and other important reference-point work.

Finally, many practitioners who understand high-precision positioning concepts also want an easier way to apply high-precision positioning in daily fieldwork. The static method is valuable where careful post-processing is required, such as in control-point maintenance, but for on-site positioning, checks, as-built management, and record-keeping, combining smartphone-based high-precision positioning can be effective. LRTK, an iPhone-mounted GNSS high-precision positioning device, leverages smartphone usability to make high-precision positioning more accessible, allowing the precision awareness cultivated through the static method to be applied in field operations. If you want to bring high-precision positioning closer to everyday practice, consider such options as well.