Skip to main content

Upload a trajectory

POST 
/v1/trajectory

Upload a trajectory file in either OEM or Modified ITC format.

If a file starts with "CCSDS_OEM_VERS", the system attempts to parse it as an OEM file. Otherwise, it attempts to parse it as a Modified ITC file.

OEM files must have position and velocity in the ITRF or EME2000 reference frame, and covariance in either the same reference frame, or RTN.

Modified ITC files must have position and velocity in the EME2000 reference frame, and covariance in the UVW (a.k.a. RTN) frame.

See https://public.ccsds.org/Pubs/502x0b3e1.pdf (Section 5) for the OEM spec, and the https://www.space-track.org/documents/Spaceflight_Safety_Handbook_for_Operators.pdf p. 19 for Modified ITC spec.

Trajectory files must have at least 6 data points. Each data point must have an accompanying covariance, and all position covariance must be non-zero.

Trajectories must stay below 70km/s velocity.

All states within a trajectory must be no more than 21 days in the future.

The state_source field is optional, but if specified must be "operator_ephemeris".

A "hypothetical" trajectory will not override the object's current active trajectory, but it will be screened against other trajectories for possible conjunctions.

A "definitive" trajectory will override the object's current trajectory.

A "candidate" trajectory will transform into a "definitive" if all CDMs are below the relinquish threshold.

This endpoint is rate limited per operator. Email support if you need your rate limit increased.

Request​

Body

required

Trajectory

    auto_relinquish_pc_threshold stringrequired
    created_at_utc date-time
    file stringrequired

    Possible values: <= 26214400 characters

    object_id uuidrequired
    state_source services.TrajectoryStateSource

    Possible values: [operator_ephemeris]

    upload_type services.TrajectoryTyperequired

    Possible values: [hypothetical, definitive, candidate]

Responses​

Trajectory UUID

Schema
    id uuid
Loading...