My WebLink
|
Help
|
About
|
Sign Out
Home
Search
06-25-2018 Council Meeting Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2018
>
06-25-2018 Council Meeting Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/2/2024 2:25:53 PM
Creation date
3/2/2024 12:06:54 PM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
151
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 /> <br />Updated TP removals will be included in the updated SWMP <br />11.The applicant shall verify HWLs for ponds. In some instances, they differ between the <br />HydroCAD modeling and the plans. HWLs confirmed. <br />The applicant shall revise the HWLs on the plans to match HydroCAD <br />modeling. <br />Plans are updated. <br />Applicant shall clarify why two different 100-yr HWL and 10-day Snowmelt <br />elevations are shown on the plans. <br />12.The applicant shall clarify the intent of the low area on Outlot D. If intended to be a <br />stormwater pond, please include it in modeling. Node added <br />13.The applicant shall revise the ACD number it varies throughout the Stormwater <br />Management Plan and SWPPP narratives. Comment Noted and ditch ID consistent in <br />report <br />Addressed in Stormwater Management Plan. Applicant shall update the <br />SWPPP. <br />SWPPP updated per the SWMP. <br />14.The applicant shall verify the lot lines on Lot 12 Block 4, Lot 4 Block 1, and Lot 5 <br />Block 1. It appears the structures may encroach on the drainage and utility easements. <br />Plan updated. <br />The applicant shall verify the lot lines on Lot 24 Block 7. It appears the <br />structure may encroach on the drainage and utility easement. <br />Lot lines revised in this area as well as pad locations. <br />15.The applicant shall include the bottom elevation of the infiltration basin on the grading <br />plans. Elevations added. <br />Applicant shall verify the bottom elevation, as it differs between HydroCAD <br />model, plans, and Appendix C. Verify the culvert outlet elevation; outlet should <br />be above the exfiltration elevation. As a note: planting medium is not necessary <br />below the bottom of the infiltration basin. <br />The infiltration is not intended to provide above-ground retention to prevent <br />oversaturating the back yards of the adjacent lots. The area is a flat infiltration swale <br />area. <br />The plan and HydroCAD Model now show the outlet elevation equal to the <br />infiltration basin bottom. Note that with this design, infiltration volume credit <br />cannot be claimed for IB10 and the SWMP must be updated. Volume of <br />infiltration is the ponded volume (volume from basin bottom to the outlet <br />elevation). <br />16.The applicant shall verify the retention volume calculation for Pond 400 in Appendix C <br />as there appears to be an error. The volumes are correct. <br />17.If needed, the opportunity may exist to maximize infiltration at the infiltration basin by <br />constructing the basin to minimize the separation between the bottom of the basin and <br />the water table. The basin needs minimum 3 feet separation from the water table and <br />cannot be lowered. <br />18.The applicant shall verify that the HWL of the Infiltration Basin is 2.0 feet below the <br />low entry elevations of surrounding buildings. Separation requirement is met <br />19.The applicant shall display and label emergency overflows with spot elevations and <br />drainage arrows at all ponds and sags, specifically at the intersection of Street A and <br />Street C and at the cul-de-sac of Street C. EOF’s added. <br />20. The applicant shall confirm that there is a 10-ft. setback between the HWL of the
The URL can be used to link to this page
Your browser does not support the video tag.