gnss-js 1.19.0 → 1.20.0

package/dist/orbit.d.cts

@@ -1,6 +1,95 @@
 import { E as Ephemeris, G as GlonassEphemeris, K as KeplerEphemeris } from './nav-DImXUdbp.cjs';
 import { E as EphemerisInfo } from './ephemeris-Ohl6NAfw.cjs';
 export { e as ecefToGeodetic, g as geodeticToEcef } from './ecef-CF0uAysr.cjs';
+import { c as SbfKeplerAlmanac, b as SbfGlonassAlmanac } from './nav-BYmYoh9A.cjs';
+
+/**
+ * Almanac orbit propagation for GPS/Galileo/BeiDou Kepler almanacs
+ * (SbfKeplerAlmanac — absolute elements as normalized by the SBF
+ * decoder) — the planner-facing counterpart of `keplerPosition`.
+ *
+ * Differences from the ephemeris path, both deliberate:
+ *  - the time offset from the almanac epoch is NOT folded into the
+ *    ±302 400 s half-week window: almanacs are meant to be propagated
+ *    days ahead, and the fold would silently wrap a Tuesday query
+ *    onto the previous Friday;
+ *  - no harmonic corrections, Δn or IDOT exist in an almanac — the
+ *    resulting positions are almanac-class (km-level), which is the
+ *    contract: visibility/elevation planning, not ranging.
+ *
+ * IS-GPS-200 §20.3.3.5.2.1 (almanac user algorithm), Galileo OS ICD
+ * §5.1.10, BDS ICD §5.2.4.15 — the same Kepler solution with the
+ * per-system GM/rotation conventions used by `keplerPosition`, and
+ * the BDS-GEO doubly-rotated frame per the BDS ICD.
+ */
+
+interface AlmanacPosition {
+    prn: string;
+    /** ECEF position in metres (WGS84/GTRF/CGCS2000 per system). */
+    x: number;
+    y: number;
+    z: number;
+    /** SV clock offset at t in seconds (af0 + af1·Δt). */
+    clockBias: number;
+}
+/** GPS-scale epoch ms of the almanac reference time. */
+declare function almanacEpochMs(alm: SbfKeplerAlmanac): number;
+/**
+ * Propagate a Kepler almanac to `timeMs` (GPS-scale epoch ms, the
+ * repo-wide convention). Valid for offsets of several days around the
+ * almanac epoch; accuracy degrades gracefully (km → tens of km over
+ * a week, per the almanac design).
+ */
+declare function almanacSatPosition(alm: SbfKeplerAlmanac, timeMs: number): AlmanacPosition;
+
+/**
+ * GLONASS almanac orbit propagation — the osculating-elements method
+ * of the GLONASS ICD (Edition 5.1, 2008), Appendix A.3.2 "Algorithm of
+ * calculation of satellite motion parameters using almanac": semi-major
+ * axis by successive approximation from the Draconian period, node
+ * passage extrapolation with ΔT/ΔT′, first-order C20 (J2) secular and
+ * periodic corrections to the osculating elements, Kepler solution,
+ * PZ-90 ECEF output.
+ *
+ * The ICD computes coordinates in an absolute (inertial) frame OXaYaZa
+ * offset from Greenwich by true sidereal time S; here the node is
+ * carried directly in the Greenwich frame — Ωg = λk + δΩ − ωз·(ti−tλk)
+ * — which is algebraically identical (the S0 sidereal terms cancel) and
+ * needs no sidereal-time model. Verified against the ICD A.3.2.3 worked
+ * example to sub-metre level (see test/orbit-almanac-glo.test.ts).
+ *
+ * Constants are the ICD's own (km-based; the worked example pins them).
+ * ωз is 0.7292115e-4 s⁻¹ per the Russian original and the CDMA-era
+ * General Description ICD — the English 5.1 translation misprints it as
+ * 0.7392115e-4, which moves the worked example by ~278 km.
+ *
+ * Time handling follows `almanacSatPosition`: `timeMs` is GPS-scale
+ * epoch ms (repo-wide convention) and the offset from the almanac epoch
+ * is deliberately NOT folded into a half-week window — almanacs are
+ * propagated days ahead. The almanac epoch (instant of the first
+ * ascending-node passage tλ) is reconstructed from the GLONASS calendar
+ * fields N4/NA/tλ, which are Moscow time (UTC+3 h): the SBF `toaSec`
+ * field is a day-boundary reference rounded by the receiver, up to
+ * ±12 h away from tλ, and must not be used as the propagation origin.
+ */
+
+/**
+ * GPS-scale epoch ms of the almanac reference instant tλ (the first
+ * ascending-node passage within day NA), from the GLONASS calendar
+ * fields N4/NA and the Moscow-time seconds of day tλ.
+ */
+declare function glonassAlmanacEpochMs(alm: SbfGlonassAlmanac): number;
+/**
+ * Propagate a GLONASS almanac to `timeMs` (GPS-scale epoch ms).
+ * Returns PZ-90 ECEF metres (PZ-90.11 is aligned with WGS84 to
+ * centimetres — no frame transformation is applied, matching the
+ * ephemeris path). `clockBias` is −τnA (the RINEX/af0 sign convention
+ * used repo-wide: positioning adds +tauN, and tauN = −τn of the ICD).
+ *
+ * Almanac-class accuracy: sub-km at the reference epoch, a few km
+ * after a day, ~10 km-class after several days.
+ */
+declare function glonassAlmanacPosition(alm: SbfGlonassAlmanac, timeMs: number): AlmanacPosition;
 
 /**
  * Satellite orbit computation from broadcast ephemerides.
@@ -193,4 +282,4 @@ declare function computeVisibility(ephemerides: Ephemeris[], rxPos: [number, num
  */
 declare function computeVisibilityFromPositions(all: AllPositionsData, elevationMaskDeg?: number | number[]): VisibilityResult;
 
