My WebLink
|
Help
|
About
|
Sign Out
Home
2013_10_02_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2013
>
2013_10_02_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/21/2014 11:31:27 AM
Creation date
10/21/2014 11:31:26 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.
/
9
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, October 2, 2013 <br />Page 7 <br />of the depth, Mr. Lloyd confirmed for Vice Chair Boguszewski that this would adequately address <br />299 <br />the neighbor concerns for noise abatement to the north. <br />300 <br />With Vice Chair Boguszewski opining that the fence should be 8’ all the way around to “not be <br />301 <br />inconsistent with code,” as staff addressed in a former and unrelated application discussion, Mr. <br />302 <br />Paschke advised that the goal was to provide the same fence height throughout, with the <br />303 <br />exception of the retaining area to achieve that same height, which he felt was appropriate in this <br />304 <br />situation. <br />305 <br />In response to Vice Chair Boguszewski observing that a Conditional Use was “forever,” not only <br />306 <br />for a set term, Mr. Paschke clarified that this was a distinction between two separate land use <br />307 <br />applications: an Interim Use for a set period, typically three years, and this purpose-driven <br />308 <br />process to consider a Conditional Use without a term limit for a permitted use. <br />309 <br />Vice Chair Boguszewski closed Public Hearing at approximately 7:31 p.m. <br />310 <br />In his role as Chair for tonight’s meeting, Vice Chair Boguszewski noted that the City Council had <br />311 <br />recently asked that Members provide their rationale for their support or denial of a <br />312 <br />recommendation; and personally asked that the vote be split into three (3) separate motions: <br />313 <br />1) Zoning Text revision regarding fences in residential areas; <br />314 <br />2) Striking language regarding the 6’ fence requirement, and providing for written <br />315 <br />support of 100% of adjacent residential property owners; and <br />316 <br />3) The Conditional Use request. <br />317 <br />Vice Chair Boguszewski advised, that overall, he would support this proposal. <br />318 <br />Member Murphy concurred, stating that at first he thought the proposal was too restrictive, but <br />319 <br />after Mr. Paschke’s explanation, he found more clarity. <br />320 <br />MOTION <br />321 <br />Member Boguszewski moved, seconded by Member Murphy to recommend to the City <br />322 <br />Council APPROVAL of a proposed ZONING TEXT CHANGE as follows: <br />323 <br />RESIDENTIAL 1011.08 FENCES IN ALL DISTRICTS – B Residential Fences – “The following <br />324 <br />standards shall apply to all fences constructed in any residential zoning district --- or <br />325 <br />directly adjacent to any residential zoning district.” <br />326 <br />Ayes: 6 <br />327 <br />Nays: 0 <br />328 <br />Motion carried. <br />329 <br />In providing his rationale for seeking three (3) separate motions, Vice Chair Boguszewski <br />330 <br />expressed his concern that this was not being pursued as a Variance process versus this <br />331 <br />recommendation and potential impact to other properties in the area. Therefore, Vice Chair <br />332 <br />Boguszewski advised that he would be voting in opposition to this, as he didn’t agree with <br />333 <br />changing the code in this way, while recognizing that the majority vote will prevail. Vice Chair <br />334 <br />Boguszewski noted that this was basically a symbolic gesture on his part, and if the majority vote <br />335 <br />so indicates, he may vote to approve the request of the applicants. <br />336 <br />Member Daire spoke in support of the proposed text revision not to exceed 6’ in height, opining <br />337 <br />that her personally thought height should be determined by staff based on the situation that this <br />338 <br />particular section of code is being applied to. Member Daire advised that he would be more <br />339 <br />comfortable if staff was involved in determining fence height or screening; and expressed his <br />340 <br />support of this motion if that is the intent. <br />341 <br />Mr. Paschke responded to Member Daire, that whether in practice or in force, that determined the <br />342 <br />height of a fence, with staff reviewing each application and advising the applicant what is best for <br />343 <br />their particular situation (i.e., administrative review process), similar to landscaping issues. Mr. <br />344 <br />Paschke advised that having a “not to exceed 6’ in height” provision didn’t preclude staff working <br />345 <br />with the applicant and determining what is appropriate for fence height and its required <br />346 <br />placement, but this text revision simply dovetailed into other sections of the code addressing <br />347 <br />screening and buffering. Mr. Paschke assured all that staff would continue to work the public, the <br />348 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.