---
description: Frequently Asked Questions
---

# FAQ

<details>

<summary>How do reductions behave with partial pixels? </summary>

{% code overflow="wrap" %}
```
The weights of pixels used during an aggregation process are based on the overlap between the smaller pixels being aggregated and the larger pixels specified by the output projection. This is illustrated in the figure below.
```
{% endcode %}

<img src="https://3342101665-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fp6krz4jcrv0IsfRERGXc%2Fuploads%2FSCKIkuZGGCSneqbWao4k%2Fimage.png?alt=media&#x26;token=98abea7a-efcc-46ab-b33a-c2415bb229d5" alt="" data-size="original">

{% code overflow="wrap" %}
```
The default behavior is that input pixel weights are computed as the fraction of the output pixel area covered by the input pixel. In the diagram, the output pixel has area a, the weight of the input pixel with intersection area b is computed as b/a and the weight of the input pixel with intersection area c is computed as c/a. 

This behavior can result in unexpected results when using a reducer other than the mean reducer. For example, to compute forested area per pixel, use the mean reducer to compute the fraction of a pixel covered, then multiply by area (instead of computing areas in the smaller pixels then adding them up with the sum reducer).
```
{% endcode %}

</details>

<details>

<summary>How <em>r<strong>esample</strong></em> work within the API &#x26; what is natively resampled? </summary>

{% code overflow="wrap" %}
```
OpenET uses Google Earth Engine’s bilinear resampling method for precipitation (Pr) and reference evapotranspiration (ETo) datasets. Bilinear resampling is an interpolation technique that estimates the value of a new pixel using the four nearest neighboring pixels (a 2×2 grid). It performs linear interpolation in both the x and y directions, resulting in smoother, more continuous outputs than simpler methods like nearest neighbor.

This method is particularly useful for continuous data such as precipitation and ETo. In some cases—especially near raster edges—it can also be used to resample coarser-resolution data (e.g., 30m) to finer resolutions (e.g., 10m) for improved visualization or analysis.
```
{% endcode %}

</details>

<details>

<summary>What do the different variable names stand for? </summary>

{% code overflow="wrap" %}
```
ET: Evapotranspiration 
ET_MAD_MIN: Evapotranspiration Median Absolute Deviation Minimum
ET_MAD_MAX: Evapotranspiration Median Absolute Deviation Maximum
ETo: Grass Reference Evapotranspiration
ETr: Alfalfa Reference Evapotranspiration
ETof: Fraction of Reference Evapotranspiration
NDVI: Normalized Difference Vegetation Index 
PR: Precipitation 
COUNT: Number of Cloud Free Landsat observations 
MODEL_COUNT: Number of model included in observation for Ensemble query
```
{% endcode %}

</details>

<details>

<summary>What are the requirements for an asset ID? </summary>

{% code overflow="wrap" fullWidth="false" %}
```
Each asset must be shared with READ permission to OpenET (See Earth Engine Tab). Each geometry in your shapefile must be simple and non-overlapping. Each polygon must contain a unique identifier and your shapefile must conform to the limits of your account (See Quota).     
```
{% endcode %}

</details>

<details>

<summary>Can I export to my own Google Bucket? </summary>

{% code overflow="wrap" fullWidth="false" %}
```
No. This functionality is currently deprecated
```
{% endcode %}

</details>

<details>

<summary>For daily overpass collections, what models have what native variables?</summary>

<pre data-overflow="wrap"><code><strong>Ensemble: et
</strong><strong>SIMS: etof
</strong>DisAlexi: et
eeMETRIC: etof
geeSEBAL: et
PTJPL: et
SSEBop: etof
</code></pre>

</details>

<details>

<summary>What happens if I exceed the request limits?</summary>

{% code overflow="wrap" %}
```
Queries which attempt to exceed the limits of the account's quota will be blocked. If you have exceeded your requests per month, you must wait until the following 1st of the month (UTC time) query the API again.
```
{% endcode %}

</details>

<details>

<summary>What data is considered provisional?</summary>

<pre data-overflow="wrap"><code><strong>Realtime OpenET data is considered “provisional” for the last 120 days. This data can and will change and is not considered stable/static/final. The two main sources for this change are the gridMET data not being finalized until after 60 days, and new Landsat images needing to be run through the models and used to interpolate previous months. To account for all of this, we make monthly updates of the last 3 to 4 month for all models and the ensemble.
</strong></code></pre>

</details>

<details>

<summary>I linked my Earth Engine account, does OpenET now have access to my whole Google Drive?</summary>

{% code overflow="wrap" %}
```
OpenET can only see, edit, create, and delete only the specific Google Drive files you use with our API. This access can be revoked by you at anytime by access your Google account settings.  
```
{% endcode %}

</details>

<details>

<summary>Using the parameter <em>overpass=true</em> returned an error. What does this mean? </summary>

{% code overflow="wrap" %}
```
The overpass flag only works for certain model and variable combinations at this time. The satellite overpass data varies for each model and passing overpass=true will only work with the native band of the model. Ensemble, geeSEBAL, DisALEXI, and PTJPL support ET as the native band while eeMETRIC SSEBop, and SIMS support ETof directly.
```
{% endcode %}

