Conjunction screening with external services

OKAPI:Aether

All uploaded OEMs (both operational and tentative) will be sent to OKAPI:Aether for conjunction screening against the whole catalog. As a result, all conjunction events involving the satellite for which you uploaded data will be updated.

Supported formats:

OPMs are currently not propagated, so they are not used for conjunction screening.

Supported state vector reference frames:

EME2000
GCRF
ICRF
ITRF2000
J2000
TEME

Supported covariance reference frames:

GCRF
RTN
RSW
UVW

Other restrictions:

The object ID specified in the OEM needs to be a NORAD ID. It can be a COSPAR ID only if the satellite is configured in OKAPI:Aether (so the system can look up the NORAD ID).
Timestamps have to be UTC.

Starlink

If a satellite of yours is in the same orbital region as the Starlink satellites, you can configure to send uploaded ephemerides to Starlink, in order to get fast, up-to-date screening against their whole constellation.

Supported formats:

Supported state vector reference frames:

ITRF
EME2000

Supported covariance reference frames:

RTN
ITRF
EME2000

Starlink prefers ITRF 2008, as this is what they use for the screening.

Other restrictions:

Timestamps have to be UTC.
All covariance timestamps must have a 1-to-1 mapping with state vector timestamps, so there has to be a covariance for every position.

In order to share ephemerides with Starlink, you need to set the following section in each satellite for which you want to do so:

{
    "external": {
        "starlink": {
            "screen_ephemerides": true,
            "screen_maneuvers": true
        }
    }
}

You can decide whether to share only operational ephemerides, only tentative maneuver plans, or both.

See the defining satellites section on how to create or update satellite details via API, or get in touch with us.

Note that you need to specify the hard_body_radius and maneuverability properties, as these are required by Starlink.

Supported data formats Troubleshooting