Comparing RTK Fix and Float Solutions｜7 Differences and Remedies You Should Check On Site

When positioning with RTK, whether the status shown on the screen is Fix or Float greatly affects on-site decisions. Even if coordinates appear on the display, you cannot judge whether those coordinates can be adopted as-is or should be put on hold without correctly understanding the solution state. Especially for tasks where coordinates directly affect downstream work—such as as-built checks, staking out positions, geotagging photos, and setting reference for point clouds—treating the difference between Fix and Float loosely can lead to remeasuring or rework.

In practice, Float solutions can sometimes look numerically stable. As a result, many cases occur where people see the displayed numbers and decide “looks fine.” However, the essence of RTK is not merely that a position is displayed, but how certain that position is. The Fix solution represents the typical state when RTK has achieved high precision, while the Float solution is safer to interpret as an intermediate or unstable state where conditions are not yet fully met.

This article organizes, from seven perspectives, the basic differences between Fix and Float, concrete ways to tell them apart on site, and what to do when Float persists. It explains in operational terms—so that practitioners who search for “Fix solution Float solution difference” can directly apply it on site—not only the theory but also practical procedures.

Table of Contents

• Understand the basics of Fix and Float solutions first

• Difference & remedy 1: How to assess precision differences

• Difference & remedy 2: How to judge initialization stability

• Difference & remedy 3: How to read the impact of satellite reception environment

• Difference & remedy 4: How to check correction data and communication status

• Difference & remedy 5: How to organize measurement movements and holding methods

• Difference & remedy 6: How to be wary of vertical (height) discrepancies

• Difference & remedy 7: How to separate situations where measurement is acceptable from those to put on hold

• Troubleshooting steps when Float persists

• Philosophy for continuously obtaining stable Fix solutions

• Summary

Understand the basics of Fix and Float solutions first

With RTK, high-precision positions are obtained by comparing information between the base and rover using signals received from satellites. An important concept in the positioning calculation is how well the integer number of signal cycles can be fixed. When this is stably and definitively resolved, it is called a Fix solution; when it cannot yet be fully resolved, it is a Float solution.

In practice, it helps to understand Fix as “a state where a high-precision solution has been resolved” and Float as “a provisional solution.” When you have a Fix, both horizontal and vertical positions tend to be relatively stable and it is easy to use for on-site staking and inspection tasks. Float is not entirely unusable, but it tends to fluctuate more and is more susceptible to environmental effects, so adopting it as a final value requires caution.

It is important to note that this is not a simple binary where Fix is always perfect and Float is always unusable. Even with a Fix, poor reception conditions or improper instrument holding can cause offsets, and Float can sometimes be used for rough position checks depending on the purpose. However, for work that requires reproducibility and traceability—such as surveying or construction management—base your decisions on Fix solutions. Treat Float as a sign that conditions are not yet met; this conservative approach is safer in practice.

A common on-site misconception is that small movement in displayed coordinate values implies high accuracy. However, Float solutions can appear superficially stable while having a systematic offset from the true value. In other words, a small display fluctuation is not the same as indicating a correct position. Understanding this distinction is the first step in telling Fix and Float apart.

Difference & remedy 1: How to assess precision differences

The biggest difference between Fix and Float is the achievable precision. Generally, Fix can be treated as a state aiming at centimeter-level accuracy (half-inch accuracy). In contrast, Float has greater uncertainty and can range from several centimeters (several in) to several tens of centimeters (several tens of in), or in some cases even larger offsets. On site, what matters is understanding this difference not as a matter of impression but in terms of its impact on work.

For example, verifying piling positions, locating points near boundaries, and managing installation positions for structures can be directly affected by differences of a few centimeters. If you adopt values measured in Float for such tasks, you may need to recheck on another day when you get a Fix and find the positions don’t match, creating work to determine which is correct. Conversely, for tasks that only require a rough position over a wide area, Float can be used with limited scope. Even then, clearly separate values intended as deliverables from provisional on-site references.

