Astro-SpaceTrack
view release on metacpan or search on metacpan
Suppress appending of '--rcs' to the common name by the REST interface
when RCSVALUE is null.
Fix problem with merging names from an observing list into JSON REST
data.
0.063 2012-08-29 T. R. Wyant
Imposed Space Track REST cookie expiration of an hour. The cookie
appears to come with no expiration, but the docs say it's only good
for about 2 hours.
Followed change to representation if International Launch Designator
(INTLDES) in Space Track REST class tle. It was yyyy-lllp, but is
now yylllp, just like Space Track version 1.
0.062 2012-08-25 T. R. Wyant
Fix the joining of JSON data when one of the lists is empty.
Have the celestrak() and file() methods supply common names from their
sources if the with_name attribute is true and the
space_track_version attribute is 2. This functionality will be
retracted when (and if) the Space Track REST interface becomes
capable of supplying NASA-format TLEs.
Document the fact that Space Track has deprecated bulk data downloads,
and plans to remove them in October 2012. This will break the
spacetrack() method.
Use more recent datas for launch date and historical query tests in
t/query.t, since it seems that Space Track purged the version 2 TLE
database on August 24 2012.
0.061 2012-08-15 T. R. Wyant
Reinstate the headings returned by -notle searches done with
space_track_version set to 1. These were lost in version 0.060_09.
When the space_track_version attribute is 2, implement the -exclude
search option in terms of the OBJECT_TYPE field rather than by
simulating the version 1 exclusion rules in the client. This can
mean different search results depending on the interface used (e.g.
Westford needles are debris under v1, but payload under v2), but
since the change seems to be deliberate on the part of Space Track,
I am following it.
0.060_12 2012-08-07 T. R. Wyant
Turn on autoflush in t/query.t to try to prevent overwriting of
prompt.
Have the REST version of retrieve() issue multiple queries if the
number of OIDs is over 50.
Add the ability to handle OID ranges to the REST versions of
retrieve() and search_oid().
Have the output of names( 'spacetrack' ) depend on the value of the
space_track_version attribute.
Have the shell() method extract redirections from the command line
before un-quoting and un-escaping the data, so that we have a way to
force something that looks like a redirection to be taken as an
argument.
Add ':' to the list of 'safe' characters when URI-escaping arguments
to the Space Track REST interface. Percent-encoded colons seemed to
stop working some time between 13:15 and 19:15 GMT on July 27 2012.
Un-encoded colons go through fine.
Accept ':' as well as '/' as punctuation between username and password
in environment variable SPACETRACK_USER.
Have t/query.t try to load Term::ReadKey. If successful, it uses it to
turn off password echoing. If not successful, it adds '(ECHOED)' to
the prompt.
Fix problem associating RCS data with TLEs when using version 1 of the
Space Track interface and the OID in the search results is less than
five digits.
Change default value of verify_hostname attribute to false. And about
time.
Add attribute 'pretty' to reqest that JSON text (and potentially
others) be pretty-formatted.
Expose the name of the Space Track session cookie as an attribute.
This is one of those attributes which have distinct values for each
value of space_track_version.
Have the parser for the retrieve() -start_epoch and -end_epoch options
accept time of day as well as just date. Pass time of day to the
server when using the Space Track REST interface.
Further deprecate celestrak( 'sts' ) and spaceflight( 'shuttle' ) so
that they give a warning every time they are used.
If both -json and -rcs are in effect, return RCSSOURCE as well as
RCSVALUE.
Have the attribute_names() method take account of the fact that the
'cookie_expires' attribute does not exist if the space_track_version
attribute is set to 2.
Ignore the -sort and -descending retrieve() options when using the
Space Track REST interface. As things now stand, I have to force the
equivalent of -sort=epoch -descending when retrieve()-ing multiple
OIDs to get sane results.
Add a -json retrieve() option, valid only if the REST interface is in
use. This also works with celestrak() and file() if the
space_track_version attribute is 2, but with celestrak() the usual
restrictions on retrieve() options apply.
Retrieve TLEs for multiple OIDs in a single call to the Space Track
REST interface.
Require HTTP::Status 6.03, because I can't forebear to use the
"teapot" status for testing purposes.
Expose spacetrack_query_v2(), which is our lowest-level interface to
Space Track version 2.
( run in 0.571 second using v1.01-cache-2.11-cpan-39bf76dae61 )