Indexed News on:

--the California "Mega-Park" Project

Tracking measurable success on efforts across California to preserve and connect our Parks & Wildlife Corridors



WE POST NEWS THREE WAYS:
1. long detailed stories on blogspot (here!)
2. short messages on Twitter
3. automated news feeds from CA enviro websites in the right-hand column which change frequently and are not archived by our website (that's why we now have a twitter account to permanently capture the memorable feeds)

Monday, March 9, 2009

-
Project near San Diego River Sent Back for Redesign due to Fire Danger



City told to revise Fanita Ranch fire plan for 1400 home project in coastal sage scrub habitat; Groups had sued over development plans on the 2550 acres...
http://www.biologicaldiversity.org/news/center/articles/2009/san-diego-union-tribune-02-14-2009.html

for aerial photo:
http://members.cox.net/savefanita/Pages/MapPage2.html

http://preservewildsantee.org/ for maps and photos

ET 4/97: Santee's Fanita Ranch: open space or urban sprawl?
http://www.sdearthtimes.com/et0497/et0497s1.1.html

from one of the attorneys:

http://org2.democracyinaction.org/dia/track.jsp?v=2&c=j%2F6WtuJnIDW5CSv6m20kbk82phARHZCK

In further arguing the need for a new “EIR” it was pointed out that the City needed to take a hard look at the proposed lay out of the project and consider, among other things, eliminating the difficult to defend peninsulas and drawing the villages back from the most hazardous wildfire areas. The project as designed would add approximately 20 miles of wildland/urban interface to the City of Santee.

Judge Linda Quinn ruled that the failure to adopt open space fuel load management plans made the conclusion that wildfire impacts had been mitigated to a level of insignificance unsupportable. She has ordered the City to re-write the “EIR” section on wildfire impacts.

(Planning and Conservation League Vice President and Board Member Kevin Johnson was on the legal team representing the petitioners. He can be reached at KKJ@JohnsonandHanson.com.)

No comments: