What’s the difference between a Fix solution and a Float solution? 5 decision criteria to avoid confusion in RTK positioning

When you start using RTK positioning in the field, the difference between Fix and Float solutions invariably shows up early. Even if the solution state displayed on the screen is visible, many field staff hesitate about how much they can trust it: whether they should record a measurement now or wait. Especially in tasks where coordinate reliability directly affects overall quality—such as as-built checks, stakeout, current-condition capture, or geo-tagging photos—vague understanding of Fix versus Float solutions can lead to positions that initially look fine but later show shifts or require re-measurement.

The difference between Fix and Float solutions is not just about higher or lower accuracy. It concerns how deterministically the receiver’s internal positioning computations can interpret the signals received from satellites, and that difference directly affects field judgments and operational rules. In other words, correctly recognizing whether a solution is Fix or Float is less about theoretical accuracy and more about making field decisions that prevent rework.

This article first clarifies the basic meanings of Fix and Float solutions, then explains five practical decision criteria so field personnel won’t hesitate. It’s not just terminology: you’ll learn which tasks absolutely require a Fix solution, when a Float solution can be used temporarily, and when apparent stability can be misleading—organized from a practical, field-oriented perspective.

Contents

• First, sort out the basics of Fix and Float solutions

• In one sentence: what is the difference between Fix and Float?

• Decision criterion 1: Check whether the solution meets the required task accuracy

• Decision criterion 2: Judge by convergence stability, not just the displayed solution

• Decision criterion 3: Include poor positioning environment in your judgment

• Decision criterion 4: Verify by reproducing the same point repeatedly

• Decision criterion 5: Prevent incidents by how you record and by operational rules

• Common failures when teams measure immediately on a Float solution

• Why you shouldn’t be overconfident even with a Fix solution

• Practical measures to make getting a Fix solution easier

• Understanding the difference stabilizes RTK operations

First, sort out the basics of Fix and Float solutions

RTK positioning determines a rover’s position with high precision by using information received from satellites. This process does not simply measure distances from satellites; it also uses finer carrier-phase information and applies corrections to narrow down the position. A crucial point here is whether quantities that should be treated as integer values can be resolved.

A Fix solution refers to the state where the ambiguity in those integer values has been resolved, and the position solution is determined definitively. Generally, when high-precision positioning is expected from RTK, a Fix solution is the premise. Centimeter-level positioning in the field is basically conditional on the solution being stably Fix.

A Float solution, by contrast, means that while the position is being computed, the integer ambiguities are not yet fully resolved and the solution has not completely converged. Even if coordinates are displayed, those values are prone to fluctuation and can vary under environmental influence. In other words, a Float solution is close to an intermediate stage of computation and should be treated with caution in practical work.

It’s important to note that a Float solution is not merely an error display. A Float solution does provide a position, and in some cases the displayed value may not be far off. That leads to a common field judgment: “A value is displayed, so it’s probably fine.” However, that is the most dangerous point. A Float solution may only momentarily show a nearby value and then change by several centimeters (a few inches) to several tens of centimeters (several tens of inches) in the next instant.

Because both Fix and Float solutions display coordinate values on the screen, newcomers can easily downplay the difference. But in reality the distinction affects downstream deliverables—drawings, point clouds, as-built checks, and stakeout—in fundamental ways. Start with a simple understanding: a Fix solution is close to a state where measurement is acceptable; a Float solution should still be handled with caution.

In one sentence: what is the difference between Fix and Float?

Put briefly, the difference between Fix and Float solutions is whether the position is determined with high precision or still in the process of being determined. That sounds abstract, but in practice it becomes very clear. A Fix solution is more likely to be suitable for use as a coordinate; a Float solution is often usable only as a reference value.

One reason field staff hesitate is that Float solutions can sometimes look usable. For example, when measured near a known point, a Float solution may appear almost coincident on the map. But if you re-observe the point after a short time or move slightly and return, the value may not reproduce. That lack of reproducibility is the decisive difference from a Fix solution.

Also, while Fix often evokes an image of high accuracy and Float of low accuracy, it’s more useful practically to see it as an operational difference. Fix solutions better withstand tasks that require later accountability—stakeout, as-built checks, aligning to control points, etc. Float solutions can be used for situational checks or provisional references, but are unreliable as final deliverables.