When judging precision, do not rely solely on the instrument’s displayed estimated accuracy. That estimate is only a computational guideline and cannot fully represent degraded surrounding conditions or reception. Important is a comprehensive assessment: the solution state, satellite status, openness of the measurement location, and recent communication history.

As a remedy, set an operational rule that deliverable measurements must be obtained in Fix. Treat Float values as provisional—used for temporary placement, movement checks, or initial guidance. Also, recheck the same point after some time to confirm reproducibility; this reduces being misled by apparent stability. Understand that precision differences are not just display differences but define what kinds of tasks can safely adopt the measurement.

Difference & remedy 2: How to judge initialization stability

The Fix vs. Float difference appears not only in the positioning result but also in initialization stability. RTK does not always reach Fix immediately after starting positioning. If reception and communication are sufficient, Fix is reached relatively quickly; but under poor conditions Float may persist for a long time. In other words, persistent Float itself can be a sign of problematic site conditions.

What matters here is not to over-rely on the thought that “if we wait it will become Fix.” Of course, if you have just started positioning, waiting a little is worthwhile. However, if Float persists after a reasonable waiting period, it is often faster to review environment and settings. On site, time spent passively waiting for a Fix tends to add up and reduce overall work efficiency.

When judging initialization stability, it’s important not only to look at the time until the first Fix, but also whether Fix can be maintained after being reached. A solution that flips to Fix for only a few seconds and then returns to Float is not stable for practical operations. That might simply be a momentary lock-in, and values measured at that moment may lack reproducibility. A stable Fix means the state does not swing significantly during observation and can be continuously maintained under consistent conditions.

As a remedy, start positioning in an open location and get to Fix before beginning measurements. Initializing right next to a building or under trees wastes time and may start work under an unstable solution. Also, rather than moving while waiting for initialization, stop and let the state stabilize. How well initialization is done affects the entire subsequent task quality, so spend the first few minutes carefully.

Difference & remedy 3: How to read the impact of satellite reception environment

One major factor separating Fix and Float is the satellite reception environment. In open sky areas you can more easily receive the necessary number of satellites and the signal quality tends to be stable, making Fix more likely. Near buildings, under trees, around elevated structures, beside slopes, or where heavy machinery and materials are concentrated, satellites may be hard to see and signals can suffer multipath. As a result, Float may persist or a temporary Fix may be hard to maintain.

A common on-site assumption is that conditions are the same across the same site, but in reality moving only a few meters can change sky openness and the solution state. Especially next to tall structures or where sky is only open on one side, reception can be worse than it appears. To judge Fix vs. Float, you must not rely only on screen text but also on observing what kind of sky you are under.

Measuring in a bad reception area can result not only in prolonged Float, but also in unreliable data even if Fix briefly appears. Biases in which satellites are received or multipath effects can distort computations. Therefore, do not only confirm a Fix display but also whether that Fix was obtained in a reasonable environment.

As a remedy, find the most open spot near the point to be measured, stabilize the state there, and then measure. If you must measure near obstructions, check the same point multiple times and at different times to see reproducibility. On sites where many points are measured in a short time, mapping areas with high obstruction influence before measuring reduces rework. The reception environment is the fundamental cause of Fix vs. Float differences; do not leave it to the equipment—people must read the site.

Difference & remedy 4: How to check correction data and communication status

RTK depends not only on satellite signals but also on stable reception of correction data. If correction data arrival is delayed, interrupted, or incorrectly configured, you may not reach Fix even if satellites are visible. On site, when Float persists despite open sky, the correction side problem is often overlooked.

In operations using mobile communications to receive corrections, fluctuations in communication quality directly affect positioning state. If you worry only about antenna reception and not about communications, cause separation is delayed. Because the screen still shows a position, you might continue working despite unstable communication, but if correction updates are not stable, maintaining Fix will be difficult.

