Raster
Gridded raster retrieval and custom data services.
Last updated
Gridded raster retrieval and custom data services.
Last updated
Note: daily data is limited to 10 year retrievals for this endpoint.
Supports queries against OpenET's raster datasets for timeseries data summarized for a single point.
Take a look at how you might call this method:
Note: daily data is limited to 10 year retrievals for this endpoint.
Provides support for queries against OpenET's raster datasets summarized for a polygon specified by a list of longitude latitude pairs.
Take a look at how you might call this method:
Note: daily data is limited to 1 year retrievals for this endpoint.
Provides support timeseries queries against OpenET's raster datasets summarized for multiple polygons specified by an Earth Engine asset ID or temporary uploaded GeoJSON file. For more information on Earth Engine assets, see the Earth Engine page.
The results of this endpoint will generate a 5 minute retrieval link for a .CSV file. Each request will include the spatial aggregation of your choice with the area and volume of each polygon. See FAQ for requirements for an asset ID.
For large regions, please use Export Multipolygon.
Take a look at how you might call this method:
Allows the user to define a region of interest and request a subset of OpenET's monthly raster datasets as a single temporal aggregated composite raster GeoTIFF. Each image will be clipped to the geometry provided and have a maximum return size of 32 MB. Note, asset_id can be used in place of geometry. See FAQ for requirements for an asset ID.
The results of this endpoint will generate a 5 minute retrieval link for a .TIFF file. Data return is in a JSON format.
For large regions use Export Composite.
Take a look at how you might call this method:
Note: retrieval is limited to 31 time steps per request. Each file counts as an individual request.
Allows the user to define a region of interest and request a subset of OpenET's raster datasets as multiple stacks of raster GeoTIFFs. Each image will be clipped to the geometry provided and have a maximum return size of 32 MB. Note: asset_id can be used in place of geometry. See FAQ for requirements for an asset ID.
The results of this endpoint will generate 5 minute retrieval links for a list of .TIFF files. Data return is in a JSON format.
For large regions use Export Stack endpoint.
Take a look at how you might call this method:
Allows the user to define a region of interest and export a subset of OpenET's monthly raster datasets as a single temporal aggregated composite raster GeoTIFF. Each image will be clipped to the geometry provided. Note, asset_id can be used in place of geometry. See FAQ for requirements for an asset ID.
Data return in JSON format includes:
Tracking identifier
Encryption boolean
Generated file name
Take a look at how you might call this method:
Note: retrieval is limited to 31 time steps per request. Each file counts as an individual request.
Allows the user to define a region of interest and export a subset of OpenET's raster datasets as multiple stacks of raster GeoTIFFs. Each image will be clipped to the geometry provided. Note, asset_id can be used in place of geometry. See FAQ for requirements for an asset ID.
Data return in JSON format includes:
Tracking identifier
Encryption boolean
Generated file name
Take a look at how you might call this method:
Note: Daily data is limited to 1 year retrievals for this endpoint.
Provides support for large timeseries queries against OpenET's raster datasets summarized for multiple polygons specified by an Earth Engine asset ID or temporary uploaded GeoJSON file. For more information on Earth Engine assets, see the Earth Engine page and see FAQ for requirements for an asset ID.
Data return in JSON format includes:
Tracking identifier
Encryption boolean
Generated file name
Take a look at how you might call this method:
Provides support for tracking OpenET export queries. If the job is found it will return one of four states, the export type, and attempt number:
UNSUBMITTED
RUNNING
SUCCEEDED
FAILED
If a job has FAILED you will see the error field in the return with details. If you are using a custom bucket to override the default export location, you must set the IAM permission of the bucket correctly or the job will fail to write (see the FAQ). If you experience continued failed requests contact OpenET support.
Note: it is not unusual to see a job in the PENDING state for long periods. It just means there is high traffic to the API during this time.
Take a look at how you might call this method:
Exposes metadata as a JSON from an OpenET raster dataset summarized for a region specified by the user. Results will vary based on the collection being queried. An example set is shown below:
model_name: Name of the OpenET model used, e.g., "openet-geesebal".
model_version: Version of the OpenET model, e.g., "0.2.2".
tool_name: Name of the tool used for data processing, e.g., "scene_interpolate_mgrs_export".
tool_version: Version of the tool used, e.g., "0.2.1".
core_version: Core version of the OpenET system, e.g., "0.1.2".
start_date, end_date: Date range for the dataset period.
interp_method: Interpolation method used, e.g., "LINEAR".
interp_days: Number of days for interpolation, e.g., 32.
cloud_cover_max: Maximum cloud cover percentage allowed in the dataset, e.g., 70.
scale_factor_et, scale_factor_count: Scaling factors used for evapotranspiration (ET) and other counts.
et_reference_band: Reference band used for ET calculation, e.g., "eto".
et_reference_resample: Resampling method used for ET reference, e.g., "nearest".
et_reference_factor: Scaling factor for ET reference.
build_date: The date on which the data was ingested into the system, in YYYY-MM-DD format.
mgrs_tile: MGRS tile code for the region queried.
Special: The build_date result will be the date of the most recent update from OpenET to the source collection. Note, this may be called date_ingested for older collections.
Take a look at how you might call this method:
Returns a map id and token in JSON format, suitable for generating a map overlay from an OpenET raster dataset. Generated cache will expire after 2 hours. Supports super sampling of ET data up to 10x10m pixels.
Take a look at how you might call this method:
Use an OpenET raster dataset to create an 900x900px .gif animation and film strip of corresponding images accessible by temporary url for 2 hours. Supports super sampling of data in 10 meter intervals up to 10x10m pixels.
Take a look at how you might call this method:
To track your file, see the Export File Tracking endpoint. To retrieve your exported files, use the endpoint. If your account is linked with Earth Engine, the exported files by default will be found in the OpenET Exports folder in the root of your Google Drive. If the bucket parameter is passed to override the export location to a private bucket, the export will go their instead if it is shared properly. For more detailed information on data exporting, see the FAQ.
To track your file, see the Export File Tracking endpoint. To retrieve your exported files, use the endpoint. If your account is linked with Earth Engine, the exported files by default will be found in the OpenET Exports folder in the root of your Google Drive. If the bucket parameter is passed to override the export location to a private bucket, the export will go their instead if it is shared properly. For more detailed information on data exporting, see the FAQ.
To track your file, see the Export File Tracking endpoint. To retrieve your exported files, use the endpoint. If your account is linked with Earth Engine, the exported files by default will be found in the OpenET Exports folder in the root of your Google Drive. If the bucket parameter is passed to override the export location to a private bucket, the export will go their instead if it is shared properly. For more detailed information on data exporting, see the FAQ.
Once an export state returns SUCCEEDED you may use the endpoint to retrieve the link within 7 days. If your account is linked with Earth Engine the export will be found in the OpenET Exports folder in the root of your Google Drive.
Provides support for queries against the OpenET raster datasets summarized a point.
/raster/timeseries/point
No body
Provides support for queries against the OpenET raster datasets summarized for a polygon.
/raster/timeseries/polygon
No body
Provides support for queries against the OpenET raster datasets summarized for multiple polygons.
/raster/timeseries/multipolygon
No body
Provides support for queries against the OpenET monthly raster datasets summarized as a composite GeoTIFF.
/raster/geotiff/composite
No body
Provides support for queries against the OpenET raster datasets summarized for a stack of GeoTIFFs.
/raster/geotiff/stack
No body
Provides export support for large queries against the OpenET monthly raster datasets summarized as a monthly composite GeoTIFF.
/raster/export/composite
Opt for a cloud optimized version
No body
Provides export support for large queries against the OpenET raster datasets summarized as a stack of GeoTIFFs.
/raster/export/stack
Opt for a cloud optimized version
No body
Provides export support for large queries against the OpenET raster datasets summarized for multiple polygons.
/raster/export/multipolygon
No body
Provides tracking support a file in the OpenET queue.
/raster/export/track
No body
Provides support for queries against the OpenET raster metadata.
/raster/metadata
No body
Provides support for dynamic tile generation from OpenET's raster datasets.
/raster/visual/tile_cache
No body
Provides support for gif and image animation from OpenET's raster datasets.
/raster/visual/animate
No body