What's the difference between Fix and Float solutions? Explaining accuracy, causes, and how to tell in 6 points

In practical work using RTK positioning, whether the status displayed on the screen is Fix or Float changes the decision of whether to adopt the coordinate as is, wait and observe, or review the observation conditions. However, on site people often remain at the level of understanding "Fix seems to be more accurate" and operate without clear knowledge of why Float appears, how much it can be trusted, how to distinguish it, or how to respond.

Especially in situations where decisions on the order of several centimeters directly affect work quality—such as as-built verification, setting out, simple surveying, positioning of photo records, and equipment placement checks—it is important to understand the difference between Fix and Float solutions as a practical judgment rather than an intuitive feeling. Whether a solution is Fix or Float is not merely a display difference: it is the result of a combination of how satellite signals are received, the state of correction information, observation duration, surrounding obstructions, communication status, and more. Therefore, rather than reacting only to the on-screen status, it is necessary to operate while considering why that status has occurred.

This article first organizes the basics of Fix and Float solutions, then explains clearly in six items the differences in accuracy, causes of occurrence, stability, how to distinguish them on site, decision criteria, and improvement measures. It is useful not only for those who are just starting to use RTK positioning but also for practitioners already using it on site who want to review the meaning of the status display.

Table of contents

• Grasp the basics of Fix and Float solutions first

• Difference 1: difference in accuracy and repeatability

• Difference 2: difference in stability until the solution is fixed

• Difference 3: difference in causes that make Float solutions likely

• Difference 4: difference in how to tell on site

• Difference 5: difference in decision criteria for adoption in work

• Difference 6: difference in operations to maintain Fix solutions

• Practical points to review when Float persists

• Understanding the difference between Fix and Float solutions speeds up on-site decisions

Grasp the basics of Fix and Float solutions first

To understand the difference between Fix and Float solutions, you first need to grasp how RTK positioning achieves high accuracy. In RTK positioning, signals from satellites are received and high-accuracy positions are obtained using correction information from a base station or equivalent while compensating errors. At this time, the system does not merely count the number of satellites; it calculates positions using very precise information called carrier phase.

What becomes important here is the idea of how far the integer ambiguity has been resolved. High-precision positioning using carrier phase requires knowing how many whole wave cycles have been received, and if the integer part cannot be fully resolved, the position solution remains ambiguous. This ambiguous state is a Float solution, and the state in which the integer values have been resolved and the solution is consolidated with high confidence is a Fix solution.

In other words, Fix is not simply a “good state” and Float a “bad state.” More precisely, a Fix solution means the integer ambiguities have been resolved, making centimeter-level stable positioning more likely. A Float solution means corrections are applied but the integers are not yet sufficiently fixed; the position has improved but has not fully converged.

This difference may be shown on site by a single character or a single status indicator. In reality, however, the confidence level of the positioning computation differs significantly. Therefore, even when observing the same spot, the reliability of the coordinates and the operational decisions should differ between Fix and Float states.

Another commonly misunderstood point is that Float solutions are not necessarily completely unusable. Depending on the application, they can sometimes be used as a reference value. However, for surveying, setting out, construction management, and comparisons with drawings—where repeatability and absolute accuracy affect work quality—operations should be based on Fix solutions. Conversely, for rough position awareness or temporary displays while moving, Float solutions can sometimes be used temporarily. The important thing is to understand the meaning of the status and use it appropriately for the intended purpose.

Difference 1: difference in accuracy and repeatability

The biggest difference between Fix and Float solutions is accuracy and repeatability. Practitioners first want to know "how much difference is there after all," and that difference appears not only as a numerical gap but also in whether repeated measurements of the same point yield consistent results.

With Fix solutions, given appropriate observation conditions, high repeatability on the order of a few centimeters in horizontal position can be expected. Of course, this varies with the site environment, equipment configuration, correction conditions, and satellite geometry, but at least Fix solutions tend to provide coordinates stable enough for operational decision-making. A notable characteristic is that repeated measurements at the same point are less likely to produce large jumps.

Float solutions, on the other hand, tend to show larger coordinate scatter compared to Fix. Even if the displayed estimated precision looks reasonable, the values can fluctuate over time due to attitude changes or the surrounding reflective environment, reducing the agreement when the same point is repeatedly observed. A common on-site issue is discovering later that positions measured in Float mode have slightly shifted or do not match when re-measured at a different time.

It is important not to judge accuracy only by a single displayed value. Float solutions can sometimes appear to give a good value by chance. However, when evaluating repeatability as well, the difference from Fix can be substantial. In practice, what is needed is not just a single occurrence of a close value but the ability to obtain the same quality repeatedly when required. In this sense, Fix solutions are more likely to be acceptable for operational use, while Float solutions should often be limited to reference displays.

