STRATUM:

1
STRATUM

• Overview Process

2
Session Purpose

• i-Tree
• STRATUM Savvy
• Community forest management

3
Whats In Store for You?

• Background
• Process
• Data Collection
• Field Practice
• STRATUM
• Create a project
• Inputs
• Reports

4
(No Transcript)
5
Background
Center for Urban Forest ResearchUSDA Forest
ServicePSW Research StationDavis, CA

• To demonstrate new ways that trees add value -
  quality of life - to communities.

6
(No Transcript)
7
What We Need?

• Value of trees to human health and well-being
• Increased investment in management
• Planning integrated up-front, not as
  after-thought
• Green and gray infrastructure working together
• Increased return on investment and customer
  satisfaction
• Tools to quantify the value of trees

8
Tree Value

• Trees are assets, management adds value by
  increasing return on investment

9
Heart of Sustainable Funding

• Sufficient local budget appropriation
• Engage in outreach, public relations, special
  events
• Regularly educate and lobby community leaders
• Develop clear argument to justify budget
• Resource assessment
• Resource value

10
STRATUM Helps You

• Justify and leverage funds
• Highlight benefits to public
• Plan, prioritize, and budget
• Benchmark progress

11
The Foundation Reference City Research

• Regional Tree Guide studies to develop growth
  models of representative street trees and their
  dimensions as a basis for Benefit-Cost Analysis.

12
Tree Size, Growth, and Functionality
13
Sweetgum in three climate zones at age 40
Inland Empire Coastal S. CA
Central Valley
14
STRATUM was designed to extend Reference City
data to all communities within a climate zone
15
(No Transcript)
16
Reference City Research

• Collected data street park trees
• Analyzed growth rates and dimensions
• Estimated magnitude of annual benefits
• Priced benefits
• Priced tree care costs
• Calculated net annual benefits, benefit-cost
  ratios

17
Sample Design

• Reference city data collection is used to develop
  growth models of representative street trees and
  calculate benefits.
• Predominant species
• 18 25 species representing gt65 of forest
• Random sample of 35 70 trees per species
• Stratified, minimum 40 year age range

18
Measurements

• 25 field measurements for each tree, including
• Diameter-at-breast-height
• Tree height
• Crown (bole) height
• Crown diameter
• Leaf area
• Crown shape
• Tree orientation and setback
• Condition and location
• Pruning level
• Grow space type and size
• Hardscape damage

19
Research ProcessStructural Analysis

• Data collection
• 900 trees, 20 predominant species
• age, species, dbh, ht., crown dia., condition,
  digital photos, foliar biomass samples, etc.
• Calculate leaf area and foliar biomass
• Regression models predict growth.

20
Research ProcessFunctional Analysis

• Models use structural data (size at various
  ages).
• To determine magnitude of annual benefits
• Energy saved
• Atmospheric CO2 reduction
• Air pollutants removed
• Rainfall intercepted
• Aesthetics other

21
Research ProcessValue Analysis (Benefits)

• Heating Cooling Energy - Regional market prices
  (0.095/ kWh, 0.97/therm)
• Carbon trading credits - CO2 (15/ton)
• Air Pollutants - Transaction costs, damage value
  and control cost of emissions (1-15,000/ton)
• Stormwater Runoff - Retention/detention costs
  (0.005/gal)
• Residential Property Increase - Average resale
  price (median sales price 254,000)

22
Research ProcessValue Analysis(Costs)

• Planting
• Pruning
• Removal and disposal
• Pest and disease control
• Irrigation
• Infrastructure
• Leaf litter cleanup
• Liability
• Administration

23
Research ProcessValue Analysis(Net Benefits)

• Convert resource units (kWh, lbs) to
• Annual Benefits
• B Energy CO2 AQ Hydrology property
  value
• Annual Costs
• C Plant Trim Removal IPM Irrigation
  Clean-Up Sidewalk Liability Admin Other
• Net Benefits B C
• Benefits/Costs ratio B/C

24
STRATUM Information for Better Tree Management

• Computer application
• Allows managers to evaluate current benefits,
  costs, and management needs.
• Input
• - Sample inventory (3-5)
• - Or existing inventory
• - Price adjustments, mgmt. costs
• Output
• - Graphs, charts, tables
• Benefit
• - Baseline data to more effectively manage the
  street tree resource

25
What makes STRATUM different?

• Street trees, not entire urban forest
• Costs, not only benefits
• Management tool, not only for advocacy
• Tree inventory-based, not GIS
• Answers the question do the accrued benefits of
  street trees outweigh the cost of their
  management?

26
The STRATUM Process
27
How do you conduct a STRATUM Analysis?

• The STRATUM Process
• Data Collection
• STRATUM default data fields
• i-Tree PDA Utility
• Creating a STRATUM project
• Importing data
• Defining the inventory
• Reporting and interpretation

28
STRATUM Process
29
STRATUM Data Collection

