What is RTK Float? Explaining the difference from Fix in 3 minutes

When you start using RTK on site, you will increasingly see displays indicating positioning states such as "Float" and "Fix." However, even if you know the terms, many people are unsure what the actual differences are and which state is acceptable for use in surveying or construction management. What is especially important for practitioners is not memorizing the definitions of the terms, but correctly judging how much the current positioning results can be trusted.

RTK provides high-precision positioning, but it does not always maintain the same level of accuracy. Positioning quality varies depending on the reception environment, the number of satellites, the reception status of correction information, nearby obstructions, communication conditions, and so on. To understand those variations, the difference between Float and Fix is a basic concept you should grasp first.

This article uses the meaning of "Float" in RTK as a starting point and, from a practical perspective, clearly organizes the differences from "Fix", the causes of Float, the risks of using it while still Float, and on-site measures to move closer to Fix. It explains in a way that avoids excessive technical jargon and makes actual operations easy to visualize so that those gathering information under the keyword RTK can make confident, unhesitating decisions on site.

Table of Contents

• What is Float in RTK?

• What is an RTK Fix?

• How should one understand the difference between Float and Fix?

• Main causes of RTK becoming Float

• Risks of continuing to work with floats

• Approach to stabilizing from Float to Fix

• What to look for as on-site decision criteria

• Practical points for stabilizing RTK operations

• Summary

What is RTK Float?

An RTK float refers to a state in which RTK positioning is operating but the solution obtained is still intermediate and has not yet reached the highest accuracy. Put simply, the position has been narrowed down considerably, but it is not yet in the final, high-precision fixed state; this understanding is practically useful.

In RTK, signals received from satellites are combined with correction information to achieve far higher accuracy than standalone positioning. In the process, the receiver calculates its current position based on observed signal offsets and phase relationships. If the necessary conditions are not sufficiently met at this stage, the candidate positions can only be narrowed down to a certain extent. This stage is called Float.

Float is not completely unusable. It often yields better results than standalone positioning, and in some situations it can be used as a rough indication of position. However, in practical work where cm-level accuracy (half-inch accuracy) is required, treating Float and Fix the same way is dangerous. What you should know on site is that Float is an intermediate stage toward high-precision positioning, that its accuracy is still unstable, and that the range of error variation can be comparatively large.

Put in the practical person’s terms, "Float" means "it looks pretty good but cannot yet be regarded as certain." Even if coordinates are displayed on the screen and it appears that measurements are normal, whether those values actually meet the required accuracy is another matter. In particular, for as-built verification, staking out, checks near boundaries, and observations where reproducibility is important, making decisions while the solution is still Float can lead to problems later due to shifts.

Also, Float is not a fixed state. Even small changes in the surrounding environment or in communication conditions can cause it to switch from Float to Fix, or conversely from Fix back to Float. Therefore, it is not enough to be reassured simply because positioning has started once; it is important to use it while confirming which state it is in at this very moment.

What is an RTK Fix?

Fix refers to a state in RTK positioning in which the necessary conditions are sufficiently met and the position is resolved with higher accuracy. In general, when you want to take advantage of the cm-level accuracy (half-inch accuracy) expected from RTK, the state you should aim for in the field is Fix.

The reason Fix is important is that the value of RTK lies in high-precision positioning. In surveying, construction, inspection, and as-built management, many of the purposes for adopting RTK are to obtain high positional accuracy that can be used in practice, rather than just a rough indication of position. Therefore, when reviewing positioning results, not only the coordinate values themselves but also whether those coordinates were obtained as Fix or as Float is extremely important.

In the Fix state, the receiver has sufficiently processed satellite signals and correction information and can determine the position solution with greater confidence. In practice, you can think of this as a condition in which positional variation tends to be smaller and repeatability when reobserving tends to be higher. Of course, Fix does not mean it is unconditionally perfect. If the environment is poor, error sources remain, and there are also instabilities immediately after initialization and effects from equipment installation conditions. However, compared with Float, the reliability of the result as a basis for judgment is greatly increased.

