TimberID
Log In
  • 🌳Welcome to TimberID
  • Overview
    • 🌳Background
  • User Guide
    • πŸ”°Registering
    • πŸͺ΅Single Reference Sample + Import
      • ⁉️Import Errors
    • πŸ”ŽOrigin Verification
    • πŸ“€Exporting
    • 🌎Earth Engine API
    • ⚑Administration Guide
      • πŸ§‘β€πŸ€β€πŸ§‘Creating Organizations
      • 🚸Managing Users
    • πŸ“—Glossary
    • πŸ›Report an Issue
  • Architecture of TimberID
    • πŸ› οΈHigh Level Design
    • πŸ“šOpen Source Github Repositories
    • 🏯Detailed Design
      • 🌐Client
      • πŸ–₯️Server
      • πŸ—ΊοΈExternal integrations and maps
      • 🌎Earth Engine
      • πŸ‘©β€πŸ”¬Research Colabs
        • Data Ingestion
        • Model Training (Variational Inference)
        • Isoscape Generation
        • Validation of Isoscapes
    • 🌩️GCP Guide
      • πŸ“ˆAnalytics
      • πŸ’ΎDatabase Query Builder
      • πŸ’°Budget Alerts
      • πŸŒ„Domain Name Configuration
      • ⚠️Backups and Disaster Recovery
    • πŸš€Test Procedure for Production Release
  • Internal
    • πŸ”Internal Information
Powered by GitBook
On this page

Was this helpful?

  1. User Guide

Earth Engine API

PreviousExportingNextAdministration Guide

Last updated 1 year ago

Was this helpful?

The interactive colab for using our API can be found in our .

Much of the earth engine API is built as wrappers around the Earth Engine Python API which has . What the Ddf EE API adds is:

  • Improved usability through automatic authorization of TimberID users. You do not have to set up your own GCP project to use the API. You only need register with TimberID.

  • Easy to use APIs to access TimberID entered data. All data imported into TimberID is automatically exported to Earth Engine in a FeatureCollection. You can access this data with a single API call.

  • Easy to use APIs to access important climate data. Rasters such as digital elevation are surfaced for you as a Python function, allowing you to access them without requiring knowledge of the Earth Engine path.

  • Performant raster access. For the rasters we load, there are highly parallel routines for downloading data. You can query raster locations in a bulk query and that will be chunked to many subprocesses for faster downloads.

🌎
ddf_common github repository
a very good tutorial