Skip to main content

Supported File Formats

The Consultative Committee for Space Data Systems (CCSDS) is a multi-national forum for the development of communications & data systems standards for spaceflight. CCSDS Recommendation Standards (Blue Books) define specific protocols and interfaces, including file format standards for describing Resident Space Objects (RSOs).

View CCSDS Blue Book Publications Website


Conjunction Events

Conjunction Data Messages

Conjunction Data Messages (CDMs) are sent to operators when future close approaches between operator assets and other RSOs are identified. Space-Track.org and other space sensor network data providers will continue to send CDMs until the event is resolved by mitigating actions or the event TCA passes.

CDMs are defined using Key=Value Notation (KVN) files, however Kayhan Space services also allow CDM uploads to be in JSON-format KVN files.

CDM Format Example
CONSTELLATION = Kayhan Space Corp
CDM_ID = 5XXXXXXXX
INSERT_EPOCH = 2023-01-01T00:00:00
CCSDS_CDM_VERS = 1.0
CREATION_DATE = 2023-01-01T00:00:00.000000
ORIGINATOR = CSpOC
...

Download the CCSDS 508.0-B-1 CDM Blue Book

Operational CDM Reports

Satcat Operations will generate additional CDMs based on operator data. These operational CDM reports follow the same file formats as third-party CDMs. Operators that upload their owner/operator ephemeris will be able to immediately see how their data affects the conjunction geometry and risk assessment, and download or share these reports as needed.

Learn more about Operational Data in Satcat


Orbit Data Messages

File formats that describe orbits are defined by the CCSDS Orbit Data Messages Blue Book. These data formats include definitions for state vectors, Keplerian and mean elements, and entire trajectories with or without acceleration and covariance.

Each ODM file format also includes a metadata section which describes the ODM version, creation date, and other important data. Please read the ODM Blue Book for the complete description of each format.

Download the CCSDS 502.0-B-3 ODM Blue Book

Orbit Parameter Message (OPM)

The OPM file format is used to describe any of the following data:

  • State vector (Required)
  • Spacecraft parameters (Required if maneuvers are included)
  • Osculating Keplerian elements
  • Maneuver parameters
  • Covariance matrix of position and velocity
  • User-defined parameters
OPM Format Example
CCSDS_OPM_VERS      = 3.0
CREATION_DATE = 2022-11-06T09:23:57
ORIGINATOR = JAXA

COMMENT GEOCENTRIC, CARTESIAN, EARTH FIXED
OBJECT_NAME = OSPREY 5
OBJECT_ID = 1998-999A
CENTER_NAME = EARTH
REF_FRAME = ITRF2000
TIME_SYSTEM = UTC

EPOCH = 2022-12-18T14:28:15.1172
X = 6503.514000
Y = 1239.647000
Z = -717.490000
X_DOT = -0.873160
Y_DOT = 8.740420
Z_DOT = -4.191076
MASS = 3000.000000
SOLAR_RAD_AREA = 18.770000
SOLAR_RAD_COEFF = 1.000000
DRAG_AREA = 18.770000
DRAG_COEFF = 2.500000

Orbit Mean-Elements Message (OMM)

The OMM file format may be used to describe any of the following data:

  • Mean Keplerian elements (Required)
  • Spacecraft parameters
  • TLE-related parameters
  • Covariance matrix of position and velocity
  • User-defined parameters
OMM Format Example
CCSDS_OMM_VERS              = 2.0
CREATION_DATE = 2007-06-05T16:00:00
ORIGINATOR = NOAA/USA

OBJECT_NAME = GOES 9
OBJECT_ID = 1995-025A
CENTER_NAME = EARTH
REF_FRAME = TEME
TIME_SYSTEM = UTC
MEAN_ELEMENT_THEORY = SGP/SGP4

