Diagnosing cycle slips in GNSS observations

Understand continuity in carrier phase measurements

Carrier phase observations are precise measurements that include an unknown integer ambiguity for a continuous tracking arc. A loss of tracking can interrupt that continuity and create a change in the integer relationship, commonly described as a cycle slip. The processing software must detect or otherwise handle the discontinuity appropriately. A cycle slip is therefore more than a momentary inconvenience on a controller; it can affect which observations belong to a continuous usable arc.

Not every jump in a coordinate plot is a cycle slip, and not every cycle slip produces an obvious coordinate jump. Receiver behavior, available signals and processing strategy influence the effect. Start with the raw observation evidence and the processor's diagnostics. Avoid diagnosing the cause from a single visual symptom or assuming that a smooth output trajectory proves every carrier phase arc remained uninterrupted.

Continue learning Cycle slips: what interrupted phase tracking can change

Link interruptions to field conditions

Common circumstances associated with tracking interruptions include obstruction, rapid signal changes, difficult reception and some atmospheric conditions. Inspect the actual site and platform behavior. Trees, bridges, building edges and moving equipment can affect a static or kinematic session differently. Record events and approximate times during collection so the office can connect diagnostics with physical conditions rather than speculate after the crew has left the site.

Equipment and recording issues also deserve attention. Check cable condition where relevant, power continuity, receiver restarts and file gaps. A missing interval caused by a recording failure is not the same as a signal specific carrier discontinuity, even though both reduce usable data. Keeping those categories separate helps the team choose an appropriate corrective action and prevents an antenna or storage problem from being mislabeled as an atmospheric event.

Continue learning Carrier phase and code measurements in practical GNSS surveying

Inspect signal and epoch information

Use software that can inspect the observations and report relevant continuity indicators. Depending on the data and format, loss of lock information, combinations of observations and processing diagnostics may help identify candidate slips. Interpretation requires attention to the signals actually recorded and the processor's detection method. A flag is evidence to review, not a universal statement about how much coordinate error occurred at that epoch.

Plot events against time, satellite and signal where the tools permit. A problem concentrated on one low elevation satellite suggests a different investigation from simultaneous interruptions across many observations. Compare with signal quality, receiver events and route conditions. Preserve the original data and diagnostic output before editing. This makes it possible to distinguish what the receiver recorded from what a later processing step inferred or changed.

Continue learning Documenting coordinate epoch in GNSS survey data

Review how the processor handles discontinuities

Processing methods can detect, repair, split or reject affected arcs according to their supported models. Read the software documentation and retain the relevant settings. Do not assume that an automatic repair is valid merely because the solution completes without an error. Examine the quality evidence around the event and the amount of usable observation remaining, especially when a short session or a critical trajectory segment depends heavily on that interval.

Avoid manually joining arcs or changing ambiguity related information without a defensible procedure. Such edits can create an apparently continuous dataset that no longer represents the recorded observations transparently. If editing is required by the approved workflow, retain the original, describe the operation and identify the affected span. A reproducible edited derivative is preferable to an overwritten file whose changes cannot be reconstructed.

Continue learning Caring for GNSS equipment in heat and rain

Assess consequences for static sessions

In a static occupation, repeated interruptions can reduce continuous data and weaken the intended solution. Review whether enough suitable observations remain under the project's processing requirements. The appropriate response may be a longer or repeated occupation, a better site or another technique. Extending recording at the same obstructed location without reviewing the cause may simply create a longer file with the same unresolved weakness.

Compare independent sessions or network connections as planned. A coordinate that agrees with another result is useful evidence, but shared reference and setup errors can remain. Read ambiguity information, residuals and observation completeness together. If the accepted coordinate depends on a heavily edited session, explain why the evidence is sufficient and what independent check supports the decision rather than hiding the editing history in an intermediate folder.

Continue learning Cycle slips: what interrupted phase tracking can change

Assess consequences for moving platforms

For kinematic work, a tracking interruption can affect a particular segment of the route and the recovery that follows. Review solution state and quality through time. If inertial or other sensor information bridges a gap, use the integrated system's documented quality assessment. A continuous output file does not mean that every epoch has equal observational support, and interpolation should remain distinguishable from directly supported positions.

Plan independent checks or repeated passes where the final product is important. An event near a turn, bridge or dense canopy can have downstream effects on sensor georeferencing. Review the complete measurement chain, including timing and lever arms, rather than assigning every mapped discrepancy to the carrier phase interruption. The event timeline helps focus the investigation, but the final conclusion should be supported by the system records and check evidence.

Continue learning Carrier phase and code measurements in practical GNSS surveying

Improve the next collection

Use the diagnostic findings to change the field plan where appropriate. That may mean improving site selection, adjusting an approved observation strategy, protecting power continuity or verifying equipment condition. Keep configuration changes controlled and test them with representative data. A successful test in open terrain may not establish robustness along an obstructed route, so document the conditions under which the improvement was evaluated.

Train crews to record meaningful events and recognize when observation continuity is deteriorating. They do not need to solve every carrier phase diagnostic in the field, but they should know when to pause, inspect the setup or collect a planned repeat. Clear escalation rules are more useful than telling operators simply to wait until the controller looks stable again.

Continue learning Documenting coordinate epoch in GNSS survey data

Keep event counts in their proper context

A diagnostic count can help compare sessions, but it needs a denominator and a definition. A longer file or a file containing more satellites can naturally contain more detected events than a shorter restricted dataset. Record the observation span, signals and detection method before ranking sessions by a raw count. Review the affected intervals and their consequence for the accepted solution. This avoids rejecting useful data solely because it contains more reported events while overlooking a short critical interruption in an otherwise small file.

Continue learning Caring for GNSS equipment in heat and rain

Retain an interpretable continuity record

Archive the original observations, event log, processing diagnostics, editing history and accepted output together. Identify important affected intervals and the action taken. The report should describe practical consequences for the coordinate or trajectory, avoiding a claim that every detected slip caused a known error magnitude. What matters is whether the final result has adequate support under the approved method.

A disciplined cycle slip review connects carrier phase theory with real field decisions. It distinguishes recording gaps, tracking interruptions and processing treatment, then evaluates their effect with independent evidence. That approach produces a more credible survey record than either ignoring every warning or rejecting an entire dataset solely because a diagnostic counter is nonzero.

Continue learning Cycle slips: what interrupted phase tracking can change