OpenTreeMap is a collaborative platform for crowdsourced tree inventory, ecosystem services calculations, urban forestry analysis, and community engagement.
Instances that were migrated into the database have species rows that do not have an otm_code, which modeling scenarios depend on.
To resolve this we have:
Added class method to Species to try fetching a species and fall back to using an ITreeCodeOverride
Added a validation to prevent loading species into the scenario drop-down lists that cannot be matched to an instance species
PhillyTreeMap before
PhillyTreeMap after
Modified the scenario run view function to use the new species fetch method.
Testing
Create a modeling scenario on PhillyTreeMap and add a single tree for every species in the list. Verify that the "Calculate Scenario" button works.
Create a modeling scenario on PhillyTreeMap, add a distribution area, and add a distribution for every species in the list. Verify that the "Calculate Scenario" button works.
Coverage decreased (-0.06%) to 83.85% when pulling 878484193eef0d4c5de9d94bd5dd269b93671c89 on jwalgran:feature/modeling-species-overrides into 7b3f08b490e83a9479e9db53568d84043902b462 on OpenTreeMap:develop.
Instances that were migrated into the database have species rows that do not have an
otm_code
, which modeling scenarios depend on.To resolve this we have:
Added class method to
Species
to try fetching a species and fall back to using anITreeCodeOverride
Added a validation to prevent loading species into the scenario drop-down lists that cannot be matched to an instance species
PhillyTreeMap before
PhillyTreeMap after
Testing
Connects to https://github.com/OpenTreeMap/otm-clients/issues/352