Access And Coverage

Access modules turn propagated trajectories and sensor constraints into visibility windows, coverage grids, and operational opportunity products. The live OrbPro sensor coverage Sandcastle attaches a Sensor to a propagated satellite entity and uses the shared module artifact rather than reimplementing coverage in the viewer.

Open Sandcastle View demo source

Live Sandcastle

OrbPro sensor coverage time swaths runs the SDK module at space-data-network-modules/analysis/sensor-coverage/dist/isomorphic/module.wasm through compute_sensor_coverage. The demo samples a propagated OrbPro Sensor source and renders module-returned Orekit-style along-track swath polygons as the primary visual, with grid cells kept as a secondary figure-of-merit overlay.

For verification and live smoke checks, the page exposes window.__sensorCoverageTimeSwathsDebug with the request, Sensor provenance, resolved module URL, swath count, grid cell count, selected figure of merit, coverageIntervals, finite-statistics flag, and raw module output. The module output includes percent_coverage, gap_time, revisit_time, and response_time products.

What it can do

Evaluate ground-station contact, inter-satellite links, swath coverage, revisit time, constraints, and fastest-path routing across space and ground nodes.

Reference modules

space-data-network-modules/analysis/access
space-data-network-modules/analysis/coverage
space-data-network-modules/analysis/fastest-path

Contract shape

Inputs include assets, trajectories, terrain or body models, constraints, and time windows. Outputs include access intervals, coverage cells, path candidates, and explanation metadata.

Authoring checklist

Keep geometric constraints separate from scheduling preferences.
Return intervals with deterministic boundary semantics.
Validate against simple analytic horizon and field-of-view cases.
Make occlusion, atmosphere, and terrain assumptions explicit.