In short, the difference is not merely a numerical accuracy gap but whether you can adopt that coordinate as a project deliverable. Framing it this way reduces field uncertainty: decide whether the current coordinate will be used as a final deliverable or treated as provisional—that decision starts with whether the solution is Fix or Float.

Decision criterion 1: Check whether the solution meets the required task accuracy

When judging Fix versus Float, the first thing to consider is what level of accuracy the task requires. If you only focus on the solution state itself without clarifying this, you may become overly cautious or, conversely, make risky decisions. The important point is to align the solution type, not just its label, with the task’s accuracy requirements.

For instance, tasks like stakeout for structures, boundary verification, as-built management, and capturing current conditions intended for overlay with drawings or point clouds are sensitive to even small position shifts. For such tasks, having a stable Fix solution is practically a prerequisite. If you adopt measurements taken under a Float solution, you may not notice the error in the field, but later overlaying will reveal offsets and require re-measurement.

On the other hand, for rough position awareness in the field or for deciding which areas need detailed measurement later, Float solution values can be useful. The crucial point is not to reinterpret “Float can be used” as “Float can be accepted as final deliverable.” Float values should be used only as provisional guidance, not as final records or deliverables.

In practice, clearly specifying required accuracies by task within your organization helps prevent inconsistent judgments. For example: final deliverable coordinates require Fix; provisional location checks may use Float but must be re-measured; important points require re-observation—arranging rules like this reduces quality variance caused by individual judgment differences.

If you’re unsure whether to accept a Fix or Float, return to what precision the task demands. The higher the required precision, the more reason there is to wait for a Fix. If the objective is merely provisional awareness, Float values may be used temporarily on condition that they are not adopted as deliverables and will be re-measured.

Decision criterion 2: Judge by convergence stability, not just the displayed solution

A common field misconception is believing that the moment the screen shows Fix, it’s safe to measure immediately. In practice, more important than the Fix label itself is how the solution converged to Fix and whether it remains stable afterward.

RTK convergence depends on receiver environment, satellite geometry, and the status of correction data reception. Under good conditions, the solution may converge to Fix quickly and remain stable. Under poor conditions, the solution may switch between Float and Fix or show Fix while the values remain unsettled. Coordinates obtained under such conditions are risky if you trust the display alone.

What you really need to check is whether the convergence to Fix was reasonable, whether fluctuations after Fix are small, and whether the state holds if you wait a bit. In other words, assess the smoothness of the path to Fix rather than the label. A momentary Fix that immediately reverts to Float is not trustworthy operationally.

A practical approach is to avoid immediately recording the instant Fix appears; instead, observe briefly. Confirm the magnitude of value fluctuations, the continuity of the solution, and the stability of satellite reception; record only when things appear settled. Skipping this check to rush through measurements is common, but a few seconds to a dozen seconds of verification can significantly reduce the risk of wrong measurements.

This is especially true near buildings, under trees, below slopes, or near heavy machinery, where apparent Fix may still be unstable. In such locations, don’t rely solely on the Fix display; check reproducibility and convergence behavior. Understand that the solution state should be evaluated over time rather than by a single instant on the screen.

Decision criterion 3: Include poor positioning environment in your judgment

The difference between Fix and Float is not determined solely by receiver performance or settings; the surrounding environment greatly influences the solution state. Therefore, when judging solution state in the field, always consider the environment you are standing in as well as the screen display.

A typical issue is sky visibility. In open areas with a wide view of the sky, satellite signals are easy to receive and correction computations tend to stabilize. Conversely, locations surrounded by buildings, trees, bridges, retaining walls, or mountains often have poor reception conditions. In such settings, Float may persist or Fix may collapse again.

Reflections are another aspect to watch. When satellite signals reflect off surrounding structures or the ground, distinguishing those reflected signals from direct signals becomes difficult and causes solution instability. Even if the sky looks open, nearby metal surfaces or large structures can destabilize the solution. Judging that “a value is displayed so it must be fine” in these cases is dangerous.

