Forest Canopy Height in Mexican Ecosystems


Airborne light detection and ranging (lidar) data have great potential to map vegetation structure at a fine resolution, including estimating carbon stocks, canopy closure, and tree height. While airborne-lidar-derived vegetation structural measurements could play an important role in ecological restoration monitoring, these data are limited to only a tiny fraction of the Earth’s surface. Data fusion to combine high-resolution lidar data with medium resolution satellite data (such as Landsat imagery) represents one way to extend the spatial and temporal reach of airborne data.

This data set includes 1,105 aerial images captured over Mexico as part of the NASA G-LiHT program, along with lidar-derived canopy height values and Landsat-derived vegetation indices for 499,925 sample points within those images.

The associated open-source repo provides tools required to replicate this sampling methodology.

Data format

G-LiHT images are in GeoTIFF format.

Annotations are provided in a .csv file with 499925 rows, each representing one sample, and 12 columns:


If you use these data in a publication or report, please use the following citation:

Requena-Mullor JM, Caughlin TT. Lidar-derived canopy height data and Landsat-derived vegetation indices for the G-LiHT NASA acquisitions in Mexico. Dataset.

Contact information

For questions about this data set, contact Juan Miguel Requena Mullor (


G-LiHT images are released according to NASA’s Data and Information Policy.

The .csv file containing canopy height and vegetation information is released under the Community Data License Agreement (permissive variant).

Download links

Metadata (GCP link, 21MB)
Metadata (Azure link, 21MB)
Metadata (AWS link, 21MB)

Images (62.9GB) are available in the following cloud storage folders; see LILA’s direct image access guide for download instructions.

  • gs://public-datasets-lila/boise-state-vegetation/tifImages (GCP)
  • s3:// (AWS)
  • (Azure)

Having trouble downloading? Check out our FAQ.

Posted by Dan Morris.