Accuracy & Known Issues

Understanding Accuracy in OpenET

At OpenET, transparency and scientific rigor are core values. This page offers a clear overview of how accurate our evapotranspiration (ET) data are across different models, regions, and land cover types.

We also provide guidance on how to interpret the data for different use cases — including where data are most reliable and where uncertainties may be greater. In addition, this page serves as a central hub for reporting known issues, such as technical bugs, anomalies in data outputs, or temporary limitations in platform tools. This is an ongoing effort, and the information here will be updated regularly as the OpenET team and community identify new issues or make progress in resolving existing ones.

Accuracy Summary for Croplands for
the OpenET Ensemble ET Value

Time Period
Slope
Mean Bias Error
Mean Absolute Error
Root Mean Squared Error
r-squared
Mean flux tower ET
Water Year:
16 sites with 72 total water years
0.91
-73.91 mm (-7.5%)
112.12 mm (11.3%)
121.87 mm (12.3%)
0.84
991 mm
Growing Season:
39 sites with 177 growing seasons
0.96
-11.9mm (-2.0%)
78.14 mm (12.9%)
93.79 mm (15.5%)
0.87
605 mm
Monthly:
46 sites with 1,791 total months
0.92 (n = 53)
-5.27 mm (-5.8%)
15.84 mm (17.3%)
20.44 mm (22.4%)
0.90 (n = 53)
91 mm
0.86 (n = 60)
-0.35 mm (-10.0%)
0.83 mm (23.6%)
1.09 mm (31.1%)
0.81 (n = 60)
3.5 mm

Summary of Information

Satellite-derived OpenET data were compared against ET measurements collected by 151 flux tower stations and four precision weighing lysimeters located throughout the continental U.S. The key results for croplands are summarized below, and information for other land cover types will be provided in the OpenET Intercomparison and Accuracy Assessment Report, along with the technical details of the methods used in the assessment. Descriptions of the methods used to calculate the satellite-derived ET values are available in the Methodologies page.

For croplands, the ensemble performed as well as or better than any individual model across most accuracy metrics, though nearly all models demonstrated high accuracy measures for croplands. Accuracy metrics for the slope of the best fit line through the origin (slope), mean bias error (MBE), mean absolute error (MAE), root mean squared error (RMSE), and r-squared (r2) value are summarized in the table below for the water year (October-September), growing season (determined dynamically, as described in the full report), and monthly and daily timesteps. 

At annual timescales, 16 sites had data for at least one full water year, which required at least 12 consecutive months of data and a minimum of one cloud-free Landsat satellite observation per month. The data records for these 16 sites included 72 total water years. The OpenET ensemble value had a slope of 0.91, and MAE and RMSE values of <10%, with an r2 value of 0.84, demonstrating excellent overall agreement with the flux tower data. The MBE was -7.9%, which is still excellent, but indicates a small negative bias in the ensemble ET value relative to the ground-based ET, and this bias should be accounted for in evaluating annual ET totals. 

For the growing season, 39 sites had at least one complete growing season with a total of 177 complete growing seasons across these sites. The OpenET ensemble value had a slope of 0.96, MBE of -2.0%, MAE of 12.9%, RMSE of 15.5%, and r2 of 0.87. These results demonstrate very strong agreement between the ensemble value and the ground-based ET datasets during the growing season. The slope of 0.96 and MBE of -2.0% indicates that on average, the ensemble ET value has almost no bias during the growing season, and when combined with the low MAE and MBE and high r2, demonstrates good accuracy across a wide range of crops and meteorological conditions.

At a monthly timestep, 44 sites (53 sites for slope and r2) had at least three full complete months of data with a minimum of one cloud-free Landsat overpass per month, and a total of 1,638 months in the dataset (1652 months for slope and r2). The OpenET ensemble value had a slope of 0.92, MBE of -5.8%, MAE of 17.3%, RMSE of 22.4%, and r2 of 0.90. The slope near 1.0, minimal bias error, and very high r2 indicate excellent overall accuracy for the ensemble ET value at monthly timescales with near-zero bias. The MAE of 17.3% and RMSE of 22.4% are still very good, but slightly above the OpenET target of <15% at a monthly timestep. The low bias error suggests that the higher MAE and RMSE are likely due to random error in both the satellite and ground-based datasets, as well as periodic error in the satellite data when monthly values are calculated from only one or two cloud-free satellite observations. The OpenET team will be working on integration of Sentinel-2, and future NASA and European Space Agency missions to increase the observation frequency, and further reduce the MAE and RMSE values at monthly timesteps.

