GEDI Filenames

GEDI filenames (i.e., the local granule ID) follow a naming convention which gives useful information regarding the specific product.

In this example of a Version 2 Level 01B product, the filename GEDI01_B_2019110110221_O01997_03_T03335_02_005_01_V002.h5 indicates:

• GEDI01_B = Product Short Name
• 2019110 = Julian Date of Acquisition in YYYYDDD
• 110221 = Hours, Minutes, and Seconds of Acquisition (HHMMSS)
• O01997 = O = Orbit, 01997 = Orbit Number
• 03 = Sub-Orbit Granule Number
• T03335 = T = Track, 033335 = Track Number
• 02 = Positioning and Pointing Determination System (PPDS) type (00 is predict, 01 rapid, 02 and higher is final)
• 005 = PGEVersion = SDPS Release Number
• 01 = Granule Production Version
• V002 = Version Number
• .h5 = Data Format

In this example of a Version 2 Level 01A product, the filename GEDI02_A_2019110014613_O01991_01_T04905_02_003_01_V002.h5 indicates:

• GEDI02_A = Product Short Name
• 2019110 = Julian Date of Acquisition in YYYYDDD
• 014613 = Hours, Minutes, and Seconds of Acquisition (HHMMSS)
• O01991 = O = Orbit, 01991 = Orbit Number
• 01 = Sub-Orbit Granule Number
• T04905 = T = Track, 04905 = Track Number
• 02 = Positioning and Pointing Determination System (PPDS) type (00 is predict, 01 rapid, 02 and higher is final)
• 003 = PGEVersion = SDPS Release Number
• 01 = Granule Production Version
• V002 = Version Number
• .h5 = Data Format

In this example of a Version 2 Level 02B product, the filename GEDI02_B_2019110045136_O01993_01_T02061_02_003_01_V002.h5 indicates:

• GEDI02_B = Product Short Name
• 2019110 = Julian Date of Acquisition in YYYYDDD
• 045136 = Hours, Minutes, and Seconds of Acquisition (HHMMSS)
• O01993 = O = Orbit, 01993 = Orbit Number
• 01 = Sub-Orbit Granule Number
• T02061 = T = Track, 02061 = Track Number
• 02 = Positioning and Pointing Determination System (PPDS) type (00 is predict, 01 rapid, 02 and higher is final)
• 003 = PGEVersion = SDPS Release Number
• 01 = Granule Production Version
• V002 = Version Number
• .h5 = Data Format

In this example of a Version 2 Level 03 product, the filename GEDI03_rh100_mean_2019108_2023081_002_05.tif indicates:

• GEDI03 = Product Short name
• rh100_mean = Variable name. There are five measured variables "counts", "rh100_mean", "rh100_stddev", "elev_lowestmode_mean", or "elev_lowestmode_stddev"
• 2019108 = Start Julian Date in YYYYDDD
• 2023081 = End Julian Date in YYYYDDD
• 002 = PGEVersion = SDPS Release Number
• 05 = Granule Production Version
• .tif = Data Format

In this example of a Version 2 Level 04A product, the filename GEDI04_A_2019110045136_O01993_01_T02061_02_002_02_V002.h5 indicates: 

• GEDI04_A = Product Short Name
• 2019110 = Julian Date of Acquisition in YYYYDDD
• 045136 = Hours, Minutes, and Seconds of Acquisition (HHMMSS)
• O01993 = O = Orbit, 01993 = Orbit Number
• 01 = Sub-Orbit Granule Number
• T02061 = T = Track, 02061 = Track Number
• 02 = Positioning and Pointing Determination System (PPDS) type (00 is predict, 01 rapid, 02 and higher is final)
• 002 = PGEVersion = SDPS Release Number. The granules with a release number <=’002’ were processed by the GEDI Science Team at the University of Maryland. Those with a release number >=’003’ were published by the Science Operations Center (SOC) at Goddard Space Flight Center.
• 02 = Granule Production Version
• V002 = Version Number
• .h5 = Data format

In this example of a Version 2 Level 04B product, the filename GEDI04_B_MW019MW223_02_002_02_R01000M_MU.tif indicates:

• GEDI04_B = Product Short name
• MW019MW223 = Starting and ending weeks of the GEDI mission included in the product. Mission week 19 ("MW019") starts 2019-04-18 and mission week 223 ("MW223") ends 2023-03-16
• 02 = Positioning and pointing determination system (PPDS) type  (00 is predict, 01 rapid, 02 and higher is final)
• 002 = Software Release Number (University of Maryland)
• 02 = Granule Production Version
• R01000M = Spatial Resolution (1000M = 1km)
• MU = variable: MU=Mean; V1=Variance Component 1; V2=Variance Component 2; SE=Standard Error; PE=Percentage Standard Error; NC=Number of Clusters; NS=Number of Samples; QF=Quality Flag; PS=Prediction Stratum, MI=Mode of Inference
• .tif = Data Format

