My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
5.3. PCSR 04-10-2007
ElkRiver
>
City Government
>
Boards and Commissions
>
Planning Commission
>
Planning Packets
>
2006-2010
>
2007
>
04-10-2007
>
5.3. PCSR 04-10-2007
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/25/2008 3:51:28 PM
Creation date
2/11/2008 12:17:55 PM
Metadata
Fields
Template:
City Government
type
PCSR
date
4/10/2007
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
32
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
Case File: OA 07-OS <br />Page 3 <br />General Information <br />Ordinance Amendment <br />City of Elk River <br />Applicant: City of Elk River <br />Requested Action Ordinance Amendment <br />Location and Size: N/A <br />Background <br />A property owner in the subject area has an open application for a Zone Change, which is the <br />catalyst for this Ordinance Amendment request. The property in the Zone Change request is a <br />result of a previous lot line adjustment. The lot was at one time two individual lots that were the <br />same size as the neighboring properties. In the past the lot line was removed between the two <br />properties and the lots were combined into one. The property owner's desire is to subdivide the <br />130-foot lot back into two lots, which would create a new buildable lot. With the current zoning <br />and the minimum lot frontage requirement, the current lot is not wide enough to create the two lots. <br />The property is zoned R2(a) with an 80-foot minimum width requirement. If it were zoned R2(b), <br />which has a frontage requirement of 60-feet, the property could be divided. <br />Staff has not identified any issues with the lot being split, as the newly created lot is consistent with <br />the character of the neighborhood. The issue that would be raised, with the original request, is the <br />practice of spot zoning. This practice is not typically supported by staff or the Council. After <br />reviewing the Zone Change request, staff realized that a majority of the lots in the R2(a) zoning <br />district are non-conforming. It was with this knowledge that staff recommended the applicant <br />postpone his Zone Change request to May 8, 2007 Planning Commission meeting to allow the City <br />explore an Ordinance Amendment for the area. The applicant agreed to this. <br />Overview <br />As a result of the aforementioned Zone Change request, this Ordinance Amendment request was <br />brought before the City Council on February 20, 2007 for direction. The Council questioned if the <br />request was premature, given the possibility of redevelopment in the area. The Council wanted <br />feedback from the HRA in regards to the request. At their March 5, 2007 meeting, the HRA stated <br />they would prefer to see an Ordinance Amendment over a Zone Change to the properties. <br />Analysis <br />The "subject area" is approximately 345-feet wide, east of Jackson Avenue, north of 5`h Street and <br />south of School Street. Although this request began with a Zone Change request in the "subject <br />area", this Ordinance Amendment would affect each lot in the R2(a) zoning district. <br />The "subject area" is currently zoned R2(a) with asingle-family frontage requirement of 80-feet and <br />a lot size requirement of 10,000 square feet. The properties in the subject area range in width from <br />approximately 34-feet to 130-feet. In order to comply with the current zoning requirements, each <br />single-family lot must have 80-feet of frontage. There are 20 properties north of 5th Street to <br />School Street, of which only three meet the minimum lot widths. These three lots are wider than <br />C:\Documents and Settings\dhuebner\Local Settings\Temporary Internet Files\OA 07-05 PC.doc <br />
The URL can be used to link to this page
Your browser does not support the video tag.