GNSS Integer Ambiguity Resolution Errors in RTK: What They Mean and How to Fix Them

Applies to: All RTK GNSS systems used in survey, machine control, and construction layout

What Is Integer Ambiguity?

RTK (Real-Time Kinematic) GNSS measures positions using the phase of carrier waves from satellites rather than just the timing of code signals. Each carrier wave cycle is approximately 19–24cm long (depending on frequency). The receiver knows the fractional phase offset but not how many complete cycles (the integer N) separate the satellite from the antenna. This unknown integer N is called the integer ambiguity. RTK achieves centimeter accuracy only when N is correctly determined to an exact whole number — this is "fixed" RTK. When N cannot be resolved, the system uses a best-estimate non-integer (float) solution with 30–50cm accuracy.

Why Does Integer Ambiguity Resolution Fail?

• Insufficient common satellites — base and rover need to track the same satellites simultaneously; obstructions reduce this
• Multipath at rover or base antenna — reflected signals corrupt carrier phase measurements
• Cycle slips — brief signal interruptions (crossing under a bridge, tree canopy) reset the ambiguity count
• Poor satellite geometry (high PDOP) — insufficient spread of satellites across the sky for ambiguity resolution
• Long baselines — corrections degrade at long distances from base; ambiguity resolution success rate drops beyond 10–20km
• Ionospheric disturbance — solar activity and time-of-day effects increase differential ionospheric error
• Wrong base coordinates — errors in base station position cause systematic errors that prevent correct ambiguity resolution

How to Resolve Integer Ambiguity Failures — Step by Step

1. Move to an open sky location — clear 15° above the horizon in all directions if possible
2. Allow 2–5 minutes stationary initialization time — moving the antenna during initialization prevents ambiguity resolution
3. Verify base station is operating and correction age is <10 seconds on the rover controller
4. Check baseline length — if rover is more than 15km from base, consider setting up a closer base station or using a VRS network
5. Check for cycle slips — if the receiver was under tree cover or near structures, cycle slips may require re-initialization in a clear area
6. Verify base coordinates are correct — even a 1m error in base coordinates prevents correct ambiguity resolution
7. Check that multi-constellation tracking is enabled — more satellites dramatically improves initialization reliability and speed
8. If ambiguity never resolves under apparently good conditions: check receiver firmware version and contact technical support

Float vs. Fixed — When Is It Safe to Measure?

RTK Fixed (integer resolved): centimeter accuracy — safe for all precision survey, stakeout, and machine control. RTK Float (ambiguity unresolved): 30–500mm accuracy depending on baseline and conditions — not suitable for precision stakeout or machine control. Autonomous/SBAS: 0.5–3m accuracy — suitable only for navigation, not construction or survey measurements.

Improving Initialization Speed

Modern multi-frequency (L1/L2/L5) receivers initialize significantly faster than single-frequency L1 receivers — often in 5–30 seconds vs. 1–5 minutes. If initialization speed is critical for your workflow, upgrading to a dual-frequency or triple-frequency receiver greatly reduces initialization time and improves ambiguity resolution reliability.

Related Topics

GNSS Multipath Interference | Leica E01 RTK Float | RTK Float Error Guide