My WebLink
|
Help
|
About
|
Sign Out
Home
2013_11_06_PC_MInutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2013
>
2013_11_06_PC_MInutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/21/2014 11:32:39 AM
Creation date
10/21/2014 11:32:38 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.
/
5
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, November 6, 2013 <br />Page 4 <br />Mr. Paschke advised that most developers and contractors that staff dealt with performed their <br />144 <br />due diligence and research, and came to staff to review them before finalizing their designs. Mr. <br />145 <br />Paschke noted that it was infrequent that a problem occurred unless someone prepared their <br />146 <br />design and was ready to proceed with the permit process without realizing the design standards <br />147 <br />adopted by the City. Mr. Paschke noted that staff had already supported several design features <br />148 <br />with unique situations that met code and still accomplished the design goals of the applicant. <br />149 <br />Member Boguszewski stated that his contention remained that the residential character of a <br />150 <br />street was more dependent on landscaping and overall massing relative to the road than the <br />151 <br />relative distance of the face of a garage compared to the home itself. Member Boguszewski <br />152 <br />further stated that he agreed that the City didn’t want new homes up against a road to retain the <br />153 <br />residential feel. Given the variables in architectural detail possible, Member Boguszewski opined <br />154 <br />that he wasn’t sure that should be included in code. However, Member Boguszewski advised that <br />155 <br />while he was not concerned with the first two bullet points (lines 11 – 12); he preferred language <br />156 <br />added to Section 2 (lines 31-32) similar to the following: <br />157 <br />“If no part of the structure is closer than 50’ from the front property line, this setback requirement <br />158 <br />could be waived…” <br />159 <br />Member Cunningham expressed her interest in addressing flexibility for lots having physical <br />160 <br />constraints (e.g. lake lots, etc.), or if on a smaller lot, there was limited ability to make sure the <br />161 <br />garage is in an exact location; and provided several possible scenarios. Member Cunningham <br />162 <br />stated that she was not opposed to adding flexibility to City Code to allow the Planning <br />163 <br />Department to have more discretion in those types of decisions if there were extenuating <br />164 <br />circumstances, and staff encouraging owners to do more architectural detailing, without actually <br />165 <br />defining those components. Member Cunningham stated that she trusted staff’s discretion, and <br />166 <br />noted other areas in City C ode that allowed them that same discretion. <br />167 <br />Mr. Lloyd referenced Section B “Requirements Apply to All New Construction” (page 2, lines 33 – <br />168 <br />41) consisting of existing language already utilized in several circumstances allowing staff <br />169 <br />interpretation and administrative deviation ability. Mr. Lloyd provided several examples of those <br />170 <br />situations used where lots had physical restraints. <br />171 <br />Member Keynan questioned how problematic this requirement is right now, or how many issues <br />172 <br />staff was finding; whether the Commission was trying to fix something that really was not a <br />173 <br />problem. <br />174 <br />Mr. Lloyd opined that, depending on who you spoke to, there was room for debate as to whether <br />175 <br />or not there was a problem with garage placement. Mr. Lloyd advised that current code language <br />176 <br />had been based on Comprehensive Plan guidance; and usually when a problem came forward, it <br />177 <br />was due to the applicant designing their home without being aware of City requirements. <br />178 <br />However, Mr. Lloyd noted that this infrequent issue certainly had no effect on the safety or <br />179 <br />neighborhood degradation typically part of an analysis. <br />180 <br />Mr. Paschke advised that of the 45-50 single-family home permits issued since the new code was <br />181 <br />put in place, he was aware of only 1 instance where the applicant sought a variance, that was <br />182 <br />subsequently not approved by the Variance Board, nor on appeal by the City Council. Mr. <br />183 <br />Paschke noted that this one applicant strongly expressed his lack of support of those design <br />184 <br />standards. <br />185 <br />Under those circumstances, Member Keynan stated that he was fine with staff having additional <br />186 <br />flexibility on a case by case basis. <br />187 <br />Member Boguszewski concurred, noting that the applicant/developer had indicated that such a <br />188 <br />design standard would require a variance process and cause homes to be priced higher; and in <br />189 <br />his case, having to redesign the configuration, it would hurt his ability to sell the home or market it <br />190 <br />cost-effectively based on that current code language. Member Boguszewski questioned whether <br />191 <br />or not the Variance Board or the City Council on appeal had ultimately supported that assertion, <br />192 <br />but that it was irrelevant at this point; but questioned if the City had observed any other problems <br />193 <br />in the housing market that would support that assertion. <br />194 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.