Auto scheduling

Hi @Jferns,

Thanks for sharing, certainly a really interesting & important topic! I guess you already know the Automatic scheduling - #4 by pierros proposal formed during Hamvention 2018, or at least your implementation pretty much matches what was proposed. :smiley:

Currently all observations in satnogs-network have to be scheduled via the /observations/new/ in advance. I’ve created the issue satnogs-network#543 in order to track this issue. In the meantime you could use e.g. the code by @KD9KCK to create the observation in advance (there is curently no API, the server-side implementation of the current endpoint is in satnogs-network/…/views.py#L297) and let the satnogs-client upload the observation data as usual.

When you upload the observation, the unique observation number in satnogs-network is returned. So you can continue to use the epoch number as a local identifier (at least as long as no observation was created in satnogs-network).

Most of the TLEs in satnogs-network and -db are downloaded from CelesTrak (with the exception of 8 satellites not available via CelesTrak, see this notebook). Unfortunately as of now, satnogs doesn’t have the right to redistribute TLEs downloaded from Celestrak (citation-needed).

Sincerely,
Fabian

1 Like