My WebLink
|
Help
|
About
|
Sign Out
Home
Search
2004-057 Council Resolution
LinoLakes
>
City Council
>
City Council Resolutions
>
2004
>
2004-057 Council Resolution
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/5/2014 12:59:56 PM
Creation date
11/5/2014 11:33:28 AM
Metadata
Fields
Template:
City Council
Council Document Type
Master List Resolution
Meeting Date
07/26/2004
Council Meeting Type
Regular
Resolution #
04-057
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
Highland Meadows East 2 "° Addition <br />page 4 <br />For future consideration, there will be 108± feet remaining between the rear lot line of <br />Lot 1 and the Outlot A boundary directly to the south. This does not allow for the <br />minimum lot widths or depths of the existing two- or multi - family residential zoning <br />districts. How Outlot A will be developed in the future has yet to be seen, but approval of <br />the present plat application should not be considered implied approval of any future plan <br />in Outlot A. <br />The proposal includes a narrowed access road as well as reduced setbacks around the periphery <br />of the site. The 26' private drive is narrower than a public street, which would be a minimum <br />28' (measured back of curb to back of curb.). The setbacks from this private drive were <br />increased since an original submittal and now meet the normally required 25'. <br />The PUD requirements state that "front and side yard restrictions at the periphery of the Planned <br />Unit Development site at a minimum shall be the same as imposed in the respective base <br />districts. The PUD standards do not specify a rear setback minimum. Typically, a 30' rear <br />setback is required in an R -3 zone. The goal is to maintain adequate buffering around the site <br />while allowing flexibility inside the site <br />After an original submittal, changes to the plan included the removal of two structures from the <br />north central area. This created extra space to move other units in order to keep a 30' setback <br />from the site boundary lines. Unit 2 is 21' from the south property line, but this is on the side of <br />the unit. There is ample space behind the unit to the east. The decks would be 20± feet from the <br />property lines, other than unit 2. <br />The City Engineer's previous review noted that a swale or storm sewer is needed along the south <br />property line, which has been added. <br />As required by the ordinance, the applicant submitted a "yield plan" to show what could be done <br />on the site by adhering to the standard zoning requirements. The yield plan is reasonable, and <br />shows 20 units. The current plan provides ample open area with 18 units. <br />Landscaping: Where a side or rear lot line in an R -3 District abuts an R, R -X, R -1, R- <br />1X, R -EC, or R -2 District, or public road right -of -way, a landscape buffer area not less than <br />twenty (20) feet in depth shall be provided along such side or rear lot line and shall contain <br />landscaping, planting, berming or other screening suitable to provide an effective visual screen. <br />Property on three sides of the site is zoned R -1. Though future zoning likely will change, the site <br />should include screening for the benefit of residents both around the site and within the site <br />Landscaping has been added to an original landscaping plan. Screening has been added to the <br />plan on the north and south sides of the site Existing trees provide additional screening on the <br />east and west sides. Because some existing trees will be lost due to the installation of the storm <br />sewer, additional spruce have been added in the extreme southwest corner, behind units 9, 10, <br />
The URL can be used to link to this page
Your browser does not support the video tag.