Tracking data

The service determines orbits from the navigation fixes of the satellite’s GNSS receiver. Upload them as they come down; a run uses all the fixes inside its arc.

upload = client.tracking.upload(satellite, "fixes.csv")
print(upload.fix_count, upload.first_epoch, upload.last_epoch)
client.tracking.upload(satellite, data=csv_bytes, filename="pass_1234.csv")  # from memory
client.tracking.list(satellite)  # the uploaded files

The fixes file

A CSV with one fix per line: the epoch with its time scale, and the position in the Earth-fixed frame (ITRF) in kilometres.

# frame: ITRF
# units: km
epoch,x,y,z
2026-10-01T00:00:18 GPS,-2749.380960,4977.646860,3825.584070
2026-10-01T00:00:28 GPS,-2769.338560,5014.925560,3762.195550
  • The time scale is GPS, UTC, TAI or TT. GPS receivers report GPS time, which is 18 seconds ahead of UTC.

  • Epochs must increase. Any cadence works; data denser than one fix per 10 seconds is thinned.

  • Velocities may follow as vx,vy,vz in km/s. They are not used yet.

  • SP3 files are accepted as well. If a file holds several satellites, name the one meant: client.tracking.upload(satellite, "orbits.sp3", satellite="L47").

What the upload says

The answer describes what was read: the number of fixes and the first and last epoch. A file that cannot be used is refused with the line and the reason, as an InvalidRequest, for example line 5: the position is 6.8e+06 km from the Earth's centre (positions are in kilometres, not metres). Uploading the same file twice is harmless; files may overlap.

One file may be up to 64 MB, and an organisation’s tracking data up to 5 GB (Errors, waiting and limits).