Laserfiche WebLink
<br />an injunction to enjoin development within the <br />protected area. <br />The "Whole Parcel !.lule" is alive and <br />well in the context of tree protection plans. <br />Key to the defensibility-of most tree protection <br />ordinances is the so-called .whole-parcel <br />rule," which is sometimes misapplied by the <br />courts. Recent decisions affirm that when <br />evaluating economic loss occasioned by land- <br />use regulation, courts must consider the <br />whole parcel owned by the plaintiff and not <br />just the portion subject to the regulation. <br />In Coast Range Conifers v. State of Oregon <br />. (339 Or. 136 (2005)), a logging company chal- <br />lenged the denial of a permit request to log tim' <br />ber within an area designated by the state asa <br />bald eagle nesting site. In 1996, the plaintiff <br />company acquired a 40-acre tract of timberland. <br />Two years later, state employees observed two <br />adult bald eagles nesting on the property. ' <br />Pursuant to a state law that protected the habitat <br />of species listed as endangered by the U.S. gov- <br />emment, the plaintiffs were required to submit a <br />plan to the state forester before cutting down <br />any trees on the property. The forester rejected <br />the plaintiff's plan, which proposed to log within <br />330 feet of the nest, and recommended that the <br />plaintiffs resubmit a plan that protected a 400- <br />foot buffer around the site (about nine acres). <br />The plaintiffs did so, and the plan was approved. <br />At the conclusion of the nesting season a <br />few months later, the plaintiffs submitted a new <br />plan to resume logging the remaining nine <br />acres surrounding the eagles' nest. The forester <br />denied the plan, and the board of forestry <br />upheld that decision. The plaintiffs filed suit <br />against the State of Oregon and its forestry <br />board, alleging that the denial of the plan <br />deprived them of all economically beneficial <br />use of the remaining nine acres of timberland <br />and that the denial amounted to a "takingn <br />under the Oregon and United States constitu- <br />tions. The state did not dispute the beneficial <br />use claim as applied to the protected area; <br />instead, it contended that the plaintiffs were <br />able to make beneficial use of the other 30 <br />acres of their parcel, which were unaffected by <br />the state's regulation of the eagle habitat. <br />On appeal, the Oregon Supreme Court <br />held that both constitutions require a plaintiff <br />to show that there is no remaining economi- <br />cally beneficial use of the land as a whole <br />parcel (i.e., all 40 acres owned, and not just <br />the nine acres affected) as a result of the <br />state's habitat protection regulations. <br />Regulations requiring preservation of <br />trees do not give rise to physical occupation <br /> <br />oJ property to support a per se takings claim. <br />In recent years, the Court of Appeals for the <br />Federal Circuit has twice heard and rejected <br />per se physical taking claims allegedly aris- <br />ingfrom regulations and government actions <br />that prevented the harvesting of timber on <br />lands designated as spotted owl habitat <br />(Seiber v. United States, 364 F.3d 1356 (Fed. <br />Cir. 2004)) and Boise Cascade Corporation v. <br />United States, (296 F. 3d 1339 (Fed. Cir. <br />2002)). A claim for a physical occupation tak- <br />ing rests on showing that the government <br />has compelled a complete and permanent <br />physical occupation of private land for a pub- <br />Ii.c purpose. <br /> <br />Increasingly rare is <br />the modern development <br />code in a progressive <br />community-urban, <br />suburban, and rural <br />alike-that does n.ot have <br />some form of tree or <br />vegetation conservation <br />regulation. <br /> <br />In Boise, the court of appeals affirmed the <br />dismissal of Boise Cascade's takings claims <br />against the U.S. Fish and Wildlife Service. Boise <br />Cascade's complaint included a claim that a <br />federal injunction that enjoined the cutting of <br />old growth timber in a designated spotted owl <br />habitat resulted in a physical occupation of pri. <br />vate property under Loretta v. Teleprompter <br />Manhattan G4TC Corp. (458 U.S. 419 (1982)). <br />The court ruled that the physical occupation <br />claim (that the owls physically invaded the <br />property) was untenable primarily because the <br />govemment did not force and could not control <br />the owls' occupation of the property. <br /> <br />REGULATORY APPROACHES <br />While surveys conducted in the 1980s revealed <br />that relatively few jurisdictions had tree protec- <br />tion standards on the books, today, increas- <br />ingly rare is the modern development code in a <br />progressive community-urban, suburban, and <br />rural alike-that does not have some form of <br />tree or vegetation conservation regulation. <br />These new ordinances are increasingly strin- <br />gent and sophisticated, often protecting <br />smaller trees as well as specimen trees and <br /> <br />large tracts of woodland. They frequently <br />require mitigation either on- or off-site if trees <br />are destroyed during construction or provide <br />for cash.in-lieu payments into a local tree <br />preservation fund. These ordinances are often <br />part of a more comprehensive effort to protect <br />wildlife habitat or scenic vistas and even to <br />counter the impacts of global warming. <br />Specimen and special tree protection. <br />Many jurisdictions require permits for the <br />removal or alteration of "special" trees on pri. <br />vate property. "Specialn is typically defined as <br />those exceeding a certain diameter, size, or <br />other physical parameter. Terms such as "cham- <br />pion" or "monarch" trees may be the operative <br />nomenclature in the local ordinance. Addition. <br />ally, special trees may be defined to include <br />those with special historical associations (for <br />example, a treaty may have been signed under a <br />tree's boughs). Some communities maintain reg- <br />istries for large trees, much like lists of landmark <br />buildings. Others rely on identification through <br />surveys required during the site planning <br />process as outlined in the previous section. <br />Probably the most common approach to <br />protecting special trees is to require protection <br />of all specimens that exceed certain physical <br />specifications. In Austin; Texas, for example, a <br />"protected tree" means "any tree having a trunk <br />circumference of 60 inches or more, measured <br />four and one-half feet above natural grade <br />level." Other ordinances are similar but use <br />diameter at 4.5 feet above the ground instead of <br />circumference (what is commonly known in the <br />trade as diameter at breast height, or "DBH"). <br />While trunk size specification is a simple <br />and straightforward way of protecting trees, it <br />can be very imprecise and result in protecting <br />unworthy trees or missing critical ones. Thus, <br />while an oak with a DBH of one foot is not <br />particularly unusual, a dogwood of that size is <br />quite remarkable. To deal with this issue; an <br />increasing number of jurisdictions are estab- <br />lishing variable size specifications depending <br />on the species of the tree. Another protection <br />criterion, although far less common than size, <br />is the tree species itself. Some communities, <br />including Thousand Oaks, California, concen- <br />trate their protection efforts on only one <br />species of tree-in this case. oak trees. <br />Tampa, Rorida,,focuses its specimen tree pro- <br />tection efforts o~ 12 species, although others <br />can be protected by the parks department <br />upon adoption of appropriate standards. A <br />variation on this approach, which is gaining <br />more adherents, is to protect all native vege- <br />tation to the maximum extent possible. <br /> <br />ZONING PRACTICE 7.06 101 <br />AMERICAN Pu\NNING ASSOCIATION I page 5 <br />