Accuracy differences also affect vertical measurements as well as horizontal. In RTK positioning, vertical errors generally tend to be larger than horizontal errors, and this tendency can be more pronounced in Float solutions. When checking ground or installed heights or relationships of structure elevations, the confidence in judgments changes significantly depending on whether the solution is Fix or Float, so especially careful operation is needed.

The most dangerous thing on site is to think "the position seems to match somehow." The difference between Fix and Float may not always be visually obvious. However, when comparing with drawings, ensuring consistency among multiple points, or considering downstream use, the difference accumulates. The difference in accuracy is not just a difference in error width but a difference in whether the data can be left as work data.

Difference 2: difference in stability until the solution is fixed

The difference between Fix and Float solutions appears not only in final accuracy but also in the process and stability until the solution is fixed. On site, sometimes positioning becomes Fix immediately after startup, and sometimes Float continues for a while. If this difference is not understood, you may hastily adopt data on site or, conversely, unnecessarily move location when waiting would have produced a Fix.

A Fix solution is achieved when the necessary satellite information, correction information, and observation conditions are met and sufficient information is obtained to resolve the integer ambiguities. Therefore, some observation stabilization time may be required before Fix is obtained. Especially right after startup, immediately after moving, or immediately after entering an area with many obstructions, it is common to see Float initially followed by transition to Fix.

Float solutions often appear as this intermediate convergence state. That means Float does not always indicate a malfunction or anomaly. Rather, it can naturally appear as an intermediate stage when corrections are received and satellites are being tracked but high confidence has not yet been reached. However, the meaning changes depending on whether the Float transitions to Fix quickly or remains stalled for a long time.

If Float appears only briefly and then stabilizes to Fix, it can often be treated as a normal transition after observation start. On the other hand, if Float persists for a long time at the same place or the system frequently switches between Fix and Float, you should suspect problems with the surrounding environment, communications, or reception conditions. Thus, the difference between Fix and Float is not just a single momentary display difference like a still image; it is important to judge by observing how the status changes over time.

Stability is also affected by the instrument's attitude, how it is held, and how the receiver is installed during positioning. If the reception environment is unstable, a Fix that was once achieved can revert to Float. In practice, it is not enough to be reassured by a single Fix indication; you must confirm that it remains stable for some time. For critical observations, rather than immediately adopting data right after Fix appears, judging while watching the stability of the display, the trend in estimated precision, and the settling of coordinates during continuous observation helps ensure quality.

Difference 3: difference in causes that make Float solutions likely

Fix and Float solutions differ in result, but the background causes also differ. Understanding causes that make Float solutions likely clarifies what to review instead of merely worrying that "it won't Fix."

The most representative cause is the satellite signal reception environment. In places where the sky is not sufficiently open, the number of satellites may be insufficient or the visible satellite geometry may be biased. Near buildings, under trees, along slopes, or around heavy machinery or structures, even if the sky seems visible, some directions may be heavily blocked. In such conditions, the amount of usable information for computation is insufficient, making it more likely to remain in a Float solution.

The next major cause is multipath from reflections. When satellite signals reflect off walls, metal surfaces, water, vehicles, or structures, the received signals are distorted. This is the so-called multipath problem, and even when many satellites appear to be received, poor-quality observations can be mixed in. Reflection environments often underlie phenomena such as unstable Fix or Fix briefly followed by a return to Float.

The reception state of correction information is also important. RTK positioning demonstrates its performance by receiving corrections that provide higher accuracy than standalone positioning. Therefore, if correction data reception is interrupted or delayed, conditions necessary to resolve integer ambiguities are disrupted and the system may remain in Float. In places with weak communication, during times of network congestion, or when the device’s communication settings are unstable, Fix becomes harder even if the satellites are visible.

Observing immediately after startup or right after movement is also a condition where Float tends to appear. When the receiver has just moved to a new location, sufficient observation history may not yet be accumulated and the computation may not have settled. If you try to measure immediately after walking or driving, you may adopt the pre-Fix Float state. This is a common on-site mistake.

Satellite geometry should not be overlooked. Even with many satellites, if their spatial arrangement is biased, solution stability decreases. Feeling that Fix is easier at certain times of day is often due to satellite geometry. In practice you don't need to always consider celestial conditions in detail, but it is quite possible that the ease of Fixing varies by time even at the same place.