In this example of a Version 2 Level 04C footprint product, the filename GEDI04_C_2019110045136_O01993_01_T02061_02_001_01_V002.h5 indicates: 

• GEDI04_C = Product Short Name
• 2019110 = Julian Date of Acquisition in YYYYDDD
• 045136 = Hours, Minutes, and Seconds of Acquisition (HHMMSS)
• O01993 = O = Orbit, 01993 = Orbit Number
• 01 = Sub-Orbit Granule Number
• T02061 = T = Track, 02061 = Track Number
• 02 = Positioning and Pointing Determination System (PPDS) type (00 is predict, 01 rapid, 02 and higher is final)
• 001 = Release number, representing the SOC SDS (software) release used to generate this L4C dataset
• 01 = Granule Production Version
• V002 = Version Number
• .h5 = Data format

In this example of a Version 2 Level 04C gridded product, the filename GEDI_L4C_WSCI_gridded_1km_20190418_20230317_V2.tif indicates: 

• GEDI_L4C_WSCI_gridded = Product Short Name 
• 1km = grid resolution 
• 20190418 = Start Julian Date in YYYYDDD 
• 20230317 = End Julian Date in YYYYDDD
• V2 = Version Number 
• .tif = Data Format 

In this example of a Version 2 Level 04C fusion product, the filename GEDI_L4C_WSCI_FUSION_00N051W_01N050W_20220701_20221001.tif indicates:

• GEDI_L4C_WSCI_FUSION = Product Short Name 
• 00N051W = Lower left geographical limits (southwest corner) 
• 01N050W = Upper right geographical limits (northeast corner) 
• 20220701 = first day considered for SAR acquisitions (SAR dates on or after YYYYMMDD) 
• 20221001 = day after the last day considered for SAR acquisitions (SAR dates before YYYYMMDD) 
• .tif = Data Format

In this example of a Version 2 Level 04D product, the filename GEDI_L4D_UTM60_South_20190418_20230316_rh_098.tif indicates:

• GEDI_L4D = Product Short Name 
• UTM60 = two-digit number of UTM zone 
• South = Hemisphere is the area of terrestrial globe within the corresponding UTM zone (“North” or “South”) 
• 20190418 = First date of the GEDI track used for imputation 
• 20230316 = Last date of the GEDI track used for imputation 
• rh_098 = One of the imputed variables or shot number 
• .tif = Data Format

GEDI Product Long Name

The GEDI Product Long Name (i.e., Collection-Level) convention provides useful information regarding all GEDI products.

Below is an example of a GEDI Level 1B product. All GEDI Footprint-level Product Long Names for Version 2 follow the same basic structure.

The GEDI L1B Geolocated Waveform Data Global Footprint Level V002 collection has the following characteristics:

• GEDI – Instrument
• L1B – Processing Level
• Geolocated Waveform Data – Geophysical Parameter
• Global – Global Coverage
• V002 – Version

The location of the ranging point (also referred to in this document as a bounce point) can be commonly described in terms of geodetic latitude, longitude, and height above a reference ellipsoid, or it can be represented in Cartesian coordinates in an Earth Centered Inertial (ECI) or Earth Centered Fixed (ECF) reference frame.

Several reference frames are used in the precise positioning and precise pointing required for geolocation of GEDI footprints. The Space Station Analysis Coordinate System (SSACS) and GEDI frame are used to orient instruments relative to one another. The Optical Bench Frame (OBF) provides a connection to the GEDI frame and a reference system for targeting calculations. Star tracker frames connect these to the ECI frame allowing conversion to geodetic coordinates.

GEDI products have two sources of metadata: the embedded HDF5 metadata and the external ECS metadata. The HDF5 metadata contains valuable information, including global attributes and dataset specific attributes pertaining to the granule. The ECS (generated by the EOSDIS Core System) .met file is the external metadata file in XML format, which is delivered to the user along with the GEDI product. It provides a subset of the HDF metadata.

The dataset attributes contain specific SDS information, such as the data range and applicable scaling factors for the data. The LP DAAC data products page provides these details within a concise document for each of the products. An HDF5 file also contains core metadata essential for search services. It should be noted that it is difficult for a standard HDF call to interpret HDF5 geolocation or temporal information without further knowledge of the file structure.