SatNOGS Operations Manual - Revision history

Kerel+satnogs at 16:04, 19 November 2025

2025-11-19T16:04:40Z

Kerel+satnogs at 16:04, 19 November 2025

2025-11-19T16:04:19Z

Kerel+satnogs: Add note for Satellite Operators to share TLE via launch thread

2025-11-19T16:02:40Z

Add note for Satellite Operators to share TLE via launch thread

Pierros: /* 5. Update provisional TLEs (~12 hours before launch) */

2020-06-27T12:23:01Z

‎5. Update provisional TLEs (~12 hours before launch)

Pierros at 18:03, 19 June 2020

2020-06-19T18:03:31Z

Fredy: /* Requirements */ typo

2020-06-19T16:42:32Z

‎Requirements: typo

Pierros at 16:32, 19 June 2020

2020-06-19T16:32:57Z

Pierros: wip

2020-06-19T11:46:42Z

wip

New page

{{Warning|This manual is intended for SatNOGS Moderators. For a guide on how to add your mission to SatNOGS see [[Satellite Operator Guide]]}}

=== Requirements ===
his manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations!

=== Adding a new Satellite ===

==== 0. Should we add it? ====
In principle SatNOGS DB aims to capture all information about satellites regardless of their origin, ownership or purpose. So the simple answer is "Yes you should add it". That said we do prioritize the satellites that can be (and will be) tracked by the SatNOGS Network and especially the ones that have been pro-active in reaching out and sharing as much information as possible.

1. Find new satellites

Besides the missions that will actively reach out to us by filling issues in [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo]

@@ Line 40: / Line 40: @@
 <br />
 ====6. Update provisional TLEs (~12 hours before launch)====
-{{Warning|This manual is intended for SatNOGS Moderators. If you are not a SatNOGS Moderator, please share TLEs in the '''Launch Thread''', so that one of the moderators can add it. Follow the [[Satellite Operator Guide#3._Operations]] for more information. }}
+{{Warning|This manual is intended for SatNOGS Moderators. If you are not a SatNOGS Moderator, please share TLEs in the '''Launch Thread''', so that one of the moderators can add it. Follow [[Satellite Operator Guide#3._Operations]] for more information. }}
 * Acquire provisional TLEs (either constructed from the community or shared by the launch provider)

@@ Line 40: / Line 40: @@
 <br />
 ====6. Update provisional TLEs (~12 hours before launch)====
-{{Warning|This manual is intended for SatNOGS Moderators. If you are not a SatNOGS Moderator, please share TLEs in the '''Launch Thread''', so that one of the moderators can add it. Follow the [[Satellite Operator Guide]] for more information. }}
+{{Warning|This manual is intended for SatNOGS Moderators. If you are not a SatNOGS Moderator, please share TLEs in the '''Launch Thread''', so that one of the moderators can add it. Follow the [[Satellite Operator Guide#3._Operations]] for more information. }}
 * Acquire provisional TLEs (either constructed from the community or shared by the launch provider)

@@ Line 1: / Line 1: @@
 ===Requirements===
 This manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations!
 ===Adding a new Satellite===
 ====0. Should we add it?====
@@ Line 41: / Line 40: @@
 <br />
 ====6. Update provisional TLEs (~12 hours before launch)====
 * Acquire provisional TLEs (either constructed from the community or shared by the launch provider)

@@ Line 36: / Line 36: @@
 ====4. Add and approve transmitters in DB====
 <br />
-====5. Update provisional TLEs (~12 hours before launch)====
+* Acquire provisional TLEs (either constructed from the community or shared by the launch provider)
-<br />
+** You can verify the integrity of the TLE [https://www.vcalc.com/wiki/MichaelBartmess/TLE+Checksum here] and [https://oraas.orekit.space/oraas-tools-tletranslator.html here]
 <br />
 ====7. Schedule LEOP====
 <br />

@@ Line 20: / Line 20: @@
 ====2. File the issues in satnogs-ops====
-Once you have the information it is needed then navigate to [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo] and open new issues containing all the information needed. Some websites and online resources for digging up information (if not already provided by the mission teams):
+Once you have the information it is needed then navigate to [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo] and open new issues containing all the information needed.
 *http://nanosats.eu/

@@ Line 2: / Line 2: @@
 ===Requirements===
-his manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations!
+This manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations!
 ===Adding a new Satellite===
@@ Line 9: / Line 9: @@
 In principle SatNOGS DB aims to capture all information about satellites regardless of their origin, ownership or purpose. So the simple answer is "Yes you should add it". That said we do prioritize the satellites that can be (and will be) tracked by the SatNOGS Network and especially the ones that have been pro-active in reaching out and sharing as much information as possible.
-==== 1. Find new satellites ====
+====1. Find new satellites====
 Besides the missions that will actively reach out to us by filling issues in [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo], we need to track launch activity to ensure we are adding new satellites in our DB. Some resources for tracking launches:
-* https://space.skyrocket.de/doc_chr/lau2020.htm
+*https://space.skyrocket.de/doc_chr/lau2020.htm
-* https://spaceflightnow.com/launch-schedule/
+*https://spaceflightnow.com/launch-schedule/
-* https://www.space.com/32286-space-calendar.html
+*https://www.space.com/32286-space-calendar.html
 Tip: As of 2020 we are not adding any swarm satellite entries (e.g. Starlink, OneWeb etc)
 <br />
-==== 2. File the issues in satnogs-ops ====
+====2. File the issues in satnogs-ops====
 Once you have the information it is needed then navigate to [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo] and open new issues containing all the information needed. Some websites and online resources for digging up information (if not already provided by the mission teams):
-* http://nanosats.eu/
+*http://nanosats.eu/
-* http://www.amsatuk.me.uk/iaru/index.php
+*http://www.amsatuk.me.uk/iaru/index.php
-* https://fcc.report/
+*https://fcc.report/
-* https://apps.fcc.gov/oetcf/els/index.cfm
+*https://apps.fcc.gov/oetcf/els/index.cfm
-* Search Google and Twitter for mission posted information!
+*Search Google and Twitter for mission posted information!
-==== 3. Add satellite in DB ====
+====3. Add satellite in DB====
 <br />
-==== 4. Add and approve transmitters in DB ====
+====4. Add and approve transmitters in DB====
 <br />
-==== 5. Update provisional TLEs (~12 hours before launch) ====
+====5. Update provisional TLEs (~12 hours before launch)====
 <br />
-==== 6. Sync SatNOGS Network ====
+====6. Sync SatNOGS Network====
 <br />
-==== 7. Schedule LEOP ====
+====7. Schedule LEOP====
 <br />
-==== 8. Review results ====
+====8. Review results====
 <br />