</details>

<details>

<summary>What do I do if I receive the Invalid API Credentials error message?</summary>

{% code overflow="wrap" %}
```
This error can occur for a few different reasons. The most common being a miss-typed or expired api key. Remember, when querying the api you will need to use the "Authorization" header format as shown in the code examples. If you have ruled out the previous three possibilities retry the query after a few seconds as the system may be experiencing high volumes of traffic.

If you api key has expired you will need to generate a new one from you project dashboard.
```
{% endcode %}

</details>

<details>

<summary>Do field boundaries in the geodatabase change year to year? </summary>

{% code overflow="wrap" %}
```
Field boundaries generally remain static, however priority updates are ingested to include more recent field boundary datasets provided by each state if they include significant revisions.
```
{% endcode %}

</details>

<details>

<summary>What spatial reference system is used for raster geoTIFF exports?</summary>

{% code overflow="wrap" %}
```
EPSG:4326
```
{% endcode %}

</details>

<details>

<summary>What is a C.O.G.? </summary>

{% code overflow="wrap" %}
```
A Cloud Optimized GeoTIFF (COG) is a regular GeoTIFF file aimed at being hosted on a HTTP file server with an internal organization that enables more efficient workflows on the cloud. It does this by leveraging the ability of clients issuing ​HTTP GET range requests to ask for just the parts of a file they need.
```
{% endcode %}

</details>

<details>

<summary>What is an Earth Engine Compute Unit (EECU)</summary>

{% code overflow="wrap" %}
```
An Earth Engine Compute Unit (EECU) is a mechanism for representing an amount of instantaneous processing power. OpenET tracks the total computational footprint of tasks as a function of their EECU usage through time (EECU-seconds).
```
{% endcode %}

</details>

<details>

<summary>What is the largest response the API can return? </summary>

{% code overflow="wrap" %}
```
The OpenET API is limited to a 32mb maximum response size. Any response which exceeds this size may be returned as a compressed zip file. See specific endpoint documenation for more details.  
```
{% endcode %}

</details>

<details>

<summary>When downloading a raster url return I get the error <em>"Parameter 'left' is required."</em></summary>

{% code overflow="wrap" %}
```
This error may occur if the geometry used fully overlaps a portion of masked pixels within a raster. This can most frequently happens with the SIMS model as it is masked for irrigated agriculture only. Remove any polygon ID listed in the error message and retry the query. An example of what this looks is shown below. 
```
{% endcode %}

<img src="https://3342101665-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fp6krz4jcrv0IsfRERGXc%2Fuploads%2F6rdcYIbsaoEpLLOUacJr%2FScreen%20Shot%202023-02-06%20at%202.07.57%20PM.png?alt=media&#x26;token=e265ff96-fc3f-4345-94ea-aa2a95d4fbd1" alt="" data-size="original">

{% code overflow="wrap" %}
```
This can also occur with overlapping polygon geoemtries in your shapefile. You will need simple, non-overlapping geometries for all OpenET endpoints.
```
{% endcode %}

</details>

<details>

<summary>Where can I find more information about OpenET's models?</summary>

{% code overflow="wrap" %}
```
The OpenET website's methodologies page: https://openetdata.org/methodologies will be yout best resource here. 
```
{% endcode %}

</details>

<details>

<summary>When I use the <em>drive_folder</em> parameter multiple destination folders get created. What can I do to solve this? </summary>

{% code overflow="wrap" fullWidth="false" %}
```
This is a know bug with Earth Engine when exporting to Google Drive. You can mitigate this issue by creating the export folder in the root of your Google Drive in advance. 
```
{% endcode %}

</details>

<details>

<summary>How do I cite OpenET data?</summary>

{% code overflow="wrap" %}
```
We have citations available for each model in our Earth Engine collections. Here is a link for the Ensemble v2_0 collection: 

https://developers.google.com/earth-engine/datasets/catalog/OpenET_ENSEMBLE_CONUS_GRIDMET_MONTHLY_v2_0#citations
```
{% endcode %}

</details>

<details>

<summary>What is the latency associated with the OpenET daily and monthly collections?</summary>

{% code overflow="wrap" %}
```
Each data product used to generate OpenET data has the potential to introduce additional latency. In addition to the meteorological and ancillary data inputs, OpenET relies on the Landsat system of satellites. Current data production uses imagery from Landsat 8 & 9. Each satellite makes a complete orbit every 99 minutes, completes about 14 full orbits each day, and crosses every point on Earth once every 16 days. The satellite orbits are offset to allow 8-day repeat coverage of any Landsat scene area on the globe. Coverage may change depending on the regions you are looking to retrieve data. OpenET does mask for clouds, which during rainy months may add additional latency between usable observations.

Provisional monthly data typically becomes available on the 5th or 6th of the following month. However, this may vary if there is a high number of cloudy scene for the region of interest. 

Using the OpenET raster/metadata endpoint, you can retrieve the date_ingested parameter which will provide the most recent time data was added for a specific region.
```
{% endcode %}



</details>

{% hint style="info" %}
Don't see your question here? [Contact](https://openetdata.org/contact/) us.
{% endhint %}