At a daily timestep, 52 sites (60 sites for slope and r2)  had at least 6 daily observations concurrent with satellite observations, with a total of 5,225 total paired daily estimates in the dataset (5,255 days for slope and r2). The OpenET ensemble value had a slope of 0.86, MBE of -10.0%, MAE of 23.6%, RMSE of 31.1%, and r2 of 0.81. These accuracy metrics are all very good, though as expected, at a daily timestep the influence of random error increases. The effects of outliers due to cloud contaminated pixels or model errors also have a stronger influence, especially during the winter months when ET rates are low. Overall, the slope, MBE, and r2 values are considered to be very good to excellent, and indicate good overall accuracy. The MAE and RMSE values were slightly above the OpenET target of 20%, and it will be important that this uncertainty is accounted for in irrigation management applications. The work described above to improve the monthly data products is expected to also improve the ensemble ET accuracy at daily timesteps.

For water resource management and water accounting applications, the low bias error at all timesteps indicates that over large areas, the random error that affects the monthly and daily data should partially cancel (Allen et al., 2007), and the OpenET ensemble value should be highly accurate. The bar graph below shows the average growing season ET across all flux tower sites (both closed and unclosed) along with the average ET for the ensemble value and each of the individual models. While all models agree very well and are within +/- 15% of the average flux tower ET, the OpenET ensemble value is within 2% (10 mm) of the average growing season ET measured by the flux towers, following correction for energy balance closure.

Average Total Growing Season ET (n=39 sites and 177 total growing seasons). The solid line indicates the mean closed station ET for croplands and the dashed lines represent +/- 10% of the mean.

In considering these results, it is important to note that most cropland sites were located in expansive regions with well-watered crops. In these regions, (including most of California’s Central Valley and Delta, and most agricultural regions in the Midwest), the ensemble value appears to provide the most reliable and stable estimate of ET. However, when looking at the limited number of cropland in-situ flux stations located in very arid environments, there is evidence that some models have a systematic low bias for smaller agricultural areas in very arid regions. In these areas, the MAD (median absolute deviation) outlier filtering approach does not filter outliers as desired due to the large range in ET values from the ensemble relative to the ensemble median, resulting in a low bias in the ensemble ET value. Over the coming months, the team will continue to conduct additional research in these more challenging settings. As the ensemble calculation evolves based on this research, additional comparisons will be conducted and this page will be updated, along with our Best Practices Manual.

For more details and results for natural land cover types (evergreen forests, mixed forests, grasslands, shrublands, and wetland/riparian), see the OpenET Intercomparison and Accuracy Assessment Report. Accuracy metrics were more variable for some natural land cover types than for croplands, but demonstrated good overall accuracy. A positive bias in the ensemble ET was identified in evergreen forests, mixed forests, and wetlands, and monthly MAE and RMSE values were higher than the OpenET target accuracies, highlighting areas for future research. Quantifying the accuracy of both the individual models and the ensemble ET value is an important first step, and will allow water managers and agricultural producers to account for uncertainty in ET estimates when integrating data from OpenET  into water management applications. An important part of the mission for OpenET.org is to continue advancing the underlying science, and the OpenET team will continue to improve the ensemble value and individual model accuracies.

