Hi Matt,
The OTM Code roughly, though not exactly, corresponds with the
USDA symbols/codes (which in turn sometimes correspond with the i-Tree Streets codes for each species in the data that ships with i-Tree Streets). There are some codes that are identical to the USDA / i-Tree Streets codes and some which vary - there's no overarching formula.
The OTM Code is what the ecobenefits service uses to calculate the environmental benefits of the tree - using the code, it looks up and performs the calculations for that particular type of tree based on the data from i-Tree Streets.
So, as a random example, you could add a new species "Matt Vanderhorst Specialtree" and give it the OTM Code "AEHI" (in reality the
code listed here [or
here] for a Horsechestnut), and OTM would calculate ecobenefits for these trees as if they were Horsechestnuts, but display them in the GUI as "Matt Vanderhorst Specialtree" or whatever naming you decided to give it.
The link between OTM code and i-Tree code is in the ecobenefits project's
species.json file, which is separated first into i-Tree regions. There's another link between i-Tree region, i-Tree code, and OTM code in OTM2's
species package.
There are a few generic i-Tree codes that may come in handy if you're adding a rare species for which there isn't a more precise i-Tree Streets analog. These codes often end in "OTHER". You'll notice for instance in
species.json that our AEHI Horsechestnut is actually a "BDM OTHER" for the ecobenefits project's calculations. That's because i-Tree Streets doesn't have precise data on the environmental benefits of Horsechestnuts, but the scientists were able to develop more general calculations for Broadleaf Deciduous Medium-size trees.
Hope this helps explain the codes a bit.
Thanks,
Andrew