Mobile communications status is an easily overlooked factor. For correction services that depend on communication, interruptions or delays can make convergence difficult even if satellite reception is good. In other words, persistent Float may stem from correction reception issues rather than satellite reception. To isolate the cause in the field, check not only sky visibility but also communication status and correction reception.

Importantly, in poor environments you shouldn’t make achieving a Fix the sole objective. Rather than forcing a Fix at that point, it may be more practical to move slightly, reposition where the sky is more visible, or perform supplementary checks from a nearby area with better conditions. Don’t interpret solution-state issues as only internal receiver problems; understanding them in relation to the surrounding environment leads to better decisions.

Decision criterion 4: Verify by reproducing the same point repeatedly

The difference between Fix and Float is most tangible in the field through reproducibility—whether repeated measurements of the same point at different times yield nearly the same result. This check is more practical than theoretical and offers a highly reliable decision basis.

Coordinates obtained under a Float solution may appear plausible at one moment but shift when the same point is re-measured. The shift might be only several centimeters (a few inches) or, depending on conditions, much larger. The problem is that such shifts are hard to notice on the spot—especially when the map or background imagery is coarse, subtle discrepancies get overlooked.

By contrast, when Fix is stable, re-observations of the same point yield smaller differences. While perfect agreement under all conditions isn’t guaranteed, results usually stay within practically acceptable limits. This reproducibility difference is crucial for distinguishing Fix from Float.

In the field, it’s good practice to repeatedly observe important points. For control points, points used for later overlays, or points where errors would be critical, don’t stop after a single measurement. Re-measuring to confirm the same result provides much greater confidence in the solution’s reliability.

This approach is useful not only for telling Fix from Float but also for assessing the quality of a Fix. If the display shows Fix but reproducibility is poor, treat the solution cautiously. Conversely, if a stable Fix with good reproducibility is confirmed, you have solid grounds for your field decision. When in doubt, don’t just look at the display—measure the same point again. That extra step is the quickest practical shortcut to judging solution quality.

Decision criterion 5: Prevent incidents by how you record and by operational rules

Even if staff understand the difference between Fix and Float, vague field rules can still lead to quality incidents. On multi-person teams, someone may take measurements while a Float solution persists, and those data can mix into the dataset. Therefore, standardize how you record the solution state and how you handle data.

The most basic practice is to record the solution state at the time of measurement. If only the coordinate is recorded and it’s unclear whether it was Fix or Float, later verification becomes impossible. Especially on projects where rework is difficult, it’s valuable to log the solution state, the acquisition time, whether re-observations were performed, and, if necessary, brief notes on surrounding conditions.

Also effective is predefining conditions for adopting measurements into deliverables. For example: accept only stable Fix solutions for final deliverable points; manage Float solution data separately as provisional; require re-observation of critical points. Having such rules reduces variability caused by individual judgment and stabilizes field quality.

Because fieldwork is time-pressured, the temptation to think “This time it’ll be okay” is natural. But RTK issues often don’t manifest immediately; they surface later as mismatches during drawing overlay, discrepancies with data from other teams, or inconsistency with past data. That’s why a system to manage solution state at the time of measurement is necessary.

Knowing the difference between Fix and Float is not enough. To make it a practical field decision criterion, embed it in recording practices and operational rules so that any operator produces the same quality. Field accuracy is not determined solely by the equipment; operational discipline plays a large role.

Common failures when teams measure immediately on a Float solution

There are practical reasons teams sometimes proceed with a Float solution: they want to finish quickly, Fix is taking a long time, the display doesn’t look that off, coordinates are present. These factors lead to taking measurements while the solution is still Float. It’s important to understand what failures can result downstream from that choice.

A common failure is stakeout error. Even if a Float measurement seems acceptable on site, another team member using a Fix solution later may find positions don’t match and it becomes unclear which is correct. When work spans multiple days, these differences can cause significant confusion.

Another frequent issue is poor overlay of current-condition data. Small offsets between captured coordinates, photos, point clouds, and plans can go unnoticed during acquisition but later show up as misalignment. This creates extra correction work in analysis and drawing stages and can easily cost more time than the field team saved by moving faster.

