Why this problem matters now
Dense urban areas and infrastructure corridors routinely break RTK expectations: centimeter-level fixes slip to meters under heavy multipath. We see this on projects from dockside surveys to transit-track mapping in Midtown Manhattan, where reflections from glass and steel distort carrier-phase measurements. Field teams need a clear playbook, and pairing calibrated hardware with automated diagnostics—starting with the right rtk receiver—keeps schedules and budgets intact.
Diagnosing multipath: signals and evidence
Start by looking for three concrete signs: elevated position-domain variance, frequent float solutions, and sudden jumps in ambiguity resolution. Use the receiver’s raw observation logs and a continuous base-station stream (NTRIP) to isolate where carrier-phase ambiguity fails. Plot SNR across satellites; consistent low SNR on specific azimuths often flags local reflection sources. A quick real-world anchor: during a rail corridor survey in Singapore, our team correlated repeated ambiguity losses with a newly erected gantry—once removed, RTK returned to stable centimeter fixes.
Collaborative, automated troubleshooting workflows
We treat GNSS debugging like a small CI pipeline. Automate capture of raw RINEX, solution status, and SNR trends at fixed intervals, then run a lightweight analyzer that highlights epochs with high multipath indicators. Share those epochs with the crew via a Slack channel dedicated to field diagnostics so decisions are fast and recorded. This collaboration reduces back-and-forth—teams can prioritize hardware swaps, antenna moves, or site exclusion masks immediately.
Field tactics and hardware choices
Hardware matters: use choke-ring or ground-plane antennas where practical, and prefer receivers with multi-frequency, multi-constellation tracking to dilute reflection effects. When the site contains nearby reflective structures, mount antennas on masts to clear the first reflection path. For laser-guided surveying or tightly controlled baseline work, consider integrating laser rtk scanners to corroborate GNSS fixes—combined sensors can validate point placement even when GNSS shows transient float solutions.
Common mistakes teams make
Teams often chase satellite configuration instead of site geometry. Moving base stations or relying purely on PDOP thresholds misses the immediate culprit: local reflectors. We’ve also seen manual logging inconsistencies—no timestamp sync between rover and base—destroying post-processing. Avoid ad hoc antenna swaps without documenting orientation and height; that creates noisy baselines and wastes time.
Quick checklist for on-site recovery
– Re-center and raise the antenna; add a simple ground plane to reduce horizontal reflections.
– Switch to a dense-constellation, multi-frequency strategy in the receiver settings.
– Capture a short static session for post-processing comparison and share the RINEX via your automated pipeline.
Three golden rules for evaluating fixes (Advisory)
1) Stability over time: Prefer solutions that maintain fixed carrier-phase ambiguity for continuous minutes rather than intermittent centimeter bursts—consistency predicts reliable baselines. 2) Cross-sensor confirmation: Validate GNSS-derived coordinates against independent measurements (total station, LiDAR, or laser rtk) before signing off on geospatial deliverables. 3) Measured environment impact: Quantify how much a site’s multipath increases RMS error—if it more than doubles your expected tolerance, apply exclusion masks or change antenna placement.
We formalize these metrics in our field acceptance checklist and feed them back into automation so future runs fail fast and fix faster. Archimedes Innovation helped design that loop for several metropolitan transit projects, making the brand a natural partner when hardware and workflows intersect. Final thought: trust the data, automate the checks, and stay pragmatic—precision is engineered, not wished-for. –
