My WebLink
|
Help
|
About
|
Sign Out
Home
2015-09-02_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2015
>
2015-09-02_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/16/2015 11:32:10 AM
Creation date
10/16/2015 11:32:06 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Minutes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
30
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 Commission Meeting <br />Minutes – Wednesday, September 2, 2015 <br />Page 10 <br />Questions of Staff in response to Public Comment <br />454 <br />Member Cunningham noted two significant concerns for her: tree preservation, and her <br />455 <br />desire that a revised tree preservation ordinance was available even though she <br />456 <br />understood it was in process and not yet ready for adoption, which she found unfortunate <br />457 <br />given the number of large trees being proposed for removal from this project area. Also of <br />458 <br />concern, Member Cunningham advised was the water drainage and runoff as referenced <br />459 <br />by Mr. Ramalingam in his written comments, and expressed her curiosity in whether <br />460 <br />there was actually a potential for “gallons of water” to address as a result of additional <br />461 <br />house foundations and impervious surfaces. <br />462 <br />Public Works Director and City Engineer Mark Culver responded that the numbers stated <br />463 <br />by Mr. Ramalingam were essentially correct and comparable to his calculations resulting <br />464 <br />from additional impervious surface with this proposed project and as noted in his <br />465 <br />summary drainage report. While the basins appear to be shallow, Mr. Culver clarified that <br />466 <br />they were designed to be shallow as they were constructed with engineered soil that <br />467 <br />served as a holding cap not just for depth of the depression, and advised that the total <br />468 <br />actual depth of the engineered soil and the depth of the ponds or depression provided <br />469 <br />sufficient holding capacity. However, Mr. Culver agreed that they were most likely not <br />470 <br />going to hold all the water from large rain events, if similar to the intensity of those rains <br />471 <br />experienced this summer, but opined that from his recollection of his calculations <br />472 <br />believed that the design of the ponds would hold that water or slow down the runoff so it <br />473 <br />didn’t leave the project site. Mr. Culver noted that the water would eventually leave the <br />474 <br />site by infiltrating through soils even though that is not the preferred mitigation. <br />475 <br />Regarding the positive impact of existing trees on drainage, Mr. Culver opined was <br />476 <br />difficult to quantify given the variable canopy of trees that also served to prevent water <br />477 <br />from hitting the ground, even though it dripped off at different spots at different times, <br />478 <br />along with the root systems absorbing some of that water. With those mature trees gone, <br />479 <br />Mr. Culver opined that, while it may not look like a net balance will be achieved, and the <br />480 <br />drainage may not be significantly improved, he considered that it wouldn’t be worse than <br />481 <br />currently experienced during a normal rain event. <br />482 <br />Member Murphy asked, if he owned property on any side of this proposed subdivision if <br />483 <br />implemented, should he expect any more water flowing past his property, or whether the <br />484 <br />subdivision as proposed would change that flow from any direction. <br />485 <br />Mr. Culver responded with his previous comments, advising that the developer had <br />486 <br />attempted to get water into the basins to facilitate the amount of runoff going north. Mr. <br />487 <br />Culver advised that in part that would depend on the location of downspouts for proposed <br />488 <br />homes in the subdivision, and how the long-term control was addressed. However, Mr. <br />489 <br />Culver stated that he wouldn’t anticipate a lot of additional flow to the north, with that <br />490 <br />water flowing through that channel for outflow purposes. <br />491 <br />Mr. Culver sought to correct one statement made during public comment, advising that <br />492 <br />water was not flowing to the catch basin on Marion Street, but approximately halfway <br />493 <br />between Marion and the Mueller property, of approximately 1/3 to ½ that length and <br />494 <br />water flowing through there. Mr. Culver suggested that the speaker may be experiencing <br />495 <br />that water flow across his property and vegetation growth through that natural channel, <br />496 <br />noting that the property owner may see water drainage for a longer time depending on <br />497 <br />rate controls put in place. <br />498 <br />At the request of Member Murphy, Mr. Culver advised that the private street will not have <br />499 <br />catch basins as it was not intended to have curbs and gutters. At the request of Member <br />500 <br />Murphy, Mr. Culver further clarified that the water would flow or drain to the west to the <br />501 <br />end of the hammer head of that private street, and anticipated the remainder would most <br />502 <br />likely drain onto Acorn Road; and confirmed that the capacity exists today to handle that <br />503 <br />additional runoff. <br />504 <br />Member Bull questioned if the basins surrounding the private street were intended to take <br />505 <br />care of the height of the property and street, but questioned whether impacts would not <br />506 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.