Use AWS open data source from ASF

[scottstanie]

Nice news from ASF, which means we should switch over the source and set this as the default:

ASF has made Sentinel-1 orbits available in Amazon S3 and the https://registry.opendata.aws/s1-orbits/. The main advantages of the new archive are 1) files are publicly accessible without authentication, and 2) it's built for high availability using AWS infrastructure...our archive at https://s1qc.asf.alaska.edu is still available and still supported

Our https://s1-orbits.s3.us-west-2.amazonaws.com/README.html has the details, including some small tools we built to make finding the orbit you need easier. In particular, we published an https://pypi.org/project/s1-orbits/ python library for our most common use case

[cmarshak]

@dbekaert 👆

[cmarshak]

Just as an aside, I am very partial to the API design - well the SLC input as I am not as well versed in S1 metadata - might be nice to add this as well i.e. fetch_orbit(<SLC_ID>)

[scottstanie]

do you mean just the naming fetch_orbits vs download_eofs? or as a positional argument?
there is the option for sentinel_file for download_orbits now which would work with any string that parses to a granule correctly

[cmarshak]

sentinel_file solves that - thanks for sharing!