astrodynamics-gnss 0.9.1

GNSS domain layer (SP3, broadcast ephemeris, multi-GNSS single-point positioning, ionosphere/troposphere, DOP) built on the astrodynamics core
Documentation
//! # astrodynamics-gnss
//!
//! GNSS domain layer built on top of the [`astrodynamics`] core crate. This is
//! a **sibling crate, not a cargo feature** of `astrodynamics`: a
//! propagation-only consumer must never have to compile the IONEX/SP3 parsers.
//!
//! This crate defines the foundational GNSS types and a public façade organized
//! by user-facing tasks:
//!
//! - [`ephemeris`] — precise SP3 and broadcast ephemeris products,
//! - [`rinex`] — RINEX navigation/observation parsing and CRINEX decoding,
//! - [`positioning`] — single-point positioning and DOP diagnostics,
//! - [`atmosphere`] — ionosphere and troposphere corrections,
//! - [`orbit`] — compact reduced-orbit fitting/evaluation.
//!
//! Implementation modules (`sp3`, `rinex_nav`, `spp`, etc.) are crate-private.
//! This is a clean 0.9 public surface rather than a compatibility shim around
//! the original implementation-shaped module layout.
//!
//! ## Units policy (internal representation)
//!
//! All quantities are stored and computed in **SI base units**, with the frame
//! and datum encoded in the type name (per the spec's frames-in-the-type-system
//! rule), never hidden behind a bare `position_m`:
//!
//! - **Length / position:** meters (`_m`). SP3 positions are ITRF/IGS-frame
//!   ECEF meters; SPP receiver positions are WGS84/ITRF-compatible ECEF meters.
//!   (The core `astrodynamics` state crate works in kilometers; conversions
//!   happen explicitly at the boundary, never implicitly.)
//! - **Time / clock:** seconds (`_s`). Epochs are represented by the core
//!   `astrodynamics` time family (`Instant`/`TimeScale`), always scale-tagged;
//!   there is no bare ambiguous epoch.
//! - **Velocity:** meters per second (`_m_s`).
//! - **Angles:** radians (`_rad`) internally. Degrees appear only at I/O edges
//!   and are named `_deg`.
//! - **Frequency:** hertz (`_hz`).
//!
//! Field and parameter names carry the unit suffix so the unit is visible at
//! every call site. Matrix/vector linear algebra uses `nalgebra`
//! (`DMatrix`/`DVector`) per the spec.

// ---------------------------------------------------------------------------
// Module layout. Additional product modules are added as each lands.
// ---------------------------------------------------------------------------

mod broadcast; // broadcast-ephemeris (GPS LNAV / Galileo I/NAV) orbit + clock
pub mod constants; // shared GNSS physical/time constants
mod crinex; // Hatanaka (CRINEX) observation-file decoder
mod dop; // dilution-of-precision geometry (GDOP/PDOP/HDOP/VDOP/TDOP)
mod glonass; // GLONASS PZ-90.11 state-vector RK4 propagation
mod ionex; // Klobuchar broadcast model + IONEX ionospheric maps
mod reduced_orbit; // compact mean-element orbit approximation (fitted)
mod rinex_nav; // RINEX 3 navigation-message parsing (GPS/Galileo broadcast)
mod rinex_obs; // RINEX 3 observation parsing + single-frequency pseudoranges
mod sp3; // SP3-c / SP3-d parser + arbitrary-epoch interpolation
mod spp; // single-point positioning (least-squares PVT)
mod tropo; // Saastamoinen zenith + Niell (NMF) mapping troposphere

mod error;
pub mod frame;
mod id;
mod parse;

pub mod atmosphere;
pub mod ephemeris;
pub mod geometry;
pub mod orbit;
pub mod positioning;
pub mod prelude;
pub mod rinex;

pub use error::{Error, Result};
pub use frame::{ItrfPositionM, ItrfVelocityMS, Wgs84Geodetic};
pub use id::{GnssSatelliteId, GnssSystem};