-
-
Notifications
You must be signed in to change notification settings - Fork 208
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
Unable to load TLE without name line #163
Comments
It is expected that the link return "You must be logged in to complete this action" when I visit it? |
Yes, you need to create an account to view their data. The account is free if you want to check it out, but as an example, if you save the following two TLEs to a file and try to load it as shown, you will get that error:
|
Thank you, that sample file will be perfect! I'll see what I can do. |
In the meantime, note that you can loop across the lines yourself and create Earth satellite objects with:
In case that gets you moving again and not waiting for the next release! |
Thank you. I did get this direct implementation of the class constructor working for me, and just fed it the satellite ID for the |
See pull request #177 |
Thanks, I'll go take a look at that pull request! |
(Fixed by #177.) |
When using
load.tle()
, it would be nice to add a check to either grab the first line as the satellite name (if three lines are provided per TLE), or just parse out the satellite ID and use that as the name if the list is only TLEs. For instance, if I download the latest TLE list from space-track.org (two-line elements, not three), to'satcat.txt'
and try toload.tle('./satcat.txt')
, I get the following traceback:I know you can get the three-line elements from space-track.org, but sometimes I am working with TLE files that I have no control over and only use two lines per satellite (no ID).
If I have time I will try to implement this check and submit a pull request. Otherwise if somebody else gets to it first, I think it would be a nice improvement.
The text was updated successfully, but these errors were encountered: