My WebLink
|
Help
|
About
|
Sign Out
Home
2016-01-06_PC_Agenda_Packet
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Agendas and Packets
>
2016 Agendas
>
2016-01-06_PC_Agenda_Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/8/2016 4:22:35 PM
Creation date
4/8/2016 4:22:30 PM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Agenda/Packet
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
44
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
Regular Planning CommissionMeeting <br />Minutes –Wednesday, December 2, 2015 <br />Page 2 <br />considerations; with the City’s Engineers continuing to work with the applicant and review <br />45 <br />requirements or changes to ensure the project continued to conform to city code and <br />46 <br />watershed requirements throughout the process. <br />47 <br />Mr. Lloyd briefly reviewed the tree preservation reviewed by the City’s tree consultant <br />48 <br />Mark Rehder, S & S Tree Service,with monitoring continuing as the project proceeded. <br />49 <br />Specific to Park Dedication, Mr. Lloyd reported that with two additional lots, the Parks & <br />50 <br />Recreation Commission had determined cash in lieu of land. <br />51 <br />As noted in the staff report (line 99), Mr. Lloyd advised that the Development review <br />52 <br />Committee (DRC) provided several comments for recommendation, and highlighted the <br />53 <br />need for including Item D (lines 121 –123) to ensure a homeowners association be a <br />54 <br />condition of approval to ensure long-term private street and stormwater infrastructure <br />55 <br />maintenance remains intact. <br />56 <br />Discussion <br />57 <br />Chair Boguszewski asked for clarification if the additional flow capacity for Acorn Road <br />58 <br />was new or had been there before; and whether the City Engineer had an estimate of the <br />59 <br />total flow pulled toward Acorn Road and away from that southwest corner. <br />60 <br />Mr. Lloyd responded that the routing is new for this iteration of the OakAcres <br />61 <br />Development proposal, as in the past runoff was routed to rain gardens at the southwest <br />62 <br />corner of the proposed development.Mr. Lloyd reported that the City Engineer had not <br />63 <br />specifically isolated the total flow from the southwest corner now proposed to be directed <br />64 <br />to Acorn Road stormwater infrastructure, but the difference in volume of stormwater <br />65 <br />leaving the southwest corner ofthis proposal versus previous iterations reduced that <br />66 <br />runoff by approximately 58% for a 100 year rain event calculation.At the request of Chair <br />67 <br />Boguszewski, Mr. Lloyd clarified that (as noted in line 106 of the staff report) overall flow <br />68 <br />was actually reduced by approximately 82% with this latest development proposal, and <br />69 <br />reduced 58% from the previous iteration.As noted by Chair Boguszewski, this provided <br />70 <br />the neighborhood with an approximate 82% improvement in stormwater flow compared to <br />71 <br />current runoff flowing from the property. <br />72 <br />On line 113, Chair Boguszewski questioned the subjective term “aggressive proposal” <br />73 <br />and asked Mr. Lloyd to describe what was intended for a homeowners association and <br />74 <br />their financial burden. <br />75 <br />Mr. Lloyd advised that that term originated with review by the City’s Public Works <br />76 <br />Department, and opined the proposal was certainly aggressive in the sense it provided <br />77 <br />many places for water infiltration for rate control, and significantly reduces current rates <br />78 <br />and volumes.However, Mr. Lloyd noted there was also a cost component and need to <br />79 <br />make sure funding remained available long-term to address those many maintenance <br />80 <br />components and their complexities. <br />81 <br />Member Murphynoted that water runofffrom the subject site to neighboring properties <br />82 <br />had continued to be of great concern in past iterations, and asked staff if this iteration <br />83 <br />was implemented as designed indicated only 18 gallons of stormwater runoff.Member <br />84 <br />Murphy asked if there would be anycost to the city for connectingand diverting <br />85 <br />stormwater flow to the Acorn Road system or if itwould borne entirely by the developer. <br />86 <br />Mr. Lloyd clarified that runoff was measured by cubic feet per second, not gallon, and <br />87 <br />confirmed that 100 year rain event model numbers indicated that would be the case and <br />88 <br />as compared with typical rain events where stormwater runoff should easily be addressed <br />89 <br />through infiltration of one mode or another.Mr. Lloyd confirmed that the cost to divert <br />90 <br />stormwater flow to the Acorn Road infrastructure would be at the cost of the developer to <br />91 <br />implement. <br />92 <br />Member Murphy asked staff for a comparison with this latest tree removal plan with that <br />93 <br />of the most recent past iteration. <br />94 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.