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

Added ability to set coverage color based on status #131

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

jasonuher
Copy link
Contributor

Adds additional color options for spot beam coverage based on the operational status of the satellite.

  • Default behavior is unchanged (all colors are the same)
  • Additional options to change the color for certain operational statuses

You can set independent colors for these statuses:

  • Fully Operational
  • Partially Operations
  • Non-Operational

The following statuses will always be the default color:

  • Unknown
  • standby
  • spare
  • extended

It wouldn't be too hard to extend the settings to the full list of statuses, but:

  • this is all I needed (it's all my TLE Files support)
  • It's a pain to add a bunch of new settings, so a design decision should be made about the best way to set it up. a few options
    • Just 'brute force' through all the color options for the full set of {map, polar} times {satellite, ground track, coverage)
    • Come up with a nested/OO approach to settings
    • Change the way settings are stored all together (ick)

@jasonuher
Copy link
Contributor Author

Screenshots

2018-06-20-215747_2900x1527_scrot
2018-06-20-215809_1640x1576_scrot

@csete
Copy link
Owner

csete commented Jul 6, 2018

Same comment as for pull request #132; however, in this case, there is also issue #8 to keep in mind.

@csete
Copy link
Owner

csete commented Apr 1, 2020

I just tried this and it looks like resetting the colors to default does not apply to these new settings.
On one hand, I'm fine with getting this in although it would be nice to have options for some of the other statuses as well. On the other hand, I agree that the existing config system is a pain and should probably rewrite that first... Unfortunately, the same applies to most of the application, haha 😀

spsvihla pushed a commit to lasp/gpredict that referenced this pull request Nov 29, 2022
spsvihla pushed a commit to lasp/gpredict that referenced this pull request Nov 29, 2022
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.

2 participants