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 3 <br />Mr. Lloyd advised that staff didn’t perform a comparison between previous and this latest <br />95 <br />proposal.However, Mr.Lloyd advised that the arborist’s review indicated there would <br />96 <br />probably be no replacement required with the trees proposed for removal and fewer <br />97 <br />structures with this development proposal and based on updated tree inventory <br />98 <br />information (e.g. dead trees listed in the previous inventory versus their size and <br />99 <br />condition, and review by diameter breast height, of DBH, in this review). <br />100 <br />Regarding staff comments and review by the DRC related to stormwater flow toward <br />101 <br />Acorn Road, Member Bullsought clarification of the actual flow as displayed on the <br />102 <br />grading plan.Member Bull expressed concern that the proposed infiltration basins may <br />103 <br />not be empty before the next rain event occurs, causing overland flow issues.Member <br />104 <br />Bull questioned long-term maintenance of the basins or how the city would address that <br />105 <br />maintenance. <br />106 <br />Mr. Lloyd reviewed the underground connections, overland flow, and reduced flow <br />107 <br />percentages, noting that not all runoff would be overland, and as modeled, with City <br />108 <br />Engineers and Mr. Mueller’s Engineer still refining the plan, maintenance of the basins <br />109 <br />would be a requirement of the homeowner’s association.However, if the homeowner’s <br />110 <br />association was found at fault in providing that maintenance, the City would step in to <br />111 <br />address maintenance itself or by hiring a third party to do so, and then assess those <br />112 <br />property owners accordingly for that cost . <br />113 <br />If and when city code or watershed district standards change in the future, Member Bull <br />114 <br />asked if these stormwater runoff options would be grandfathered in at the old standards <br />115 <br />or if they would require updating as well. <br />116 <br />Mr. Lloyd clarified that “grandfathering” was a term related to land use, but other parts of <br />117 <br />code provided protections and address that ongoing maintenance and stormwater <br />118 <br />monitoring via a public infrastructure contract. <br />119 <br />Given the fact that this proposal includes a private road, Member Gitzen questioned if <br />120 <br />that required a homeowner’s association to ensure its maintenance, even without the <br />121 <br />addition of stormwater ponds and their maintenance.Member Gitzen noted reference in <br />122 <br />the staff report (lines 121-123) of documents for review and approval by the City <br />123 <br />Attorney, and whether or not that meant they would have input into the contract <br />124 <br />language. <br />125 <br />Mr. Lloyd verified that an association would be required for maintenance of the road.Mr. <br />126 <br />Lloyd confirmed that the purpose of the City Attorney’s review was to protect the City and <br />127 <br />its residents and advised they would revise language accordingly to provide those <br />128 <br />protections. <br />129 <br />Applicant RepresentativeEngineer Charles W. Plowe, PloweEngineering <br />130 <br />Specific to drainage questions raised tonight by commissioners, Mr. Plowe advised that <br />131 <br />the rate control would be addressed through catch basins, with the upstream pond built to <br />132 <br />allow water to drain slowly with minimal if any pooling.Mr. Plowe clarified that this would <br />133 <br />address the same volume of water flowing into the catch basins as experienced today, <br />134 <br />but at a slower rate to avoid street flooding. <br />135 <br />Specific to volume control, a concern brought up by neighboring residents in the past, Mr. <br />136 <br />Plowe clarified that the rate had been slowed as well as the volume reduced, but not by <br />137 <br />82%, but more in the range of 16% volume of water reduced.The reduction by 82% of <br />138 <br />the rate was huge and critical.Mr. Plowe provided rationale in routing the water to Acorn <br />139 <br />Road to help the volume of water flowing in to the southwest portion of the property; and <br />140 <br />with this iteration, water would leave the site very slowly and infiltrate into the drainage <br />141 <br />tile system, connecting to an 8” pipe and downstream into that underground system to <br />142 <br />Acorn Road.Mr. Plowe advised that the City Engineer had indicated there would be no <br />143 <br />problem with this additional flow with existing stormwater management in the area. <br />144 <br />Member Cunningham noted that one reason for previous proposals being ultimately <br />145 <br />denied by the City Council was due to concerns with emergency vehicle access; and <br />146 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.