My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 07/25/2017
Ramsey
>
Public
>
Agendas
>
Council
>
2017
>
Agenda - Council - 07/25/2017
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/17/2025 3:34:56 PM
Creation date
8/16/2017 2:24:14 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
07/25/2017
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
656
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
noted during the Sketch Plan review, the DNR just recently completed a rulemaking process that created new <br />districts in the MRCCA and, for non -riparian lots, primarily defers to the underlying zoning district for dimensional <br />standards. However, the City has yet to receive the necessary guidance from the DNR to proceed with updating our <br />Zoning Code and Comprehensive Plan and thus, are caught in a transitional time. <br />As a result, the Applicant has also applied for a Zoning Amendment to rezone the land to a Planned Unit <br />Development, which, if approved, is a legal instrument that would allow deviations from certain standards <br />(setbacks, use of private utilities rather than municipal services, etc.). The proposed lot size, lot width, and density <br />all appear to conform to the R-1 Residential (MUSA) bulk standards, as outlined in the Staff Review Letter. <br />Furthermore, the DNR has previously commented that they would be generally supportive of this approach as the <br />proposed lots would comply with the new MRCCA rules. The public benefit would be the fifty (50) foot wide outlot <br />(Outlot A) along the rear boundary of the existing homes on the north side of the road to serve as a buffer to future <br />development. This area is heavily wooded and would provide both visual and noise buffering from future uses. This <br />idea came out of the public workshops held last year and is supported by the developer and property owner. <br />At the public workshops last year, the primary concerns raised by attendees focused on concerns with construction <br />traffic on Bowers Drive and the lot sizes proposed. More recently, Staff understands that concerns have been raised <br />about the loss of vegetation along Bowers Drive. As previously noted, per the new MRCCA rules, one (1) acre lots <br />would be acceptable. They also seem to be compatible with many of the other lots along Bowers Drive, with the <br />exception of four or five lots directly across the street. These lots were platted as part of Bowers Mississippi Acres <br />3rd Addition and are each approximately 200 feet in width. When measured at the building setback line, the <br />proposed lots range from approximately 103 feet in width up to 127 feet in width. While narrower than those <br />directly across the street, the lots are very similar to the majority of existing lots on Bowers Drive. Additionally, the <br />proposed lots range in size from 1.04 acres to 1.89 acres in size, which is consistent with the existing lots (ranging <br />from about 0.44 acres to 1.84 acres in size). <br />The submittal does include a preliminary Tree Preservation and Landscape Plan that does identify the significant <br />trees, as defined in City Code, within the limits of construction. The only real impact to this thin strip of vegetation <br />along the right-of-way will be the result of installing a driveway to access each lot. However, based on the <br />submitted plan set, no significant trees would need to be removed in the development of these lots. The Developer <br />has also indicated that each lot will be planted with two (2) front yard trees, per City Code requirements. <br />As noted previously, Bowers Drive is a long cul-de-sac with no other access point. While many of the residents <br />noted at the workshops that they enjoy this setting, it is also a major factor in their concern about construction <br />traffic and potential road damage due to heavy equipment. At the direction of the City, the Sketch Plan and now the <br />Preliminary Plat does reserve a sixty (60) foot wide corridor (Outlot C) that could serve as a future access if/when <br />the remaining agricultural land develops in the future, even if only reserved for emergency access. The City's Public <br />Works and Public Safety Teams very much prefer improved access abilities to this neighborhood for a variety of <br />reasons. <br />The proposal includes serving each lot with a private well and septic system, similar to all the existing homes on <br />Bowers Drive. The plan set does identify both a primary and secondary site for a septic system, a requirement that <br />was not in place when this neighborhood was originally platted. The primary and alternate sites are a requirement <br />of Minnesota Rules 7080, which exist to provide baseline protections against contamination due to septic systems. <br />Alternatives <br />Alternative 1: Approve the Preliminary Plat and Zoning Amendment for Pearson Place, contingent upon <br />compliance with the Staff Review Letter. The bulk standards (lot size, lot width, setbacks) of the R-1 Residential <br />(MUSA) district and the new MRCCA district (albeit not yet adopted) standards are generally met with this <br />proposal with the exception of the use of private utilities rather than municipal sewer and water. However, the use <br />of private utilities matches the existing development pattern on Bowers Drive and includes both primary and <br />alternate locations for a septic system on each lot. Since this is a transitional time between existing MRCCA rules <br />and new MRCCA rules, Staff supports the use of a PUD to address the differences in standards with the inclusion of <br />the outlot that will serve as a buffer for the existing homes along Bowers Drive against potential development in the <br />
The URL can be used to link to this page
Your browser does not support the video tag.