• Defining the inventory scheme
• Considerations before the inventory begins
• Data Collection
• STRATUM default data fields
• Paper vs. PDA
• Tree inventory PDA Utility
• Desktop Configuration
• PDA Synchronization
• Choosing a PDA
• Field data collection (groups)

30
OR
OR
31
OR
OR
32
OR
OR
33
OR
OR
34
STRATUM

• Data Collection

35
Data Collection
STRATUM is customizable to the needs of most any
community

• Minimum data fields for complete inventories
• Tree ID (TreeID)
• Species Code (SpCode)
• Diameter at Breast Height (DBH)

• Minimum data fields for sample inventories
• Tree ID (TreeID)
• Street Segment ID (StreetSeg)
• Species Code (SpCode)
• Diameter at Breast Height (DBH)

36
STRATUM Default Data Fields

• 17 total
• TreeID
• Zone
• StreetSeg
• CityManaged
• SpCode
• LandUse
• LocSite
• DBH
• MtncRec

• MtncTask
• SwDamg
• WireConflict
• CondWood
• CondLvs
• OtherOne
• OtherTwo
• OtherThree

37
TreeID

• A unique number assigned to each tree within a
  particular city in order to distinguish trees and
  count the number of trees per city. Each record
  must have a TreeID and it must be unique range
  is numeric, 1999,999.

38
Zone

• A number that represents the management area or
  zone that the tree is located in within a
  particular city. Range is alpha/numeric, 120. If
  no zones or areas are associated with inventoried
  trees, 1 is entered for each record.

39
StreetSeg

• The street segment within a city where the tree
  is located. StreetSeg is synonymous with Tiger
  Line ID (TLID), where a sample inventory was
  carried out. For Full Inventories, 0 (zero) is
  entered for each record.

40
CityManaged

• A numeric code to distinguish trees owned by the
  city (0) and those privately planted and
  managed (1). If private trees were not
  distinguished (i.e., all inventoried trees were
  municipal), 0 is entered for each record.

41
SpCode

• A 26 character alphanumeric code consisting of
  the first two letters of the genus name and the
  first two letters of the species name followed by
  two optional letters or numbers to distinguish
  two species with the same four-letter code.
  Additional four-letter codes for available
  planting sites or empty planting basins e.g.,
  AVPS (Available Planting Site) or EMBA (Empty
  Basin) may be entered. A SpCode must be entered
  for each record.

42
LandUse

• A numeric code to describe the type of area where
  the tree is growing. The default values are as
  follows
• 1 Single-family residential
• 2 Multi-family residential (duplex, apartments,
  condos)
• 3 Industrial/Institutional/large commercial
• 4 Small commercial (minimart, retail boutiques,
  etc.)
• 5 Park/vacant/other (agricultural, riparian
  areas, greenbelts, park, etc.)
• Additional or alternative definitions (up to 10)
  can be defined in STRATUM. If no LandUse value is
  associated with inventoried trees, 0 (zero) is
  entered for each record.

43
LocSite

• A numeric code to describe the part of the site
  where the tree is growing. The default values are
  as follows
• 1 Front yard
• 2 Planting strip
• 3 Cutout (tree root growth restricted on all
  four sides by hardscape within dripline)
• 4 Median
• 5 Other maintained locations
• 6 Other un-maintained locations
• 7 Backyard
• Additional or alternative definitions (up to 10)
  can be defined in STRATUM. If no LocSite value is
  associated with inventoried trees, 0 (zero) is
  entered for each record.

44
DBH

• A numeric entry for the diameter at breast height
  4.5 ft (1.37 m) to the nearest inch or
  centimeter. Alternatively, up to 9 numerical
  categories can be used to define classes (e.g. 1
  trees in the 06 in DBH size class) classes
  must be defined in STRATUM. Each record must have
  a DBH value. Enter 0 (zero) for all non-tree
  SpCode entries.

45
MtncRec

• A numeric code to describe the recommended
  maintenance for the tree. The default values are
  as follows
• 1 None
• 2 Small tree (routine)
• 3 Small tree (immediate)
• 4 Large tree (routine)
• 5 Large tree (immediate)
• 6 Critical concern (public safety)
• Additional or alternative definitions (up to 10)
  can be defined in STRATUM. If no MtncRec value is
  associated with inventoried trees, 0 (zero) is
  entered for each record

46
MtncTask

• A numeric code to describe the highest priority
  task to perform on the tree. The default values
  are as follows
• 1 None
• 2 Stake/train
• 3 Clean
• 4 Raise
• 5 Reduce
• 6 Remove
• 7 Treat pest/disease
• Additional or alternative definitions (up to 10)
  can be defined in STRATUM. If no MtncTask value
  is associated with inventoried trees, 0 (zero)
  is entered for each record.

47
SwDamg

• A numeric code to describe the amount of sidewalk
  damage. The default values are as follows
• 1 None Sidewalk heaved less than ¾ inch,
  requiring no remediation.
• 2 Low Sidewalk heaved ¾ to 1½ inches,
  requiring minor grinding or ramping.