Configuration errors must also be considered. If the correction source, authentication, coordinate system, or height handling are incorrect, RTK performance may not be achieved even if values move plausibly on screen. Especially with equipment unused for a while or shared among multiple people, prior settings can remain and produce unintended states.

As a remedy, if Float persists check not only received satellites but also the correction connection status and update flow. In areas with weak communication, moving the measurement point slightly may improve reception. Also incorporate a settings review into on-site checklist procedures to reduce basic configuration mistakes. Fix is not achieved by satellites alone; correction data must be stable for Fix to be established—understanding this speeds diagnosis.

Difference & remedy 5: How to organize measurement movements and holding methods

Differences between Fix and Float are influenced not only by mechanical conditions but also by how the operator moves and holds the instrument. Even if Fix is achieved, large shaking during measurement or insufficient static time when stopping can destabilize the solution. When taking many points quickly, state checking can become sloppy and Float values can be mixed in while assuming Fix.

In practice, operators often walk with the rover and stop briefly to measure. Right after stopping, attitude and reception conditions may not have settled. Even if the screen shows Fix, waiting a moment to confirm stability improves reproducibility. Also, changes in the orientation of the positioning unit or how obstructions affect it can vary each time and slightly change conditions even at the same point.

Holding method matters: instrument height, tilt, and body shielding cannot be ignored. Human body can block satellites in some directions, and holding at different orientations each time causes instability. In narrow places, changing stance or body direction slightly can change the solution.

As a remedy, always pause briefly and remain still at the measurement point to confirm the solution is stable before recording. Standardize holding methods on site—consistent height and posture reduces variation. On rushed sites, individual operator habits tend to appear, so share Fix confirmation standards as operational rules rather than only verbally. The Fix vs. Float difference manifests not only as device performance but also as measurement practice differences.

Difference & remedy 6: How to be wary of vertical (height) discrepancies

When considering Fix vs. Float differences, attention tends to focus on horizontal position, but in practice vertical discrepancies often require the most caution. In many jobs, horizontal positions may seem fairly consistent while height alone is noticeably off. Float often shows instability earlier in height, so repeated measurements at the same spot can yield fluctuating elevations.

This is because satellite geometry and signal conditions tend to affect vertical components more, and height fluctuations become more apparent under environmental influence. On site, because discrepancies are less obvious on a plan view, height checks are often postponed, but for tasks where elevation matters—such as as-built checks, earthwork volumes, drainage slopes, and installation heights—neglecting this can cause major issues.

Height also involves reference plane handling, so proximity of numeric values alone is not assurance. Confirm what height datum is used and whether it matches required on-site height representation. Fix with an incorrect datum will still be offset, and Float's observational instability compounds interpretation issues.

As a remedy, for tasks where height is important, in addition to confirming Fix, compare measurements with known points or known structure heights. If a site has a reference height, measuring it at the start to check consistency greatly increases confidence. Don’t assume horizontal agreement guarantees vertical adequacy—treat height verification separately when managing Fix and Float.

Difference & remedy 7: How to separate situations where measurement is acceptable from those to put on hold

Finally, to translate the Fix vs. Float difference into practice, drawing a clear line between situations where you can proceed and those to put on hold is crucial. If this is ambiguous, on-site decisions vary by operator and quality differences arise even within the same company. Therefore, Fix and Float must be more than technical terms—they must be embedded as decision rules in operations.

As a principle, values that will be deliverables, require third-party explanation, or serve as reference values for downstream processes should be obtained in Fix. Float should be limited to provisional uses such as positional awareness while moving, rough checks, or sizing out work ranges. If you adopt Float values as official and they later conflict with Fix values, confusion occurs about which to accept.

Also, adopting a Fix display as an immediate go-ahead is insufficient. Fix obtained in an enclosed environment, after unstable communications, or only maintained briefly should be treated cautiously. Practically reliable cases are those where three factors align: solution state, environment, and reproducibility.

