Closed probinso closed 1 year ago
The TLEs you get back from Space-Track.org are the same regardless of how many you query at once.
Your query doesn't make much sense, as you are querying within a 400 day window and returning the 3 nearest the end of that window, then you only read the first (i.e. latest) TLE.
The actual error you're getting appears to be from the pyephem library. It's refusing to propagate a TLE past a given point. For example, the TLE you've used might have an epoch of 2020-01-01 but you're trying to propagate it to 2022-01-01 or something, and pyephem refuses to do so. You should instead be finding the closest TLE to the epoch you wish to propagate to. This is off topic as far as spacetrack
is concerned, so I'm closing this.
I am looking to download historical data for multiple years and multiple satellites. The
spacetrack
api states that you should not exceed one call per hour-,TLE,-1%C2%A0/%C2%A0hour) fortle
. Because of this i'm trying to requestst.tle
data in chunks of400
days.however after the call, when using the tle data I am receiving this error.
Firstly, I couldn't find in the documentation what
only valid for a few weeks
comes out to, so I don't know how long my largesttle
op.includive_range
should be. Secondly, I'm looking to set this up for multiple satellites that may not have overlapping operating dates, so I seem to need to requestst.tle(
separately per satelite and so will have to make many requests. Do you have any guidance on using this api for downloading entire multiple years ofst.tle
data of this form?