At sites, it is common practice to begin full-scale observations and recordings only after seeing a "Fix" indication. This is not because anything other than "Fix" is meaningless, but rather to reduce variability in quality and cut down on rework in later stages. The more the subsequent work at a site relies on high-precision positional information, the more essential it becomes to confirm that a "Fix" has been obtained.

How should we understand the difference between Float and Fix

The difference between Float and Fix is not simply that their display names are different. The most significant differences are the confidence in the position solution and the level of accuracy usable in practical applications.

Float is a state in which the position has not yet been fully resolved. Some corrections are applied, and although it is often an improvement over standalone or coarse positioning, residual error fluctuations tend to remain, and the position may appear to drift slightly over time. In contrast, Fix is a state in which the position is determined more stably, with higher reproducibility, making it easier to use for high-precision tasks required in practical work.

The important point here is not to see Float and Fix merely as two alternative labels, but to understand them as different quality levels. For example, even when using the same equipment at the same location, the situation can change depending on whether the sky above is open, whether there are nearby buildings or trees, and whether correction data is being received stably. As a result, you may have Fix at one moment and Float at another. In other words, the positioning status is also an indicator that reflects environmental conditions.

Another point that is easily overlooked is that the mere fact numbers are displayed can become a source of reassurance. When coordinates or accuracy readouts appear on the screen, people tend to feel that measurements are being taken correctly. However, with RTK, what is visible and what is usable are different. If you later compare coordinates obtained while still in Float, you may find position discrepancies larger than expected. This is why confirming Fix on-site is considered important.

Moreover, although Fix is more accurate, it is not desirable to rely solely on the Fix indication. By considering the positioning status together with observation time, coordinate stability, reception conditions, and the surrounding environment, you can make a more reliable judgment. However, as an entry point, keeping the basic understanding that Float tends to be unconfirmed while Fix tends to be a high-precision confirmed solution will make on-site decisions less likely to fluctuate greatly.

Main causes of RTK becoming Float

There is not a single reason why RTK becomes Float. In many cases, multiple conditions overlap, causing the observation quality required for a Fix to be unmet. To isolate causes in the field, it is easier to avoid overcomplicating the mechanism and organize your thinking around five perspectives: satellites, corrections, communications, installation, and the surrounding environment.

The main factor is satellite reception conditions. In locations where the sky is not sufficiently open, the number of satellites that can be received decreases and reception quality deteriorates. Near buildings, under trees, beside slopes, or in places surrounded by heavy machinery or structures, satellite signals are easily blocked or reflected, making it difficult for the Fix to remain stable. Even if the sky appears to be somewhat visible, it can still be insufficient for the conditions required for positioning.

Next is the reception of correction information. RTK improves accuracy by receiving information from reference stations and correction broadcasts, but if those corrections are interrupted or delayed, they may fail to achieve a Fix and tend to revert to Float. Even when correction data are being received, unstable content, irregular update intervals, or large communication delays can still have an impact. On site, the connection may appear to be established, but the quality is not necessarily sufficient.

The third is the communication environment. In operations that use mobile communications, reception of corrections can become unstable in places with weak signal, heavy congestion, or many obstructions. Near tunnels, in mountainous areas, in the shadow of buildings, or in locations close to underground, communication quality can suddenly deteriorate. When communication is unstable, initialization to Fix can take longer, and it is more likely to revert from Fix to Float.

The fourth factor is the equipment installation conditions. The antenna’s orientation, height, how securely it is fixed, and its positional relationship to people and equipment also affect positioning quality. Conditions such as a tilted pole, unstable support, slight movement during observation, or nearby metallic objects can degrade the stability of the positioning results. Because RTK is highly accurate, even small installation disturbances cannot be ignored.

The fifth is reflections from the surroundings. Satellite signals that should arrive directly can be reflected by walls, vehicles, metal equipment, water surfaces, etc., and when the receiver picks up signals that have traveled different paths than intended, observation quality deteriorates. This can make it harder to obtain a Fix, and even if a Fix is achieved it may not be stable. Extra caution is required in urban areas and locations with dense equipment.

