My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2013/01/09 Council Agenda Packet
>
Council Agenda Packets
>
2013
>
2013/01/09 Council Agenda Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/8/2018 10:45:22 AM
Creation date
5/24/2017 9:44:55 AM
Metadata
Fields
Template:
Council Agenda Packet
Date
1/9/2013
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
984
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
4 Exhibit A to Ordinance No. <br />Central Waterfront Redevelopment Plan <br />above in section G.2. and discussed further below, for non -water -dependent development to the <br />extent allowed by law in the review of all shoreline permits with some exceptions. It requires <br />that public access be provided on site, except for projects that meet one of the following specific <br />criteria, including, but not limited to, <br />• The project is in the Deep Water Port Enviromnent (Kimberly-Clark mill site is in this <br />environment) or <br />• The provision of public access would result in an unavoidable health or safety hazard to <br />the public that cannot be prevented by any practical means. The applicant must <br />demonstrate that the health or safety hazards cannot be mitigated through the application <br />of alternative design features or other solutions such as regulatnlg access by such means <br />as maintaining a gate and/or limiting hours of use; designing separation of uses and <br />activities (e.g. bridges, pedestrian overpasses or underpasses, fences, terracing, use of <br />one-way glazing, hedges, landscaping, etc.). Projects that meet these exceptions must <br />construct off-site public access improvements or contribute to a fund to construct off-site <br />improvements. <br />• The provision of public access would result in significant environmental harm, and the <br />impact cannot be mitigated. <br />• The provision of on-site public access is not practical (e.g., small or odd -shaped lots, lots <br />where fiuictional requirements of the primary use would hinder access). <br />• More meaningful access that is better than that provided by the application of the goals, <br />objectives and policies of this plan can be provided off-site. <br />Everett's SMP also requires that water -enjoyment uses and nonwater-oriented uses that front on <br />the shoreline provide continuous public access along the entire site's shoreline. Everett's SMP <br />includes a variety of standards for public access and requires that when a project is located <br />within an area covered by an adopted public access plan, public access improvements shall be <br />generally consistent with the adopted plan. <br />The City's SMP, adopted in 2002, and Shoreline Public Access Plan, adopted in 2003, did not <br />anticipate redevelopment of the Kimberly-Clark site. The Kimberly-Clark site is designated <br />Deep Water Port, so it would not be required to provide on-site public access under the current <br />SMP, unless uses include water -enjoyment and/or nonwater-oriented uses in the shoreline area. <br />Water -enjoyment commercial uses are permitted in the Deep Water Port Environment and would <br />be required to provide on-site access if proposed. <br />The specific public access improvements to be provided under any alternative will be established <br />at time of review of shoreline permits based upon the nature of any use that is proposed within <br />the 200 foot jurisdiction of the Everett Shoreline Master Program, the policies and regulations in <br />this adopted plan, and the SMP requirements in effect at the time. The future use, operational <br />safety needs, location of development on the site, and specific design measures will be evaluated <br />7: <br />114 <br />
The URL can be used to link to this page
Your browser does not support the video tag.