Datasets and schemas
Every tracker, app, and status page is built on a handful of sources. Click one for its schema and an example record.
Fixed-width text
TLE (Two-Line Element set)
The orbital elements every tracker consumes. Fixed-column text, one satellite per two lines (three with a name line).
TLE, 2LE, 3LE, XML, KVN, JSON, JSON-PRETTY, CSV
CelesTrak GP API
Current elements for any satellite or group, in TLE or the newer OMM (Orbit Mean-elements Message) format.
JSON (REST, paginated)
SatNOGS DB API
Community-maintained catalog of satellites and their transmitters: frequencies, modes, status. The de facto open frequency database.
HTML grid
AMSAT OSCAR Status page
Crowd-sourced reports of who heard what, when. The quickest answer to "is it working today?"
Semicolon-separated CSV
JE9PEL satellite frequency list
Mineo Wakita's long-running master list of every amateur satellite and frequency, with status. Consumed by many tracking programs.
TLE, 3LE, JSON, CSV, XML, KVN
Space-Track.org
The primary source of TLEs. CelesTrak and everyone else redistribute from here.
JSON
N2YO REST API
Precomputed pass predictions, positions and TLEs, keyed by NORAD ID. Handy when you do not want to run SGP4 yourself.
JSON (REST)
SatNOGS Network observations
Recordings, waterfalls and decoded data from hundreds of volunteer ground stations. The best way to see what a pass actually sounds and looks like before you try one.
INI (Gpredict .trsp) / CSV (SatPC32 Doppler.sqf)
Tracker config files (Gpredict, SatPC32)
How desktop trackers store transponder definitions so they can tune your radio with Doppler correction.
Join key across all of them: the NORAD catalog number. Names differ everywhere; IDs do not.