Laserfiche WebLink
Regular Planning Commission Meeting <br />Minutes – Wednesday, July 9, 2014 <br />Page 4 <br />Member Daire advised that he had visited the site earlier today, and noted the downhill <br />145 <br />gradient bottoming out in the middle of where the berm was being shown. <br />146 <br />Mr. Hanson concurred, noting that, while it couldn’t be completely blocked off, the berm <br />147 <br />could be used to create planting and visual amenities to direct eyes to the plantings <br />148 <br />versus the house. <br />149 <br />Member Stellmach questioned if the rain gardens and berms would be maintained by the <br />150 <br />homeowners or by an association. <br />151 <br />Applicant Nathan Fair, partner of Landmark of Roseville, LLC <br />152 <br />Mr. Fair advised that, typically with larger Landmark developments, they created an <br />153 <br />association. However, with this smaller development of five lots, covenants would be put <br />154 <br />in place that the owner of Lot 5 would maintain the berm, and owners of Lots 3 and 4 <br />155 <br />would maintain the rain garden. <br />156 <br />Vice Chair Boguszewski closed Public Hearing at 7:23 p.m.; no one spoke for or against. <br />157 <br />Member Daire noted that, between the open house and formal presentation of this <br />158 <br />preliminary plat, the developer had reduced the development from six to five lots. <br />159 <br />MOTION <br />160 <br />Member Stellmach moved, seconded by Member Murphy to recommend to the City <br />161 <br />Council APPROVAL of the proposed PRELIMINARY PLAT for the residential <br />162 <br />property at 301 – 305 S Owasso Blvd., into five lots; based on the comments and <br />163 <br />findings, and subject to conditions as detailed in the staff report dated July 9, <br />164 <br />2014. <br />165 <br />Ayes: 6 <br />166 <br />Nays: 0 <br />167 <br />Motion carried. <br />168 <br />Anticipated City Council review of this Case is scheduled for July 21, 2014. <br />169 <br />b. PROJECT FILE 001, Subdivision Ordinance <br />170 <br />Request by the Community Development Department to amend in its entirety Title <br />171 <br />11, Subdivision of Roseville City Code <br />172 <br />Vice Chair Boguszewski opened the Public Hearing for Project File 001 at 7:24 p.m. <br />173 <br />Senior Planner Bryan Lloyd reviewed the request as detailed in the staff report dated July <br />174 <br />9, 2014; and similar to the rewrite of the 2010 zoning code, and reformatted accordingly; <br />175 <br />and staff’s request for Planning Commission feedback before moving forward. <br />176 <br />Discussion <br />177 <br />Vice Chair Boguszewski noted, in general, other than alignment and reconciliation, City <br />178 <br />Code and Subdivision Code seemed to be moving toward a higher level versus specific <br />179 <br />detail. Vice Chair Boguszewski opined that this should make it simpler for changes to <br />180 <br />occur versus the current extensive process. Vice Chair Boguszewski noted that revisions <br />181 <br />could also address the potential for a Large Lot Zoning District, as discussed preliminarily <br />182 <br />in the past. Vice Chair Boguszewski also noted that the recommended changes would <br />183 <br />allow documentation triggering certain zoning or specific guidance of regulatory code to <br />184 <br />occur at a lower level versus having to make revisions to overarching documents. <br />185 <br />Mr. Lloyd concurred, and reviewed the proposed changes to the Subdivision Code that <br />186 <br />included areas that were redundant to other Codes or regulated in Zoning Districts (e.g. <br />187 <br />lot sizes and various uses). Mr. Lloyd advised that the Subdivision Code was intended to <br />188 <br />provide direction in how to address lot sizes and applicable districts, but not to actually <br />189 <br />proscribe lot size itself. <br />190 <br />Vice Chair Boguszewski opined that he personally thought this was a great idea. <br />191 <br />Member Stellmach questioned the process for items removed and put in other <br />192 <br />applications and whether those would be accomplished at the staff level. <br />193 <br /> <br />