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
However,theApplicanthasconsistentlyrefusedtoprovidethePlanningDept.andthe <br />community-at-largeanyindicationofthepossibleheightandbulkoffuturehomesonthe <br />buildableportionoftheproposedlots.Undoubtedly,theApplicant’sconsultanthasthe <br />professionalcapabilityofprovidingsuchdatawithrelativeease.TheCommittee(and, <br />moreover,thecommunityatlarge)wouldfindananalysisofbuildingheightandbulkvery <br />beneficial.Whyhavetheyrefused? <br />TocontinuallystatethroughouttheApplicationthattheproposedprojectwill“blendinwiththe <br />naturalcharacteristicsoftheSouthHillsarea,”thattheprojectwillnotbevisiblefromthe <br />RibbonTrail;orthatthe“developmentsiteisanattractiveandvariedneighborhoodthatis <br />reasonablycompatiblewiththesurroundingresidentialenvironment”whennofactualorvisual <br />evidenceisprovidedtosupportsuchclaimsdoesnotaddressthevalidissuesraisedbyour <br />understandablyalarmedcommunity. <br />OnceagaintheCommitteeisextremelyconcernedbytheApplication’scarelessnessregarding <br />theultimateintegrityofthelongtermprojectitproposes. <br />HowdoestheproposedPUDtakeshapeasbuildingpermitsmovethroughtheapprovalprocess? <br />Thereisnoguaranteedconsistencyofdesign.Page35of67ofthe8/22/17Application <br />referencesa“DesignReviewTeam”andthatthe“CapitalHillCC&Rs willprovide guidelinesfor <br />thebulk,heightandscaleofthebuildings.”(Emphasisadded.) <br />However,onceagain,withoutevendraftCC&Rs,thecommunityhasnowrittenevidencethat <br />suchguidelinesand/orreviewcommitteewillbeinplace.Whatisthepossiblecompositionof <br />themembersoftheDesignReviewTeam?Whatwillthe(nownon-existent)guidelinesconsist <br />ofandhowwilltheycontrolhomedesignandconstruction? <br />StatementssuchastheonefoundonPage62of67ofthe8/22/17Applicationunderscorethese <br />concerns.OnPage62theApplicationstates“TheCC&Rs(notyetdeveloped)mayprovidesome <br />controloverthebuildingsize,colorandothersuchdetails….”(Emphasisadded.) <br />“Will”provideand“may”provideareworldsapartwhentheintegrityofanhistoric <br />neighborhoodisatstake. <br />TheApplication’sobstinaterefusaltoaddressevenbasicdesignstandardsmeansthatresidence’s <br />exteriorcolorscouldvarywidelyandtraditionalcolonialhomestylescouldawkwardlyabut <br />high-techmodernhomestyles.Atotallackofconsistency–aliteral“hodgepodge”ofhome <br />styles,setbacks,roofheights,landscapechoicesandlightingdesignwillemanatefromthe <br />Application’sobviousefforttoleavefuturedesigndecisionstoothers,regardlessoftheircertain <br />impacttofuturegenerations.Ourcommunitydeservesbetter. <br />Additionally,thisnebulousareawillwreakhavocfortheCity’sPlanningandDevelopment <br />Departmentbecausedesignstandardsarenon-existentfortheproposedproject,everybuilding <br />permitrequestemanatingfromthesubjectdevelopment,over(perhaps)a10to15yearperiod, <br />willseektostretchthelimitsasfaraspossible.TheApplicationhasshiftedtheburdenofdesign <br />consistencytotheCity.Precedentswillbesetbyinitiallyapprovedhomeconstructionfrom <br />whichtheCitywillfinditdifficulttobackaway. <br />129 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.