Orbit products

Besides a run’s own products (its ephemeris, uncertainty table, residuals and result), the service makes the orbit in other forms.

A run as a report

run.report("reports/")  # one HTML page with its charts inside: to read, mail or print to PDF

Other ephemerides, and a state as an OPM

A run’s ephemeris is in the inertial frame (GCRF), a state a minute, with a covariance every five minutes. Whoever cannot take that asks for it written again, or for one state of it as a CCSDS Orbit Parameter Message for a hand-over:

fixed = run.orbit_file(
    frame="ITRF", step_s=30, covariance=False, start="2026-10-02T00:00:00Z"
).wait()
fixed.download("orbits/")  # under the name the service gives it

state = run.orbit_file("opm", epoch="2026-10-02T06:00:00Z").wait()
print(state.elements, state.covariances, state.manoeuvres)
state.download("state.opm")
  • An ephemeris ("oem", the default): frame (GCRF or ITRF), step_s (1 to 3600; none: the run’s own time tags), start and end (none: the whole ephemeris) and covariance (False: states only). A run’s ephemeris holds its fitted arc and its prediction. States between the run’s time tags are interpolated, to well under a millimetre; covariances are the run’s own, never interpolated.

  • An OPM ("opm"): the state at epoch (none: the end of the run’s arc) with the osculating Keplerian elements, the spacecraft’s mass, areas and coefficients as the run had them, the covariance in RTN where the ephemeris has one at the epoch, and the run’s manoeuvres after the epoch as the OPM’s manoeuvre parameters.

The reconstructed orbit

What the accepted runs determined, put together: for an archive, for processing the payload’s data, for a lifetime estimate.

orbit = client.orbits.reconstructed(
    satellite, "2026-10-01T00:00:00Z", "2026-10-08T00:00:00Z"
).wait()
print([(piece.run_id, piece.start, piece.end) for piece in orbit.pieces], orbit.gaps)
orbit.download("orbits/")

A CCSDS OEM with a segment or more for each run: the fitted arcs only, never a prediction. Two arcs that overlap meet in the middle of what they share; a stretch no arc covers stays a gap. Where two pieces meet the orbit steps by the runs’ difference there (decimetres to metres, within their uncertainty): nothing is smoothed, so do not interpolate across two segments.

The drag coefficient over time

history = client.orbits.drag_coefficients(satellite, start="2026-10-01T00:00:00Z")
for row in history:
    print(row.arc_start, row.arc_end, row.drag_coefficient, row.sigma)
client.orbits.drag_coefficients_file(satellite, "drag.csv")  # as a table

The coefficient takes up what the atmosphere model misses, so it follows the space weather. With pandas, lunaspace.frames.drag_coefficients(history) is a data frame (Diagnostics and trends).

TLE and OMM

Tools that take only a two-line element set get one fitted to the satellite’s own orbit: SGP4’s mean elements fitted to two days of the orbit’s prediction, as a TLE and as a CCSDS OMM, with how far it strays from the orbit.

client.assets.update(
    satellite, norad_id=39452, international_designator="2013-067B", tle_enabled=True
)  # a TLE with every new orbit
tle = client.tle.request(satellite).wait()  # or one now; client.tle.get(satellite): the latest
print("\n".join(tle.lines), tle.fit.rms_m)
tle.download("tle", "elements.tle")

fit says how well it holds the orbit over the two days (rms_m, largest_m, at_end_m): for a low orbit some hundreds of metres, mostly along the track, which is SGP4’s own limit. Where a tool takes the ephemeris, use that. Without a NORAD number the TLE carries 99999 and blank designators.