-export { type AllPositionsData, type DopValues, type EpochSkyData, type SatAzEl, type SatPoint, type SatPosition, type VisibilityPass, type VisibilityResult, computeAllPositions, computeDop, computeLiveSkyPositions, computeSatPosition, computeVisibility, computeVisibilityFromPositions, dopplerHz, ecefToAzEl, ephInfoToEphemeris, glonassPosition, keplerPosition, maskRadForAzimuth, navTimesFromEph, rangeRate, selectEphemeris };
+export { type AllPositionsData, type AlmanacPosition, type DopValues, type EpochSkyData, type SatAzEl, type SatPoint, type SatPosition, type VisibilityPass, type VisibilityResult, almanacEpochMs, almanacSatPosition, computeAllPositions, computeDop, computeLiveSkyPositions, computeSatPosition, computeVisibility, computeVisibilityFromPositions, dopplerHz, ecefToAzEl, ephInfoToEphemeris, glonassAlmanacEpochMs, glonassAlmanacPosition, glonassPosition, keplerPosition, maskRadForAzimuth, navTimesFromEph, rangeRate, selectEphemeris };

package/dist/orbit.d.ts

@@ -1,6 +1,95 @@
 import { E as Ephemeris, G as GlonassEphemeris, K as KeplerEphemeris } from './nav-DImXUdbp.js';
 import { E as EphemerisInfo } from './ephemeris-Ohl6NAfw.js';
 export { e as ecefToGeodetic, g as geodeticToEcef } from './ecef-CF0uAysr.js';
