ABOUT

About Orbital Relay

What this project is, where its data comes from, how it works, and its privacy and legal terms.

About

Orbital Relay is a satellite visualization platform: a live 3D globe, a 28,000+ object catalog, conjunction (close-approach) screening, RF link budgets, pass prediction and catalog analytics — built directly on government and public orbital-element data, not a mockup of it.

Eight views, one catalog:

For a field-by-field reference of what each view shows and what its derived data terms mean, see the Wiki.

Data sources

Two upstream sources, both public:

Element sets refresh on a regular ingest cycle — TLE/GP baselines are re-fetched roughly every six hours. The catalog age shown on the home page live-stat strip reflects the most recent ingest.

Data source: Space-Track.org (USSPACECOM / 18th Space Defense Squadron). Redistributed under USSPACECOM express blanket approval for basic SSA data.

This citation is a condition of that redistribution approval, not a courtesy — it accompanies Space-Track-derived data everywhere it appears on this site, including every API response.

How it works

Every object's position is computed, not looked up. Orbital elements (TLEs / GP element sets) are propagated with SGP4 — the same standard orbital-mechanics model used across the tracking community — to derive a satellite's position and velocity at any point in time, including forward and backward along its orbit.

Some fields shown alongside an object are derived rather than reported directly by Space-Track or CelesTrak:

See the Wiki glossary for the full list of derived terms.

⚠ Conjunction and pass-prediction output on this site is unofficial and must never be used for collision avoidance or operational maneuver decisions. It is a derived screening pass over public element sets, not an official conjunction data message (CDM).

Privacy

There are no user accounts anywhere on this site, and no cookies are set for visitors. Nothing you enter into a search box, filter, or form is sent anywhere other than this site's own API to fetch catalog data.

A minimal, anonymous pageview beacon runs on every page to understand traffic. Per pageview, it records:

Automated crawlers and bots are detected and excluded from these counts. This data is used only to understand which views are used and roughly how much traffic the site gets — it is never sold or shared with third parties.