Granule Data Field Returns "https" when in region s3 data are available

[meteodave]

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])

Output:

found US-West-2
Collection: {'ShortName': 'XAERDT_L2_ABI_G16', 'Version': '1'}
Spatial coverage: {'HorizontalSpatialDomain': {'Geometry': {'GPolygons': [{'Boundary': {'Points': [{'Longitude': -147.0, 'Latitude': -72.0}, {'Longitude': -3.0, 'Latitude': -72.0}, {'Longitude': -3.0, 'Latitude': 72.0}, {'Longitude': -147.0, 'Latitude': 72.0}, {'Longitude': -147.0, 'Latitude': -72.0}]}}]}}}
Temporal coverage: {'RangeDateTime': {'BeginningDateTime': '2019-09-25T23:50:00.000Z', 'EndingDateTime': '2019-09-26T00:00:00.000Z'}}
Size(MB): 49.1438646316528
Data: ['https://data.laadsdaac.earthdatacloud.nasa.gov/prod-lads/XAERDT_L2_ABI_G16/XAERDT_L2_ABI_G16.A2019268.2350.001.2023253054738.nc']

Environment

- OS:Debian GNU/Linux 11
- Python: 3.12.7
- earthaccess: 0.12.0

Additional Context

No response

[asteiker]

@meteodave Thanks for reporting this. I don't think this is unique to your LAADS example, as I see the same results when searching for an ICESat-2 collection in the cloud. I believe that the search_data results are only grabbing the first data access URL, which would be the HTTPS link in this case. @betolink does that sound right to you? Regardless, the s3 URL should still be found and utilized when using earthaccess.open().

So, I don't know if this is truly a bug versus an enhancement that we need to make to search_data() to provide all data access URLs that exist for the granule results, including s3.