OpenET selected five key metrics to characterize the accuracy of OpenET data:
  • Slope: The slope of the best-fit line forced through the origin provides a measure of how the satellite ET data scale compared to the ground-based ET data. A slope of less than 1.0 indicates that the satellite ET data tend to be lower than the ground-based ET data (underestimation), and a slope greater than 1.0 indicates that the satellite ET data tend to be higher (overestimation). Because the line is fit using all data points, days or locations with higher ET values have a stronger influence on the slope. A slope of 1.0 indicates no consistent scaling difference between the two, and values between 0.9 and 1.1 are generally considered excellent for remotely sensed ET.
  • Mean Bias Error (MBE): As the name suggests, MBE provides a measure of overall bias and is closely related to the slope. MBE quantifies the bias in the satellite ET data relative to the ground-based ET data, and characterizes the expected overall error when the remotely sensed ET data are aggregated over large areas. A negative bias indicates that the satellite ET data are, on average, less than the ground-based ET data. A positive bias indicates that, on average, the satellite ET data are greater than the ground-based ET data. A value of zero would represent no bias, and values in the range of +/- 10% are considered excellent for remotely sensed ET.
  • Mean Absolute Error (MAE): MAE provides a measure of the expected error for a given location and time period, and quantifies the average absolute difference between the satellite and ground-based ET data. Since MAE provides the absolute error, the value is often considered to characterize typical expected error both above and below the reference data. A value of zero represents perfect agreement and values in the range of 0-15% (interpreted as up to +/-15%) are considered excellent for remotely sensed ET data over agricultural lands. Accuracy requirements for remotely sensed ET vary by application, however, values in the range of 0-25% are considered to be very good and acceptable for many applications. MAE includes random error in both the satellite-based ET data and the ground-based ET data that are used as a reference. When MBE is much lower than MAE, it may indicate that random error in the satellite data is the primary contributor to error, or that error in the ground-based reference ET is also contributing to the MAE. When MAE and MBE are similar in magnitude, it usually indicates that error is due to a persistent bias in the satellite-based ET data.
  • Root Mean Squared Error (RMSE): RMSE is another widely used measure of the expected error for a given time and location. It is interpreted in the same way as MAE, but provides greater weight to outliers or large ‘misses’ in the satellite-based ET data. RMSE may be used as a measure of expected error when the intended use of the data is sensitive to large errors in the satellite data for any given location or time period. A value of zero represents perfect agreement, and values in the range of 0-25% RMSE are generally considered to be very good for satellite-based ET data.
  • r-squared: The r-squared value provides a measure of the proportion of the variance in the ground-based ET data that is explained or reproduced by the satellite-based ET data. It can be interpreted as a measure of the ability of the satellite-based ET to accurately estimate the relative magnitude of ET in the ground-based ET data. A value of 1.0 would mean that the satellite-based ET data explains 100% of the variance in the ground-based ET data. Values above 0.6 are considered to be very good, and values above 0.85 for remotely sensed ET data are considered to be excellent. It is important to note that a model can have an r-squared value near 1.0, and still have a consistent high or low bias.

Landsat Collection v2.0 Known Issues Impacting OpenET

OpenET uses Landsat imagery that’s been specially processed and filtered to improve accuracy for evapotranspiration (ET) modeling and water applications.

Data gaps/holes over Colorado/Kansas & Texas

In certain areas of Colorado, Kansas, and Texas, some ET images include small regions of missing data. These gaps are linked to missing information in the Landsat Collection 2 Level 2 land surface temperature (LST) product, which is caused by data gaps in the ASTER Global Emissivity Dataset (GED). For more details, please refer to the Landsat Collection 2 Known Issues.

Example:

Large region of missing data over the Colorado/Kansas border (largest hole is ~30 x 60 km).

Example:

Large region of missing data over central Texas (~5 x 45 km)

Impact

The DisALEXI, GEESEBAL, PTJPL, and SSEBop models are affected by these data gaps and will therefore show no data in the impacted regions. EEMETRIC is not affected because it internally generates a sharpened LST product using filled emissivity data and raw thermal radiance rather than relying on the Level 2 LST product. SIMS is also unaffected since it does not use the LST product in its calculations. As a result, in these areas, the OpenET ensemble is based on data from only one or two models (EEMETRIC and SIMS over agricultural land cover types, and EEMETRIC alone over non-agricultural land cover types).

In addition to the two large affected areas mentioned, smaller clusters of missing data are scattered throughout the central United States. The full extent of these regions can be explored using the ASTER GED emissivity layer here.

Action

OpenET has developed a solution to address these data gaps, building upon the methodology used in the EEMETRIC model. This fix will be incorporated into the next OpenET data collection release.

Blockiness & invalid ET values resulting from anomalies in LST calculation

Some ET images for certain models may exhibit pronounced “blockiness” and invalid ET values. This issue stems from problems with the emissivity data used to generate the Landsat Collection 2 Level 2 LST product. Detailed information on these emissivity issues can be found on the Landsat Collection 2 Known Issues page.

Example:

Example of blockiness and artifacts in SSEBop ET for image from May 2023 near Amarillo, TX.

Example:

Example of the ensemble ET for the same location and date as the image above. The blockiness and artifacts are still present but not as prominent.

Impact

