<div dir="ltr">Hi,<div><br></div><div>I've used space-track quite a bit and have worked with their developers, so I may have useful additional context.</div><div><br></div><div>First, I can't figure out how you got those TLES/OMMs. It looks nearly identical to the response you would receive from their GP class API endpoint, but that endpoint doesn't seem to support KVN anymore. Maybe they've deprecated the KVN format since January when those were produced. Their API documentation does say they've been working on deprecating some of their OMM formats. If it would be helpful, I could ask if they did that.</div><div><br></div><div>Second, I think space-track knows that the equal signs are not required, but pretty much any space-track KVN product I've seen has equal signs in the comments. I believe it is so anyone who builds parsers specifically for space-track instead of for the OMM in general can build parsers that split each line at the equal sign.</div><div><br></div><div>Presumably you retrieved these through the space-track API, right? Space-track doesn't keep OMMs inside a file structure. They instead use a relational database. So when requesting multiple of any of their data products through their API, it will return all of them to you in the same response. </div><div><br></div><div>It's also probably worth mentioning that JSON OMM's do not follow CCSDS standards in that they remove the USER_DEFINED_ tag off the user defined fields. They also actually have the true TLE lines contained in the non-CCSDS compliant versions (HTML, CSV, JSON), but not in the CCSDS compliant versions (XML, KVN?). I think it would be fair to say the space-track, and the past version do not believe that CCSDS standards apply to JSON formats.</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 11, 2025 at 9:54 AM Lamy Alain via MOIMS-NAV-EXEC <<a href="mailto:moims-nav-exec@mailman.ccsds.org" target="_blank">moims-nav-exec@mailman.ccsds.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<div lang="EN-US">
<div>
<p class="MsoNormal">Hi everyone, <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I recently got TLEs from the <a href="http://spacetrack.org" target="_blank">spacetrack.org</a> website. <u></u><u></u></p>
<p class="MsoNormal">Many formats are available, including classical TLEs, JSON, OMM-XML, OMM-KVN.
<u></u><u></u></p>
<p class="MsoNormal">Attached is the KVN version (SWOT S/C). <u></u><u></u></p>
<p class="MsoNormal">There are 2 (possibly) interesting points : <u></u><u></u></p>
<p style="margin-left:18pt">
<u></u><span>-<span style="font:7pt "Times New Roman"">
</span></span><u></u>The “COMMENT” lines are written : COMMENT = xxx<u></u><u></u></p>
<p style="margin-left:18pt">It may means that the description is not precise enough ?
<u></u><u></u></p>
<p style="margin-left:18pt">
<u></u><span>-<span style="font:7pt "Times New Roman"">
</span></span><u></u>As they wanted to minimize the number of files (I suppose), all KVNs are grouped in one single file.
<u></u><u></u></p>
<p style="margin-left:18pt">Not strictly compliant but convenient.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Alain<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br>
MOIMS-NAV-EXEC mailing list<br>
<a href="mailto:MOIMS-NAV-EXEC@mailman.ccsds.org" target="_blank">MOIMS-NAV-EXEC@mailman.ccsds.org</a><br>
<a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-nav-exec" rel="noreferrer" target="_blank">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-nav-exec</a><br>
</div></blockquote></div>