Question 1

What is included in Orbits?

Accepted Answer

Orbits covers the full pipeline from raw tracking data to a trusted orbit: measurement ingestion, state vector import and export, orbit determination, ephemeris generation, visualization, and an automatic public-TLE fallback when fresh tracking data isn't available. One connected system instead of separate point tools for tracking, estimation, and reporting.

Question 2

Batch least squares vs sequential: which does Valar use?

Accepted Answer

Batch least squares fits a single best orbit solution to a fixed window of past measurements, reprocessed as a whole each time. Sequential estimation instead updates the orbit state incrementally as each new measurement arrives. Valar's orbit determination is built around continuous, sequential processing, the same reason each orbit solution carries an age and convergence status rather than a one-off report.

Question 3

How do I know how much to trust a given orbit solution?

Accepted Answer

Every orbit solution carries three concrete quality signals: its age (time since the underlying state vector), a convergence status, and covariance data describing its uncertainty. Orbit age also drives the degraded/stale grading shown in the orbit-data-age footer, so reduced-accuracy solutions are always clearly labeled rather than presented as equivalent to a fresh, converged one.

Question 4

What measurement types and file formats does Valar's orbit determination ingest?

Accepted Answer

Five measurement types: AZEL (azimuth-elevation), RADEC (right ascension-declination), range, PVT (position-velocity-time), and Doppler (range-rate). These arrive via three file formats: TDM (Tracking Data Message), SP3 (Standard Product 3), and OEM (Orbit Ephemeris Message).

Question 5

Can I import an existing state vector directly?

Accepted Answer

Yes. Valar imports state vectors in OPM or SpaceX OPM format and automatically identifies the right spacecraft, so operators don't have to manually match records.

Question 6

What does Valar generate from an orbit solution?

Accepted Answer

Each orbit solution can export as a CCSDS OPM or OMM (mean Keplerian elements via DSST conversion), or as an OEM ephemeris spanning up to 30 days. Valar also generates TLEs and automatically pushes ephemerides to Space-Track and EU-SST.

Question 7

Can I visualize orbit solutions, not just export them?

Accepted Answer

Yes. Valar renders 3D ground tracks, Keplerian element plots over time, and side-by-side state vector comparisons against a reference orbit.

Question 8

What happens if there's no recent state vector for a spacecraft?

Accepted Answer

Valar automatically falls back to a public TLE, retrieved natively via the spacecraft's NORAD ID, no manual upload required, and flags the spacecraft Degraded in the orbit-data-age footer until a fresh state vector arrives. The same fallback applies once an orbit ages past its degraded-level threshold.

Question 9

Do I need a dedicated flight dynamics engineer to use it?

Accepted Answer

No. Valar's orbit determination is designed to run operator-less: it ingests tracking data and maintains orbit solutions automatically, so operations teams don't need an in-house flight dynamics specialist running the numbers by hand.

From tracking data to a trusted orbit solution

What's inside Orbits

Batch least squares vs sequential estimation

Frequently asked questions

Ready to Transform Your Operations?

Product

Resources

Legal