Skip to main content

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​

InputWhere it comes from
The satellite's orbitIts 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 positionIts ground station's latitude, longitude and altitude
The elevation maskThe antenna's min_elevation_deg; 0 degrees when it has none, which the config flags as no_mask
The linkA 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:

CodeMeaning
norad_not_in_catalogThe public catalog has no orbit for the satellite's NORAD ID. Give it a tle
band_mismatchNo radio on the satellite pairs with a frequency range on the antenna
orbit_propagation_failedThe orbit cannot be propagated to the window, such as a catalog element set too old for it
below_min_elevationThe 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.