Skip to content

Reference Analyses

This section tracks the upstream OSS implementations used as primary design references for the next round of libgnss++ improvements.

The rule is simple:

  • study the upstream projects directly,
  • translate the useful ideas into native libgnss++ modules, tests, and sign-off gates,
  • avoid adopting large external stacks wholesale.

Current reference set

Upstream Main value for libgnss++ Current status
MADOCALIB PPP, PPP-AR, L6E/L6D correction handling Gap analysis published
CLASLIB Compact SSR, CLAS grid/atmosphere, PPP-RTK ideas Gap analysis published
MALIB replay, config, regression, MADOCA-PPP ops patterns Ops gap published
rtklibexplorer/RTKLIB RTK tuning for low-cost and mixed-quality receivers Gap analysis published
commaai/laika precise product fetch/cache and product tooling ideas Gap analysis published
tomojitakasu/PocketSDR SDR frontend, IF capture/replay, PocketSDR convbin, L6D/L6E ingest ideas Future note published
globsky/SignalSim synthetic scenario, observation, and IF generation for validation Future note published

Execution order

  1. MADOCALIB gap analysis
  2. CLASLIB gap analysis
  3. demo5 / rtklibexplorer RTK tuning delta review
  4. MALIB replay/config/testing review
  5. laika product-fetch/cache review
  6. PocketSDR replay/import interoperability review
  7. SignalSim synthetic-validation interoperability review

Why this ordering

  • RTK quality and runtime are already much stronger than they were earlier in this project.
  • The next large payoff is PPP / PPP-AR.
  • After that, CLAS/MADOCA accuracy and correction coverage become the next meaningful step.
  • Operations and product tooling should follow once solver-side gaps are clearer.

Available analyses

What "done" means here

For this section, "done" means:

  • each upstream has a published note or gap analysis,
  • the note points to concrete PR families rather than vague inspiration,
  • the adoption roadmap stays in terms of native libgnss++ modules, tests, and sign-off gates.