EPOCH = 2007-06-04T10:34:41.4264
MEAN_MOTION = 1.00273272
ECCENTRICITY = 0.0005013
INCLINATION = 3.0539
RA_OF_ASC_NODE = 81.7939
ARG_OF_PERICENTER = 249.2363
MEAN_ANOMALY = 150.1602
GM = 398600.8
EPHEMERIS_TYPE = 0
CLASSIFICATION_TYPE = U
NORAD_CAT_ID = 23581
ELEMENT_SET_NO = 0925
REV_AT_EPOCH = 4316
BSTAR = 0.0001
MEAN_MOTION_DOT = -0.00000113
MEAN_MOTION_DDOT = 0.0

COV_REF_FRAME = TEME
CX_X = 3.331349476038534e-04
CY_X = 4.618927349220216e-04
CY_Y = 6.782421679971363e-04
CZ_X = -3.070007847730449e-04
CZ_Y = -4.221234189514228e-04
CZ_Z = 3.231931992380369e-04
CX_DOT_X = -3.349365033922630e-07
CX_DOT_Y = -4.686084221046758e-07
CX_DOT_Z = 2.484949578400095e-07
CX_DOT_X_DOT = 4.296022805587290e-10
CY_DOT_X = -2.211832501084875e-07
CY_DOT_Y = -2.864186892102733e-07
CY_DOT_Z = 1.798098699846038e-07
CY_DOT_X_DOT = 2.608899201686016e-10
CY_DOT_Y_DOT = 1.767514756338532e-10
CZ_DOT_X = -3.041346050686871e-07
CZ_DOT_Y = -4.989496988610662e-07
CZ_DOT_Z = 3.540310904497689e-07
CZ_DOT_X_DOT = 1.869263192954590e-10
CZ_DOT_Y_DOT = 1.008862586240695e-10
CZ_DOT_Z_DOT = 6.224444338635500e-10

Orbit Ephemeris Message (OEM)

OEM format is the primary format used for transmission of trajectory and covariance data between operators and Kayhan Space. The OEM file format data conforms to specific requirements, some of which are described here:

  • The order of the ephemeris data items is fixed
    • Epoch, X, Y, Z, X_DOT, Y_DOT, Z_DOT, X_DDOT, Y_DDOT, Z_DDOT
  • The above set of data must be contained on a single line
  • The epoch, position and velocity terms are mandatory

Additional requirements can be found in the CCSDS Blue Book.

OEM Format Example
CCSDS_OEM_VERS      = 2.0
CREATION_DATE = 2020-12-15T15:38:49.225
ORIGINATOR = NONE

META_START
OBJECT_NAME = CLOUDSAT
OBJECT_ID = 29107
CENTER_NAME = Earth
REF_FRAME = EME2000
TIME_SYSTEM = UTC
START_TIME = 2020-12-15T00:00:00.000
STOP_TIME = 2020-12-15T00:04:00.000
META_STOP

2020-12-15T00:00:00.000 3122.64037649000011 -4990.45786587000021 -3916.75557478000019 1.08772865495000 -4.14753007890000 6.15926256354000
2020-12-15T00:01:00.000 3181.52799254999991 -5229.02201325999977 -3539.48705998000059 0.87451084064000 -3.80189141424000 6.41211163702000
2020-12-15T00:02:00.000 3227.50864269000022 -5446.37293529999988 -3147.82158600999992 0.65764187955000 -3.44066000995000 6.63899379231000

