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
SeealsoinSection EC9.8320(6)and(10)(d)ofthisResponsedocumentadditionaldiscussion <br />oflandslidepotential. <br />NotethatamoreacceptablesolutionwouldbefortheApplicanttodedicateLots18and19tothe <br />Citysothatthemoreseverelandslideareaistrulyblockedfromdevelopment.Doingsowould <br />createalargernaturalbufferonthesouthernendoftheproposedprojectandwouldalsoprovide <br />greateraccessforthepublicandthepotentialPUDresidentstotherecreationalareasofthe <br />RibbonTrailandHendricksPark.AdedicationtoHendricksParkofsomelotsatthenorthern <br />endoftheproposedPUDwoulddothesame.Bothofthesededicationswouldimprovesafety <br />withintheprojectanddecreasetheneedforlotfrontagevariances. <br />The8/22/17ApplicationstatesthefollowingonPage59of67: <br />“WeareaskingforflexibilityforlotfrontageforLots5,6,8,9,16,17,18,19and33,asthey <br />donotmeettheminimumfrontagerequirements.Similarlytoourrequestforflexibilityfor <br />lotcoverageabove,flexibilityisprovidedthroughboththePUDprocessandtheEugene <br />Codetopromotedesignthatmeetscommunityvalues.Thelotfrontagerequirementsare <br />basedonatraditionallot-by-lotapproachtodevelopment,whichisnotaone-size-fits-all <br />approachtodevelopment.R-1lotsarerequiredtohave50feetoffrontage,whileother <br />residentialzones(excludingR-1.5)arepermitted35feet.Moreover,rowhouselotsareonly <br />requiredtohave15feetoffrontage.ThePUDprocesspermitstheapplicanttorequest <br />flexibilityregardinglandusecriteriatodesignadevelopmentthatisunique,livable,and <br />sustainable.”(Emphasisadded.) <br />TheCommitteequestionstheApplication’sstatementaboveregardingcommunityvalues.How <br />doshorterlotfrontagelengthspromotedesignthatmeetsso-called“communityvalues”?This <br />statementisnonsenseandthetypeof“landplanningspeak”thatseekstocamouflagedesign <br />deficiencies,notpromotethem.Ofcourselotfrontagerequirementsarebasedonthetypeof <br />structureproposedi.e.,rowhousesshouldhaveashorterrequiredfrontagethansinglefamily <br />detachedhomes.Amore“livable”designwouldbeonewhereresidentscouldactuallyseethe <br />streetandtheirneighborsandtheirchildrenatplay,seevehiclesandpedestriansapproaching <br />theirfrontdoor(safetyfactor)andbeapartofcommunityactivities. <br />“Throughnotrequiringeverylottohavefrontage,thePUDisabletoprovideathoughtful <br />designthatprovidesaccesstopublicandprivatestreets,whilepreservingtreesand <br />vegetationthroughreducingtheuseofextraneousgradingandcutandfill.”(Emphasis <br />added.) <br />TheCommitteehaspreviouslydiscussedthatthecurrentsiteplanfortheproposedprojectis <br />“contrived”becauseofthegeologicalchallengeson-site.Together,theApplication’sdesireto <br />retainseverallargelots,thelandslidedangerinthesouthernportionofthesite,andthesteep, <br />unbuildableportionalongtheeasternedgeofthesitecombinetoforcethelocationofbuildings <br />alongCupolaDrive.Amore“thoughtful”designwouldreducethenumberoflotssothatfewer <br />lotswouldfrontontoCupolaandwouldalso,perhaps,dedicateLots18and19(andevenLots5, <br />6and8)totheCityforexpansionofHendricksParkandRibbonTrailaccess. <br />153 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.