These artifacts and blockiness are most evident in the SSEBop and GEESEBAL model outputs because both rely directly on the uncorrected LST data as a primary input. SIMS is unaffected since it does not use LST in its calculations, and PTJPL is only indirectly influenced by LST, resulting in less noticeable impacts. EEMETRIC and DisALEXI are either unaffected or minimally affected because they utilize sharpened LST products that mitigate the impacts from degraded emissivity data. The OpenET ensemble is only minimally impacted, as it integrates data from all six models and thus dilutes the effect of any single model’s input anomalies.

Action

OpenET has developed a fix for this issue that will be applied in the next OpenET data collection release.

Landsat 7 Scan Line Corrector (SLC) Off Data Gaps

The scan line corrector (SLC) on Landsat 7 failed on May 31st, 2003, resulting in wedge shaped gaps (or “stripes”) in all images collected after that date. The SLC-off images contain data for ~75% of the nominal scene area, with the center of the scene having full coverage while the gaps increase in size toward the edge of the scene.

Example:

Example of Landsat 7 SLC-off striping in a single overpass image.

Example:

Example of SLC-off striping artifacts in the OpenET ensemble monthly ET.

Example:

Example of SLC-off striping resulting in “no data” gaps for monthly ET images in 2012.

Impact

All models and the OpenET ensemble are affected by the presence of the Landsat 7 SLC-off data gaps. Artifacts resulting from SLC-induced striping may be present in all monthly ET images from May 2003 to Jan 2022, and may result in a decrease in the number of clear observations and an increase in uncertainty for pixels for which the SLC issue resulted in fewer Landsat observations within each month during this period. The impact of the striping in the Landsat overpass images is moderated in the monthly ET images, since the interpolation process uses all available Landsat observations, including images in neighboring WRS2 “paths”. Also, there was a second Landsat satellite operating during most of this time period providing additional observations to interpolate from.

The data gaps resulting from the SLC failure are especially problematic in scenes for the period from November 2011 through May 2013, after the Landsat 5 mission ended and before Landsat 8 was launched, and there may be insufficient cloud free observations to compute a monthly ET image for some regions. Users are encouraged to consult the metadata layers that provide information on the number of cloud-free scenes that were used to generate monthly data for each pixel during this time period. Pixels with fewer cloud-free observations per month are generally expected to have higher uncertainty from temporal interpolation and users are advised to account for this higher uncertainty in applications of OpenET data that require data during this time period.

Action

There is currently no plan to perform any additional or separate filling of the Landsat 7 SLC-off data gaps in the next collection release. Users are encouraged to conduct additional evaluation of the OpenET monthly ET data for 2012 for applications where absolute accuracy of the monthly data is an important consideration.

Clouds not always flagged as cloud in QA_PIXEL band

In OpenET Collection v2.0, the cloud mask bits from the QA_PIXEL band were used directly to remove pixels identified as cloud, shadow, dilate, cirrus (Landsat 8/9), and snow (for all models except EEMETRIC). If a cloud is not flagged in the QA_PIXEL band, it will not be masked and will be included in model calculations unless the individual model applies its own additional masking.

Example:

Examples of unmasked clouds shown with the true color Landsat image on the left, and the cloud masked image is shown on the right. The cloud mask images are light blue for snow, dark blue for shadow, gray for cloud, and purple for water.

Unmasked clouds/fog in California Central Valley (in bottom left corner of image).

nmasked clouds over Texas.

Smoke is often not masked correctly.

Another example of unmasked clouds.

Impact

All models and the OpenET ensemble are affected by the presence of unmasked clouds. Although the full magnitude and significance of this impact are not yet well understood, models do not handle these cloud-affected pixels as intended. Unmasked clouds often result in extreme ET data values—either unusually high or low—because the land surface temperature (LST) values are cold, while the associated reflectance values are frequently saturated and unreliable.

While monthly interpolation, and outlier flagging and removal used in calculation of the ensemble ET value, helps to moderate these extreme values, some of the resulting artifacts may still propagate into the ensemble. For example, in the figure below there are noticeable regions of high ET (darker green) in the OpenET ensemble that appear clipped to the Landsat WRS2 tile boundary. The model ET images for the same date show large differences in the model values that lead to much more variation in the ensemble value.

OpenET Ensemble Monthly ET for Oct. 2009 over central Texas with the WRS2 path 27 row 39 tile boundary shown.

Cloud masked true color Landsat image for this same tile collected on Oct 13th, with more than half of the image having unmasked clouds. The CLOUD_COVER_LAND property that is used to screen for cloudy images is computed using the QA_PIXEL band, so this image has a CLOUD_COVER_LAND value of 41% and would not be automatically excluded.

