Forest Digital Twin

A shared single-tree database for forest digital twins: field inventories, trees derived from LiDAR, sensor time series and growth simulations, each kept with where it came from. The data you bring is what the lab's VR forests are built from. The four doors below all read and write that same database; pick the one that fits what you want to do. What we mean by a forest digital twin is on the docs page.

Explore

No account needed

Contribute

Account with the contributor role

Manage

Team leads (curator) and admins

  • Create accounts for your team, grant or revoke contributor, reset passwords
  • Correct and delete field data
  • Full SQL console (Supabase Studio): lab administrators only, through an SSH tunnel

Build

Developers

  • Developer guide — auth, read and write recipes in curl, Python and R, running models
  • Docs — how the data is organised, reference documentation, source repositories
  • Every table on this site is an endpoint under /db/rest/v1/

Tree look survey

Experts rate whether the lab's procedurally grown trees look right for their species. The answers are kept apart from the twin database and guide the work on the tree catalogue that the VR forests are built from. By invitation: open it with the link you were sent.

Go to the survey

Getting access

Reading needs no account. To add data or run models, ask the curator of your team for an account; they can create one on the spot and give you a one-time password, which you change on the account page after your first sign-in.

RoleCan
read-onlyread everything public, see your own job history
contributoradd field data, edit sites and metadata (species, plots, sensors, campaigns, …), request model runs
curatoralso correct and delete field data, see every job, create accounts and grant contributor
adminalso grant curator and admin

Every correction to trees, stems, environments, point clouds and phenology is logged with who made it and can be reverted.