My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
12-03-2003
MoundsView
>
Commissions
>
Planning & Zoning Commission
>
Agenda Packets
>
2000-2009
>
2003
>
12-03-2003
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/4/2018 7:25:53 AM
Creation date
9/4/2018 7:25:35 AM
Metadata
Fields
Template:
MV City Council
City Council Document Type
City Council Packets
Date
12/3/2003
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
28
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).
Show annotations
View images
View plain text
Item No: 8 <br />Meeting Date: December 3, 2003 <br />Type of Business: Discussion <br />City of Mounds View Staff Report <br />To: Mounds View Planning Commission <br />From: Kristin Prososki, Planning Associate <br />Item Title/Subject: Consideration of Possible Revisions to the Zoning <br />Code to Allow for an Administrative Variance <br />Approval Process; Special Planning Case SP-120-03 <br /> <br />Introduction: <br /> <br />Currently, a resident may seek relief from Zoning Code by applying for a variance. The <br />process of applying for a variance entails submitting an application and a fee, staff <br />reviewing the application and situation, staff presenting the case to the Planning <br />Commission and the Planning Commission voting to approve or deny the variance <br />request. The process can take up to one month and is somewhat time consuming for the <br />resident, Staff and the Planning Commission. Due to the number of variance requests <br />received, Staff has researched another option called an administrative variance. <br /> <br />Discussion: <br /> <br />Administrative variances are used in many other cities in Minnesota and the United <br />States. The process for an administrative variance is similar to the formal variance <br />process, except that Staff makes the decision in approving or denying the variance <br />instead of the Planning Commission. This process is allowed only for variance requests <br />within certain limitations, set by the Planning Commission. For example, an <br />administrative variance could be requested if the request is within 10% of the code <br />requirement. In order to qualify for this process, a hardship must exist and the same <br />variance criteria will be evaluated for each request. Staff researched administrative <br />variance processes in other cities and has developed a chart for comparison of each of <br />the requirements. (See attached). <br /> <br />If the Planning Commission wishes to go forward with an administrative variance process, <br />the process will need to be discussed and a recommendation for a code amendment will <br />need to be made to the City Council. Some of the topics that need to be discussed <br />include: <br /> <br />1) Limits and Standards – There are many different options when it comes to <br />deciding what qualifies for an administrative variance and how much deviation <br />from code to allow. For example, the City of White Bear Lake, MN limits <br />administrative variances to the square footage of accessory structures, the <br />location of air conditioners and pre-existing, nonconforming structures. In this <br />case, the administrative variance process does not apply to other requests. <br />Another example is Boulder, CO. They grant administrative variances for up <br />to 20% of a required setback. The Planning Commission may review the <br />chart and based on past experience with variances in Mounds View decide <br />which topics would be suitable for administrative variances. All other topics <br />would need to go through the formal variance process. In addition, limits <br />need to be set for how much a request can differ from code. <br />
The URL can be used to link to this page
Your browser does not support the video tag.