Model ET images for the same month and region for (a) DisALEXI, (b) EEMETRIC, (c) GEESEBAL, (d) PTJPL, (e) SIMS, (f) SSEBOP. GEESEBAL and SSEBop both show very high ET for the unmasked cloud portions, while PTJPL returns ET values near 0.

Action

In OpenET Collection v2.1, enhanced quality control measures are being implemented to address the issue of unmasked clouds. Specifically, Landsat scenes containing extensive unmasked cloud cover will be excluded from use in calculation of ET values. Additionally, for a small subset of scenes that are otherwise mostly clear but contain unmasked clouds, a similar ACCA-based cloud score calculation will be applied to provide supplemental masking and improve data quality.

Misclassified cloud and snow pixels in QA_PIXEL band (EEMETRIC Only)

Cloud and snow pixels are frequently misclassified in the QA_PIXEL band. For most models, this is not problematic since both cloud and snow are masked out based on the QA_PIXEL classification. However, EEMETRIC does not mask out snow pixels because it applies an aerodynamic function to estimate sublimation from snow, making it more susceptible to misinterpretations—either treating cloudy pixels as snow or failing to properly include snow-covered pixels.

Examples:

September image over Wyoming with clouds flagged as snow shown in light blue.

Image from May over North Dakota with clouds flagged as snow shown in light blue.

Another image from May over Georgia (that was not used in Collection v2.0) but clearly shows clouds that are misclassified as snow (the light blue areas).

Impact

Only the EEMETRIC model is directly affected by the misclassification of snow and cloud pixels because it applies an aerodynamic sublimation function to snow. All other models mask both of these conditions and do not provide estimates. The exact impact on ET values is currently unknown, but misclassified pixels can produce ET fractions anywhere from 0 to 1, potentially increasing uncertainty. Moreover, the OpenET ensemble may also be influenced, as it can produce a value even when only a single model (such as EEMETRIC) is contributing data (see Issue 8). This may occur when other models report NoData due to snow cover, and eeMETRIC is the only model that is run.

Action

No action is being taken at this time. The EEMETRIC team has reasonable confidence in its sublimation estimates and does not plan to mask snow in future collections.

Clear scenes along the coast sometimes flagged as all shadow in QA_PIXEL

Coastal scenes are sometimes flagged as all shadow in the QA_PIXEL band if the ocean is very cloudy and/or bright. All of the models are masking using the shadow bit in the QA_PIXEL band and will exclude these areas or scenes.

Example:

Example of clear coastal pixels being flagged as shadow.

Impact

For all models and the ensemble, coastal regions may have increased uncertainty as a result of having fewer Landsat scenes to interpolate between, and there may be fewer monthly values overall.

Action

OpenET is identifying Landsat scenes with this issue and may consider manually building the cloud mask for some or all of these images so they can be included in the OpenET data Collection v2.1.

Water pixels may be masked out due to negative at-surface reflectance values

Clear water pixels can sometimes yield negative at-surface reflectance values in Landsat Collection 2 Level 2 images. When using the ee.Image.normalizedDifference() function in Google Earth Engine (GEE) on these values, the function will return masked pixels if the inputs are negative. In contrast, manually computing the normalized difference index (e.g., NDVI) will produce unmasked pixels. However, these values may vary widely, swinging between extremely positive and negative, due to the small (or negative) denominators in the calculation.

Example:

The example shows conditions over Lake Tahoe, where large portions of the lake have very low or negative at-surface reflectance values. When NDVI is computed using the GEE .normalizedDifference() function (middle image), negative values become masked. By manually computing NDVI (image on the right) the resulting pixels are not masked, but the NDVI values can be extremely high or low because of the small values in the denominator.

The missing data can be seen in the NDVI time series for Lake Tahoe using the OpenET Data Explorer.

Impact

This issue has been confirmed in PTJPL and SSEBop and may also affect other models, including DisALEXI and EEMETRIC. The extent of the impact is not fully understood, but it may contribute to increased uncertainty in areas with clear water pixels.

Action

In future model versions, water pixels may be identified more reliably by leveraging the QA_PIXEL band water mask, either in place of or as a supplement to normalized difference index methods. If normalized difference indices continue to be used, additional filtering or processing will be implemented to reduce extreme value swings. Improved detection of water pixels will help determine where and when open-water-specific routines or masking should be applied. See Issue 10 for more information on open water estimates.

