Ground networks and ground station services
Constellation computes every pass itself, from each satellite's orbit and each antenna's elevation mask in your network config. It does this the same way for antennas you own and for antennas you book from a ground station service: to the API, both are antennas at a ground station.
How a pass is computed
| Input | Where it comes from |
|---|---|
| The satellite's orbit | Its norad_id, read from the public orbit catalog, or a tle of your own. A run reads the catalog snapshot for the middle of its window, never one taken after the run was made, so a run over a past week uses that week's orbits. A tle is used whatever its age |
| The antenna's position | Its ground station's latitude, longitude and altitude |
| The elevation mask | The antenna's min_elevation_deg; 0 degrees when it has none, which the config flags as no_mask |
| The link | A downlink radio on the satellite paired with a frequency range on the antenna |
A pass runs from when the satellite rises to the antenna's mask until it sets below it, sampled every step_s. List them with GET /topology/passes; each carries a pass_id that a workflow run's item for it carries too, and source: computed.
A pair that never makes a pass is named under declined with why:
| Code | Meaning |
|---|---|
norad_not_in_catalog | The public catalog has no orbit for the satellite's NORAD ID. Give it a tle |
band_mismatch | No radio on the satellite pairs with a frequency range on the antenna |
orbit_propagation_failed | The orbit cannot be propagated to the window, such as a catalog element set too old for it |
below_min_elevation | The satellite never rises above the antenna's mask in the window |
The Fleet tab shows which lanes can price each satellite and ground station, and what each lacks; the API equivalent is readiness on GET /topology/config.
Your own antennas
Add each ground station with its position and each antenna with its mask and RF values, as in Build your fleet from the catalog. The antennas' G/T and the satellites' EIRP set the link budget every pass is priced from.
Antennas you book from a provider
Add the provider's site as a ground station. A pick from the asset catalog, such as {"station_id": "ksat/svalbard"}, fills its position; add the antennas you book there yourself, with their masks and RF values, since the catalog never adds an antenna or an RF value.
From then on its passes are computed and priced like your own. A computed pass is one the geometry allows, whether or not you have booked it. rain-fade-swap takes this into account: its backup is another computed pass, and its deadline is 15 minutes before the pass starts, the cut-off most providers use for cancellations; set the swap step's cancel_lead_s to your provider's.
What the API does not do yet
- Import a provider's schedule or your bookings: passes are computed, never imported.
- Book, cancel or swap a pass with a provider: a swap is a recommendation your operators or your mission control system (MCS) carry out.
- Record which antennas you own and which you book, or what a provider charges.
Related
- Passes: what a pass is and how it is priced
- LEO contact scheduling: planning contacts with
GET /topology/passes - Ground station contention: sharing antennas between satellites