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

Operational Status as a List View Option #132

Closed
wants to merge 2 commits into from

Conversation

jasonuher
Copy link
Contributor

Adds a checkbox for the operational status to be added to the list view. I realize this information is (not obviously) available to the user by looking at the name suffixes, but for quick reference (ie, in a dashboard) it is helpful to have it in the list directly.

2018-06-20-220644_2864x521_scrot

@csete
Copy link
Owner

csete commented Jul 6, 2018

I'm not crazy about the idea of showing static information in the views. The views are intended to show information that changes as the satellites move. Static information should be shown in static views, like the satellite information dialog.

We can leave this open for a while to see whether there is broader interest in it.

@jasonuher
Copy link
Contributor Author

I understand your intended paradigm and it's fine to close this.

That said, for posterity I'll explain why it's useful to me:

For something like a constellation of satellites that perform the same function (for example, the NOAA weather birds) I find it useful to see the whole constellation regardless of their current operational status. Without this information readily available it may be easy to mistake your current coverage in the sense that you think you are covered by a satellite, but it is not currently operational. This feature is most useful when using custom/local TLE files that are updated at highly regular (ie, 'daily') intervals.

I think the general use case here is to exclude non-operational satellites from the list and map view to avoid that confusion, this just gives the option of adding extra information if necessary.

Same applies to #131

@csete
Copy link
Owner

csete commented Jul 6, 2018

Thanks for the explanation, now I understand it better why it can be useful. Let's keep this in TBD for the next release.

@csete csete closed this in 837cfca Oct 17, 2018
@csete
Copy link
Owner

csete commented Oct 17, 2018

Merged manually because I wanted the two commits squashed.

spsvihla pushed a commit to lasp/gpredict that referenced this pull request Nov 29, 2022
The information has been taken from
https://www.pe0sat.vgnet.nl/satellite/amateur-radio-satellites/go-32/

A sample recording is not available

See csete#132
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

Successfully merging this pull request may close these issues.

None yet

2 participants