Thus, there is not a single cause for Float solutions. Satellite environment, reflection environment, correction communication, observation timing, receiver attitude, and surrounding structures combine to produce Float. Understanding the difference between Fix and Float means not only memorizing status names but also grasping the layers of underlying causes.

Difference 4: difference in how to tell on site

You can to some extent judge the difference between Fix and Float by looking at the status shown on the screen, but in practice that alone is insufficient. This is because even if Fix or Float is displayed, the stability and reliability depend on on-site conditions. Therefore, in addition to the display status, it is important to know how to distinguish them on site.

The basic starting point is the status display itself. Many RTK systems indicate distinctions such as Fix, Float, standalone positioning, or corrections not applied. This display is the first thing to check but it is only an entry point. What matters is seeing how stably that status continues.

For example, instead of measuring immediately after Fix is displayed, you can make a more practical judgment by checking whether the values have settled, whether Fix continues, and whether estimated precision is not fluctuating sharply. Conversely, if Fix and Float switch at short intervals, even if Fix appears momentarily it is safer to defer adoption.

Next, check how much the coordinate values fluctuate. If you are stationary at the same spot and the horizontal or vertical positions visibly move, it is likely a Float solution or an unstable Fix. For critical points, simply confirming whether the values are settling on the spot improves status judgment.

Estimated precision displays are also helpful. Many devices and apps show estimated errors for horizontal and vertical components. These numbers are not universal, but they are effective auxiliary information for distinguishing Fix from Float. In general, Float solutions tend to show worse estimated precision than Fix and larger temporal variations. However, do not over-rely on display values; combine the status display, continuity, and coordinate settling behavior for an overall assessment.

Re-observing the same point is another effective method. Leaving the point and returning or measuring again after a short interval allows you to check consistency. If a Fix solution is stable, re-observation will not produce large deviations. A Float solution, however, tends to show subtle changes from time to time and reveals poor repeatability. For verification of critical spots, the re-observation concept is extremely effective.

In practice, people tend to rely only on whether the screen shows Fix, but what is really needed is a comprehensive view that includes status display, continuity, estimated precision, coordinate stability, and consistency on re-observation. The difference between Fix and Float appears in the overall behavior of the observation, not a single display. Understanding this greatly reduces on-site judgment mistakes.

Difference 5: difference in decision criteria for adoption in work

When understanding the difference between Fix and Float solutions, the most important final point is the decision criterion: "Can the coordinate be adopted in the work?" Theory alone is not enough for on-site personnel. What is needed is a practical demarcation of which states are acceptable for use, which should be waited for, and when to re-measure.

As a rule, tasks that require centimeter-level consistency—such as setting out, as-built verification, survey records, drawing checks, and construction position checks—should assume Fix solutions. If you adopt coordinates while still in Float, the positions may look fine at the time but discrepancies can appear later when overlaying point clouds, drawings, photos, and other observation points. When multiple people observe on different days, mixing Float solutions can easily break data consistency.

On the other hand, during site walkthroughs for rough position checks or when temporarily recording reference positions for draft drawings, Float solutions can sometimes be treated as provisional reference values. However, even in such cases, the premise is not to reuse them as official data downstream. In other words, Float solutions are safer considered as provisional position information for temporary confirmation rather than final operational values.

It is also important not to base adoption criteria solely on the status display. Even with a Fix display, if the surrounding environment is poor and Float persisted until just before, it may be better to wait and confirm stability. Conversely, if improvements to observation conditions can likely convert a Float to Fix soon, there is no need to give up immediately. Do not stop at seeing the status name; make adoption decisions including the background and continuity.

In practice, predefining observation rules reduces inconsistency in decisions. For example: adopt critical points only after confirming continued Fix, verify consistency with re-observation, change observation location slightly if the status is unstable, and avoid critical observations during times when correction communication is unstable. Understanding the difference between Fix and Float must be translated into operational rules to stabilize quality.

Especially on sites operated by multiple people, individual judgment differences can cause quality differences. If one person accepts Float and another uses only Fix, results from the same site will lack consistency. For that reason, it is important to verbalize Fix vs. Float decision criteria as a team standard.

Difference 6: difference in operations to maintain Fix solutions

The difference between Fix and Float is reflected not only in how you view results but also in operations that make one state easier to achieve. Fix is not something that happens by chance; it is stabilized by arranging conditions that make Fix achievable and adopting habits that maintain it. Conversely, sites where Float tends to persist share common operational quirks.

First, choosing the observation location is important. Simply selecting a position with a broad open sky can greatly affect how easily Fix occurs. On site, you may want to measure very close to the target, but being near a high wall, trees, vehicles, temporary materials, or metal surfaces increases vulnerability to reflections and blocking. Measuring a little away from the target where the sky is more open and stabilizing before observing can help maintain a Fix solution.

