My WebLink
|
Help
|
About
|
Sign Out
Home
pm_990908
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
199x
>
1999
>
pm_990908
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/17/2007 3:35:41 PM
Creation date
12/15/2004 7:56:47 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Minutes
Commission/Committee - Meeting Date
9/8/1999
Commission/Committee - Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
7
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
<br />Nays: 0 <br /> <br />The amended motion carried. <br /> <br />Chair Klausing explained that the Code leaves too much latitude regarding the size and definition of structure (Seaberg's <br />building is considered one accessory building, not two buildings). <br /> <br />Member Mulder noted that this site is unique because of pre-existing conditions. <br /> <br />- 10 minute break - <br /> <br />Gc. Planning File 3133. City of Roseville request for an amendment to Sections 1101.02 (Subdivision Definitions), <br />Section 1103.06 (Lot Standards), and Section 11 04.04E (Minor Subdivisions) of the City Code, creating a procedure for <br />approving Flag Lots. <br /> <br />Chair Klausing opened the public hearing and explained the proposed ordinance amendment discussed at the August <br />Planning Commission meeting. <br /> <br />The proposed flag lot ordinance has ten conditions. <br /> <br />Member Cunningham asked if lots to be subdivided as flag lots could be reviewed based on taxable value. More study is <br />necessary. <br /> <br />Member Egli asked if the "flag" area still contained 11,000 s.f. (no). <br /> <br />Member Cunningham asked if there was screening required by the flag lot, to protect privacy of adjoining parcels. Thomas <br />Paschke suggested adding screening phase in condition #10. <br /> <br />Member Olson stated she was concerned about the frontage; should it be more than 40%. The frontage should include <br />the addition of setback adjacent to the flag lot so as to not create lots which cannot comply with setbacks on corner lots. <br /> <br />A letter from Phyllis Christofferson (8.30.99) was read into the record. She opposed the flag lot proposal. (letter attached <br />to minutes) <br /> <br />There was no public comment offered. Chair Klausing closed the hearing. <br /> <br />Motion. Member Mulder moved, seconded by Member Olson, to recommend that the Planning Commission affirm to the <br />City Council the current prohibition of flag lots. <br /> <br />Ayes: 2, Egli, Olson <br /> <br />Nays: 3, Klausing, Wilke, Cunningham <br /> <br />Abstain: 1, Mulder <br /> <br />Motion failed. <br /> <br />Member Mulder noted there are 250 parcels which could be divided; there would be strong opposition. This changes the <br />character and conditions of adjacent parcels. New houses should have to meet all setbacks. The Planning Commission <br />should send a clear recommendation to the City Council not permitting flag lots throughout the city. Each lot should be <br />reviewed on its merits. <br /> <br />Thomas Paschke noted that many lots could meet the size and frontage but there are far less than 250 lots that could <br />actually be developed. <br /> <br />Chair Klausing asked Thomas Paschke to describe the past history of this request. The City Council tabled a flag lot <br />request and requested the staff to prepare options. The City Council asked for a draft ordinance and sought input. <br /> <br />Member Cunningham noted that there is one flag lot on County Road B for which more detail would be helpful. He <br />suggested more information from neighbors adjoining existing flag lots. <br />
The URL can be used to link to this page
Your browser does not support the video tag.