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

Improved ground track when number of orbits is 1 #197

Open
srcejon opened this issue Feb 23, 2020 · 0 comments
Open

Improved ground track when number of orbits is 1 #197

srcejon opened this issue Feb 23, 2020 · 0 comments

Comments

@srcejon
Copy link

srcejon commented Feb 23, 2020

When the number of orbits to display for ground tracks is set to 1, the tracks typically start near the equator, which means they aren't too useful when the satellite is near the equator. E.g: here the satellite is moving north, but the track doesn't show where it is going.

GroundTrack1Orbit

In this branch: #194 I've changed it so that when the number of orbits is less than 2, the ground track starts 25% of an orbit behind the current satellite position, which I think is a bit more useful, when a satellite is near the equator. (Here the ISS is moving East)

GroundTrack1OrbitNew

Also, I've added support for a fractional number of orbits, from 0.5 to 1.9, so you can get a little bit of a wrap around over the current position, without there being too much clutter of having several complete orbits. E.g. here is it set to 1.4 (so the arrow head I added for #94 happens to be in just the right position to show which way the satellite is moving).

GroundTrack1p4Orbits

spsvihla pushed a commit to lasp/gpredict that referenced this issue Nov 29, 2022
One of the problems is caused by a ternary operator having
different lambdas in the "if" and "else" clauses. This gives some
problem regarding type conversion. The ternary operator has been
replaced by an if/else construct.

The other problem regards a constexpr variable that is not captured. The
constexpr variable has been set to static constexpr.

This closes csete#197
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

1 participant