My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2012/01/25 Council Agenda Packet
>
Council Agenda Packets
>
2012
>
2012/01/25 Council Agenda Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/8/2017 11:01:49 AM
Creation date
5/8/2017 11:01:11 AM
Metadata
Fields
Template:
Council Agenda Packet
Date
1/25/2012
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
147
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
• Site projects outside the floodplain if possible,or at the point in the parcel farthest from <br /> 1 any stream if not,id.; <br /> 2 • Maintain low density of five-acre lots or greater,id.; <br /> • Limit new impervious surfaces to no more than 10%of site, and limit clearing of native <br /> 3 vegetation to 35%,id. at 225; <br /> • Design and locate projects so that they will not need new structural protection, id.; <br /> 4 • Prohibit new road crossings, id., and; <br /> • Employ concepts of"cluster development, density transfer, credits and bonuses, planned <br /> 5 unit development and transfer of development rights"wherever possible, id. <br /> 6 Not a single one of these standards exists under the Door 3 "permit-by-permit"approach <br /> 7 applicable to most communities. They are not incorporated into any requirement or directive. They <br /> 8 are either not mentioned in the vague Habitat Assessment Guidance,or are made optional. Under <br /> 9 Door 3,a project that violates every single one of these specific proscriptions could be authorized. <br /> 10 At best, all that is required would be an"assessment"and mitigation package, prepared by the <br /> 11 project proponent and reviewed by the community, claiming that no net adverse effects would <br /> 12 occur. Id.; Wald Decl.,¶26. <br /> 13 The other two compliance pathways are not notably better. Some of these directives are <br /> 14 absent altogether from the Model Ordinance and checklist. For example,these make no mention of <br /> 15 requirements relating to large woody debris, or the tracking and reporting that is emphasized so <br /> 16 heavily throughout the FEMA BiOp. The Ordinance makes voluntary many RPA standards,for <br /> 17 example the delineation of CMZs,use of stricter variance criteria and cluster development,and <br /> 18 adoption of"low impact development"criteria to eliminate stormwater. Id. at 7 ("All language is <br /> 19 optional unless noted in the commentary as an NFIP requirement[],an ESA requirement[],or <br /> 20 Washington state law...")(emphasis in original). Crucially,while the Ordinance includes a <br /> 21 provision that appears to prohibit compensatory mitigation in the protected area(a critical protection <br /> 22 of the BiOp), it is identified as optional. Id. at 53.17 And for standards identified as mandatory,the <br /> 23 Ordinance allows them to be waived as long as there is an individual habitat assessment and <br /> 24 <br /> 25 t'Not surprisingly, some jurisdictions approved by FEMA as compliant have not adopted this"optional" <br /> proposed language from the Model Ordinance. Wald Decl.,¶ 18. In other words,FEMA allows them to <br /> 26 use compensatory mitigation in the protected area, in clear violation of RPA standards. <br /> 27 Earthjustice <br /> PLAINTIFF'S MOTION FOR PRELIMINARY 705 Second Ave.,Suite 203 <br /> Seattle, WA 98104 <br /> 28 INJUNCTION(Case No. 2:11-cv-02044-RSM) -22- <br /> (206)343-7340 <br />
The URL can be used to link to this page
Your browser does not support the video tag.