GNSS in Ports and Open-Pit Mines: Why a Fixed RTK Solution Can Still Be Unreliable

· ⏱ 6 min read · 👁 views

A port vehicle may lose its RTK fix beneath a quay crane. A haul truck entering an open pit may retain many satellites while its reported position drifts toward the slope. Both situations require more than a check of nominal positioning accuracy.

Ports combine metal structures, water surfaces, and moving obstructions. Open-pit mines restrict sky visibility through steep walls, stockpiles, and pit depth. This article explains how observations, correction links, and sensor fusion affect ground vehicles in these environments, and how to evaluate whether positioning remains usable.

1. Satellite count does not describe the whole solution

Positioning depends on satellite distribution, direct signal reception, measurement noise, and timely corrections. Even a dozen satellites can provide weak geometry when most occupy the same part of the sky. Container aisles and winding haul roads also change which satellites remain visible.

Centimeter accuracy in open sky does not establish continuous performance beneath structures. Evaluate fix rate, recovery time, and outage duration alongside position error. PDOP describes geometry, but a reasonable value cannot rule out non-line-of-sight reception, interference, or incorrect ambiguity fixing.

2. Multipath and NLOS affect observations differently

Multipath occurs when reflected copies arrive alongside the direct signal. In non-line-of-sight (NLOS) conditions, the direct path is blocked and the receiver tracks reflected or diffracted signals. Multipath bias depends on relative amplitude, delay, and phase; it is not simply a uniformly positive range error.

Figure 1. Multipath combines direct and reflected signals. In the illustrated NLOS case, the direct path is blocked and only a reflected signal arrives. Not to scale.

Cranes, container walls, vessels, and water can produce strong reflections. Pit walls and large machinery create persistent obstructions. These conditions change as vehicles and equipment move, making a static open-sky test an incomplete assessment.

RTK differencing reduces common errors but cannot fully remove reflections local to the rover. Pseudorange and carrier phase respond differently to multipath. Contaminated measurements can also cause incorrect fixing. A fixed status means the receiver has accepted an integer ambiguity solution; the resulting position still needs quality checks.

3. Separate radio interference from correction outages

Radios, radar, motor drives, and nearby transmitters can degrade GNSS reception through harmonics, intermodulation, or front-end overload. Falling carrier-to-noise density, C/N0, and tracking losses may indicate interference, although neither symptom identifies the cause by itself.

Correction delivery is a separate failure path. Pit walls and container stacks can interrupt cellular or radio coverage while satellite tracking remains healthy. Correction age then increases and the RTK solution may degrade. Log signal quality, tracking status, packet loss, correction age, and solution status together so the sequence can be reconstructed.

4. Improve reception and installation

Multiple constellations improve the chance of retaining useful geometry under partial obstruction. Multiple frequencies support ionospheric modelling and ambiguity resolution. Unaffected bands may remain usable during narrowband interference, depending on receiver design. These capabilities do not remove local reflections or restore a missing correction link.

Place antennas above nearby structures where practical. Follow the antenna manufacturer's requirements for the ground plane or mounting surface, secure the installation, and separate it from transmitters, motors, and unshielded wiring. Inspect connectors and cables for vibration damage and wear.

The base station also needs clear sky, a stable monument, and verified coordinates. Moving it closer does not cancel rover-local multipath. Test correction coverage at pit bottoms, turns, and container corridors.

5. Use fusion with explicit quality checks

GNSS/INS can maintain output through brief obstructions, with wheel odometry, vision, or lidar supplying additional constraints. Continuous output does not mean constant accuracy: errors may grow during an outage. Test the allowable duration for the actual sensors, calibration, and operating conditions. Wheel slip, fog, and dirty optics can weaken supporting measurements.

Figure 2. Observation quality, correction delivery, and sensor consistency inform the operating mode. A GNSS-aided fused trajectory is not an independent reference.

Check estimated uncertainty, residuals, C/N0 changes, correction age, and sustained fix duration. Compare motion against wheel speed, map boundaries, and fused predictions. A trajectory already fused with GNSS is correlated with GNSS and should not be treated as an independent accuracy reference.

After recovery, retain speed restrictions until quality and consistency stabilize. If confidence falls below the operating requirement, use remaining valid sensors within a restricted area or stop safely. A controlled exit is appropriate only when the remaining navigation capability supports it.

6. Define the field test before collecting statistics

Test beneath cranes, between containers, near pit walls, and through communication blind spots. Repeat each route and record antenna placement, receiver and INS configuration, speed, time, and site layout. Changing vehicle orientation or operating time helps expose changing reflections and interference.

For a repeatable test beneath a crane, align three traces on one time axis: cross-track error against an independent reference, Fixed/Float status, and correction age. Rising error with normal correction age points investigation toward observations and processing. If correction age rises first, inspect communications. These are diagnostic clues requiring confirmation.

Define fix rate as fixed epochs divided by valid GNSS output epochs during the specified operating period; report stationary periods and missing output separately. Specify whether recovery time starts at obstruction exit, observation recovery, or correction recovery. Use the same definition across comparisons.

Report positioning availability separately as the fraction of mission time meeting the project's error and continuity requirements. Identify periods without adequate reference coverage rather than assuming compliance. Fix rate measures solution status; availability measures how often positioning meets the job's needs.

An apparent jump alone does not prove incorrect fixing. Use an independent reference or other reliable evidence. Report outage duration, maximum error, and time above the permitted error, because a small average can hide a dangerous excursion. Preserve logs and check reference quality and communications before deciding whether reinitialization is necessary.

Observed symptom Investigate first Useful records
Tracking losses Obstruction or RF interference C/N0 and tracking by band
Position bias with many satellites Multipath or NLOS Residuals and reference error
Increasing correction age Correction delivery Latency and packet loss
Jumps while Fixed Fixing, state changes, reference Raw logs and reference quality

Table 1. Symptoms guide investigation; they do not establish a diagnosis.

Conclusion

Define acceptable error, continuity, and degraded operation for each route segment. Then evaluate synchronized field logs against those requirements. Multiple constellations, RTK, and sensor fusion help, but useful operating time depends on installation, observation quality, correction delivery, and the vehicle's response when confidence declines.

📘 Recommended Reading

GNSS Integrity and RAIM: A Practical Introduction

Learn the difference between GNSS accuracy and integrity, how RAIM detects or excludes faulty measurements, and why positioning systems need to identify when their solutions can no longer be trusted.

Continue the Conversation

Have questions about this topic or want to share your experience? Join the Qtalis Community to discuss GNSS technologies, exchange ideas, and connect with other users and developers.

Join the Discussion
Back to blog