🌎Earth Engine

Source Location

The Earth Engine Ddf API is built in the ddf_common github repository. As described in the Earth Engine API userguide, the Ddf EE API is mostly a wrapper around the existing Earth Engine API.

However it is more turnkey due to automatic management of Earth Engine assets and authorization from TimberId.

How it works

The TimberID front end manages information auto exported to Earth Engine

Two earth engine based cloud functions export the reference sample data in a per-organization layout and the user information that automatically grants access either directly in the earth engine code editor or through the Ddf EE API.

The Earth Engine Code Editor

These assets can be seen by directly loading the Earth Engine Code editor. Note that you must have developer admin permissions (see the Admin page for details) to see the Assets in the asset collection. Without this permission, you can still write script applications and read assets, but not list them.

Updating Isoscapes

You must upload a stamped isoscape using the EE API upload script (see the codelab for an example). This preserves important medata on the isoscape used during analysis.

Functions that use Earth Engine

Many cloud functions that analyze timber use data from Earth Engine (whether its one of our generated isoscapes or data from 3rd parties like mapbiomas). These functions use the normal EE API when necessary. We have not yet packaged the Ddf EE API in a standalone pip installable package.