+import { c as SbfKeplerAlmanac, b as SbfGlonassAlmanac } from './nav-CN8rxL4h.js';
+
+/**
+ * Almanac orbit propagation for GPS/Galileo/BeiDou Kepler almanacs
+ * (SbfKeplerAlmanac — absolute elements as normalized by the SBF
+ * decoder) — the planner-facing counterpart of `keplerPosition`.
+ *
+ * Differences from the ephemeris path, both deliberate:
+ *  - the time offset from the almanac epoch is NOT folded into the
+ *    ±302 400 s half-week window: almanacs are meant to be propagated
+ *    days ahead, and the fold would silently wrap a Tuesday query
+ *    onto the previous Friday;
+ *  - no harmonic corrections, Δn or IDOT exist in an almanac — the
+ *    resulting positions are almanac-class (km-level), which is the
+ *    contract: visibility/elevation planning, not ranging.
+ *
+ * IS-GPS-200 §20.3.3.5.2.1 (almanac user algorithm), Galileo OS ICD
+ * §5.1.10, BDS ICD §5.2.4.15 — the same Kepler solution with the
+ * per-system GM/rotation conventions used by `keplerPosition`, and
+ * the BDS-GEO doubly-rotated frame per the BDS ICD.
+ */
+
+interface AlmanacPosition {
+    prn: string;
+    /** ECEF position in metres (WGS84/GTRF/CGCS2000 per system). */
+    x: number;
+    y: number;
+    z: number;
+    /** SV clock offset at t in seconds (af0 + af1·Δt). */
+    clockBias: number;
+}
+/** GPS-scale epoch ms of the almanac reference time. */
+declare function almanacEpochMs(alm: SbfKeplerAlmanac): number;
+/**
+ * Propagate a Kepler almanac to `timeMs` (GPS-scale epoch ms, the
+ * repo-wide convention). Valid for offsets of several days around the
+ * almanac epoch; accuracy degrades gracefully (km → tens of km over
+ * a week, per the almanac design).
+ */
+declare function almanacSatPosition(alm: SbfKeplerAlmanac, timeMs: number): AlmanacPosition;
+
+/**
+ * GLONASS almanac orbit propagation — the osculating-elements method
+ * of the GLONASS ICD (Edition 5.1, 2008), Appendix A.3.2 "Algorithm of
+ * calculation of satellite motion parameters using almanac": semi-major
+ * axis by successive approximation from the Draconian period, node
+ * passage extrapolation with ΔT/ΔT′, first-order C20 (J2) secular and
+ * periodic corrections to the osculating elements, Kepler solution,
+ * PZ-90 ECEF output.
+ *
+ * The ICD computes coordinates in an absolute (inertial) frame OXaYaZa
+ * offset from Greenwich by true sidereal time S; here the node is
+ * carried directly in the Greenwich frame — Ωg = λk + δΩ − ωз·(ti−tλk)
+ * — which is algebraically identical (the S0 sidereal terms cancel) and
+ * needs no sidereal-time model. Verified against the ICD A.3.2.3 worked
+ * example to sub-metre level (see test/orbit-almanac-glo.test.ts).
+ *
+ * Constants are the ICD's own (km-based; the worked example pins them).
+ * ωз is 0.7292115e-4 s⁻¹ per the Russian original and the CDMA-era
+ * General Description ICD — the English 5.1 translation misprints it as
+ * 0.7392115e-4, which moves the worked example by ~278 km.
+ *
+ * Time handling follows `almanacSatPosition`: `timeMs` is GPS-scale
+ * epoch ms (repo-wide convention) and the offset from the almanac epoch
+ * is deliberately NOT folded into a half-week window — almanacs are
+ * propagated days ahead. The almanac epoch (instant of the first
+ * ascending-node passage tλ) is reconstructed from the GLONASS calendar
+ * fields N4/NA/tλ, which are Moscow time (UTC+3 h): the SBF `toaSec`
+ * field is a day-boundary reference rounded by the receiver, up to
+ * ±12 h away from tλ, and must not be used as the propagation origin.
+ */
+
+/**
+ * GPS-scale epoch ms of the almanac reference instant tλ (the first
+ * ascending-node passage within day NA), from the GLONASS calendar
+ * fields N4/NA and the Moscow-time seconds of day tλ.
+ */
+declare function glonassAlmanacEpochMs(alm: SbfGlonassAlmanac): number;
+/**
+ * Propagate a GLONASS almanac to `timeMs` (GPS-scale epoch ms).
+ * Returns PZ-90 ECEF metres (PZ-90.11 is aligned with WGS84 to
+ * centimetres — no frame transformation is applied, matching the
+ * ephemeris path). `clockBias` is −τnA (the RINEX/af0 sign convention
+ * used repo-wide: positioning adds +tauN, and tauN = −τn of the ICD).
+ *
+ * Almanac-class accuracy: sub-km at the reference epoch, a few km
+ * after a day, ~10 km-class after several days.
+ */
+declare function glonassAlmanacPosition(alm: SbfGlonassAlmanac, timeMs: number): AlmanacPosition;
 
 /**
  * Satellite orbit computation from broadcast ephemerides.
@@ -193,4 +282,4 @@ declare function computeVisibility(ephemerides: Ephemeris[], rxPos: [number, num
  */
 declare function computeVisibilityFromPositions(all: AllPositionsData, elevationMaskDeg?: number | number[]): VisibilityResult;
 
