My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2102 ROSS AVE 2018-01-02 MF Import
>
Address Records
>
ROSS AVE
>
2102
>
2102 ROSS AVE 2018-01-02 MF Import
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/3/2022 8:50:57 AM
Creation date
2/27/2017 2:51:35 PM
Metadata
Fields
Template:
Address Document
Street Name
ROSS AVE
Street Number
2102
Imported From Microfiche
Yes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
342
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
consider geological, hydrological, and biological studies to determine impact of <br />the proposal. The Applicant submitted a biological assessment (exhibit 5) that <br />concluded that the project would net adversely impact any endangered species. <br />The City did not dispute the findings of the biological assessment. (exhibit 1, <br />staff report; exhibit 5, assessment; Jimerson testimony) <br />17. The Applicant submitted a Critical Areas Report/Habitat Management Plan. <br />(exhibit 4) In the plan, the conclusions were that the project with mitigation would <br />result in the maintenance of 14 environmental indicators and the improvement of <br />eight other indicators. (Indicators are plants and animals that are used to <br />determine the feasibility of development in an area. Based on the conclusions <br />of the plan, it was concluded that only one indicator would initially be degraded, <br />but would be benefited when the buffer plantings mature. The City did not <br />dispute the findings of the Critical Areas Report/Habitat Management Plan. <br />(exhibit 4, plan) <br />18. As part of the Shoreline Permit review, developments must include mitigation for <br />any impacts to water quality. This includes compliance with City storm water <br />regulations that are consistent with the storm water regulations of the State of <br />Washington. Water quality monitoring during construction and operation would <br />be required pursuant to conditions of this Shoreline Permit. (see conditions 12, <br />14-22, and 33) (exhibit 1, staff report) <br />19. Neither the federal government nor the state government has mandated any <br />environmental cleanup for the site. There would be cleanup, however, of <br />concrete debris that has been placed on the site over the years. The concrete <br />debris would be removed on all areas below the OHWM and would be removed <br />from the site. (McClean testimony: Jimerson testimony; exhibit 1, staff report) <br />20. The City submitted that a buffer restoration plan is required for the proposed <br />project. Such a plan was presented. The conclusions are that dense planting of <br />native vegetation would occur. These plantings would have no impact on views <br />but would "soften" the appearance of the industrial activities for individuals <br />viewing from the Snohomish River. The plan calls for control of invasive species <br />in order to protect the restoration plantings. The City did not dispute the findings <br />of the buffer restoration plan. (exhibit 1, staff report; exhibit 3, narrative; <br />Jirerson testimony) <br />21. The ESMP establishes 200-foot buffers for those areas adjacent to designated <br />Aquatic Conservancy areas. As part of any development, a function assessment <br />is completed to demonstrate that the buffers will experience no net loss of <br />wetland or stream functions. If there is a loss of said functions, a wider buffer <br />could be required to protect the wetlands and the stream ecological functions. <br />Buffers can also be reduced in instances where there has been prior legal <br />alteration of the buffer and when the Applicant has completed an approved <br />function assessment and prepared a habitat plan that includes discussion of the <br />[c] <br />
The URL can be used to link to this page
Your browser does not support the video tag.