Change Log
Here you can find release highlights, bug fixes, and other updates as we continue to develop and improve the OpenET API.
Last updated
Here you can find release highlights, bug fixes, and other updates as we continue to develop and improve the OpenET API.
Last updated
Count Variable (Model Only Addition)
Added support for retrieving the number of cloud-free satellite observations using the count
variable in OpenET models. This feature is available exclusively for monthly model collections and not the model ensemble.
Example: The image below demonstrates the average monthly coverage for 2023, with the number of observations ranging from 1 (red) to 6+ (blue).
Model Count Variable (Ensemble Only Addition)
For the monthly Ensemble collection only, view the number of models contributing to each observation using the model_count
variable.
Example: The image below demonstrates the average monthly model inclusivity coverage for 2023, with the number of observations ranging from 1 (red) to 3 (orange) to 5+ (blue).
Precipitation Bug (Fixed)
Fixed a bug where resampling would run into issues in masked regions along the west coast.
Account Initialization Bug (Fixed)
Fixed a issue which would add additional latency when querying across multiple accounts. This will result in overall faster queries.
Raster Queries Timestep Increase (Improvement)
Enhanced memory handling for daily raster data retrieval via the multipolygon endpoint. Users can now retrieve data for up to 366 timesteps (previously limited to 62), enabling more comprehensive analyses. Be wary of running into memory limits for complex or large areas.
2008-2012 Added to Public Data Catalog (Addition)
OpenET monthly model datasets are now available from 2008-2023 in the Google Earth Engine public data catalog and are now accessible through the API.
Daily Data Interpolation with different Date Ranges (Fixed)
Fixed a bug where the API would return a different value for interpolated data depending on the date range.
FRET Stack Bug (Fixed)
Fixed a bug where the API would return only the first day of a forecasted reference ET.
Geodatabase Queries (Improvement)
The latest updates have significantly reduced latency for large queries, resulting in an average speed improvement of 1.6x for all geodatabase returns.
Quota Max Area Bug (Fixed)
Fixed an issue where if a query exceeded the users quota an incorrect error message would return.
date_ingested
(Deprecated)We are updating the metadata keyword from date_ingested
to build_date
.
2013-2015 Added to Public Data Catalog (Addition)
OpenET monthly model datasets are now available from 2013-2023 in the Google Earth Engine public data catalog and are now accessible through the API.
EECUs Showing 0's (Fixed)
Fixed a bug which was not correctly displaying EECU compute use for exported data.
Super Sampling to 10m (Addition)
Raster image generation now supports 10m resampling for increased fidelity for analysis.
Rapid Query Issue (Fixed)
When querying the API rapidly some requests return a 401 error incorrectly. This is now resolved.
Upload geoJSON (Fixed)
Fixed a bug when using the account/upload endpoint in which the resulting call to retrieve the file would fail during high volume server autoscaling.
Using NOAA's FRET product eto data can now be queried for 7 day forecasts. Change reference_et
to "fret"
and date_range
to the current day and 7 days into the future. Note this is experimental and has not yet been fully evaluated for accuracy.
We've increased the limit from 365 days to 10 years. With large polygons, you can run into memory limits with this update.
When using the multipolygon endpoints the hectares and megaliter calculations were off by a factor of 10.
Exports to a personal Google Bucket are now supported. This new parameter supersedes drive exports even if your Cloud Project is linked. See FAQ for more details.
queue_number
(Deprecated)Calculating queue placement has become too slow with the latest updates to the Earth Engine API and our growing user base. This return feature has been removed which will on average result in a 42x time reduction when exporting files.
In some areas precipitation data preloaded in the geodatabase was incorrectly projected resulting in erroneous data.