Global WatchGW Docs
Features

Tree Detection Matching

Tree Detection Matching

When tree detection runs over a project's imagery, each detected tree is compared with the tree assets already registered in that project.

  • A detection on top of an existing tree asset (within 1 metre) is treated as the same tree and is not shown again.
  • A detection 1 to 3 metres from a tree asset is ambiguous, so the map asks about it instead of guessing.

Answering a question

Selecting a detection near an existing tree asset opens a question with three answers:

  • Same tree — the detection and the asset are the same tree. The asset inherits the measurements from the detection: crown outline, height and health, along with the image they came from.
  • Different tree — the detection is a different tree than that asset, so both are kept.
  • Not a tree — the detection is a false positive and is hidden.

Answers are shared and kept

Answers are stored with the project, not with your session or your browser. Anyone on the project's team sees them, and they stay in place across reloads and across later detection runs, so the same question is not asked twice.

Answers also stay in place when the tree asset they are about is deleted. The answer records what was observed in the imagery, which remains useful for improving detection even after the asset is removed from the inventory. A kept answer refers to the deleted asset only historically: it is never matched against a new asset.

Deleting the project deletes its answers along with the rest of its data.

Who can answer

Answering requires permission to update assets in the project: project members with the owner, admin, manager, executor or technical role, or account owners and managers. Read-only access, including read-only support sessions, can view answers but not record them.

On this page