These factors do not necessarily occur in isolation. For example, near buildings satellite conditions can deteriorate, communications can weaken at the same time, and reflected signals can also be present, so Floats may persist due to a combination of issues. Therefore, rather than fixating on a single cause, it is effective to try several countermeasures in sequence, such as changing the location slightly, moving to a position with a clear view of the sky, waiting for a while, or reviewing the installation.

Risks of Proceeding with Floats

Because a position is displayed even when the solution is in Float, crews in a hurry on site may be tempted to carry on as is. However, if the purpose of using RTK is high-precision positioning, proceeding with a Float solution poses clear risks.

The most significant issue is that positional errors can become larger than expected. Since a Float solution has lower certainty than a Fix, even observing the same point within a short period can result in large numerical fluctuations. Even if the difference does not appear large to the eye, for tasks that require high accuracy—such as positioning (stakeout) or as-built verification—that difference can lead to quality problems and rework.

The next issue is repeatability. Coordinates that appeared reasonable at one point can look shifted when re-measured later. When this happens, it becomes difficult to determine which is correct, and the reliability of field records declines. In particular, when multiple people observe at different times or when work requires later re-verification, Float records tend to cause problems.

Also, if you use data acquired as Float as-is in subsequent design checks, construction management, inspection records, and drawing updates, deviations in the upstream process will propagate to downstream processes. A situation in which data that was treated as high-precision is actually unstable is hard to notice and tends to inflate later correction costs. Differences of several cm (a few in) on site can manifest in later processes as inconsistencies that are difficult to explain.

Furthermore, in practical work there are situations where you cannot just dismiss it as "it's having an off day." For tasks such as position verification near boundaries, checking clearances from existing structures, staking out positions in confined spaces, or keeping records intended for inspection submission, you should avoid making judgments while still in a Float state. When using RTK and results are unstable, it is often better to consider that the measurement conditions are not suitable at the moment rather than assume it is simply an equipment problem.

Of course, it’s not that every on-site task requires Fix before anything can be done. For purposes such as determining an approximate position or a rough guide for movement, Float can have value depending on the application. However, it is dangerous to repurpose that data for tasks that inherently assume Fix without first making clear what accuracy assumptions the data will be used under.

Approach to Stabilizing from Float to Fix

When you want to transition from Float to Fix, the important thing is not to keep frantically tweaking settings, but to put in place the conditions required for a Fix one by one. RTK is not a mechanism that produces the same accuracy everywhere like magic; it is a technology that becomes more stable the better the conditions you provide.

The first thing to reassess is the observation location. Simply moving to a place with a wide open sky often improves the situation. Moving a little away from the edge of a building, avoiding directly under trees, or staying clear of vehicles and metal equipment can also improve reception conditions. When a Float persists, it is important to be willing to look for a position with better conditions, even if only a few meters away, rather than clinging to the same spot.

Next, don't rush the observations. RTK may take a short time to stabilize immediately after startup or after movement. If you begin measuring before the reception has settled, you are more likely to capture data that remain in Float. Watch the on-screen status indicators, coordinate jitter, and the settling of the accuracy display, and wait until things stabilize; this will ultimately improve work efficiency.

Checking the stability of correction information is also important. In areas with weak signal, simply moving a short distance can sometimes improve it. Even if the connection appears good but you don’t get a fix, you need to verify whether corrections are being received continuously or are intermittent. On site, you may believe you are receiving them when in fact the updates are unstable.

We should also return to the basics when handling equipment. Keeping the pole straight, avoiding unnecessary movement during observations, not obstructing the area around the antenna, and firmly securing the equipment—these unglamorous details affect the stability of the Fix. The more precise the work, the more careful handling directly translates into quality.

Also, rather than aiming only for the moment when a Fix occurs, it is important to confirm that the Fix is sustained. If it momentarily becomes Fix but quickly returns to Float, the environmental conditions may be fundamentally poor. In practice, after confirming the Fix indication, it is reassuring to wait a little to see whether the coordinates stabilize and to re-observe the same point to check for reproducibility.

What to Check as On-Site Decision Criteria

