My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
11-17-1999 PC
MoundsView
>
Commissions
>
Planning & Zoning Commission
>
Minutes
>
1990-1999
>
1999
>
11-17-1999 PC
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/27/2018 5:40:44 AM
Creation date
7/27/2018 5:40:42 AM
Metadata
Fields
Template:
MV City Council
City Council Document Type
City Council Minutes
Date
11/17/1999
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
23
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
Mounds View Planning Commission November 17, 1999 <br /> Regular Meeting Page 16 <br /> • footnote at the bottom of Page 6, which refers to Section 1107.03 for more information regarding <br /> zero lot line subdivisions. <br /> Planning Associate Ericson explained that previous changes to the ordinance now appear in double <br /> underline, and basically add language to clarify the zero lot line subdivision requirements so they are <br /> no longer ambiguous. He indicated from staff's perspective,the only matter left to resolve is whether <br /> or not the stated widths are appropriate, and the Commission is requested to discuss this, and possibly <br /> forward this ordinance to the City Council with a resolution at their next meeting. <br /> Chairperson Peterson inquired if the second column of the table is intended to reflect the maximum <br /> width of curb cuts. Planning Associate Ericson stated this was correct. <br /> Chairperson Peterson pointed out that this should be indicated, to clarify that lesser widths are <br /> permissible. Planning Associate Ericson stated this was a good point. <br /> Commissioner Stevenson inquired if the intention of the language in Section 3, Subd 4, pertaining to <br /> the R-1 Zoning District, is to allow twelve feet (12'), in addition to thirty-five feet (35'), in the case <br /> of a triple wide garage. Planning Associate Ericson stated this was correct. <br /> Commissioner Miller pointed out this language specifies the width of the attached parking area, <br /> however, not the length. Planning Associate Ericson stated this was correct. He explained the Code <br /> • provides there are some limitations on the amount of gravel that is permitted, however, there are no <br /> restrictions in terms of an attached parking pad. <br /> Commissioner Hegland inquired regarding the curb cuts widths on the townhome units located on <br /> Silver Lake Road and Knollwood Drive. <br /> Planning Associate Ericson explained that the curb cuts of the units on Silver Lake Road are all forty <br /> feet (40') wide, and with the exception of one property on Knollwood Drive, which has two <br /> driveways and two eighteen-foot (18') curb cuts, the others are forty feet (40') as well. <br /> Commissioner Ilegland stated a normal two-car garage is twenty-two (22') wide, and a vehicle is <br /> typically 61/2 to 7 feet wide. He explained in the case of a driveway,where there is approximately two <br /> feet between vehicles, and a car is parked in the driveway, the narrow curb cut would be difficult to <br /> negotiate, when attempting to back out of the garage. He advised that a forty-foot (40') curb cut <br /> would be more appropriate. He stated Page 6 of the ordinance, pertaining to zero-lot line subdivision <br /> curb cuts in the R-2 district, should be amended to reflect twenty feet (20'), rather than eighteen feet <br /> (18'). <br /> Chair Peterson pointed out the eighteen-foot (18') requirement is also indicated on Page 4 of the <br /> ordinance, in Subd. 1. <br /> Commissioner Hegland commented that the forty-foot (40') curb cuts already exist within the City, <br /> • and this width would allow the resident to back straight out of the garage. He added that the wider <br />
The URL can be used to link to this page
Your browser does not support the video tag.