My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Appeal Materials
>
OnTrack
>
PDT
>
2017
>
PDT 17-1
>
Appeal Materials
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/10/2018 4:01:03 PM
Creation date
5/9/2018 8:58:19 AM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
PDT
File Year
17
File Sequence Number
1
Application Name
Capital Hill PUD
Document Type
Appeal Materials
Document_Date
5/7/2018
External View
Yes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
58
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
responsibilities. They are called "premature" (CHPUD, p. 30, p. 35). Thus there are no <br />guarantees that any claims and warrants anticipated in the Application would be implemented at <br />later stages in the approval process, The Application proposes "there will be a design review <br />team that will review and approve proposed plans ensuring that the intent of the CCRs is met. It <br />is premature to be preparing CCRs. These should implement final conditions imposed on the <br />approval, if any" (CHPUD, p. 35). The Application seems to consider the content of CC&Rs <br />regarding buildings and preservation of environment as merely "aspirations" (CHPUD, p. 30). <br />No long-term means are in place to protect the proposed preservation and conservation areas <br />once the applicant sells the individual lots. Such general promises at this stage in the <br />development process are not sufficient to ensure that proposed requirements will be met. <br />At the end of the buildout phase, when the individual lots with their intended protected areas are <br />sold for homesites, what's to prevent unscrupulous owners from illegally cutting some of these <br />protected trees in exchange for a small fine from the City if caught - just like the applicant did. <br />He clearcut trees on the lot in front of his house and paid a few thousand dollars for a better <br />view. On proposed individual CHPUD lots, there would not appear to be clear and enforceable <br />boundaries that would prevent encroachment between buildable and preserved areas of each lot <br />and among lots with staggered borders. <br />Appeal Issue #14: The Hearings Official failed to consider all the attributes of significant trees <br />in establishing compliance with EC 9.8320(4). <br />The Hearings Official bases her decision on compliance largely on the basis of tree preservation <br />along the eastern border of the property. This ignores: <br />1. Trees that provide a buffer between potentially incompatible land uses <br />2. Trees located along the perimeter of the lot(s) and within building setback areas <br />3. Trees and stands of trees located along ridgelines and within view corridors <br />4. Trees adjacent to public parks, open space, and streets <br />In his report (Response Document, Attachment H, p.2), the forester Mr. Mehrwein stated <br />"harvesting the designated trees would significantly increase the risk of wind damage to the <br />remaining trees. Trees not only on the CHPUD site, but also in adjacent private properties and <br />in Hendricks Park and the Ribbon Trail would be increasingly vulnerable to being blown down <br />or having tops broken. " <br />The same argument would apply to homes adjacent to the proposed PUD site near the ridgeline, <br />where cutting trees near lot lines endangers neighboring properties. The proposed PUD shares a <br />378 foot boundary with Hendricks Park, and the Applicant has failed to create a buffer between <br />the trees to be cut above 901' on the ridgeline and the trees in the Park. <br />Appeal Issue #15: The Hearings Official erred on pages 38 and 39 by stating that Applicant <br />satisfies section (4)(b) by agreeing to replace trees cut down in preservation areas for the <br />17 <br />
The URL can be used to link to this page
Your browser does not support the video tag.