You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this issue already tracked somewhere, or is this a new report?
I've reviewed existing issues and couldn't find a duplicate for this problem.
Current Behavior
I seem to be having an issue accessing LAADS data with earthaccess 0.12.0. The "Data" field of the granule returns only the "https" link but these data are in the Cloud according to earthdata search.
Expected Behavior
I would expect "Data" in the granule to return the S3 path link.
Steps To Reproduce
In Jupyter Notebook:
import earthaccess
from pprint import pprint
import boto3
auth = earthaccess.login(persist=True)
granules = earthaccess.search_data(concept_id = 'C2859273114-LAADS', temporal = ('2019-09-26','2019-09-27'))
if (boto3.client('s3').meta.region_name == 'us-west-2'):
print("found US-West-2")
else:
print("US-West-2 not found")
print(granules[0])
Is this issue already tracked somewhere, or is this a new report?
Current Behavior
I seem to be having an issue accessing LAADS data with earthaccess 0.12.0. The "Data" field of the granule returns only the "https" link but these data are in the Cloud according to earthdata search.
Expected Behavior
I would expect "Data" in the granule to return the S3 path link.
Steps To Reproduce
In Jupyter Notebook:
Output:
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: