My WebLink
|
Help
|
About
|
Sign Out
Home
2010-11-17_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2010
>
2010-11-17_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/18/2011 1:58:31 PM
Creation date
2/18/2011 1:58:29 PM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Minutes
Commission/Committee - Meeting Date
11/17/2010
Commission/Committee - Meeting Type
Special
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
13
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
Planning Commission Meeting <br />Minutes – Wednesday, November 17, 2010 <br />Page 2 <br />Further discussion included review of the existing Appeals and Enforcement <br />46 <br />sections with the existing code for comparison purposes; $50 fee for processing <br />47 <br />fees to cover additional mailings and administrative time to process the appeal to <br />48 <br />the City Council level for public hearing; confirmation that the notice provisions <br />49 <br />for appeals will run parallel with those for other established notice provisions of <br />50 <br />the City Council, without specific footages to facilitate any potential changes in <br />51 <br />those notice provisions by the City Council in the future. <br />52 <br />Additional discussion included fence height deviations being new to this section, <br />53 <br />based on past variance applications related to fence height for properties <br />54 <br />adjacent to highways, whether for aesthetics and/or noise, and usually approved <br />55 <br />as a variances; however, staff noted with recent Minnesota Supreme Court <br />56 <br />rulings during 2010 related to variances, rather than have the potential height <br />57 <br />hindered when past practice had been to approve the additional height, staff <br />58 <br />recommended adding another minimal footage for fences, with standard <br />59 <br />materials and their pre-manufactured height aligning with the eight foot (8’) <br />60 <br />maximum as proscribed in the new code. <br />61 <br />Vice Chair Boerigter expressed concern with the restrictions on location and <br />62 <br />distance in the drive-thru section limiting a drive-thru lane at the side or read, not <br />63 <br />front of a property, as previously discussed, and how a future drive-thru request <br />64 <br />could deviate if their circumstances or property was unique. <br />65 <br />Mr. Lloyd advised that staff recommending that the proposed language remain in <br />66 <br />Item A relating to the drive-thru lane’s distance and relative location to the <br />67 <br />property line; noting that it was still the preference that those properties still <br />68 <br />attempt to redesign the site to meet code requirements; or apply for a Zoning <br />69 <br />Code Text Amendment if it became evident that this proposed code provision <br />70 <br />was not working and needed amendment. <br />71 <br />Vice Chair Boerigter addressed the Animal Boarding/Kennel/Pet Daycare Section <br />72 <br />and noted that, with staff support, the City Council recently approved The Woof <br />73 <br />Room’s application for a forty-foot (40’) distance between their business and <br />74 <br />adjacent residential properties; however, now the proposed zoning code provided <br />75 <br />for a one hundred foot (100’) distance requirement, and questioned staff’s logic in <br />76 <br />those differences. <br />77 <br />Mr. Lloyd advised that consideration of The Woof Room proposal was based on <br />78 <br />existing zoning code provisions, and Comprehensive Plan land use guidance for <br />79 <br />that area being High Density Residential, with the use identified as non- <br />80 <br />conforming and using an Interim Use permitting process not intended for long- <br />81 <br />term use, as recognized by the applicant and staff. Mr. Lloyd opined that this <br />82 <br />was a reasonable approach for this site, and while staff didn’t anticipate that the <br />83 <br />use would be problematic at that location, given its close proximity to residential <br />84 <br />properties and the discomfort of those residents for potential problems, the <br />85 <br />conditions applied to the use seemed appropriate for a short-term duration. <br />86 <br />Further discussion addressed accessory dwelling units to accommodate <br />87 <br />separate dwellings on site, such as a “granny flat” but different than single-family <br />88 <br />homes being rented out, and proposed new requirements requiring a walkway <br />89 <br />connection from an accessory dwelling to the street, and practical applications. <br />90 <br />In Section 21, discussion ensued related to outdoor storage in manufacturing <br />91 <br />districts as a somewhat new section, with Mr. Lloyd noting that outdoor storage is <br />92 <br />a use presently allowed in Industrial II and General Industrial Districts, but <br />93 <br />identified as a Conditional Use with conditions written into approvals to require <br />94 <br />screening; but now in the Industrial chapter of code, the requirement for outdoor <br />95 <br />storage required screening, and was basically a reorganization of current code, <br />96 <br />with outdoor storage seen as an accessory use; definition of outdoor activities <br />97 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.