Laserfiche WebLink
<br />RCA Exhibit A <br /> <br />a. PROJECT FILE 0001, Amendment 4 <br /> <br />1 <br />Request by the City of Roseville to clarify regulations in City Code, Title 11 <br /> <br />2 <br />(Subdivisions) pertaining to configuration of boundaries for new single-family lots <br /> <br />3 <br />and to clarify applicability of specified lot size standards. <br /> <br />4 <br />C <br />hair Boguszewski opened the public hearing for PROJECT FILE 0001 at 7:04 p.m. <br />5 <br />Senior Planner Bryan Lloyd reviewed the request as detailed in the staff report dated May <br />6 <br />4, 2016 and rationale for suggested changes and specific to minimum residential lot sizes <br />7 <br />(Section 1103.06.A and B) and side lot lines (Section 1103.06.F). Mr. Lloyd presented <br />8 <br />some graphical depictions of hypothetical subdivisions, attached hereto and made a <br />9 <br />part hereof, to illustrate how the existing requirements can produce lot shapes that might <br />10 <br />not be intended by the code even though the subdivision might conform to the <br />11 <br />requirements. <br />12 <br />Mr. Lloyd noted that some Subdivision Code language remained from when Ordinance <br />13 <br />216 was originally adopted in April of 1956 and compared with reality were no <br />14 <br />long applicable in a nearly-developed first-ring suburb such as Roseville. <br />15 <br />At the request of Member Daire, Mr. Lloyd provided verbal and illustrative examples of <br />16 <br />flag lots in Roseville and other metropolitan suburbs that were not within the confines of <br />17 <br /> intention. <br />18 <br />For clarification purposes, Chair Boguszewski noted that the changes outlined and <br />19 <br />recommended by staff in the report, lines 142 164 were mostly directive with <br />20 <br />subsections guiding and defining the basic rationale for the language revisions. Chair <br />21 <br />Boguszewski noted these provided some flexibility in interpreting general guidelines <br />22 <br />when considering those lots considered suitable and appropriate, while giving some <br />23 <br />semblance of a parallel or perpendicular nature. <br />24 <br />Mr. Lloyd agreed that was a good characterization, with the intent of the code to provide <br />25 <br />for regular and predictable lots, but the ability for review on a case by case basis. <br />26 <br />Chair Boguszewski opined that, with agreement from his colleagues, this language could <br />27 <br />be incorporated with the other recommended language revisions, keyed back to the <br />28 <br />underlying zoning district, and all within one motion; as confirmed by Mr. Lloyd. <br />29 <br />Member Daire clarified with Mr. Lloyd that Item 3.F (line 161) categorically forbade flag <br />30 <br />lots, with the exception of if and when a variance was indicated for a specific situation. <br />31 <br />Mr. Lloyd advised that, as a result of a previous Lot Split Study Task Force undertaking, <br />32 <br />staff found conflicting situations after enactment of the current subdivision ordinance. <br />33 <br />While the Task Force wanted to prohibit flag lots, the majority of the task force <br />34 <br />members indicated if someone came forward to pursue a flag lot, it could be considered if <br />35 <br />subjected to a variance process, and based upon square footage, and lot width and <br />36 <br />depth. <br />37 <br />Member Bull stated his issue in keeping city code succinct, and in his interpretation of the <br />38 <br />initial Item F, and then the following language in lines 147 164, it caused flags to go up <br />39 <br />for him. While understanding clarification, Member Bull sought to ensure the code <br />40 <br />was not using vague multiple <br />41 <br />regular shapes, including circles and cones that would be considered undesirable. <br />42 <br />Member Bull opined he found the proposed revised language too subjective (e.g. line <br />43 <br />157) when talking about irregularities, and questioned who was responsible for making <br />44 <br />that call; and suggested something needed to be described to help with that definition. <br />45 <br />Member Bull reiterated his preference that any code revisions remove vagarities and be <br />46 <br />more definable for users of the code. <br />47 <br />Mr. Lloyd advised that, in general he agreed that clear and simple is preferable to <br />48 <br />convoluted and vague. However, in this case, Mr. Lloyd advised that the attempt was to <br />49 <br />remove a clear statement (line 142) that in reality was simply not feasible geometrically <br />50 <br />speaking. Therefore, Mr. Lloyd advised that the intent of the revised language was not to <br />51 <br />be brief, but address the actual reality of working with simple shapes, whether that meant <br />52 <br />rectangles, squares, cones or pie shapes, with it being hard to characterize as <br />53 <br />Page 6 of 10 <br /> <br /> <br />