My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 09/13/2016
Ramsey
>
Public
>
Agendas
>
Council
>
2016
>
Agenda - Council - 09/13/2016
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/17/2025 3:52:28 PM
Creation date
10/26/2016 8:24:53 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
09/13/2016
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.
/
1091
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
CC Regular Session <br />Meeting Date: 09/13/2016 <br />By: Tim Gladhill, Community Development <br />7. 1. <br />Information <br />Title: <br />Receive Update of Pearson Bowers Drive Concept (Project No. 16-31a) <br />Purpose/Background: <br />The intent of this case is to provide a new update since this case was last reviewed on July 21, 2016. The Minnesota <br />DNR has completed the Public Hearing and Administrative Law Review of the draft rules. The Administrative Law <br />Judge has recommended approval of the rules, with the exception of provisions related to Native Plant <br />Communities. Additionally, Staff has received additional feedback from DNR Staff on potential process related to <br />this particular development scenario. <br />As the Planning Commission is aware, Pearson Properties of Ramsey, LLC, is considering a detached single-family <br />development along Bowers Drive. <br />Notification: <br />Notification is not required at this stage. However, two (2) public workshops have been held on the topic. <br />Observations/Alternatives: <br />The project entails the creation of one (1) acre lots on private well and septic. Generally speaking, there are two (2) <br />main policy discussion points Staff is seeking direction on. Please note that there are several layers of complexity to <br />this request that will need to be solved as the development concept moves through the review process. Staff is <br />focusing on two (2) primary issues at this stage. If policy direction is in the negative on either of the two (2) points <br />below, the development concept is not feasible and the project does not move forward. <br />1. Lot Size as required by Mississippi River Corridor Critical Area (MRCCA) <br />2. Private Well and Septic in Metropolitan Urban Service Area (MUSA) <br />Lot Size <br />The driving factor for lot size is MRCCA. Current, the minimum lot size for the project is 2.5 acres. The proposed <br />lot size is one (1) acre. <br />However, as the Council is aware, the DNR is in the process of updating the Overlay District. Based on the current <br />draft, minimum lot size to this parcel would defer to the underlying zoning district. In this case, the minimum lot <br />size would be 10,800 square feet (0.25 acres), rendering the lot size question a moot point. The Administrative Law <br />Judge has recommended approval of these rules, with the exception of rules pertaining to Native Plant Species. It is <br />unknown next steps or timelines for the rule implementation at this time. Given the objection to Native Plan Species <br />definition, it is unknown at this time whether this will cause a significant delay to implementation. <br />The Minnesota DNR has recommended that the City submit the development concept for official review as a <br />Planned Unit Development (PUD) for further consideration by the DNR. The DNR may consider an allowance to <br />cluster lots, if certain areas are permanently protected as open space. This is a change in policy direction from the <br />previous Planning Commission review. <br />Underlying Zoning District <br />The site is located in the R-1 Residential (MUSA) District. The intent of this district is to provide for future <br />
The URL can be used to link to this page
Your browser does not support the video tag.