• 3 Medium Sidewalk heaved 1½ to 3 inches,
  requiring grinding or ramping and/or replacement.
• 4 High Sidewalk heaved more than 3 inches,
  requiring complete removal and replacement.
• Alternative definitions (up to 4) can be defined
  in STRATUM. If no SwDamg value is associated with
  inventoried trees, 0 is entered for each record

48
WireConflict

• A numeric code to describe utility lines that
  interfere with or are present above a tree. The
  default values are as follows
• 1 No lines No utility lines within vicinity
  of tree crown
• 2 Present and not conflicting Utility lines
  occur within vicinity of tree crown, but crown
  does not presently intersect wires.
• 3 Present and conflicting Utility lines occur
  and intersect with tree crown.
• Additional or alternative definitions (up to 5)
  can be defined in STRATUM. If no WireConflict
  value is associated with inventoried trees, 0
  (zero) is entered for each record.

49
CondWood

• A numeric code to describe the health of the
  trees wood (its structural health) as per
  adaptation of The Council of Tree and Landscape
  Appraisers (CTLA) tree appraisal. The default
  values are as follows
• 1 Dead or Dying - Extreme problems
• 2 Poor - Major problems
• 3 Fair - Minor problems
• 4 Good - No apparent problems
• Classes must be ordered in ascending order, with
  the poorest rating having the lowest numerical
  value. Additional or alternative definitions (up
  to 10) can be defined in STRATUM. If no CondWood
  value is associated with inventoried trees, 0
  (zero) is entered for each record

50
CondLvs

• A numeric code for the health of the trees
  leaves (its functional health) as per adaptation
  of CTLA tree appraisal
• 1 Dead or dying - Extreme problems
• 2 Poor - Major problems
• 3 Fair - Minor problems
• 4 Good - No apparent problems
• Classes must be ordered in ascending order, with
  the poorest rating having the lowest numerical
  value. Additional or alternative definitions (up
  to 10) can be defined in STRATUM. If no CondLvs
  value is associated with inventoried trees, 0
  (zero) is entered for each record.
• If only one condition rating is inventoried,
  enter the same values for both CondWood and
  CondLvs.

51
OtherOne

• A numeric field with up to 10 variables to be
  defined by user. If no OtherOne value is
  associated with inventoried trees, 0 (zero) is
  entered for each record.

52
OtherTwo

• A numeric field with up to 10 variables to be
  defined by user. If no OtherTwo value is
  associated with inventoried trees, 0 (zero) is
  entered for each record.

53
OtherThree

• A numeric field with up to 10 variables to be
  defined by user. If no OtherThree value is
  associated with inventoried trees, 0 (zero) is
  entered for each record.

54
STRATUM Data Field Summary

• All data fields user configurable
• Data can be classified (up to 10)
• All data numeric except for SpCode
• Minimum data fields are required, all others
  optional or adaptable to specific needs of the
  city.

55
How to Collect Data?

• Paper vs. PDA

56
Paper-based Inventory
57
PDA-based Inventory

• i-Tree PDA/Program Generator
• STRATUM compatible
• No data entry (field or lab)
• Fewer mistakes

• Two Interfaces
• Desktop
• Pocket PC

58
PDA to Desktop Data Transfer
STRATUM
59
Configuration
OR
OR
60
Configuration
61
Configuration Tree Species
62
Configuration Streets
63
PDA Sync

• From the Main i-Tree Configuration screen, click
  the Save and Exit button when your configuration
  is complete. This will take you back to the
  opening screen.
• Synchronize the desktop PC with the Pocket PC.

64
Check PDA Configuration
Configuration QA/QC

• Finally review your Pocket PC configuration by
  clicking the Check Config button on the opening
  screen of the Pocket PC i-Tree program
• Insure volunteers understand all variables and
  PDA entry
• Develop cheat sheets and clear maps for each team

65
COLLECTING DATA

• To begin collecting data, open the i-Tree Pocket
  PC application
• Log in
• Select
• Add New Tree

66
COLLECTING DATALocation
67
COLLECTING DATA
Dimension
Management
68
COLLECTING DATA
Edit
Save
Condition
69
DATA TRANSFER
70
DATA TRANSFER
71
Resources Needed

• Typical city needs
• Transportation
• Detailed street segment maps
• Project leader (create maps, manage/coordinate
  volunteers, data upload, QA/QC)
• Expertise
• Minimal
• 6-8 hrs training is adequate
• Tree ID knowledge desired
• Equipment
• DBH tape (tree diameter) or equivalent (e.g.,
  Biltmore stick)
• PDAs, Clipboard, etc.

72
Trained Volunteer Data Collection
City of 60,000 20,000 Trees 3-5 Sample
600-1,000 trees4 min / tree 50 hrs4 teams
of 3 ? Two 6-hr days 1 day training
73
Field Data Collection

• Groups of three
• DBH tape, PDA per group, manual
• Break 230-245
• 245 Running a STRATUM Analysis
• Computer lab