Unfortunately, these data are only collected and processed throught the USFS Center for Urban Forest Research at this time. However, we are in the process of determing how to extend STRATUM--and all of i-Tree--into new regions/counties and will be seeking collaborators. We will release this informat...

The Forest Service confirmed that the Tree Guides are available on line, at http://www.fs.fed.us/psw/programs/cufr/tree_guides.php

However, the database that populates the website is temporarily down so the Guides cannot be accessed. They should--we are told--be available in the next few days.

No Problem, see attached for the equations STRATUM uses along with an example of how they are used. For an example of real project results based on i-Tree sampling protocols and STRATUM reports, see the Minneapolis Street Tree Resource Analysis report: http://itreetools.org/resource_learning_center/...

The best approach would be to redefine the “City” data to reflect the specific zone or area the inventory represents. However, leaving these entries as citywide data will not cause reporting errors with STRATUM; how these reports will be interpreted is a different matter. Suppose for example, your p...

Records for the TreeID field can be any size, unique integer as long as you are importing a database into STRATUM without having used the i-Tree PDA Utility to collect and format your data. In the latter case, the TreeID field size is a “Long Integer” which is defined in Access as any integer betwee...