L1 and L2 GEDI mission collections missing HTTPS Endpoint
L1 and L2 GEDI mission collections missing HTTPS Endpoint
I'm not seeing any of the L1 and L2 GEDI data up on https://e4ftl01.cr.usgs.gov/, which has been missing since September 6th. I'm not sure if the collection has been moved to a different HTTPS endpoint but the CMR (https://cmr.earthdata.nasa.gov/search/concepts/C2142776747-LPCLOUD.html) is still pointing to e4ftl01.
Filters:
-
LP DAACx - dgolon
- User Services
- Posts: 422
- Joined: Mon Sep 30, 2019 10:00 am America/New_York
- Has thanked: 31 times
- Been thanked: 8 times
- Contact:
Re: L1 and L2 GEDI mission collections missing HTTPS Endpoint
Hi @sethdd Thanks for your inquiry. The LP DAAC is currently migrating all of our on-premises archive to NASA's Earthdata Cloud. GEDI data were migrated last week. Access to GEDI through the LP DAAC's DataPool is no longer available. However, you can still access all of the GEDI data through NASA's Earthdata Cloud: https://search.earthdata.nasa.gov/search?q=GEDI&ff=Available%20in%20Earthdata%20Cloud
). Accessing the data in Earthdata Cloud will also give you the ability to subset and customize your data for download. We apologize for the inconvenience and have updated the collection level metadata to remove the old link. Thanks -- Danielle
). Accessing the data in Earthdata Cloud will also give you the ability to subset and customize your data for download. We apologize for the inconvenience and have updated the collection level metadata to remove the old link. Thanks -- Danielle
Subscribe to the LP DAAC listserv by sending a blank email to lpdaac-join@lists.nasa.gov.
Sign up for the Landsat listserv to receive the most up to date information about Landsat data: https://public.govdelivery.com/accounts/USDOIGS/subscriber/new#tab1.
Sign up for the Landsat listserv to receive the most up to date information about Landsat data: https://public.govdelivery.com/accounts/USDOIGS/subscriber/new#tab1.
Re: L1 and L2 GEDI mission collections missing HTTPS Endpoint
Appreciate the response!
While there was a notice about the migration back in April (https://lpdaac.usgs.gov/news/gedi-version-2-migrates-to-earthdata-cloud/), I haven't seen any information on when access would be removed. Ideally, it would be nice to have awareness of when collection migrations such as this are starting/ending. I bet there's a site managed by someone at NASA, or even the DAACs themselves, that provides these details. Please do share if it does exist :-)
Has there been any improvements in accessing content from an Earthdata account using Bearer Tokens vs temporary credentials that must be updated every hour (https://data.lpdaac.earthdatacloud.nasa.gov/s3credentialsREADME)?
I'm also noticing a difference in how the GEDI mission data is stored and the XML files for each granule are missing too.
The new HTTP endpoints point to: /GEDI02_A.002/GEDI02_A_2023075201011_O24115_03_T08796_02_003_02_V002/GEDI02_A_2023075201011_O24115_03_T08796_02_003_02_V002.h5
whereas before it would have been: /GEDI02_A.002/2023.07.05/GEDI02_A_2023075201011_O24115_03_T08796_02_003_02_V002.h5
While there was a notice about the migration back in April (https://lpdaac.usgs.gov/news/gedi-version-2-migrates-to-earthdata-cloud/), I haven't seen any information on when access would be removed. Ideally, it would be nice to have awareness of when collection migrations such as this are starting/ending. I bet there's a site managed by someone at NASA, or even the DAACs themselves, that provides these details. Please do share if it does exist :-)
Has there been any improvements in accessing content from an Earthdata account using Bearer Tokens vs temporary credentials that must be updated every hour (https://data.lpdaac.earthdatacloud.nasa.gov/s3credentialsREADME)?
I'm also noticing a difference in how the GEDI mission data is stored and the XML files for each granule are missing too.
The new HTTP endpoints point to: /GEDI02_A.002/GEDI02_A_2023075201011_O24115_03_T08796_02_003_02_V002/GEDI02_A_2023075201011_O24115_03_T08796_02_003_02_V002.h5
whereas before it would have been: /GEDI02_A.002/2023.07.05/GEDI02_A_2023075201011_O24115_03_T08796_02_003_02_V002.h5
-
LP DAAC - afriesz
- Subject Matter Expert
- Posts: 71
- Joined: Tue Nov 12, 2019 4:02 pm America/New_York
- Been thanked: 3 times
Re: L1 and L2 GEDI mission collections missing HTTPS Endpoint
Our authentication approach remains unchanged, using Bearer Tokens or .netrc files with Earthdata Login credentials outside the cloud and temporary S3 credentials within the cloud (i.e., AWS us-west-2), which require hourly updates. When accessing GEDI data in Earthdata Cloud, note that HTTPS endpoints and concept IDs have changed (refer to the linked news announcement in your post). For seamless programmatic search and access, we recommend using the CMR API, earthaccess package (Python), or earthdatalogin library (R), which provide the best way to discover and access all Earthdata Cloud collections, including GEDI data.