My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
07-09-18 Drainage and Flooding Committee Meeting
LaPorte
>
.Agendas
>
Open Meetings
>
Drainage and Flooding Committee
>
Drainage Committee
>
2018
>
07-09-18 Drainage and Flooding Committee Meeting
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/7/2025 3:01:16 PM
Creation date
7/25/2025 11:51:55 AM
Metadata
Fields
Template:
City Meetings
Meeting Body
Drainage and Flooding Committee
Meeting Doc Type
Agenda Packet
Date
7/9/2018
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.
/
229
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).
Show annotations
View images
View plain text
IML <br />Exhibit 11 presents the ponding during the 5-year storm event for the proposed <br />conditions. <br />Exhibit 12 presents the ponding during the 10-year storm event for the proposed <br />conditions. <br />Exhibit 13 presents the ponding during the 100-year storm event for the proposed <br />conditions. <br />Supplemental Table C presents the maximum water surface elevation comparison <br />with existing conditions. <br />Supplemental Table D presents a comparison between water surface elevation and <br />the nearest edge of pavement. <br />Analysis of Ties to Offsite Drainage Systems <br />Areas along the southwest and northeast borders are prone to flooding during the <br />10-year storm event. A cursory analysis was undertaken to see the relationship <br />between these areas and the bordering offsite regions. In both cases, the airport <br />does not receive any runoff from the neighborhoods. No negative impacts to the <br />airport would be caused by overflow from these systems. <br />5. Affected Facilities not in this Project <br />5.1. PIPELINES <br />There are no pavement improvements that are expected to affect the pipelines. <br />There are at least 3 existing pipelines running across the airport. The existing pipelines are <br />shown in Figure 6. Three pipelines are in the pipeline corridor as identified in ALP, and one <br />pipeline (stand-alone) is running parallel and close to east property line and swings north <br />east. During the notification process, the location of this pipeline could not be confirmed, but <br />it is suspected that it is actually within the major corridor to the east of the airport. A total of 4 <br />conflicts are encountered, of which three fall into the stand-alone pipe. We were unable to <br />locate any pipeline markings for this stand-alone pipe based on the desktop review. Further <br />investigation is needed in design to confirm the actual location of the pipeline.. Figure 13 <br />shows the potential conflicts. <br />Page 131 <br />
The URL can be used to link to this page
Your browser does not support the video tag.