SEPA Compliance. The Parties acknowledge that the SEPA Determination fully and completely determined that there will be no probable significant adverse environmental impacts resulting from the cluster housing development on the Property described herein and that further SEPA review may only be required if the criteria set forth in WAC §197-11-600(3)(b) (Part Six – Using Environmental Documents, SEPA Rules) are triggered.
SEPA Compliance. 3.1 Sound Transit is the “lead agency” for purposes of Project compliance with the State Environmental Policy Act, RCW Chapter 43.21C (“SEPA”). The City agrees that the Project has been subject to full and complete procedural and substantive SEPA review through issuance of the following environmental documents, which taken together comprise the “Project Environmental Documents,” incorporated herein by reference:
SEPA Compliance. 3.1 Sound Transit is the lead agency for compliance with the State Environmental Policy Act ("SEPA"). In coordination with the City of Puyallup, Sound Transit has completed the substantive and procedural environmental review for the Project in accordance with SEPA requirements with the publication of the Determination of Nonsignificance and SEPA Checklist on February 17, 2016. The environmental review covers the City’s issuance of permits for the Project as well as environmental mitigation, and the City will use and rely upon the existing environmental documents to satisfy its SEPA responsibilities, consistent with WAC 197‐11‐600. The City agrees that the Project has been subject to full and complete procedural and substantive SEPA review.
SEPA Compliance i) All SEPA regulatory review shall be tied to the primary application. The County shall provide environmental review under SEPA on all applications which are being processed under this section. The City will assume responsibility for the environmental review of any application which the City has excluded from this agreement.
SEPA Compliance. The SEPA Checklist prepared in support of this Agreement analyzes the impacts associated with the City’s review and approval of this Agreement. The City has reviewed said SEPA Checklist and conducted additional analysis prior to issuing its Determination of Non-significance, and subsequently, issuing a SEPA Addendum, both attached as Exhibit 6 (“DNS”). The City Council has reviewed the SEPA record and DNS, and finds that its action in approving this Agreement is adequate under SEPA. No SEPA mitigation related to stormwater management or to impact fee credits will be required of future development/redevelopment applications; Development Agreement -4- provided that, the applicant documents that impacts of the future development/redevelopment applications are within the scope of impacts analyzed in the DNS. Provided that the impacts of the proposed development/redevelopment are adequately addressed in the DNS, the City will adopt the DNS, but only with specific reference to said impacts. Environmental impacts of any future development/redevelopment proposal that are not addressed in the Final DNS issued (date), and SEPA Addendum, will be addressed through a separate environmental review process. The City acknowledges that, due to the existing conditions on the Property in which there is substantial development and impervious surface coverage of approximately Percent ( %), and that development and/or redevelopment would likely entail replacement of existing levels of development of the Property, and storm water runoff from up to 100% of impervious surface coverage have been calculated to be able to be managed within the existing storm water facilities, it is likely that many aspects of development and/or redevelopment relating to stormwater impacts will not involve probable significant adverse impacts. Unless future development and/or redevelopment proposals involve new information relating to stormwater impacts to suggest that an impact is a probable significant adverse impact, pursuant to WAC 197-11-600(3)(b) and Section of the Municipal Code, it is anticipated that limited additional SEPA analysis relating to stormwater impacts will be required at the time of submission of permit applications subject to this Agreement.
SEPA Compliance. City has adopted the Planned Action pursuant to the City 364 Center EIS. The Project is within the scope of the maximum anticipated level of development in 365 the Planned Action and within the scope of environmental mitigations identified and conditioned 366 to mitigate that anticipated maximum level of development. The Parties agree that the 367 environmental impacts stemming from the Project and Conceptual Guide Plan, including the 368 potential development of the Additional Parcels, have been analyzed by the Planned Action and 369 City Center EIS. Except as provided in Section 5.2, individual projects implementing the 370 Conceptual Guide Plan and this Agreement shall be considered to have been reviewed pursuant to 371 SEPA and no individual SEPA determination for a Project or Project-phase shall be required, nor 372 shall additional conditions be imposed under the City’s SEPA authority. SEPA compliance for 373 any Project or Project-phase shall be limited to the submittal of a Planned Action SEPA process 374 checklist per LMC 17.02.300.
SEPA Compliance. For this task, HHPR will prepare a SEPA Environmental Checklist for project locations 1 through
SEPA Compliance. The project will require compliance with the State Environmental Policy Act (SEPA). Otak will prepare a SEPA checklist for the project, with vicinity map and simple plan view appropriate for the general public. Otak will submit the checklist to Lewis County with the Shoreline Permit application package for environmental review as the lead agency in the SEPA process. Assumptions ▪ The proposed project will result in a Mitigated Determination of Non-Significance (MDNS). ▪ Preparation of a SEPA EIS is not included in this scope. Deliverables ▪ Draft and Final SEPA checklist and DNS with vicinity map and site plan, submitted to the County.
SEPA Compliance