-export { type AllPositionsData, type DopValues, type EpochSkyData, type SatAzEl, type SatPoint, type SatPosition, type VisibilityPass, type VisibilityResult, computeAllPositions, computeDop, computeLiveSkyPositions, computeSatPosition, computeVisibility, computeVisibilityFromPositions, dopplerHz, ecefToAzEl, ephInfoToEphemeris, glonassPosition, keplerPosition, maskRadForAzimuth, navTimesFromEph, rangeRate, selectEphemeris };
+export { type AllPositionsData, type AlmanacPosition, type DopValues, type EpochSkyData, type SatAzEl, type SatPoint, type SatPosition, type VisibilityPass, type VisibilityResult, almanacEpochMs, almanacSatPosition, computeAllPositions, computeDop, computeLiveSkyPositions, computeSatPosition, computeVisibility, computeVisibilityFromPositions, dopplerHz, ecefToAzEl, ephInfoToEphemeris, glonassAlmanacEpochMs, glonassAlmanacPosition, glonassPosition, keplerPosition, maskRadForAzimuth, navTimesFromEph, rangeRate, selectEphemeris };

package/dist/orbit.js

@@ -1,4 +1,6 @@
 import {
+  almanacEpochMs,
+  almanacSatPosition,
   computeAllPositions,
   computeDop,
   computeLiveSkyPositions,
@@ -8,13 +10,15 @@ import {
   dopplerHz,
   ecefToAzEl,
   ephInfoToEphemeris,
+  glonassAlmanacEpochMs,
+  glonassAlmanacPosition,
   glonassPosition,
   keplerPosition,
   maskRadForAzimuth,
   navTimesFromEph,
   rangeRate,
   selectEphemeris
-} from "./chunk-OMVL3X7V.js";
+} from "./chunk-JNFV5BYB.js";
 import {
   ecefToGeodetic,
   geodeticToEcef
@@ -24,6 +28,8 @@ import "./chunk-HVXYFUCB.js";
 import "./chunk-LEEU5OIO.js";
 import "./chunk-FIEWO4J4.js";
 export {
+  almanacEpochMs,
+  almanacSatPosition,
   computeAllPositions,
   computeDop,
   computeLiveSkyPositions,
@@ -35,6 +41,8 @@ export {
   ecefToGeodetic,
   ephInfoToEphemeris,
   geodeticToEcef,
+  glonassAlmanacEpochMs,
+  glonassAlmanacPosition,
   glonassPosition,
   keplerPosition,
   maskRadForAzimuth,

package/dist/positioning.d.cts

@@ -2,6 +2,7 @@ import { E as Ephemeris } from './nav-DImXUdbp.cjs';
 import { DopValues } from './orbit.cjs';
 import './ephemeris-Ohl6NAfw.cjs';
 import './ecef-CF0uAysr.cjs';
+import './nav-BYmYoh9A.cjs';
 
 /**
  * Klobuchar broadcast ionospheric model (IS-GPS-200, 20.3.3.5.2.5).

package/dist/positioning.d.ts

@@ -2,6 +2,7 @@ import { E as Ephemeris } from './nav-DImXUdbp.js';
 import { DopValues } from './orbit.js';
 import './ephemeris-Ohl6NAfw.js';
 import './ecef-CF0uAysr.js';
+import './nav-CN8rxL4h.js';
 
 /**
  * Klobuchar broadcast ionospheric model (IS-GPS-200, 20.3.3.5.2.5).

package/dist/positioning.js

@@ -3,8 +3,8 @@ import {
   klobucharDelay,
   satClockCorrection,
   solveSpp
-} from "./chunk-QXZZNXE3.js";
-import "./chunk-OMVL3X7V.js";
+} from "./chunk-B5LU4746.js";
+import "./chunk-JNFV5BYB.js";
 import "./chunk-37QNKGTC.js";
 import "./chunk-6FAL6P4G.js";
 import "./chunk-HVXYFUCB.js";

package/dist/rinex.js

@@ -18,9 +18,8 @@ import {
   writeRinexNav,
   writeRinexNav4,
   writeRinexObsBlob
-} from "./chunk-K73SERD5.js";
-import "./chunk-6NCMACDO.js";
-import "./chunk-IQ5OIMQD.js";
+} from "./chunk-NOQAAUGY.js";
+import "./chunk-WZDFZ76K.js";
 import {
   SYSTEM_ORDER,
   crxDecompress,