Flutterby™! : Santa Rosa devastation

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Santa Rosa devastation

2017-10-12 22:38:24.487288+00 by Dan Lyke 1 comments

If you want to wrap your head around the scale of the devastation in Santa Rosa, here's some DigitalGlobe IR imagery showing the destruction, overlaid over the old imagery. Note the Fountaingrove area at the bottom of where this map opens to. Go left across 101 where it bends and look for the intersection of Coffey Ln and (zooming in a hair so the label becomes visible) Hopper Ave. Back up to the neighborhoods burned around Mark West Springs Rd. Based on this the fires didn't get as far as we'd feared, but holy crap. (And, yes, I suppose that Harbor Freight at Piner & Airway didn't burn after all).

It has been suggested that it's interesting that it seems like the primary fuel source in much of this was houses rather than foliage. Not so much in the Coffey Park area, but it sure looks like a lot of foliage left in the Fountaingrove area.

https://api.mapbox.com/styles/...SOE3HYbw#13.34/38.4721/-122.7258

[ related topics: Interactive Drama Maps and Mapping Real Estate ]

comments in ascending chronological order (reverse):

#Comment Re: Santa Rosa devastation made: 2017-10-13 10:32:53.322854+00 by: DaveP

The angle that this is mostly houses and not foliage burning is not one that I've heard before. Be safe out there, buddy.

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)




Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.


Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.