Laserfiche WebLink
Regular Planning Commission Meeting <br />Minutes – Wednesday, August 3, 2016 <br />Page 7 <br />and medium density residential (MDR), involving parcel area measurements as <br />306 <br />part of the calculation, seeking to provide some consistency and realistic <br />307 <br />measurements that didn’t prove arbitrary in nature. <br />308 <br />Mr. Lloyd briefly summarized his understanding of engineering staff’s hydrology <br />309 <br />analyses to determine runoff based on lot coverage and under certain rain event <br />310 <br />percentages. Mr. Lloyd noted engineering staff found plenty of capacity at a 30% <br />311 <br />level, and that it could still be adequately addressed at 40%, but that 50% was <br />312 <br />beyond their comfort level. As part of their technical analysis, Mr. Lloyd advised <br />313 <br />that the engineering staff had reviewed existing LDR properties and approximated <br />314 <br />impervious surfaces on those properties, finding them to be at about the same <br />315 <br />level; substantiating their recommended 40% hydrology percentage as an <br />316 <br />acceptable level. <br />317 <br />Member Gitzen asked if there was a standard definition in city code for “pervious” <br />318 <br />and “impervious” especially in light of newer technologies and permeable pavers <br />319 <br />now allowable while still meeting coverage allowances. <br />320 <br />Mr. Lloyd noted there were definitions, but also clarified that this involved more <br />321 <br />than just talking about different kinds of pervious or impervious treatments or <br />322 <br />pavements, but included filtering through grass and provided several examples <br />323 <br />(e.g. beehive cement pavers and Geogrid products) that were between <br />324 <br />impervious and pervious surfaces that required staff and the city to understand <br />325 <br />the product being proposed going forward, how it would be installed and <br />326 <br />maintained, and then pro-rate those areas and type of material used accordingly. <br />327 <br />Mr. Lloyd noted this added complexity to those calculations for either surface <br />328 <br />area. Mr. Lloyd referenced a pervious asphalt parking lot installed by the Rice <br />329 <br />Creek Watershed District on the other side of Rice Street, as well as addressing <br />330 <br />the added costs for these newer materials at this point in time, as well as <br />331 <br />agreements to address long-term maintenance to ensure the materials continue to <br />332 <br />work as permeable applications. <br />333 <br />At the request of Member Bull, Mr. Lloyd further reviewed the hydrology tests on <br />334 <br />typical LDR-2 and LDR-1 lots, with far fewer LDR-2 lots in Roseville and the <br />335 <br />rationale that if higher impervious surfaces are allowed on LDR-2 lots it may <br />336 <br />overtax the storm water system downstream. However, in addressing the square <br />337 <br />foot minimum lot sizes and comparing LDR-1 and LDR-2, Mr. Lloyd noted it made <br />338 <br />more development possible on smaller lots, if calculations were more than the <br />339 <br />current 30%, but less than the originally requested or proposed 50%. <br />340 <br />Member Kimble stated she found proposed language on Attachment A, lines 32- <br />341 <br />33 related to residential water permits based on the findings of the city engineer <br />342 <br />and intended mitigation somewhat ambiguous. However, the redlined copy <br />343 <br />following that defined more specific language; with Member Kimble asking if that <br />344 <br />should be more consistent. <br />345 <br />Mr. Lloyd clarified that the language was intentionally ambiguous in light of the <br />346 <br />aforementioned proposed stormwater permit process being drafted by the Public <br />347 <br />Works Department as an optional tool for those property owners exceeding their <br />348 <br />impervious coverage allowances and paying a fee to be accumulated with others <br />349 <br />for a broader stormwater improvement project or system. If the first part of the <br />350 <br />language is more specific at this point, Mr. Lloyd noted it would have to be revised <br />351 <br />again if and when that tool becomes available. <br />352 <br />Member Kimble recognized that intent; however, she opined it looked like there <br />353 <br />was no defined standard and that the engineer could decide independently and <br />354 <br />arbitrarily for each applicant. Specific to mitigating, Member Kimble noted there <br />355 <br />were qualifiers afterward in the redlined portion of the text. <br />356 <br />Chair Boguszewski opined there were probably a number of properties in <br />357 <br />Roseville already exceeding these proposed percentages; and asked staff what <br />358 <br /> <br />