ntrip-rtklib-knowledge-patch

# NTRIP / RTKLIB Knowledge Patch Baseline: NTRIP through 2.0 and RTKLIB through 2.4.2. Coverage extends through BNC 2.13, RINEX 3.04, RTKLIB 2.4.2 patch releases and 2.4.3 b34, and current Demo5 behavior documented by this patch. ## Use this patch 1. Identify the exact NTRIP revision, RTKLIB branch, patch level, application, receiver format, and transport before choosing syntax or defaults. 2. Read the reference file matching the task; branch-specific behavior in upstream RTKLIB, Demo5, and BNC is not interchangeable. 3. Preserve byte streams unless conversion is intentional. RTKLIB's converter decodes and re-encodes selected messages rather than mixing generated messages with untouched input. 4. Validate outputs semantically: inspect RTCM message inventory, RINEX epoch and navigation counts, reference-station coordinates, solution status, and trace warnings. 5. Treat configuration samples as starting points. Confirm option spelling and availability against the actual binary or source tree. ## Reference index | Reference | Topics | |---|---| | [ntrip-casters-and-vrs.md](references/ntrip-casters-and-vrs.md) | Rev1/Rev2 interoperability, sourcetables, GGA/VRS behavior, BKG caster deployment, TLS, ACLs, authorization, RTK2go, Centipede, Emlid | | [bnc-client.md](references/bnc-client.md) | BNC runtime and configuration, transports, TLS, RINEX, record/replay, engine feeds, PPP, correction combination, RTNET, SSR uploads | | [rinex-and-conversion.md](references/rinex-and-conv...