-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Velocity of Earth Satellite Loaded from TLE #187
Comments
Velocity is not yet supported; when I wrote that code, I knew how to rotate the position into GCRS coordinates, but not how to rotate the velocity:
If the holiday tomorrow gives me some free time, I might look at whether I can figure out the transformation and return something other than zeros! |
Oh — I should ask for a clarification: are you interested in the satellite's velocity relative to a non-rotating observer watching the rotating Earth from a distance? Or in its velocity relative to a location on Earth which is itself veering constantly in a circle at high speed? |
Thank you for the quick response! I'm interested in its velocity relative to a location on earth. I think By the way, I think it has already been asked in Issue #85, but is there a reason you don't offer a method to return I'm new to skyfield but I'm really enjoying it so far. The code and documentation is very clean and easy to follow. Thank you for all of your work! |
The SPICE routine xf2rav() may be helpful here. It's documented at: https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/cspice/xf2rav_c.html and should be available in the source code. It's description is "This routine determines a state transformation matrix from a rotation matrix and the angular velocity of the rotation." |
I'm trying to get the velocity of an EarthSatellite loaded from a TLE. For example:
But this returns
[0., 0., 0.]
. Note thatcubesat.at(t).position
,cubesat.at(t).subpoint()
both behave as expected. Am I misunderstanding whatcubesat.at(t).velocity
is supposed to return?The text was updated successfully, but these errors were encountered: