Bárðarbunga, the Toxic Tourist Trap

Posted on December 17, 2014 by Curtis_Seaman

Quick: what was the name of that Icelandic volcano that caused such a stir a few years ago? Oh, that’s right. You don’t remember. No one remembers. (Unless you live outside the U.S. in a place where you might have actually heard someone say the name correctly.) To Americans, it will forever be known as “That Icelandic Volcano” or “The Volcano That Nobody Can Pronounce” – even though it is possible to pronounce the name. Say it with me: Eye-a-Fiat-la-yo-could (Eyjafjallajökull).

Well, back at the end of August 2014 another volcano erupted in Iceland, and there is no excuse for not being able to pronounce this name correctly: Bárðarbunga. (OK, you have one excuse: use of the letter ð is uncommon outside of Iceland. In linguistics, ð is a “voiced dental fricative” which, in English, is a voiced “th”. “The” has a voiced “th”. “Theme” has an un-voiced “th” or, rather, “voiceless dental non-sibilant fricative“.) Look, you don’t want to offend any Icelanders, so say it right:

“Bowr-thar-Bunga.” See, it’s easy to say. (You may see people who are afraid of the letter ð refer to the recent eruption as Holuhraun [pronounced “Ho-lu-roin”], because Bárðarbunga is part of the Holuhraun lava field. So be aware of that.)

I know what you’re going to ask: “What is so special about this volcano? I haven’t heard anything about it up to this point, so why should I care?” You haven’t heard anything about it because you don’t live in Iceland or in Europe, which is downwind of Iceland. And, why should you care? Let me count the ways in the rest of this blog post.

You probably have heard of Kīlauea (and have no trouble pronouncing that name) and the lava flow that inched its way towards the town of Pahoa. Kīlauea has been continuously erupting since 1983. Bárðarbunga erupted on 29 August 2014 and has been spewing lava ever since, which at this point, is over 100 days of non-stop erupting. It’s Iceland’s version of Kīlauea. (Hopefully, it won’t continue to erupt for another 30 years.)

Just like Kīlauea, Bárðarbunga is attracting tourists from all over the world. It seems every wannabe photographer and videographer has gone (or wants to go) to Iceland to try to come up with the next viral video showing the breathtaking lava flows. Seriously, do a search for Bardarbunga or Holuhraun on YouTube or vimeo and see how many results show up. Here’s a pretty typical example (filmed by someone from Iceland):

Want to join in the fun? Just grab your camera, head to Iceland, hire an airplane or helicopter pilot, and find the most dramatic music you can think of to go along with your footage. Watch out, though – the airspace around the volcano can be rather crowded. As this video shows, it can be hard to film the volcano without other aircraft getting in the way.

If photography is more your thing, here are the latest images of the eruption on Twitter. (Look for the pictures of Beyonce and Jay-Z. If Twitter is correct, they flew over the volcano for his birthday. Viewing the eruption has gone mainstream! You’re too late, hipsters! Good luck getting to the next volcanic eruption before it becomes cool.)

Back to the matter at hand: why you should care about Bárðarbunga. After its first 100 days of erupting, it has created a field of new lava (76 km²) that is larger than the island of Manhattan (59 km²). The volcano has been creating a toxic plume of SO₂ for the last 100 days that is making it difficult to breathe. (Here are some of the known health effects of breathing SO₂.) SO₂ can ultimately be converted into sulfuric acid (acid rain), depending on the chemistry in the air around the volcano. And while it may not be producing as much ash as Eyjafjallajökull did, VIIRS imagery shows it is producing ash, which is a threat to aircraft.

If you follow this blog, you know the best RGB composite for detecting ash is the True Color composite. This is because the visible wavelength channels that make the composite are sensitive to the scattering of light by small particles, like dust, smoke and ash. Iceland is a pretty cloudy place, so it’s not always easy to spot the ash plume, so here it is at its most visible:

VIIRS True Color RGB composite of channels M-3, M-4 and M-5, taken 12:57 UTC 11 September 2014. The red arrow points to the location of Bárðarbunga.

Click on the image (or any other image) to see the full resolution version. The red arrow shows the location of Bárðarbunga. In case you’re wondering, the borders drawn inside the island are IDL’s knowledge of the boundaries of lakes and glaciers (jökull in Icelandic). The big one just south of the red arrow is Vatnajökull – the largest glacier in Europe and one of three national parks in Iceland. (If you want to go there, be aware of closures due to volcanic activity.)

