My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
01-22-2003 Council Agenda
>
City Council Packets
>
2000-2009
>
2003
>
01-22-2003 Council Agenda
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/22/2012 1:59:16 PM
Creation date
6/22/2012 1:49:02 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
127
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
• The map that was sent out with the notice is our best guess today as to a possible <br />development Layout based on current zoning codes and the limited information we <br />possess relative the site dimensions, wetland delineation, and utility issues. <br />• More detailed studies are needed of the previously mentioned issues before a definite <br />decision could be made on an exact thoroughfare layout. <br />• Any future development will likely take a cooperative venture among a number of <br />property owners to make a project feasible. <br />• We are at the very beginning of these discussions. Adoption of any plan would require <br />more study and the receipt of additional public input. <br />At this point, the City Planner was called upon to review the zoning considerations that were used <br />as the basis for creating the preliminary plan that was included with the meeting notice. <br />The City Planner explained that the concept thoroughfare plan was used to help focus the discussion <br />of how a proposed subdivision impacts the plan for the overall area. It is not being used to do a <br />development. Rather, it helps illustrate how things fit together in order to protect the ability of other <br />property owners to do the same. <br />The City Planner emphasized the information used to create this sketch was extremely preliminary <br />and is not likely to be totally accurate. He used an existing topographic map of the area and <br />combined it with wetland information obtained from Ramsey /Washington Metro Watershed <br />District. (Further delineation of the wetland would be necessary before a plan was to be finalized.) <br />He then attempted to overlay existing property lines to achieve this concept. He explained that is <br />the reason the lots are not perpendicular to the LaBore Road. <br />The City Planner explained the concept plan attempted to avoid long, dead -end cul -de -sacs by providing <br />connection points to existing streets. The connection to LaBore Road does not follow existing property line <br />due to the need to achieve a 90- degree intersection for safety purposes. <br />At this point, a number of questions were received from the audience. <br />Q. What happened to the old plan to connect this area with Beam Avenue? The City Planner explained <br />that a wetland area dissects the connection point rendering it unfeasible. <br />Q. Why does the proposed street go through the backyard area and take so much property? The City <br />Planner answered that without a street, development would not be possible. <br />Q. Couldn 't Maple Leaf Court be extended further south to create another connection point? The City <br />Planner stated this is not possible due to the existence of a wetland in this area. <br />A member of the audience commented that wetland and topography information contained in the concept <br />drawing don't fully correspond. Better information is needed to make a decision. The City Planner again <br />acknowledged that his information was very preliminary and further refinements are needed. <br />Q. Why conduct this meeting tf accurate information is not available? The City Administrator responded <br />that our goal was to obtain input to help us decide if it worthwhile to gather the additional information <br />that would be needed to make a decision. <br />23 103 <br />
The URL can be used to link to this page
Your browser does not support the video tag.