Current through Register Vol. 24-23, December 1, 2024
Section 365-196-335 - Identification of open space corridors(1) Requirements. (a) Each county or city planning under the act must identify open space corridors within and between urban growth areas. They must include lands useful for recreation, wildlife habitat, trails, and connection of critical areas as defined in RCW 36.70A.030.(b) The county or city may seek to acquire by purchase the fee simple or lesser interests in open space corridors using funds authorized by RCW 84.34.230 or other sources.(2) Recommendations for meeting requirements.(a) Counties and cities should consider identifying open space corridors when reviewing and updating urban growth areas, critical areas designations, and the land use element of comprehensive plans.(b) Counties and cities should consider the various purposes and uses of identified corridors, and should state the preferred uses anticipated for each identified corridor, if known. In some cases, uses preferred for an identified corridor may preclude other incompatible uses.(c) Counties and cities should consider how identified corridors exist in relationship to designated critical areas and natural resource lands, the extent and trends of public demands for recreational lands and access to public lands for recreation, and specific existing and planned recreational uses that may make use of identified corridors for specific uses, including nonmotorized transportation.(d) When identifying open space corridors, counties and cities should plan an integrated system that uses identified corridors to link established large areas of parks and recreational lands, resource lands, greenbelts, streams, and wildlife corridors to help protect fish and wildlife habitat conservation areas.(e) Counties and cities should also consider the potential to use vegetated green spaces as part of an integrated system to absorb and treat storm water.Wash. Admin. Code § 365-196-335
Statutory Authority: RCW 36.70A.050 and 36.70A.190. 10-03-085, § 365-196-335, filed 1/19/10, effective 2/19/10.