See the ash plume extending from the red arrow to the east-northeast out over the Atlantic Ocean? Now, try to find the ash plume in this animation of True Color images from 29 August to 14 October 2014:

Animation of VIIRS True Color images of Iceland 29 August – 14 October 2014

As with most of my animations, I have selectively removed images where it was too cloudy to see anything. Sometimes, the steam from the volcano mixes with the ash to make its own clouds, much like a pyrocumulus. Watch for the ash to get blown to the northwest and then southwest in early October. In case you can’t see it, here’s a static example:

VIIRS True Color RGB composite of channels M-3, M-4 and M-5, taken 12:15 UTC 10 October 2014. The red arrow shows the location of Reykjavik.

This time, the red arrow shows Reykjavik, the nation’s capitol and likely only city in Iceland you’ve heard of. The ash plume is pretty much right over Reykjavik!

Over the course of the first 100 days, no place in Iceland has been kept safe from the ash plume. But, that’s not the only threat from Bárðarbunga: I also mentioned SO₂. If you recall from our look at Copahue (Co-pa-hway – say it right!) the EUMETSAT Dust algorithm is sensitive to SO₂. So, can we detect the toxic sulfur dioxide plume from Bárðarbunga? Of course! But, it does depend on cloudiness and just how much (and how high) SO₂ is being pumped into the atmosphere.

If you read my post on Copahue, you should have no trouble picking out the sulfur dioxide plume in this image of Bárðarbunga:

EUMETSAT Dust RGB composite applied to VIIRS, 12:57 UTC 11 September 2014

This image is from the same time as the first True Color image above, when the plume was very easy to see. Also note the large quantity of contrails (aka “chemtrails” to the easily misled). Those are the linear black streaks west of Iceland. If you’re confident in your ability to see the sulfur dioxide, see how often you can pick it out in this animation:

Animation of EUMETSAT Dust RGB images from VIIRS (29 August – 10 October 2014)

Some detail is lost because an RGB composite may contain as many as 16 million colors, while the .gif image standard only allows 256. But, you can still see the pastel-colored SO₂ plume, which almost looks greenish under certain conditions due to interactions with clouds. Also note the volcano itself appears cyan – the hottest part of the image has a cool color! Unusual in a composite that makes almost everything appear red or pink.

If you want to see the volcano look more like a hot spot, here are animations of the shortwave IR (M-13, 4.0 µm) and the Fire Temperature RGB composite (which I promote whenever I can). I should preface these animations by saying I have not removed excessively cloudy images but, at least 80% of the days have two VIIRS afternoon overpasses and, to reduce filesizes, I have kept only one image per day:

Animation of VIIRS M-13 images of Iceland (29 August – 15 October 2014)

The Fire Temperature RGB is made up of M-10 (1.6 µm; blue), M-11 (2.25 µm; green) and M-12 (3.7 µm; red):

Animation of VIIRS Fire Temperature RGB images of Iceland (29 August – 15 October 2014)

No surprise, molten rock is quite hot! That area of lava has saturated my color table for M-13 and it saturated the Fire Temperature RGB. As I’ve said before, only the hottest fires show up white in the Fire Temperature RGB and lava is among the hottest things you’ll see with VIIRS. Sometimes, you can see the heat from the volcano through clouds (and certainly through the ash plume)! It’s also neat to watch the river of lava extend out to the northeast and then cool.

To quantify it a bit more, the first day VIIRS was able to see the hot spot of Bárðarbunga (31 August 2014), the M-13 brightness temperature was the highest I’ve seen yet: 631.99 K. The other midwave-IR channels (M-12 and I-4; 3.7 and 3.74 µm, respectively) saturate at 368 K. The Little Bear Fire (2012) peaked at 588 K and that fire was hot enough to show up in M-10 (1.6 µm) during the day, so it’s no wonder that we’ve saturated the Fire Temperature RGB.

There’s one more interesting way to look at Bárðarbunga using a new RGB composite. When I was first tipped to this event, I saw this image from NASA, which you can read more about here. That image was taken by the Operational Land Imager (OLI) from Landsat-8 and is a combination of “green, near-infrared and shortwave infrared” channels. Applying this to VIIRS, that combination becomes M-4 (0.55 µm), M-7 (0.87 µm) and M-11 (2.25 µm), which is similar to the Natural Color composite (M-5, 0.64 µm; M-7, 0.87 µm; M-10, 1.61 µm) except for a few notable differences. M-4 is more sensitive to smoke and ash and vegetation than M-5. And M-11 is more sensitive to fires and other hotspots than M-10.

The differences are subtle, but you can see them in this direct comparison:

Comparison between VIIRS “Natural Color” and “False Color with Shortwave IR” RGB composites (12:38 UTC 14 October 2014)

NASA calls this RGB composite “False Color with Shortwave Infrared,” although I’m sure there has to be a better name. Any suggestions?

Most of my images and loops have come from the first 45 days after eruption. This was a very active period for the volcano, and is where most of the previously mentioned videos came from. (And trust me, you and your browser couldn’t handle the massive animations that would have resulted from using all 100+ days of images.) To prove Bárðarbunga has gone on beyond that, here’s one of the new RGB composites from 17 November 2014:

VIIRS false color RGB composite of channels M-4, M-7 and M-11, taken 13:42 UTC 17 November 2014

This image really makes Iceland look like a land of fire and ice, which is exactly what it is!

Wild Week of Wildfires, Part III

Posted on June 14, 2013 by Curtis_Seaman

The last two posts covered flooding. Now, a month later, we are back to covering last year’s most common topic: wildfires. This time, we’ll make a game out of it. Keep in mind that, for many operational fire weather forecasters, this isn’t a game – it is information that could prove useful in saving lives or homes from destruction. If you have read the earlier posts on fire detection and haven’t forgotten what you’ve been told (here’s a good one to go back and read), this should be easy for you.

The following images are the unmapped data from three consecutive VIIRS granules over the Southwest U.S., starting at 20:36 UTC 11 June 2013. The “raw” data has been processed to produce the “True Color”, “Natural Fire Color” and “Fire Temperature” RGB composites. Plus, the brightness temperature data from channel M-13 (4.0 µm) has a color table applied to it to aid in fire detection. Satellite channels near 4 µm are the “industry standard”, so to speak, for detecting fires as they are highly sensitive to sub-pixel heat sources like fires. The “Natural Fire Color” and “Fire Temperature” composites are RGB composites developed just for VIIRS that both had their debut on this very blog.

The question is: how many fires can you see? Remember, you have to allocate resources (firefighters, helicopters, planes, etc.) based on your assessment. The media is hounding you for all the latest statistics on each blaze and they can’t wait until the 5:00 briefing. They need the scoop now to get higher ratings. Plus, the crew is loading fire retardant on the plane as you read this. Where should the pilot fly to? Everyone is counting on you! (Of course, you would never have just satellite data by itself in a real-life scenario – but, do you want to play this game, or just think of flaws?)

I’ll give you a hint: You won’t see any fires unless you view each image at full resolution. Click on the image, then on the “3200×2304” link below the banner to see the full resolution version. (You could even open each full resolution image in a new tab, and click between the tabs for easy comparison, assuming you’re not using some archaic version of Internet Explorer or another old browser that doesn’t allow tabs. When you would click on the “3200×2304” link, instead right-click and select “Open in New Tab”. Another option would be to save the images and open them in an image viewing software program that will allow you to zoom in more than 100% but, that is starting to sound like a lot of work and I’m not sure I want to play this game anymore. It’s too complicated. By the way, if that’s the way you feel, don’t become the manager of a fire incident team.)

I’ll give you another hint: Many of the hot spots that indicate fires are only 1-2 pixels in size. Be prepared to look for needles in the haystack, and make sure you have your reading glasses on, if you need them.

VIIRS "True Color" composite of channels M-03, M-04 and M-05, taken at 20:36 UTC 11 June 2013

VIIRS "Natural Fire Color" composite of channels M-05, M-07 and M-11, taken 20:36 UTC 11 June 2013

VIIRS "Fire Temperature" composite of channels M-10, M-11 and M-12, taken 20:36 UTC 11 June 2013

VIIRS channel M-13 image, taken 20:36 UTC 11 June 2013

So, did you see them all? You should have identified 12 fires. Did you find less than 12? Some of them are hard (or impossible) to see in some of the images. Did you find more than 12? The color scale used on the M-13 image led to false alarms, so you can be forgiven if that’s what caused you count too many.

This example shows some of the complicating factors when trying to identify fires from satellites. It also shows why fire managers never rely on satellite data alone. Now, having said that, VIIRS can and does provide useful information on fires.

First, here’s the answer (link goes to PDF) from the National Interagency Fire Center. They identified 15 active “large incident” fires on 12 June 2013. (They update their maps once per day, so all the fires that started on 11 June make it on the 12 June map.) But, there are differences between their map and what VIIRS saw.

First, the Mail Trail fire (#5 in the PDF) is outside the domain of these three VIIRS granules, so you couldn’t have found that in these images. Fires #3, 4 and 7 (Healy, Porcupine and Ferguson) are obscured by clouds, and/or were mostly contained, transitioning from active to inactive. The Tres Lagunas Fire (#13) started back in May and is undergoing mop up activities. The hot spots from that fire (if there are any left) aren’t visible in the images, but the burn scar is. That leaves the Stockade (#1), Crowley Creek (#2), Hathaway (#6), Fourmile (#8), Silver (#9), Thompson Ridge (#10), Jaroso (#11), Big Meadows (#12), Royal Gorge (#14), and Black Forest (#15) – 10 fires which are all visible in the VIIRS images. Plus, VIIRS saw two more fires that are not included on that list: one in southern California (near the Salton Sea) that I couldn’t find any information on, plus a pellet plant fire in Show Low, Arizona. (Small fires in towns are usually outside the scope of the National Interagency Fire Center, so they don’t bother to list those.)

I would argue that the “Fire Temperature” composite worked the best at identifying each of these fires, but all 4 images have their uses. Here’s the Fire Temperature RGB image with the visible fires identified:

VIIRS "Fire Temperature" composite of channels M-10, M-11 and M-12, taken 20:36 UTC 11 June 2013

Answer honestly. Which fires did you see, and which fires did you miss?

The Fire Temperature RGB takes advantage of the VIIRS channels in the portion of the electromagnetic spectrum ranging from the near-infrared (NIR) to the shortwave infrared (SWIR). The blue component is M-10 (1.61 µm), the green component is M-11 (2.25 µm) and the red component is M-12 (3.7 µm). As wavelength increases over this range, the contribution of the Earth’s emission sources increases and the contribution from the sun decreases. As a result, only the hottest hot spots show up in M-10, as they have to be seen over the large signal of radiation from the sun reflecting off the Earth’s surface. In M-12 (as in M-13), hot spots from fires produce more radiation at that wavelength than the amount of reflected solar radiation. M-11 is somewhere in the middle. That means relatively cool (e.g. smoldering) or small fires only show up in M-12, which makes those pixels appear red. Pixels containing fires hot enough or large enough to show up in M-11 will take on an orange to yellow color. Pixels containing fires hot enough or large enough to show up in all three channels will appear white.

You have to be careful, though, as some pixels in the Fire Temperature RGB appear red, even though there aren’t any fires in them. A few of these pixels show up red in the M-13 image, and are labelled as “not a fire/false alarm”:

VIIRS M-13 image, taken 20:36 UTC 11 June 2013

According to the color table used, any pixel with a brightness temperature above 340 K (67 °C) will be colored, with colors ranging from red to orange to pale yellow as temperature increases. Now, look at that area in the True Color image (or on Google Maps):

VIIRS "True Color" composite of channels M-03, M-04 and M-05, taken 20:36 UTC 11 June 2013

That area is very dark – almost black – volcanic rock with very little vegetation that has been baking in the sun all day. It has managed to acquire a brightness temperature that is higher than some of the active fire pixels. The Crowley Creek fire doesn’t show up as red in the M-13 image (the Stockade fire is the one with the yellow and orange pixels) and the Fourmile fire is barely visible. (It has two pixels warmer than 340 K, even though 10 pixels appear red in the Fire Temperature RGB). The color scale in the M-13 image could be applied to a different temperature range, but you’ll always have that trade-off: have the colors start at too high a temperature, and you’ll miss some fires; have the colors start at too low a temperature, and you’ll increase the false alarms.

The True Color image should have helped you identify 5 of the fires. The smoke plumes that show up are a dead giveaway. I’m talking about the Big Meadows, Royal Gorge, Jaroso, Thompson Ridge and Silver fires, of course. There may be smoke with the Hathaway fire, but it would be mixed in with the cirrus clouds and hard to see. Not all fires produce a lot of smoke, though. Having information on the ones that do aids in issuing air quality alerts, among other benefits.

Lastly, the Natural Fire Color image highlights most (but not all) of the fires. Look for the red pixels:

VIIRS "Natural Fire Color" composite of channels M-05, M-07 and M-11, taken 20:36 UTC 11 June 2013

The Natural Fire Color doesn’t show active hot spots at Crowley Creek, and the Hathaway and Fourmile fires are difficult to see, because they aren’t quite hot enough. (Generally speaking, any fire that shows up red in the Fire Temperature RGB is too cold to show up as red in the Natural Fire Color.) But, this composite has the advantage of showing burn scars in addition to the active fires. Burn scars appear dark brown. The Fourmile and Crowley Creek burn scars are visible. Plus, burn scars from last year’s fires still show up: The Whitewater-Baldy, High Park and Waldo Canyon scars are identified. The Tres Lagunas was mentioned above, and it’s burn scar is visible. If you look closely, I’m sure you could find more burn scars from last year’s long fire season.

Here are all four images, zoomed in on each fire at 800%, combined into an animation to highlight how each fire appears in each image:

Animation of M-13, True Color, Natural Fire Color and Fire Temperature imagery zoomed in each fire (20:36 UTC 11 June 2013)

For some reason, you have to click to the full resolution version of the image before the animation will display.

Hopefully, this exercise is useful in demonstrating the complications that arise when trying to detect fires from satellites in space, as well as the strengths and weaknesses of some of the various methods VIIRS has at it’s disposal to aid the fire weather community.

The Outback on Fire

Posted on September 21, 2012 by Curtis_Seaman

I’m not talking about a Subaru. I’m talking about the vast expanse of sparsely-populated Australia. We’ve already seen fires in the United States, Russia and the Canary Islands. Well, they have been happening down under, too. (Is there any part of this planet not currently experiencing a drought?)

Despite the risk of getting fire fatigue (“Another post about fires?” *yawn*), we’re going to look at these fires for two reasons. First, it gives me a chance to show off the “fire tornado” video clip that has been making the rounds on the Internet:

Second, VIIRS saw the fire that produced the “fire tornado” (and a whole bunch of other fires) and it gives me a chance to show off the newly christened “Fire Temperature RGB”.

First, let’s look at the boring (yet still valuable) way of detecting fires: identifying hot spots in a 3.9 µm image. Here’s what VIIRS channel M-13 (4.0 µm) saw over Australia on 19 September 2012:

VIIRS channel M-13 image of central Australia, taken 04:34 UTC 19 September 2012

Pixels hotter than 350 K show up as black in this image. Given this information, how many fires can you see? (Hint: click on the image, then on the “3200×1536” link below the banner to see the image at full resolution. And, no, wise guy – you don’t count all the black pixels outside the boundaries of the data.)

Here’s the “pseudo-true color” RGB composite (this time made of M-05 [0.67 µm, blue], M-07 [0.87 µm, green], and M-10 [1.61 µm, red]):

False-color RGB composite of VIIRS channels M-05, M-07 and M-10, taken 04:34 UTC 19 September 2012

With this RGB composite, really hot fires show up as bright red pixels. More hot spots are visible in the M-13 image than the “pseudo-true color” image because M-13 is much more sensitive to the heat from fires than M-05, M-07 and M-10 are. M-10 only picks up the signal from the hottest (or biggest) fires. M-05 and M-07 don’t pick up the heat signal at all, because the radiation from the sun, reflected off the Earth’s surface, drowns it out (which is precisely why the hot spots look red). M-13 is also better at detecting fires because it works at night, unlike these three channels.

You can make the hot spots from the smaller/less hot (lower brightness temperature) fires more visible by replacing M-10 with M-11 (2.25 µm) as the red channel in the RGB composite. M-11 is more sensitive to hot spots than M-10. If you do that, you get this image:

False-color RGB composite of VIIRS channels M-05, M-07 and M-11, taken 04:34 UTC 19 September 2012

Since the previous RGB composite is often referred to as “natural color”, maybe this one should be called the “natural fire color” RGB composite. Now, most of the hot spots (not just the hottest ones) show up as red.

It should be noted that the fire complex in the grid box bounded by the 24 °S and 26 °S latitude and 128 °E and 132 °E longitude lines is where the video of the fire tornado came from. That fire is currently burning close to Uluru (a.k.a. Ayers Rock), the site where the creator beings live, according to local legend. According to an Uluru-Kata Tjuta National Park newsletter from back in July, prescribed burns were taking place in and around the park, although it’s not clear if the fires seen by VIIRS now (in September) are part of the prescribed burns.

EUMETSAT recently held a workshop on RGB satellite products, where a new RGB composite was proposed for VIIRS: the “Fire Temperature RGB”, made from M-10 (1.61 µm, blue), M-11 (2.25 µm, green) and M-12 (3.70 µm, red). Here’s what that looks like:

False-color RGB composite of VIIRS channels M-10, M-11 and M-12, taken 04:34 UTC 19 September 2012

In this composite, hot spots from fires show up as yellow, orange, bright red or white, depending on how hot they are. Liquid clouds show up as light blue. Ice clouds, which are missing from this scene, typically show up as dark green. The background surface shows up as a shade of purple. Burn scars, which show up as dark brown in the “natural color” and “natural fire color” composites, show up as more of a maroon color in the “fire temperature” composite. Coincidently, maroon is the “official color” of Queensland, although it looks like most of the maroon burn scars show up in the Northern Territory.

To easily compare the different views of the fires (and make it obvious to everyone what the fires look like), here’s an animation, zoomed in on the lower left corner of each of the images above:

Animated loop of images of the fires in Australia as seen by VIIRS, 04:34 UTC 19 September 2012

The yellow highlighted areas are where the active fires are.

Now that you’ve seen several different ways of displaying fire hot spots with VIIRS, which one do you like best?

Fires in Paradise

Posted on August 16, 2012 by Curtis_Seaman

Sometimes, it seems like the whole world is on fire. Siberia. The western United States (which has been burning for some time). And now, the Canary Islands. The Spanish islands have been under a drought, as has much of Spain. (As an indication of how dry it has been, one fire in mainland Spain was started by someone flicking a cigarette butt out of their car window in a traffic jam – a fire that ultimately led to two deaths.) Back in July, fires got started on Tenerife – a major resort destination – and earlier this month, fires began on La Palma and La Gomera. At least two firefighters have already died battling these fires.

For your reference, here is a VIIRS “true color” image (M-3 [0.488 µm], M-4 [0.555 µm], M-5 [0.672 µm]) of the Canary Islands, with the major islands labelled:

VIIRS true color RGB composite of channels M-3, M-4 and M-5, taken 14:01 UTC 5 August 2012

If you look closely at this image, from 5 August 2012, you can see smoke plumes coming off of La Palma and La Gomera. You can also see what looks like a von Kármán vortex street downwind of La Palma. That’s the west coast of Africa in the lower-right corner of the image.

As discussed previously, the true color RGB composite is better for viewing the smoke plume, but you can’t actually see the fire directly. So, here’s the M-5 (0.672 µm), M-7 (1.61 µm) and M-11 (2.25 µm) composite from the same time:

VIIRS RGB composite of channels M-5, M-7 and M-11, taken 14:01 UTC 5 August 2012

It’s easy to see where the fires are actively burning with this composite. Let’s zoom in to make it even more obvious:

VIIRS false color RGB composite of channels M-5, M-7 and M-11, taken 14:01 UTC 5 August 2012

All the bright red pixels indicate where the fire is actively burning. You can also see the burn scar on Tenerife (not as easily as in Siberia) where the M-5, M-7, M-11 RGB composite shows the fire was back in July:

VIIRS false color RGB composite of channels M-5, M-7 and M-11, taken 14:38 UTC 18 July 2012

La Gomera has been the hardest hit island, where thousands of people had to be evacuated, and approximately 10% of Garajonay National Park has burned. Garajonay National Park is home to one of the last remaining laurisilva forests, which has been around for 11 million years. That lush vegetation burned hot, and channel I-04 (3.7 µm) reached saturation as that area went up in flames:

VIIRS channel I-04 image of fires in the Canary Islands, taken 14:01 UTC 5 August 2012

The two white pixels on La Gomera are where I-04 reached saturation and “fold-over” due to the heat from the fire. M-13 (4.0 µm), which is a dual-gain band designed to not saturate, reached a brightness temperature of 451 K over La Gomera, compared with a saturation brightness temperature of 367 K for channel I-04.

The fires also showed up in the Day/Night Band that night:

VIIRS Day/Night Band image of the Canary Islands, taken 02:25 UTC 6 August 2012

The red arrows point out the fires on La Palma and La Gomera. The fire on La Gomera covers a significant percentage of the island. The yellow arrow points to Lanzarote, which, for some reason, is not part of IDL’s map. On the night this image was taken, the moon was approximately 84% full, so you can see a number of clouds as well the city lights from the major resort areas of the Canary Islands. The biggest visible city in Africa is El Aaiún, the disputed capital of Western Sahara.

Finally, here’s the “pseudo-true color” composite of VIIRS channels I-01 (0.64 µm), I-02 (0.87 µm) and I-03 (1.61 µm) from 13:42 UTC 6 August 2012. This is a full granule at the native resolution of the Imagery bands with no re-mapping, showing the rich detail of VIIRS high-resolution imagery, including more interesting cloud vortices:

VIIRS false color RGB composite of channels I-01, I-02 and I-03, taken 13:42 UTC 6 August 2012

Make sure to click on the image, then on the “6400×1536” link to see it in its full glory.

A Wild Week of Wildfires

Posted on June 14, 2012 by Curtis_Seaman

The last few weeks have been filled with lightning-ignited wildfires across the United States. The County Line Fire, along the Florida-Georgia border was caused by lightning on 5 April 2012 and burned ~35,000 acres. The Whitewater-Baldy Complex (began 16 May 2012) – the largest wildfire in New Mexico history – started as two different fires (both caused by lightning) that merged together. It’s over 280,000 acres (that’s not a typo) and continues to burn (as of 13 June 2012). The Duck Lake Fire (began 24 May 2012) burned 21,000 acres of Michigan’s Upper Peninsula and was caused by lightning. The Little Bear Fire (began 4 June 2012), also in New Mexico, was caused by lightning and has burned ~37,000 acres. Much closer to home, the High Park Fire (began 9 June 2012) is already the largest wildfire in Larimer County history and the third largest fire in Colorado history. It has burned ~46,000 acres and I bet you can guess what caused it.

It’s not clear who is to blame here – there is a long list of suspects – but I bet it was Thor. Even though the U.S. is generally the domain of the Thunderbird, Thor has a mountain-crushing hammer called Mjöllnir, which makes him as good a suspect as any. He may have been in cahoots with Indra or Marduk who are the bringers of rain, and have been holding back on us. Look at how dry it has been across the majority of the country.

With all of these fires, it’s hard to know where to begin. We’re going to ignore the County Line Fire as it was put out over a month ago. We’re also going to ignore the Whitewater-Baldy Complex, as it is so big, it can be seen by GOES. (Kidding! We kid because we love.) Plus, it’s been done before. The VIIRS view of the High Park Fire has also been looked at by CIMSS, with an interesting comparison between VIIRS and MODIS.

What we are going to do is show off interesting features of some of these fires that haven’t been shown or discussed before (as far as we know). We begin with “saturation”. Both the High Park Fire and Little Bear Fire saturated the VIIRS 3.7 µm channels (I-04 and M-12):

Channel I-04 image of the Little Bear Fire from VIIRS taken 20:16 UTC 9 June 2012

Channel I-04 (3.7 µm) image of the Little Bear Fire from VIIRS taken 20:16 UTC 9 June 2012

Channel M-12 image of the Little Bear Fire from VIIRS taken 20:16 UTC 9 June 2012

Channel M-12 (3.7 µm) image of the Little Bear Fire from VIIRS taken 20:16 UTC 9 June 2012

Channel I-04 image of the High Park Fire from VIIRS taken 19:59 UTC 10 June 2012

Channel I-04 (3.7 µm) image of the High Park Fire from VIIRS taken 19:59 UTC 10 June 2012

Channel M-12 image of the High Park Fire from VIIRS taken 19:59 UTC 10 June 2012

Channel M-12 (3.7 µm) image of the High Park Fire from VIIRS taken 19:59 UTC 10 June 2012

The top two images are of the Little Bear Fire, which formed near the border of Lincoln and Otero counties in New Mexico. The bottom two images are of the High Park Fire in Larimer County, Colorado. For each fire, the high resolution 3.7 µm channel (I-04) is compared with the moderate resolution 3.7 µm channel (M-12). The colors range from white (cold) to black (hot). But, wait a minute! If white is cold, why are there white pixels mixed in with the black ones that indicate the hot spots? That’s because these channels are saturating and experiencing “fold-over”. The peak brightness temperatures these channels can measure is ~ 367 – 368 K. Anything warmer than that won’t be detected, so the channel is said to be saturated. When it really gets above that limit you can have “fold-over”, where not only are you not observing the higher, correct temperature, the detectors actually report a lower temperature or radiance. In these fires, the fold-over is resulting in brightness temperatures down to 203 K for M-12 and 208 K for I-04, which is about 90-100 K colder than even the area surrounding the fires!

Luckily, VIIRS has a 4.0 µm channel (M-13) that was designed to not saturate at the temperature of typical wildfires. Compare the hottest pixels in the M-13 images below with the fold-over pixels from M-12 and I-04 above:

Channel M-13 image of the Little Bear Fire from VIIRS taken 20:16 UTC 9 June 2012

Channel M-13 (4.0 µm) image of the Little Bear Fire from VIIRS taken 20:16 UTC 9 June 2012

Channel M-13 image of the High Park Fire from VIIRS taken 19:59 UTC 10 June 2012

Channel M-13 (4.0 µm) image of the High Park Fire from VIIRS taken 19:59 UTC 10 June 2012

The hottest pixel in M-13 reached a temperature of 588 K for the Little Bear Fire and 570 K for the High Park Fire – over 200 K warmer than the saturation points of M-12 and I-04!

These fires were so hot, they appeared in channels that don’t usually show a fire signal. Limiting our attention to the High Park Fire (which was almost literally in our back yard), here’s the I-05 (11.5 µm) image from 10 June 2012:

Channel I-05 image of the High Park Fire from VIIRS taken 19:59 UTC 10 June 2012

Channel I-05 (11.5 µm) image of the High Park Fire from VIIRS taken 19:59 UTC 10 June 2012

The highest temperature observed in I-05 was 380 K. Longer wavelength channels, such as in I-05 are less sensitive to sub-pixel hot spots than channels in the 3.7 – 4.0 µm range, so fires don’t often show up. For pixels to have a 380 K brightness temperature in I-05, it means that the average temperature over the entire pixel had to be above +100 °C – hot enough to boil water!

Fires don’t often show up at shorter wavelengths, either, because the amount of solar radiation usually dwarfs any signal from the Earth’s surface. But, the High Park Fire did reach saturation at 2.25 µm (M-11):

Channel M-11 image of the High Park Fire from VIIRS taken 19:59 UTC 10 June 2012

Channel M-11 (2.25 µm) image of the High Park Fire from VIIRS taken 19:59 UTC 10 June 2012

The color scale has been reversed so that it is more inline with visible imagery. The white pixels represent saturation in M-11 at a radiance of 38 W m^-2 µm^-1 sr^-1. The reflectance of these pixels saturated at a value of 1.6, which means that the amount of radiation detected in this channel was more than 1.6 times the amount you would expect to see if the surface was a perfect mirror reflecting all the solar radiation back to the satellite. Thus, the fire’s contribution to the total radiance was significant in this channel.

The contribution from the surface (i.e., the fire) was also visible in the 1.6 µm channel (M-10), but it isn’t exciting enough to show. One channel shorter down on VIIRS (M-9, 1.38 µm) and the signal disappears against the high reflectivity of the smoke plume.

It’s impossible to leave out the Day/Night Band, which shows just how large and how close the High Park Fire got to Fort Collins:

Day/Night Band image of the High Park Fire from VIIRS taken 09:58 UTC 11 June 2012. Image courtesy Dan Lindsey.

The smoke plume, while not exactly visible, is affecting the view of the east side of the fire and Fort Collins, making them appear more blurry than they would if the sky were completely clear. You can also see that, overnight on 11 June 2012, the fire covered an area larger than any of the cities visible in the image (except for Denver, which is mostly cropped off the bottom of the image).

Hopefully, Marduk will start doing his job and bring us some rain and these will be the last fires for a while.

JPSS (SNPP and NOAA-20)

VIIRS Imagery and Visualization Team Blog

Tag Archives: M-13

Bárðarbunga, the Toxic Tourist Trap

Wild Week of Wildfires, Part III

The Outback on Fire

Fires in Paradise

A Wild Week of Wildfires