Compare the proposed and current bylaw

Proposed Draft

Tree Management Bylaw

Current

Tree Protection Bylaw

Introduction of Tree Density Target to determine number of replacement trees

Replacement ratio of 3:1 required through rezoning

Replacement ratio of 3:1 applies to all tree removal, up to the tree density target

Specimen(s) of same species with aggregate truck diameter at breast height equal to aggregate trunk diameter of tree that was removed and in same location.

Tree removal within building envelope requires replacement trees

Tree removal within building envelope is exempt from tree permit

Trees with a diameter of 20cm or more are protected

Trees with a diameter of 60cm or more are protected

Incentive for tree retention through credit toward target density

No incentive for tree retention.

Cash in lieu option available if trees cannot be planted on site

No cash in lieu option

Security for replacement trees held for one year

Security for replacement trees held for three years

Fees for all tree permit applications, except those for hazardous tree removal

Most applications do not require a fee

Tree removal in Erosion District requires one permit application

Tree removal in Erosion District requires two permits, from Planning and Engineering

Removal of municipal trees due to development requires replacement trees and contribution to Tree Planting Reserve Fund

Inconsistent application of requirement for replacement trees as a result of municipal tree removal due to development

Tree removal on ALR land requires statement that removal is for agricultural purposes

Tree removal on ALR land is exempt from any permit.

Protective fencing is required to be in place prior to tree permit issuance

Protective fencing is required to be in place prior to any works on site

Share Compare the proposed and current bylaw on Facebook Share Compare the proposed and current bylaw on Twitter Share Compare the proposed and current bylaw on Linkedin Email Compare the proposed and current bylaw link

Consultation has concluded

#<Object:0x0000000024db0e60>