-
Notifications
You must be signed in to change notification settings - Fork 145
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
observerCoordsEcf, velocityEcf not defined #24
Comments
I apologize for the extreme delay in response. |
The readme code doesn't quite run. velocityEcf and observerCoordsEcf just aren't defined. velocityEcf = satellite.eciToEcf(velocityEci, gmst); |
Recommend using Eci for the dopplerFactor example in the readme. There is no available function to convert velocityEci to velocityEcf and the readme already explains you can use ecf if you have those values. |
satellite.eciToEcf converts it |
It converts ECI Position but it doesn't convert ECI Velocity because it doesn't account for the rotation of the earth. There is a reference at http://www.dtic.mil/dtic/tr/fulltext/u2/a015815.pdf on page 29 and 30 that explains the math to convert ECI Velocity to ECF Velocity. |
I realize this issue thread is really old, but thought I would post my solution here for calculating ECF velocity in case others have the same question. If accuracy is vital and you're able to track down and decipher the math mentioned above, then great! I was not though, and this seemed to worked out pretty well for me. :) Basically, you can determine ecf velocity using the eci data that satellite.js provides via the
|
Slick idea. That should actually account for the rotation of the earth perfectly. Feels super obvious now that you post it - thanks for helping out! |
Example in README references:
dopplerFactor = satellite.dopplerFactor(observerCoordsEcf, positionEcf, velocityEcf);
But neither of
observerCoordsEcf
orvelocityEcf
appear to be available.The text was updated successfully, but these errors were encountered: