gnss-navigation-knowledge-patch

What problem does it solve?

GNSS protocols, correction services, and receiver configurations have evolved since many model training cutoffs, which can cause developers to produce code that uses deprecated messages, wrong assumptions about corrections, or misconfigured receivers. This knowledge patch consolidates verified, post-cutoff implementation details so engineers and integrators can write correct, modern GNSS positioning and correction ingestion code.

Core Features & Use Cases

• Updated Protocol References: Clear summaries of RTCM 3.x message types, MSM4/MSM7 tradeoffs, and RTCM usage for RTK.
• PPP & SPARTN Guidance: SPARTN v2.0.3 details, encryption/key workflows, and practical PPP vs RTK decision guidance including Galileo HAS.
• Receiver Configuration: u-blox F9P UBX CFG keys, NAV/RXM message outputs, SPARTN key injection, and RTK activation behavior.
• IGS & Products: How to use SP3/Clock/ANTEX products in PPP workflows and expected accuracies/latencies.
• Platform APIs: Android GnssMeasurement and GnssAntennaInfo practical notes for collecting raw observables and handling carrier phase/ADR.
• Use Case Example: Configure a rover/base RTK loop with an F9P, stream RTCM via NTRIP, and validate fixes with IGS products in post-processing.

Quick Start

Load the gnss-navigation-knowledge-patch and ask for the RTCM messages, u-blox CFG keys, and Android raw GNSS fields required to enable RTK and PPP on a dual-frequency receiver.