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
PUBLIC WORKS <br />b. In general, the following comments apply: <br />i. Please update the project's address on the cover page and in each sheet's title <br />block to correctly show the project's assigned address: 3301 Seaway Blvd. <br />ii. Please call out all stormwater structures per City of Everett Standards. For <br />example, we have Type A and Type B structures rather than WSDOT's Type 1 <br />and 1 L. Please call out per the correct name and standard drawing number in our <br />Design and Construction Standards and Specifications for Development manual. <br />As long as the correct standard drawing number is called out, we do not need <br />those details in the plan set (preferred not to have them in the plan set because <br />the reference will always point to the most up-to-date version online). <br />2. The comments below were generated from this project's Stormwater Reviewer. If you have any <br />questions regarding these comments, please contact Jane Zimmerman with the City of Everett <br />Public Works Department (425-257-8885 or JZimmermangeverettwa.gov). <br />a. General stormwater requirements as detailed in the City's 2010 SWMM — the applicant <br />must show that all applicable requirements are being met: <br />i. Access road requirements per Chapter 2.2 of Volume III <br />ii. Pond berm and embankment material and construction specifications as provided <br />by a geotechnical engineer, see standards in Chapter 2.3 of Volume III for <br />minimum requirements <br />iii. Liner requirements per a geotechnical engineer's material and construction <br />specifications, must include provisions for protection/identification for <br />maintenance activities in the bottom of the pond <br />iv. Pond fencing in accordance with Chapter 2.5 of Volume III <br />v. Overflow requirements per Chapter 2.9, Volume III and the calculations <br />necessary to show the standards are being met. A secondary inlet to the flow <br />control structure must be provided in accordance with Chapter 2.9 and the <br />primary overflows to the two drainage basins must be proportioned in the same <br />way as the design release rates. In addition, due to the height of the pond berm <br />on the east side, an emergency spillway will be required. The location and <br />design of the emergency spillway must be specifically reviewed and approved by <br />the project's geotechnical engineer. <br />b. More specific plan/report comments: <br />i. A minimum of 6" of sediment storage must be provided in the bottom of the <br />pond <br />ii. The grading for the pond must stay outside of the NGPE and all pond contour <br />lines must close on the buildable area of the site, outside of the NGPE line. The <br />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 />iii. The placement of the MWS units downstream of the detention pond control on <br />this site is unacceptable due to the lack of elevation difference between the <br />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 <br />Page 2 of 3 ) <br />
The URL can be used to link to this page
Your browser does not support the video tag.