My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
5900 36TH AVE W 2025-01-06
>
Address Records
>
36TH AVE W
>
5900
>
5900 36TH AVE W 2025-01-06
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/6/2025 3:28:40 PM
Creation date
12/18/2024 2:51:38 PM
Metadata
Fields
Template:
Address Document
Street Name
36TH AVE W
Street Number
5900
Imported From Microfiche
No
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.
/
1780
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
And then we had a Landscape Modification Decision— <br />EN <br />I've attached the Landscape Plan that was included in the 2017 Public Works permit submittal (which was approved) <br />that depicts the split rail fence locations. So just in the Planned Action Determination, there is a bit of confusion <br />because the Codes are conflicting for the instance of our project because we are not allowed to have any fences in <br />the wildlife corridor, but the view analysis from 2017 (attached) shows the "wildlife corridor protection fence', <br />which appears to be outside the bubbled & hatched wildlife corridor area, but is still within a environmentally <br />sensitive area and buffers. Similarly, it is impossible to install any type of fencing in those areas depicted in the <br />approved Landscape Plan without additional clearing, which we are not approved to do so based on the Planned <br />Action Determination - <br />ME <br />This conflict in Code/Planned Action Determination/approved plans has further reared its head as we are working <br />on -site and faced with not only the native vegetation but the topography. It has become apparent that the split rail <br />fence is problematic in several areas. Here are a few keys areas of concern. <br />• On the East side, it interfered with cedar trees and a home owner's chainlink fence <br />• On the north (NE) area, the alignment is very deep into the greenbelt and goes right through the ravine -like <br />valley below Outfall C. This would require significant clearing effort. <br />• ON the north (NW) the alignment takes the fence through neighboring rockeries which may be possible, but <br />very intrusive clearing process. <br />I can provide you photos of these areas, but I do think it would be advantageous for you or the appropriate decision <br />maker to physically see the constraints and help us find a solution that would be continue to meet the Codes, <br />requirements, and design intent. If someone would like to make site visit, I would be happy to walk and talk <br />through this with you. <br />I also realize that this area is very sensitive to the residential neighbors. From my understanding, the sight line study <br />was created to help satisfy the concern of the neighbors. Because of this, I do not want to deviate from such plans <br />that were agreed upon with the neighbors, but I do not believe the logistics behind the approved plans were fully <br />considered and the impacts may be counter intuitive to the desired results. I believe avoiding these areas will <br />provide the best end product for both our project, the environment and the neighboring homes. I've attached a <br />preliminary recommendation for the new split rail fence location that will leave the wildlife corridor and buffers <br />intact without further disruption. <br />Please let me know your thoughts and would like to chat further with you on how we can make this better. <br />Angie Kim I Sr. Director, Development <br />Bridge Industrial <br />0 425 749 5557 1 C 206 832 6982 <br />
The URL can be used to link to this page
Your browser does not support the video tag.