Data Availability

The table below presents the start dates of records for each variable–timestep combination, covering data through 2025.

ET Variables

*ET data with a spacial CIMIS reference is only available starting from 2003.

2.0

Model	Daily	Monthly	Geodatabase (Monthly)	Regional Availability
Ensemble	2016	2000	2016	Western US
SIMS	2016	2000	2016	Western US
eeMETRIC	2016	2000	2016	Western US
DisALEXI*	2016	2001	2016	Western US
geeSEBAL	2016	2000	2016	Western US
PTJPL	2016	2000	2016	Western US
SSEBOP	2016	2000	2016	Western US

2.1

Model	Daily	Monthly	Geodatabase (Monthly)	Regional Availability
Ensemble	2016	2000	2016	CONUS
SIMS	2016	2000	2016	CONUS
eeMETRIC	2016	2000	2016	CONUS
DisALEXI	2016	2001	2016	CONUS
geeSEBAL	2016	2000	2016	CONUS
PTJPL	2016	2000	2016	CONUS
SSEBOP	2016	2000	2016	CONUS

*DisALEXI is only available back to 2001 due to model design and input limitations.

Meteorological Variables

1.0

Variable	Daily	Monthly	Geodatabase (Monthly)	Regional Availability
Landsat NDVI	2016	2000	2016	Western US
gridMET Bias-Corrected ETo	2000	2000	2016	Western US
gridMET Pr	2000	2000	2016	Western US
Spatial CIMIS ETo	2003	2003	2016	Western US

2.0

Variable	Daily	Monthly	Geodatabase (Monthly)	Regional Availability
Landsat NDVI	2016	2000	2016	CONUS
gridMET Bias-Corrected ETo	2000	2000	2016	CONUS
gridMET Pr	2015	2000	2016	CONUS
Spatial CIMIS ETo	2003	2003	2016	CONUS

For retrieval of large volumes of data, users are encouraged to retrieve OpenET data directly from the OpenET data archives in the Google Earth Public Data Catalog. Data will be periodically added so check back often.

The following v2.0 datasets are available from 2000-2024 on Google Earth Engine:

• Ensemble Monthly ET

• eeMETRIC Monthly ET

• SIMS Monthly ET

• PT-JPL Monthly ET

• SSEBop Monthly ET

• DisALEXI Monthly ET *

• geeSEBAL Monthly ET

Users may register their Google Earth Engine account using their Cloud Project ID in their OpenET profile. Linking a user’s Cloud Project ID to their OpenET account will increase quota limits.

Users may still need to break larger queries into smaller units (in terms of spatial area or time period) to avoid memory timeout errors on Earth Engine.