On Monday evening, city staff met with 80-100 residents in the auditorium of Slauson Middle School. Kerry Gray, coordinator for urban forestry and natural resources planning, was on hand to clarify that an initiative to develop an urban forest management plan – Gray’s main goal in the coming year – had been accelerated. Instead of beginning the public process in the fall, Monday’s meeting was effectively the kickoff to a public engagement process on developing a tree management plan for the city.

Our goal with this brief article is not to explicate the back-and-forth among residents and staff at Monday’s meeting, but rather to share some data.

Back in the spring we’d noticed the city’s tree inventory in progress. On Monday evening at Slauson, some of the results of that inventory were presented in summary form (e.g., almost 40% of the city’s trees are some kind of maple).

But in light of some recent local discussion about access to raw data, we’d looked forward to the completion of the tree inventory by Davey Resource Group, anticipating a rich data set that could serve as inspiration for anyone with the technical know-how to make use of it. It includes the location of each tree, as well as type, condition and size.

We asked the city of Ann Arbor for all the electronic deliverables from Davey. And we provide the following data with a caveat: On Monday evening, city staff stressed that they were still doing some quality control work on the initial data set – so the data provided to The Chronicle is a snapshot of the city’s trees as assessed by the Davey Resource Group. The city’s inventory will presumably be maintained as a frequently updated data set that changes as trees are pruned, removed, or planted.

• Tree Inventory Analysis Report – includes executive summary.
• Tree Inventory CSV Data – the original data set was in MS EXCEL format. Saved to CSV saves a few MB, but even so, it’s a large (15MB) file.
• Report Spreadsheet – summary data associated with the analysis report.
• GeoDatabase Zipfile – the coordinates in the CSV file don’t look like GPS coordinates, but presumably the multiple files contained in the GeoDatabase provide some sort of relational structure?