My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
3301 SEAWAY BLVD WHOLE SITE 2025-10-30
>
Address Records
>
SEAWAY BLVD
>
3301
>
WHOLE SITE
>
3301 SEAWAY BLVD WHOLE SITE 2025-10-30
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/30/2025 8:09:23 AM
Creation date
6/4/2019 9:20:56 AM
Metadata
Fields
Template:
Address Document
Street Name
SEAWAY BLVD
Street Number
3301
Tenant Name
WHOLE SITE
Imported From Microfiche
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
403
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
Sabrina Fandler <br />From: <br />Sent: <br />To: <br />Subject: <br />Attachments: <br />Follow Up Flag: <br />Flag Status: <br />Hi Sabrina — <br />Jane Zimmerman <br />Thursday, May 26, 2016 2:39 PM <br />Sabrina Fandler <br />Bertch Capital plan/report review <br />Bertch PAD.pdf <br />Follow up <br />Flagged <br />Please see below for my first, very general review comments for the Bertch Capital site. The submitted plans and report <br />lack much of the necessary detail to allow me to conduct a thorough review at this time. Therefore, my comments <br />mostly reference sections of the City's Stormwater Management Manual for requirements that must be met and <br />calculations that must be provided. In addition, I have also highlighted the City's PAD for SEPA 16-006 — see the <br />attached document — to identify additional information required to address drainage -related requirements for this <br />project. <br />Thank you, <br />Jane <br />General stormwater requirements as detailed in the City's 2010 SWMM —the applicant must show that all applicable <br />requirements are being met <br />-Access road requirements per Chapter 2.2 of Volume III <br />-Pond berm and embankment material and construction specifications as provided by a geotechnical engineer, see <br />standards in Chapter 2.3 of Volume III for minimum requirements <br />-Liner requirements per a geotechnical engineer's material and construction specifications, must include provisions for <br />protection/identification for maintenance activities in the bottom of the pond <br />-Pond fencing in accordance with Chapter 2.5 of Volume III <br />-Overflow requirements per Chapter 2.9, Volume III and the calculations necessary to show the standards are being <br />met. A secondary inlet to the flow control structure must be provided in accordance with Chapter 2.9 and the primary <br />overflows to the two drainage basins must be proportioned in the same way as the design release rates. In addition, <br />due to the height of the pond berm on the east side, an emergency spillway will be required. The location and design of <br />the emergency spillway must be specifically reviewed and approved by the project's geotechnical engineer. <br />More specific plan/report comments: <br />-A minimum of 6" of sediment storage must be provided in the bottom of the pond <br />-The grading for the pond must stay outside of the NGPE and all pond contour lines must close on the buildable area of <br />the site, outside of the NGPE line. The proposed grading shown on the southeast side of the pond is not feasible and will <br />either result in grading within the NGPE or a smaller than required pond. <br />-The placement of the MWS units downstream of the detention pond control on this site is unacceptable due to the lack <br />of elevation difference between the primary outlets and the invert elevation of the downstream drainage system. As <br />located, the MWS units will create backwater effects that will reduce the effective head on the primary orifices of the <br />flow control structures and unacceptably alter the stage -discharge relationship of the restrictor units — meaning that the <br />pond will overflow more often than is allowable. <br />
The URL can be used to link to this page
Your browser does not support the video tag.