When using RTK in the field, judging only by whether the display shows Float or Fix can sometimes be insufficient. The status display is an important starting point, but for more reliable operation it is necessary to look at several aspects together.

The first is the continuity of the positioning state. You should check not only whether a Fix has been obtained, but also how stably the Fix is maintained. If the display switches frequently, the conditions at the site may not be good. Situations in which the Fix is maintained stably yield data that are more reliable for practical use.

The second is the stability of the coordinates. It’s natural for the values to fluctuate slightly, but if they clearly appear to move or the position varies with each re-measurement, caution is required. In particular, if repeated observations at the same point do not agree, you should question the quality of the data at that time.

The third is observing the surrounding environment. Rather than relying solely on the numbers on the screen, checking how open the sky is overhead, looking for nearby structures that might cause reflections, and being aware of terrain where communications are likely to drop out—all of these ultimately lead to the quickest decisions. RTK is strongly affected by site conditions, so it's important to make a habit of viewing the display together with the on-site situation.

The fourth is alignment with the work objective. Whether high-precision positioning is required or a rough understanding is sufficient will change what conditions are acceptable. Rather than mechanically demanding Fix for every task, it is reasonable to make a judgment after clearly defining the precision required for the intended use. However, for tasks where precision directly affects deliverables or downstream processes, it is safer to make Fix confirmation the default.

Practical Points for Stabilizing RTK Operations

To operate RTK stably, refining daily procedures is more effective than focusing on complex theory. The first important thing is to check the reception conditions as soon as you arrive on site. Rather than jumping straight into live observations, check the status from a location with an open sky and assess the time to Fix and its stability; doing so will make it easier to carry out the day's work.

Next, adopting the habit of keeping records is effective. If you note where it was hard to get a Fix, which times of day communications were unstable, and in what environments it tended to return to Float, it will be easier to make improvements at the next site. RTK operations tend to be experience-dependent, but if documented they can be reproduced by the whole team.

Also, it is important to standardize the quality-check procedures for each observation point. By standardizing the workflow—Fix confirmation, checking coordinate stability, and re-observation as needed—you can reduce differences between personnel. Even if high-precision instruments are introduced, if operational procedures vary the quality of the results will not be stable.

It is important not to treat RTK as merely a convenient position display function. RTK is a technology that supports high-precision decision-making, and its value is realized only when it is used appropriately with an understanding of the positioning status. Simply having personnel on site who understand the difference between Float and Fix greatly reduces unnecessary rework and misunderstandings.

Recently, options that make high-precision positioning easier to handle in the field have expanded, such as iPhone-mounted GNSS high-precision positioning devices like LRTK. What’s important when incorporating RTK into operations is not simply owning the equipment, but understanding the meanings of Float and Fix and creating workflows that make it easy to ensure high-precision positioning when needed. If you want to make RTK more practical on site, considering such easy-to-operate high-precision positioning devices can help improve work stability and make decision-making easier.

Summary

An RTK Float is a solution that is moving toward high-precision positioning but has not yet reached a final, stable high-precision state. By contrast, a Fix is a state in which the position is determined with higher confidence and is more suitable for the high-precision operations required in practical work. If this difference is not understood, one may be falsely reassured simply because coordinates appear on the screen and proceed with observations or recording while the accuracy remains insufficient.

In practical work, it is important not to view Float or Fix merely as a display difference, but to treat them as important criteria indicating the data quality at that moment. When Float persists, the basic approach is to review, in order, satellite reception, communications, corrections, setup conditions, and the surrounding environment, and to create conditions that make obtaining a Fix easier. Basic actions such as moving to a location with an open sky, waiting until things stabilize, and checking that the coordinates have settled greatly influence the reliability of the results.

To make RTK truly useful on-site, you need not only to know the technical terms but also the ability to read the positioning status and make correct judgments. Understanding the difference between Float and Fix makes it easier to confidently decide on-site why you should not take measurements now and why you can record them now. If you want to use high-precision positioning more practically in daily work, it is important to utilize an iPhone-mounted GNSS high-precision positioning device like LRTK, improving status checks and ease of operation while translating RTK accuracy into on-site results.