My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Appeal Staff Report
>
OnTrack
>
PDT
>
2015
>
PDT 15-1
>
Appeal Staff Report
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/20/2016 4:01:57 PM
Creation date
1/19/2016 1:32:11 PM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
PDT
File Year
15
File Sequence Number
1
Application Name
CHAMOTEE TRAILS PUD
Document Type
Appeal Staff Response
Document_Date
1/19/2016
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
lots. The HO relied on these facts in his findings for denial. <br />The appellant disagrees with the HO's interpretation of the 19-Lot Rule. The appellant argues that the <br />word "disperse" is not clear and objective because it is not defined in the land use code. In effect, the <br />appellant asserts this standard cannot be applied as part of the Needed Housing Criteria. <br />The appellant also raises issue with EC 9.8325(3), which requires a 30-foot wide landscape buffer. The <br />Hearings Official did not use this criterion as a basis for denial; regardless, the appellant suggests that <br />this criterion should not be applied to any PUD proposal under the Needed Housing Criteria. In <br />summary, the appellant believes that if this criterion was applied literally, it would preclude access to <br />any potential development site. In the past, staff has applied this criterion in a manner that allows <br />driveways or streets to penetrate the landscape buffer. <br />1. First Assignment of Error: The 19 Lot Rule meaning in the Code: The Commission should find <br />that the Hearings Official selected the wrong definition of "disperse." Neither the code <br />language nor the context for the code language requires that traffic be dispersed to any <br />particular point or distance from the project. <br />Summary: <br />The appellant believes the land use code fails to specify how the word "disperse" should be applied in <br />the context of the 19-Lot Rule, and that the HO otherwise selected the wrong definition of the word <br />(see below). As a result, the appellant asserts that this criterion is ambiguous and therefore cannot be <br />applied as a clear and objective standard under the Needed Housing statutes. <br />HO Decision: <br />The HO stated "Here, where the 'layout' of the PUD relies on only one public street to disperse <br />motor vehicle traffic, that traffic at minimum must be able to go somewhere in two different <br />directions that do not terminate in a dead end" (HO Decision, page 15). <br />The HO further states: <br />"Taking this part [1b] of the definition of 'disperse' into account contradicts the argument that it is <br />enough that traffic can move in both directions along West Amazon from the proposed PUD. Mr. <br />Kloos concedes that such traffic could only travel 1000 feet to the barrier on West Amazon - but he <br />urges that even such a short distance is enough to meet the standard. By this logic the standard <br />could be met if traffic could travel even one block to an existing cul-de-sac. This interpretation is <br />contrary to the both the '1al and 1b" definition of "disperse" as used in EC 9.8325(6)(c)" (HO <br />Decision, page 15). <br />Staff Comments: <br />The HO concluded that the 19-Lot Rule is clear and objective, and that staff correctly applied it. The PC <br />is tasked with determining whether or not the HO erred in applying this standard to the subject <br />Webster's Third New International Dictionary, definition 1a of "disperse": To cause to break up and go in different <br />ways: send or drive into different places <br />Webster's Third New International Dictionary, definition 1b of "disperse": To cause to become spread widely <br />Page 3 <br />PC Agenda - Page 3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.