Skip to main content
Driver tree
Updated over a week ago

A driver tree is a feature that breaks down an emission factor into its constituent inputs and processes. We refer to these inputs and processes as emissions contributors, which are represented by nodes on the platform.

A node can be considered as an emission factor if it possesses its own driver tree. For instance, the root node (or emission factor) "Palm fruit production" might have a child node known as "Fertiliser usage". Since "Fertiliser usage" can be further broken down into its own driver tree, we can also consider this node as an emission factor.

  • Root node: This is the initial node of a driver tree, representing the emission factor itself.

  • Parent node: Has at least one child node.

  • Child node: Connected to a parent node, it may have its own driver tree. Nodes linked to the same parent are referred to as sibling nodes.

In cases where the node represents the most basic component of an emission factor, and does not have its own driver tree, we do not consider it as an emission factor. Examples of such nodes include Dinitrogen monoxide, Methane, and Carbon dioxide.

Did this answer your question?