Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bulk TLE download #181

Open
cbassa opened this issue Nov 29, 2019 · 5 comments
Open

Bulk TLE download #181

cbassa opened this issue Nov 29, 2019 · 5 comments
Labels
enhancement New feature or request
Projects

Comments

@cbassa
Copy link

cbassa commented Nov 29, 2019

It would help observers if they could have access to the TruSat TLEs through a single, static URL. Observers will want to pull the latest TLEs of all objects from several sources (space-track.org, Mike McCants but also TruSat), prior to their observing sessions.

@johngribbin johngribbin added the enhancement New feature or request label Nov 29, 2019
@interplanetarychris
Copy link
Collaborator

@Kmoneal with the full-stacking of the Front-end and API, this feature request is almost solved:

I believe all that needs to be done it to deliver the following URL requests with a plain/text MIME type

@mainnebula mainnebula added this to In progress in TruSat Mar 2, 2020
@johngribbin
Copy link
Collaborator

Both links now working as expected, see:

PR - TruSat/trusat-backend#101

Cheers to @Kmoneal for quick turnaround.

TruSat automation moved this from In progress to Done Mar 3, 2020
@interplanetarychris
Copy link
Collaborator

@mainnebula @mikeville We should figure out where to advertise that these direct URLs are available for scripted-access - in trusat-learn, or on the catalog page view?

TruSat automation moved this from Done to In progress Mar 3, 2020
@johngribbin
Copy link
Collaborator

@interplanetarychris Did a quick post on discuss after check in with @mainnebula and @mikeville yesterday evening, see here - https://discuss.trusat.org/t/new-trusat-feature-direct-urls-to-download-tles/126

We also felt it would make sense for @Kmoneal to include both links in his README for the backend repo, perhaps tied in with a further documentation of all the endpoints in TruSat.

@interplanetarychris
Copy link
Collaborator

OK, this helps, but ultimately it seems like it should be directly on the site, and not buried in repos or aging discussion forum posts...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
TruSat
  
In progress
Development

No branches or pull requests

3 participants