Laserfiche WebLink
Regular Planning Commission Meeting <br />Minutes – Wednesday, August 03, 2011 <br />Page 16 <br />Chair Boerigter suggested that in the language related to development agreements, it <br />760 <br />may make sense to expand upon and clarify language so that if a developer met other <br />761 <br />requirements, there would be no additional “hoops” added on at the point of the <br />762 <br />development agreement; and asked that staff consider how best to address that intent in <br />763 <br />their revisions. <br />764 <br />Member Strohmeier concurred with other Members that he was not yet ready to <br />765 <br />recommend this ordinance to the City Council for approval; and that it be tabled for <br />766 <br />another month. Member Strohmeier opined that he wasn’t entirely sure about his <br />767 <br />conclusions in tying costs to zoning ordinance; and while not opposed to such a <br />768 <br />provision, opined that the developer should have environmental accountability. Member <br />769 <br />Strohmeier further opined that this was a good first start; however, he would prefer that <br />770 <br />more infrastructure mitigation be required, specifically related to environmental provisions <br />771 <br />and habitat corridor issues, opining that current language was too vague, and he <br />772 <br />preferred more green space also be addressed in the ordinance in its next draft. <br />773 <br />Member Cook asked that, at the next meeting when this is brought forward again, that <br />774 <br />the City Engineer be present, or include a report on how the trips were generated and <br />775 <br />how they were formulated; as well as an update on costs if available for that meeting. <br />776 <br />While recognizing that there may be perfectly logical rationale, Member Wozniak, along <br />777 <br />that line, opined that it would be helpful to have staff provide additional information and <br />778 <br />clarification to the Commission on why there appeared to be such a disparity in trips <br />779 <br />along different parcels, even those adjacent to each other. <br />780 <br />Chair Boerigter concurred with those additional requests by Commissioners, and so <br />781 <br />directed staff to include them in their future reports. <br />782 <br />MOTION <br />783 <br />Member Boerigter moved, seconded by Member Boguszewski, to RECOMMEND <br />784 <br />TABLING consideration of the proposed Twin Lakes Overlay District Zoning <br />785 <br />Ordinance; as detailed in the Request for Planning Commission Action dated <br />786 <br />August 3, 2011, until the September Planning Commission meeting. <br />787 <br />Ayes: 6 <br />788 <br />Nays: 0 <br />789 <br />Motion carried. <br />790 <br />c. PROJECT FILE 0017 <br />791 <br />Request by Roseville City Council for approval of a ZONING TEXT AMENDMENT to <br />792 <br />allow accessory dwelling units in LDR-1 Districts as permitted rather than <br />793 <br />conditional uses. <br />794 <br />Chair Boerigter opened the Public Hearing at 8:34 p.m. <br />795 <br />Associate Planner Bryan Lloyd highlighted and briefly summarized staff’s proposed <br />796 <br />zoning text amendments for Accessory Dwelling Units (ADU’s) in LDR-1 Districts as <br />797 <br />permitted rather than as Conditional Uses (CU’s). Mr. Lloyd advised that these <br />798 <br />recommended amendments were based on practical application of the existing language <br />799 <br />with the two (2) applications having already come forward; suggesting they be considered <br />800 <br />as permitted uses with applicable permits for their regulation to a higher standard without <br />801 <br />going through the CU approval process. <br />802 <br />Recommended amendments were included in the packet materials as detailed in the <br />803 <br />Request for Planning Commission Action dated August 3, 2011; and based on the <br />804 <br />comments of Section 2-3 and input received from tonight’s public hearing. <br />805 <br />Member Boguszewski advised that his only question was related to Chapter 1011.12, <br />806 <br />Section B.6.b-d as it addressed a maximum occupancy of two (2) people (line 9), noting <br />807 <br />that the previous language used square footage guidelines, and those now seemed to be <br />808 <br />removed. Member Boguszewski questioned the rationale for that change; and why staff <br />809 <br />was recommending square footage guidelines and moving toward occupancy as the <br />810 <br />limiting number. <br />811 <br /> <br />