My WebLink
|
Help
|
About
|
Sign Out
Home
Search
06-12-2023 City Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
2023
>
Searchable Packets
>
06-12-2023 City Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2023 8:30:27 AM
Creation date
6/9/2023 8:17:02 AM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
06/12/2023
Council Meeting Type
Regular
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.
/
336
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
<br />3 <br /> <br />4. The existing LOS must be D or better for all streets and intersections providing <br />access to the proposed development. If the existing level of service is E or F, the developer must <br />provide, as part of the proposed project, improvements needed to ensure a level of service D or <br />better. <br />5. Existing roads and intersections providing access to the proposed development <br />must have the structural capacity to accommodate projected traffic from the proposed <br />development or the developer will pay to correct any structural deficiencies. <br />6. The traffic generated from a proposed development shall not require City street <br />improvements that are inconsistent with the Lino Lakes Capital Improvement Plan. However, <br />the City may, at its discretion, consider developer-financed improvements to correct any street <br />deficiencies. <br />7. The LOS requirements in paragraphs 1. to 4. above do not apply to the I- <br />35W/Lake Drive or I-35E/Main St. interchanges. At City discretion, interchange impacts must <br />be evaluated in conjunction with Anoka County and the Minnesota Dept. of Transportation, and <br />a plan must be prepared to determine improvements needed to resolve deficiencies. This plan <br />must determine traffic generated by the proposed development project, how this traffic <br />contributes to the total traffic, and the time frame of the improvements. The plan also must <br />examine financing options, including project contribution and cost sharing among other <br />jurisdictions and other properties that contribute to traffic at the interchange. <br />The applicant shall provide a Level of Service analysis of the Apollo Drive (CSAH 12) and Lilac <br />Street intersection. The proposed Level of Service is not anticipated to degrade the existing Level <br />of Service. Existing roads and intersections providing access to the development shall have the <br />structural capacity to accommodate projected traffic from the proposed subdivision or the <br />applicant/developer shall pay to correct any structural deficiencies. No street improvements are <br />proposed that are inconsistent with the City’s capital improvement plan. The city does not <br />relinquish any rights of local determination. <br /> <br />(e) The proposed development shall be served with adequate and safe water supply. <br />The proposed commercial day care facility will have an adequate water supply. The facility will <br />be municipally served by a 12” watermain located along Apollo Drive. The water supply system <br />has capacity for the proposed development. <br /> <br />(f) The proposed development shall be served with an adequate or safe sanitary <br />sewer system. <br />The proposed commercial day care facility will be served with an adequate waste disposal <br />system. The facility will be municipally served by a 21” sanitary sewer main along Apollo Drive. <br /> <br />(g) The proposed development shall not result in the premature expenditures of City <br />funds on capital improvements necessary to accommodate the proposed development. <br />The proposed commercial day care facility does not require City funds.
The URL can be used to link to this page
Your browser does not support the video tag.