MAAP-Project / Community

Issue for MAAP (Zenhub)
2 stars 1 forks source link

Getting long-term access to LANCE / for data ingest #1032

Closed wildintellect closed 1 month ago

wildintellect commented 1 month ago

Discussed in https://github.com/orgs/MAAP-Project/discussions/1031

Originally posted by **mccabete** July 16, 2024 @wildintellect here are some specific data ingest needs we have. We have been getting data daily from: Near Real Time (Via LANCE) VNP14IMGTDL - https://nrt4.modaps.eosdis.nasa.gov/api/v2/content/archives/FIRMS/suomi-npp-viirs-c2/Global/ VJ114IMGTDL - https://nrt4.modaps.eosdis.nasa.gov/api/v2/content/archives/FIRMS/noaa-20-viirs-c2/Global/ We would love a way to handle tokening that's better than "let it fail and then bug someone to change it". Also from @scoffiel The other type of permanent token that would be really helpful is permanent AWS credentials for streaming the VIIRS Level 2 swaths (VNP14IMG, VJ114IMG) from LAADS via EarthData Cloud because currently they expire every hour: ``` from earthaccess import Auth, Store, DataCollections, DataGranules auth = Auth() auth.login(strategy="netrc") store = Store(auth) fs = store.get_s3fs_session('LAADS') #daac or provider name ``` I use the following s3 paths: s3://lp-prod-protected/VJ114IMG.002 s3://lp-prod-protected/VNP14IMG.002 Getting credentials for buckets is described here: https://data.lpdaac.earthdatacloud.nasa.gov/s3credentialsREADME index
wildintellect commented 1 month ago

Seems resolved enough in https://github.com/orgs/MAAP-Project/discussions/1031 Long term do we need to improve LANCE/LAADS support?