My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Public Comments submitted at hearings official hearing (NRC 1)
>
OnTrack
>
PDT
>
2017
>
PDT 17-1
>
Public Comments submitted at hearings official hearing (NRC 1)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/12/2018 10:39:26 AM
Creation date
3/12/2018 10:38:33 AM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
PDT
File Year
17
File Sequence Number
1
Application Name
CAPITAL HILL PUD
Document Type
Public Comments submitted at hearings official hearing
Document_Date
3/7/2018
External View
Yes
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
334
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
TheproposedCHPUDsiteshouldberegardedasmorethanjusttechnically“vacantproperty,” <br />becauseitisnotbarren,emptyacreage,butitcontainsalargeforestedexpansecontiguouswith <br />HendricksParkandtheRibbonTrail.Therearefivecurrenttaxlots,threeofwhichcontain <br />habitabledwellings,withadifferentthreelotscurrentlyzonedR-1/PD.Thereisnoevidence <br />presentedintheApplicationtosupportitsdisdainfultoneinthispoorly-wordedsentence:“this <br />developmentislikelythemostcompatibleneighborabuttingpropertyownerscouldreasonably <br />expect”(p.61).Thesimplestresponsetothisclaimisthattheexistinglotscouldbedeveloped <br />differentlywithlessclustereddensityandmorerespectforthequalityofdesignandthe <br />environmentsurroundingahistoricneighborhood,thantheintrusiveproposedCHPUD. <br />Amongthemostseriousandirreversibleoff-siteimpactsoftheproposedCHPUD: <br />•itwouldjeopardizethesafetyofpedestrians,motortraffic,andemergencyservices <br />responsetime,especiallytheabilitytonavigate,throughouttheexistingneighborhood <br />roadwaysservingtheproposedprivateroad,byincreasingtrafficvolumeanduserinteractions <br />onnarrowstreets\[see EC9.8320(1),(5),(6)\]; <br />•itwouldpermanentlychangeanddepletetheenvironmentalqualityandnaturalurban <br />resourceoftheforestedlandscapeofproposeddevelopmentsite,impactingtheridgelinearea <br />oftheSouthHills,RibbonTrail,HendricksPark,andtheintegralview-shedthatisadefining <br />qualityandheritageofEugene’senvironment\[see EC9.8320(2),(4),(8)andForester’s <br />Report,AttachmentH\]. <br />BecauseoftheuniqueandiconiclocationofthesiteproposedfortheCHPUD,inahistoric <br />neighborhoodadjacenttoaheritagecitypark,itisinescapablethattheproposedCHPUDwould <br />havemajorimpactswithinandoffofthesite.Cross-referencesnotedaboveshowthe <br />interconnectionbetweentheseonandoff-siteimpacts.JustastheApplicationdoesnotmeetthe <br />abovelistedCodeCriteria,itdoesnotsatisfythis CriterionEC9.8320(11).Specificdiscussion <br />andevidencefollow. <br />Off-siteImpactsonTrafficandRoadwayAccess/EgressCausedbyProposedCHPUD <br />Thereareobviouslimitationsintheimmediateneighborhoodroadnetworkforalltraffic <br />access/egressfortheproposedCHPUD.Theselimitationsapplytoallmotorvehicles(from <br />smallprivatecarstoheavy,oversizedcommercialandemergencytrucksandvans),bicyclists, <br />motorcycles,pedestrians–joggers,runners,dogwalkers,sight-seers–allofwhichmustshare <br />thenarrowroadwayswithnarrowandshortornosidewalks.Theselimitationswouldbe <br />significantlyexacerbatedbytheadditionaltrafficattributedtotheproposedCHPUD.Thiswould <br />resultina28-31%increasefrom31-35proposednewunits,inrelationtothe112existing <br />residencesthatrequireaccesstotheneighborhoodroadnetworkabovetheFairmount <br />Blvd./SpringBlvd.intersection. <br />ThemostcriticallimitationisevidentinthatSpringBlvd.,fromitsbeginningatthenorthwest <br />intersectionwithFairmountBlvd.,mustcarryalmostalltrafficuphilltoanddownhillfromthe <br />five-wayintersectionof:(1)SpringBlvd.,(2)thebeginningofCapitalDr.,(3)MadronaSt.,(4) <br />164 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.