COSPAR ID/International Designator

[jdarpinian]

Could you add a COSPAR ID/International Designator field to the launches? I'm trying to associate objects from the space-track.org catalog with launch data from this API. Today it can be done unambiguously using launch date, but that will fail as soon as SpaceX succeeds in doing multiple launches in one day. International Designator (I guess more precisely, the "launch number" part of the International Designator) would be unambiguous. Thanks!

[jakewmeyer]

Are you trying to associate launches or payloads? That id is similar to the NORAD id we use for payloads, so that could be used to associate as well.

[jdarpinian]

I'm associating launches from the r/SpaceX API with tracked objects from the space-track.org API.

…

On Sun, May 30, 2021, 10:37 AM Jake Meyer ***@***.***> wrote: Are you trying to associate launches or payloads? That id is similar to the NORAD id we use for payloads, so that could be used to associate as well. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#815 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADO4KG4OVWEKSFAM7WF6MDTQJZT7ANCNFSM45Y6A5PA> .

[jakewmeyer]

You should be able to use the norad_ids in the payload to associate, essentially the same as the COSPAR ID.

[jdarpinian]

I don't see norad IDs in most payloads. For example, Transporter-1 has a single "payload" object with zero entries in the norad_ids array, when it should have at least 143. NORAD assigns IDs to things that aren't likely to be given "payload" entries in your database, such as the rods discarded during Starlink deployment. Also, NORAD doesn't start tracking objects right after launch. I also want to be able to associate launches with Celestrak's "SupTLEs" which are available immediately after launch (and even before launch).