COVARIANCE_START
EPOCH = 2020-12-15T00:00:00.000
COV_REF_FRAME = EME2000
3.11125239948540e-08
3.05332100221654e-09 4.22065366331391e-08
1.91488347500367e-08 -5.05183479388049e-08 8.91260119830244e-08
5.65158667231038e-12 3.05586865373066e-12 1.61288598580544e-12 2.39916702388562e-14
1.13672778417593e-12 2.55641104334951e-12 -9.39613111482829e-12 1.18293576687324e-14 1.41470877634445e-14
-5.76533288642128e-13 -2.65562940015304e-12 1.38692146152402e-11 4.72034064496763e-15 -2.83818383008073e-15 1.25133123791297e-14
EPOCH = 2020-12-15T00:01:00.000
COV_REF_FRAME = EME2000
3.17567176799718e-08
3.32437419051862e-09 4.24057768646188e-08
1.91358863774219e-08 -5.10240180121485e-08 9.04928802437245e-08
5.09608271785789e-12 3.34234474413842e-12 3.71350156780421e-13 2.36439520499879e-14
1.39741458103510e-12 8.56000885512545e-13 -5.74866253871860e-12 1.17013068858110e-14 1.35380301573490e-14
-1.77944970619585e-12 9.03094967529518e-13 8.77991679278633e-12 4.07353345582921e-15 -1.38990652946612e-15 1.25034523391769e-14
EPOCH = 2020-12-15T00:02:00.000
COV_REF_FRAME = EME2000
3.23377139987704e-08
3.60952934619480e-09 4.24350696250564e-08
1.89883124250752e-08 -5.11082343791222e-08 9.12051148059243e-08
4.60062575658043e-12 3.23303249118139e-12 -3.17881697153523e-13 2.33977779287646e-14
1.42059764281136e-12 -2.58588468684403e-13 -2.96254208827873e-12 1.14467327808721e-14 1.33822633582683e-14
-3.11806273559220e-12 4.91398479111300e-12 2.99370043747734e-12 3.55167640830622e-15 -2.50437747093092e-16 1.30925227856410e-14
COVARIANCE_STOP

Other Trajectory Formats

Kayhan Satcat Launch is a Launch Conjunction Assessment (LCA) service, and adheres to the LCA Handbook of operations.

Download the Launch Conjunction Assessment Handbook from Space-Track.org

CALIPER V2.0

CALIPER Trajectory Covariance V2.0 is a specific format used by launch providers to transmit launch vehicle stage trajectories and covariance to 18/19 SDS. This format is defined by 18/19 SDS directly for use with their SuperCOMBO/CALIPER systems.

CALIPER V2.0 Format Examples
CALIPER EPHEMERIS V2.0 COVARIANCE UVW (or PTW)
LAUNCH TIME: yyyy ddd hhmm ss.sss...
TimeSinceLaunchInSeconds X Y Z Vx Vy Vz
PosCov(1,1) PosCov(2,1) PosCov(2,2)
PosCov(3,1) PosCov(3,2) PosCov(3,3)

Satcat Data Entry Forms

Satcat services allow for manual entry of orbit data such as state vectors or TLE format.

TLE Manual Entry

TLEs are used for SGP4 analytic methods of propagation. TLEs are not recommended for operational spaceflight safety due to their lower accuracy (positional uncertainty increases by ~1 km/day).

Data FieldDescription
Strict validationEnable or disable strict validation of the TLE data
TLE dataEnter a valid TLE format string (See below for format example)
IdentificationOptionally enter the asset's NORAD ID and/or Common Name

TLE format specification

Below is an example of a three line TLE, where the header line displays the asset's Common Name.

ISS (ZARYA)
1 25544U 98067A 04236.56031392 .00020137 00000-0 16538-3 0 9993
2 25544 51.6335 344.7760 0007976 126.2523 325.9359 15.70406856328906

View TLE Format Specification on Space-Track.org


State Vector Manual Entry

State vectors describe a spacecraft at one moment in time, and are typically derived from orbit determination processes.

Data FieldDescription
IdentificationOptionally enter the asset's NORAD ID and/or Common Name
State vector positionEnter three comma separated components of the position and the data units
State vector velocityEnter three comma separated components of the velocity and the data units
Asset propertiesEnter the object

Asset properties

Enter the asset property values for accurate calculation of collision risk assessment and ephemeris propagation.

PropertyUnitsRequired
Mass$kg$No
Hard Body Radius (HBR)$m$Yes
SRP Area
Coefficient of Reflectivity
$m^2$
--
No
Drag Area
Coefficient of Drag
$m^2$
--
No

Covariance matrix data entry

Optionally enter the covariance matrix values for the state. Choose the appropriate reference frame and units, and select whether the matrix was entered as lower triangular or the full NxN matrix.

View Supported Reference Frames Documentation