Next, how you act before and after observation matters. Immediately after moving, right after changing how you hold the device, or right after reconnecting communications, the solution may not have settled. If you rush to take measurements at this stage, you are likely to adopt Float or unstable Fix. For critical points, waiting a little after starting observation to confirm stability reduces rework.

Checking the communication environment is essential. RTK positioning appears to be satellite-only, but stable reception of correction information is a key factor. In places with unstable communication, Fix can be difficult even if satellite conditions are good. In wide sites or those with elevation changes, communication quality may vary by location, so understanding this before observation makes operations easier.

Review how the receiver is held and installed. If the attitude is unstable, the way of holding changes often, or the device is placed too close to obstructions, reception can be disrupted. In high-precision positioning, small differences in handling can affect state stability. Considering not only the moment of measurement but also the preparation and how the receiver is held as part of quality control makes Fix maintenance easier.

Also important is not forcing a Fix on the spot. In locations where obstructions are heavy, reflections are severe, or communications are unstable, it is often faster to change position slightly, shift the time, or use another observation route rather than stubbornly waiting. Operations to maintain Fix involve not leaving everything to the device but reading the site environment and creating conditions that make Fix more likely.

Practical points to review when Float persists

What troubles people on site is that even if they know the difference between Fix and Float, they don't know what to review when Float persists for a long time. Here are practical points to check when Float continues.

The first thing to check is how open the sky is. Confirm there are no nearby buildings, trees, slopes, heavy machinery, signs, or scaffolding. Even if you think the sky is open, one direction may be heavily blocked. Especially when you are too close to the observation target, moving a little away can improve the status.

Next, check for reflective environments. Metal fences, guardrails, vehicles, exterior walls, puddles, and accumulations of temporary materials are common causes of multipath. If Float persists near such items, moving slightly away often improves the situation. Rather than waiting long at a spot where Fix won't occur, distancing from reflection sources can be more effective.

Also verify the reception of correction information. If communication is weak, intermittently connected, or has large delays, the conditions required for Fix won't be met even if positioning itself is possible. Communication quality can vary by spot, so having an intuitive sense of such differences speeds decision-making. Checking communication stability before observing important points reduces failures.

Review how you allocate observation time. A practice of hastily looking at numbers and taking them increases the chance of adopting pre-Fix Float. Especially right after moving or startup, waiting a little often improves the state. To increase site efficiency, distinguish between measurements that need to be rushed and those that can wait the several tens of seconds necessary for stabilization.

Re-observation is also crucial. If Fix cannot be obtained on the spot, measuring another point and returning, waiting a bit, or changing position and retrying are effective actions. Positioning is not a one-shot task. For particularly important points, an operation that assumes re-verification rather than relying on a single measurement preserves quality.

When Float continues you may be tempted to panic, but the important thing is to break down "why it won't Fix." By sequentially checking satellites, reflections, communications, time, attitude, and surrounding environment for likely causes, you will often find clues to improve the situation. You truly benefit from understanding Fix vs. Float differences when you can perform this root-cause breakdown.

Understanding the difference between Fix and Float solutions speeds up on-site decisions

The difference between Fix and Float is not just a technical term to memorize. It is a criterion for deciding whether to adopt a coordinate on site, wait a bit longer, change location, or re-measure later. A Fix solution is a high-confidence state where integer ambiguities are resolved; a Float solution is a convergence-in-progress or a state lacking sufficient conditions for confidence. Understanding this difference alone greatly reduces on-site hesitation.

In practice, what matters is not only whether Fix is displayed but whether that state is stable, repeatable, and of quality suitable for the intended use. When Float appears, don’t give up immediately; consider why it is happening and review the environment and operations. With that mindset, you can act not just as an instrument operator but as a person who can manage positioning quality.

If you handle high-precision position information routinely on site, correctly understanding the status display and operating to stably utilize Fix solutions is indispensable. If you want to efficiently proceed from setting out to photo records, simple surveying, and construction verification as a continuous workflow, how you read and handle positioning states will determine work quality.

Furthermore, incorporating mechanisms that make it easier to handle high-precision on-site positioning—such as the iPhone-mounted GNSS high-precision positioning device LRTK—makes it easier to operate with awareness of Fix and Float differences. If you want to go beyond merely acquiring coordinates and smoothly link site photos and various records to positioning for simple surveying, it is important to be able to incorporate high-precision positioning into daily operations. Correctly understanding the difference between Fix and Float and setting up an operational environment where you do not hesitate on site will greatly change the accuracy and efficiency of future positioning work.