As a remedy, document on-site standards. For example: record deliverable points only after confirming Fix and remaining still; remeasure as needed; and for height-critical points compare with known values. Formalizing operational rules reduces judgement variability among staff. The Fix vs. Float distinction is not merely conceptual but directly tied to establishing on-site quality rules.

Troubleshooting steps when Float persists

Even if you understand Fix vs. Float, you may not know what to check first when Float persists. Rather than waiting blindly, it is important to sequentially isolate causes. The key is to consider three categories: reception environment, correction data, and measurement method.

First check sky openness. If buildings, trees, slopes, metal objects, or vehicles are nearby, reception environment may be the primary cause. Move a few meters to a more open spot and check the state again. If it changes to Fix, you can diagnose the cause as environmental rather than equipment or settings.

Next check correction connectivity. Delays, disconnections, or misconfiguration of corrections can keep you in Float even under good satellite conditions. On site, people tend to be reassured when communication appears connected, but you must confirm corrections are being delivered stably. If other locations get Fix but this one does not, suspect communication weakness.

Then review how the unit is held and whether you are truly static. Ensure you are not walking, measuring immediately after stopping, or changing hold position each time. A common cause is not allowing enough still time—often a brief pause is enough to reach Fix.

If the cause is still unclear, verify at a known point or a location that previously produced a stable measurement. If Fix is obtained there, the instrument is likely fine and the site conditions are suspect. If Float persists anywhere, then check settings and connectivity. The important point in troubleshooting Float is not to fixate on one cause but to sequentially rule out conditions—this speeds recovery on site.

Philosophy for continuously obtaining stable Fix solutions

Knowing the difference between Fix and Float is important, but what is more valuable in practice is understanding how to maintain Fix steadily. On site, it is not enough to get a Fix once—you need to sustain a stable state throughout the working time. This requires not only individual techniques but an operational perspective on the whole workflow.

First, read the environment before work. Identify open areas, tough spots, places where communications may be unstable, and points where height control is critical. Working in an order that prioritizes easy-to-Fix spots reduces time wasted struggling with Float in unsuitable locations.

Next, standardize measurement procedures for deliverable points. If everyone follows the same steps—stop and confirm, record only when stable, remeasure as needed—operator-dependent quality differences shrink. RTK can provide high precision, but inconsistent operations prevent extracting that performance.

Also, review results critically. Don’t be reassured only by a Fix display; assess reproducibility at the same point, vertical consistency, and relation to the surroundings. Make securing usable coordinates—not just obtaining Fix—the operational goal. This stabilizes on-site decision-making.

Sites that consistently maintain Fix aren’t doing anything extraordinary: they prepare conditions before measuring, avoid rushing during measurement, and confirm reproducibility afterward. Turn knowledge of Fix and Float into daily procedures and rules—this is the fastest way to improve RTK operations.

Summary

The difference between Fix and Float in RTK is not just a display difference. Fix is a state where high-precision positioning is established and is suitable for deliverables. Float should be treated as an intermediate or unstable state where conditions are insufficient. Failing to understand this difference can lead to adopting plausible-looking numbers that later require remeasurement or cause insufficient explanations.

On-site checkpoints to confirm are precision, initialization stability, satellite reception environment, correction data and communications, measurement movements, vertical consistency, and decision rules for acceptance. Covering these seven aspects allows you to turn the Fix vs. Float understanding into practical on-site decisions. Especially important is to approach Float calmly as a sign of insufficient conditions and to isolate causes methodically.

To use high-precision positions stably on site, not only device performance but also ease of status verification and operational simplicity matter. If you want an RTK setup that is easy to handle on site and connects positioning results to practical work—reducing remeasures and stabilizing quality—consider solutions like the iPhone-mounted GNSS high-precision positioning device LRTK.