A particularly troublesome case is when Float-derived data are mixed into a dataset only in part. Because the overall set may look plausible, it becomes hard to identify which sections are problematic. You may see offsets only in specific segments or find certain points that don’t reproduce, leading to lengthy root-cause investigations.

All these failures share the trait that the problem looks small at the time. That’s why clear boundaries are needed for when Float can be used: is it provisional verification or final deliverable? Blurring that distinction is the most dangerous practice. Prioritizing short-term efficiency by accepting Float as final tends to increase rework and reduce overall productivity.

Why you shouldn’t be overconfident even with a Fix solution

Believing a Fix solution is always correct is another pitfall. True, Fix is more reliable than Float, but unconditionally trusting the Fix display is risky. Fix is only one computational state, and under certain field conditions or workflows it may not yield the expected quality.

For example, a temporary Fix in a poor reception environment can occur. You may get a brief Fix near buildings or trees or in the presence of reflections, but that value may not be truly stable. More important than the fact it became Fix is whether the Fix persists and whether re-observation produces the same result.

Also, errors in control setup or coordinate system handling can shift all measurements even when they are Fix. Fix indicates a locally resolved solution state, but it does not guarantee that your entire workflow—settings, reference frames, procedures—is correct. If settings or procedures are wrong, even good solution states produce incorrect deliverables.

In the field, people often relax the moment Fix appears and skip further checks. But Fix should be thought of as a starting line. From there, verify stability, reproducibility, consistency with control, and recording continuity before you can rely on the measurement operationally.

Keeping this mindset helps you avoid overtrusting Fix or underestimating Float. The key is not to take the display at face value, but to understand the conditions under which that solution was obtained.

Practical measures to make getting a Fix solution easier

Having understood the difference between Fix and Float, the next question is how to increase the likelihood of obtaining a Fix. Here are practical, device- and service-agnostic practices that work in the field.

First, choose measurement locations with some care. If the target point is near a building or under a tree, try to confirm from a nearby spot with better sky visibility before finalizing. Field teams often linger too long at a poorly conditioned target location; a small change in position can substantially improve convergence.

Second, don’t rush right after powering up. Right after startup, satellite reception and correction reception may not have stabilized. If you start measuring as soon as numbers appear, you’re more likely to record Float. Observe the transition of the solution for a moment and begin the main work after things settle.

Check communication status as well. Even with good satellite reception, an unstable correction feed makes Fix difficult. Reception strength can vary by spot, and moving a few meters (a few ft) can sometimes make a big difference. While it’s easy to focus on satellites, confirming stable delivery of corrections is equally important.

Also, for critical points don’t try to get it right in one shot. Instead of immediately recording when Fix appears, wait a bit, re-measure, and confirm from another direction. Experienced operators do this instinctively; novices tend to rely on the display. Formalizing these checks as procedures prevents reliance on individual intuition.

The gist of increasing Fix likelihood isn’t special technology but avoiding bad conditions, not rushing, and not skipping confirmations. RTK’s high precision comes with environmental dependence. How the field crew uses the equipment will make a real difference.

Understanding the difference stabilizes RTK operations

Memorizing the difference between Fix and Float as a basic RTK concept is not enough. In practice, how you judge the difference and incorporate it into operations matters. Fix is the condition that enables high-precision deliverables; Float is a provisional stage that requires caution. Even clarifying this basic point prevents much rework.

To avoid hesitation in the field, adapt your handling of solutions to required precision, look beyond the Fix display to assess stability, include the measurement environment in your judgment, confirm reproducibility, and set up recording and operational rules. These aren’t special theories but practical criteria that raise everyday measurement quality.

For stable RTK use in operations, the ability to repeatedly obtain trustworthy coordinates is more important than merely getting a coordinate to display. If you understand the difference between Fix and Float, you’ll find it easier to decide whether to accept a value, wait, or recheck. Those daily choices add up to stable field quality.

If you want to make high-precision positioning simpler and more practicable in the field, mobility and usability are key. LRTK, an iPhone-mounted GNSS high-precision positioning device, is a practical option for on-site position checks and coordinate capture. If you understand the difference between Fix and Float and want to proceed confidently with everyday positioning tasks, adopting high-precision positioning in a way that fits your workflow helps balance speed and quality in the field.