Single Landsat coverage for 2012 and early 2013

There have been two Landsat satellites operating concurrently for the full time period of OpenET Collection v2.0, except for the approximately one and half year gap in between the end of Landsat 5 observations in November 2011 and the launch and commissioning of Landsat 8 in May 2013. A single Landsat satellite will revisit the same location on the Earth every 16 days. When there are two Landsats operating, the orbits are offset such that they will revisit the same location every 8 days. The actual number of useful observations is greatly impacted by clouds, fog, smoke, sensor gaps, etc. and tends to be much lower than the nominal values, except for more arid regions such as the southwestern United States.

Example:

Number of cloud free observations in a) 2011 from Landsat 5 and Landsat 7 and b) 2012 from only Landsat 7. The areas of image overlap between the Landsat “paths” can be clearly seen, and may have up to twice as many cloud free observations. More yellow color indicates higher numbers of available clear scenes, whereas darker blue colors indicate lower numbers of clear scenes and clear pixels.

Number of SSEBop monthly ET images in 2011 and 2012 after masking all ET values with a count value of 0 to avoid the bad data discussed in Issue 9 below. More yellow color indicates higher numbers of available clear scenes, whereas darker blue colors indicate lower numbers of clear scenes and clear pixels.

Action

Users are encouraged to consult the metadata layers that provide information on the number of cloud-free scenes that were used to generate monthly data for each pixel during this time period. Pixels with less than one cloud-free observation per month are generally expected to have higher uncertainty, and users are advised to account for this higher uncertainty in applications of OpenET data that require daily or monthly data during this time period.

Impact

All models and the OpenET ensemble are affected and will have fewer cloud free observations, more data gaps, and potentially higher uncertainty. This issue is magnified by the interpolation issue discussed in Issue 9 below.

Monthly ET values with a “count” band value of 0 may be invalid

Due to a known issue in the interpolation process, some monthly ET values may have been computed using only a single day of data from outside the target month. This scenario can occur when no cloud-free Landsat observations exist within the month itself, resulting in monthly ET values with a “count” band value of 0, and thus the Landsat scenes used to compute ET may not accurately reflect conditions within that month. Background The OpenET interpolation process generates daily ET values for each day in a given month by referencing all available model ET values derived from cloud-free Landsat images within a ±32-day window of the target date. When cloud-free data points exist both before and after the target date, daily EToF values are linearly interpolated, where EToF is ET expressed as the fraction of reference ET on any day. This allows for a continuous time series, even if there are no valid Landsat observations during the month in question. For example, if data from January 30 and March 3 are available, ET values for all days in February can still be interpolated. However, if no valid ET values exist both before and after a given date, the interpolation defaults to using the single closest EToF observation within that 32-day window. While this ensures that daily ET values are generated even for months without any direct cloud-free observations, it can lead to a situation where every day in a month is assigned the same EToF value derived from a single observation outside that month. Consequently, the monthly ET is summed from daily values that were never truly “interpolated” from observations inside the month, and the “count” band—intended to track the number of cloud-free Landsat observations used in the interpolation—will register zero. In such cases, the monthly ET values are considered unreliable since they are not truly representative of the target month’s conditions. This issue is being addressed, and future releases will ensure that monthly ET estimates are only calculated when suitable data are available within or adjacent to the month. Impact Monthly ET values with a “count” band value of one or more are unaffected by this issue. Monthly ET data values for any model with a count of zero may be affected, but the overall impact on total growing season ET for recent years is likely minimal, since zero-count months typically occur during winter or outside the primary growing season. However, regions and time periods characterized by extensive cloud or snow coverage, or where Landsat coverage is limited, such as single-satellite coverage (Issue 8) or the SLC-off period (Issue 3), may experience a more pronounced effect. In these cases, users may notice more monthly ET values than would be expected and lower-than-expected ET values, as they are generated from fewer than 30 or 31 days of data.

Example:

Comparison of the number of monthly SSEBop images in 2021 before and after fixing the interpolation issue. The coverage on the left corresponds to what is currently in Collection v2.0

Action

OpenET has developed a fix that will be implemented in the next collection release. Until the fix is available, users are advised to rely only on monthly ET values with a “count” band of at least 1. Additionally, OpenET is evaluating further refinements to the interpolation process for potential inclusion in future releases.

High uncertainty for evaporation estimates for open water

OpenET models show high variability, large spread, and inconsistent estimation over large open water bodies (lakes, reservoirs, etc.).

Examples:

Model ET images for July 2022 of Folsom Reservoir for (a) DisALEXI, (b) EEMETRIC, (c) GEESEBAL, (d) PTJPL, (e) SIMS (is not run for water pixels), (f) SSEBOP.

Action

Energy partitioning in water bodies complicates evaporation calculation due to the large heat storage capacity of lakes creating a lag between incoming solar radiation and LE. Additionally, diurnal variation in LE over lakes is typically driven by wind speed and vapor pressure gradients complicating scaling from instantaneous to 24-hour ET values. While some models in OpenET use open water subroutines (i.e. PT-JPL/AquaSEBS, eeMETRIC), many rely on core ET algorithms that were not developed for calculation of ET over open water. Last, most gridded weather datasets do not consider water bodies and their influence on local atmospheric conditions. Similar to evaporative cooling effects in agricultural fields, conditions over water bodies are typically cooler and more humid. Furthermore, wind speeds differ from land surfaces over open water due to changes in surface roughness.

At this time, OpenET data values over large water bodies should be considered experimental and not used for operational decision making or planning. Additional research and review to improve calculation of ET values over open water is underway and will be incorporated in future releases.

Extreme values in DisALEXI monthly ET

There are regions of invalid extreme high and negative ET values in the DisALEXI monthly ET.

Examples:

Maximum of all DisALEXI monthly ET values for the full dataset (a) and zoomed in on Texas (b), with scaling adjusted to highlight the high ET values.

Example of extreme values in the DisALEXI monthly ET image for Sept. 2021.

Impact

The DisALEXI monthly ET values are impacted, but for the most part, these high ET values are being flagged as outliers and filtered/dropped in the ensemble calculation process. The majority of the extreme values are clustered in Texas, but smaller patches can be found throughout the dataset. The extreme values tend to result from a single bad overpass image and only impact one or two months.

Action

The DisALEXI modeling team is working on updates to the model to remove these values, with the goal of incorporating these improvements into the next collection release. Users are encouraged to check for extreme values if they are using the DisALEXI monthly ET data.

Spurious data in ensemble collection over portion of Michigan Lower Peninsula

There are a relatively small number of spurious or unmasked pixels in the ensemble image collection over Michigan that are not present in any of the models.

Example:

Impact

Only the OpenET ensemble monthly ET values for a subset of months in 2020 over the Michigan Lower Peninsula are impacted.

Action

These values will either be masked in the next collection release, or the study area will be expanded to include some or all of the eastern U.S. Until that time, users should only use OpenET Collection v2.0 data within the CONUS portions of UTM zones 10-15.

Limited availability of crop type and field boundary information prior to 2007

Prior to 2007, the USDA Cropland Data Layer was produced using different methods and with limited geographic coverage. This limits the ability of OpenET to identify perennial crops and hay pasture crops reliably prior to 2008. OpenET currently uses a combination of the USGS National Land Cover Database for 2001 and 2006 in combination with the USDA Cropland Data Layer for 2008 to identify agricultural pixels and identify perennial crops and grass/hay, creating additional uncertainty in the annual crop type data layers used by OpenET prior to 2008.

Example of Cropland Data Layer coverage for 2005 showing coverage for a subset of the states:

Impact

This impact mostly impacts the SIMS and EEMETRIC models, which have the ability to run specific functions within the models to increase expected accuracy for perennial crops. Applications of data from these models for perennial crops prior to 2008 should assume higher uncertainty relative to the period from 2008 to present.

Action

OpenET will undertake analyses to assess expected changes in accuracy resulting from the limited availability of crop type information prior to 2008, and to assess any trends or patterns in ET data prior to 2008 relative to the period from 2008 to present. One key challenge, however, is that few accurate ground-based ET datasets exist to rigorously evaluate model performance prior to 2008 at the scale of individual fields.

See How OpenET's Data is Used

How to Use Our Data

See how ET data can be used to understand greater water usage impact.

What Is ET?

Start learning about evapotranspiration and the importance of it's corresponding data.

Trainings & Tutorials

Take a look at step by step instructions and videos to see how to start utilizing ET data.

Filling the Biggest Data Gap
in Water Management

As we expand globally, our mission remains the same: deliver open, reliable, and actionable water data—developed with users, for users.