[MOIMS-NAV-EXEC] [EXTERNAL] OMM-KVN from space-track.org

[Berry, David S (US 3920)]

Alain:

Interesting observation... I suppose it’s OK though, based on this rule in the ODM:

7.8.5 All comment lines shall begin with the ‘COMMENT’ keyword followed by at least
one space. This keyword must appear on every comment line, not just the first such line.
The remainder of the line shall be the comment value. White space shall be retained (shall be
significant) in comment values.

So effectively this just means that in these examples, the first character in the comment is the equals sign “=”.

DSB


From: MOIMS-NAV-EXEC <moims-nav-exec-bounces at mailman.ccsds.org> on behalf of "moims-nav-exec at mailman.ccsds.org" <moims-nav-exec at mailman.ccsds.org>
Reply-To: Lamy Alain <Alain.Lamy at cnes.fr>
Date: Wednesday, June 11, 2025 at 06:54
To: "moims-nav-exec at mailman.ccsds.org" <moims-nav-exec at mailman.ccsds.org>
Subject: [EXTERNAL] [MOIMS-NAV-EXEC] OMM-KVN from space-track.org

Hi everyone,

I recently got TLEs from the spacetrack.org website.
Many formats are available, including classical TLEs, JSON, OMM-XML, OMM-KVN.
Attached is the KVN version (SWOT S/C).
There are 2 (possibly) interesting points :

-          The “COMMENT” lines are written : COMMENT = xxx

It may means that the description is not precise enough ?

-          As they wanted to minimize the number of files (I suppose), all KVNs are grouped in one single file.

Not strictly compliant but convenient.

Alain

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-nav-exec/attachments/20250707/9e570922/attachment.htm>