loicdtx/lsru

:mag: :globe_with_meridians:Query and Order Landsat Surface Reflectance data via ESPA

lsru's Issues

earthexplorer json search deprecation

Looks like usgs API is about to be deprecated (by December 2020)
See migration guide to switch to v1.5

Catch failed requests, filter list and re-send

Some requests fail because of scenes not available on espa.

The json returned in r.text:

{
 "message": {
   "Inputs Not Available": [
     "LT52310672004112CUB00"
   ]
 },
 "status": 400
}

conf not passed to Order when file in not standard location

Espa.order() returns an instance of Order. conf= is not explicitely passed so that it fails when config file is in non standard location

Improve warning when a scene is not downloaded

Right now, it says Missing scene downloaded! when the downloader hits an un-completed scene.

Ideas:

• Print ESPA justification of incompleteness instead
• ...

More of a comment: 429 Errors

For downloading, if you try to download more than one scene at a time, you get a 429 Error code and a 162 byte download. How does this library handle retry for that situation?

Handle date restricted property in available-products results

The following query to available-products

curl  --user username:password \
                  -X GET \
                  -d '{"inputs":["LE07_L1GT_020049_20160611_20161209_01_T2",
                                      "LE07_L1GT_021049_20200105_20200131_01_T2",
                                      "LE07_L1TP_021049_20200206_20200303_01_T1"]}' \
                        https://espa.cr.usgs.gov/api/v0/available-products

returns

{"etm7_collection": {"products": ["source_metadata", "l1", "toa", "bt", "stats", "pixel_qa", "et"], 
                                "inputs": ["LE07_L1GT_020049_20160611_20161209_01_T2", "LE07_L1GT_021049_20200105_20200131_01_T2", "LE07_L1TP_021049_20200206_20200303_01_T1"]},
                                "date_restricted": {"sr": ["LE07_L1GT_020049_20160611_20161209_01_T2"],
                                                             "sr_ndvi": ["LE07_L1GT_020049_20160611_20161209_01_T2"],
                                                              "sr_evi": ["LE07_L1GT_020049_20160611_20161209_01_T2"],
                                                              "sr_savi": ["LE07_L1GT_020049_20160611_20161209_01_T2"],
                                                              "sr_msavi": ["LE07_L1GT_020049_20160611_20161209_01_T2"],
                                                              "sr_ndmi": ["LE07_L1GT_020049_20160611_20161209_01_T2"],
                                                              "sr_nbr": ["LE07_L1GT_020049_20160611_20161209_01_T2"],
                                                              "sr_nbr2": ["LE07_L1GT_020049_20160611_20161209_01_T2"]}}

A query without date restricted scenes return

curl  --user username:password \
                  -X GET \
                  -d '{"inputs":["LE07_L1GT_021049_20200105_20200131_01_T2", 
                                 "LE07_L1TP_021049_20200206_20200303_01_T1"]}' \
                        https://espa.cr.usgs.gov/api/v0/available-products

{"etm7_collection": {"products": ["source_metadata", "l1", "toa", "bt", "sr", "sr_ndvi", "sr_evi", "sr_savi", "sr_msavi", "sr_ndmi", "sr_nbr", "sr_nbr2", "stats", "pixel_qa", "et"], "inputs": ["LE07_L1GT_021049_20200105_20200131_01_T2", "LE07_L1TP_021049_20200206_20200303_01_T1"]}}

So products appear either in products or in date_restricted, but not in both.
What need to be done is; if any of the products ordered appear in date_restricted, it needs to be removed from the inputs

Remote sensing

Hi do you can guide me please

PathRow and Sensor as Parameters

Allow a call to send a path/row in lieu of a BBox as well as specify sensor (LS4, LS5, LS7, LS8). I built this same exact solution in NodeJS and love that I found a Python alternative. I also added in the Search capability to find the scenes to order from https://earthexplorer.usgs.gov/inventory/json/v/1.4.0/search.