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

Get transponder data from SatNOGS database #49

Closed
oyvkar opened this issue Mar 13, 2017 · 1 comment
Closed

Get transponder data from SatNOGS database #49

oyvkar opened this issue Mar 13, 2017 · 1 comment
Assignees

Comments

@oyvkar
Copy link
Contributor

oyvkar commented Mar 13, 2017

The DIY open ground station network SatNOGS has a database module that contains transponder-information that can be found here.

The transponder database is based on user-inputs and contains uplink and downlink information in a reasonable format. It also indicates if the satellite is alive or not.

The database has an API which can be found here.

Flyby should ship with a tool similar to update-tle that fetches data from db.satnogs.org to generate a transponder database.

@bjorgan
Copy link
Member

bjorgan commented Mar 13, 2017

Probable steps in bash-script:

  1. Fetch transponder information from all satellites (should not be necessary to limit the satellites to satellites in TLE database since there are not that many with transponders defined, but in that case we would need flyby CLI functionality for listing all NORAD ids in TLE database and fetch transponders based on the IDs)
  2. Generate flatfile transponder database as expected by predict/flyby (see default/flyby.db for template) to temporary file.

Flyby should probably also define some new CLI options for merging in the generated file with the transponder database the user already has saved in his local directory, so that we don't overwrite user-defined information. Moved to #51

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants