EUMETSAT Meteosat-8 Infrared Window (10.8 µm) images (above) showed the intensification of Cyclone Fani to a high-end Category 4 storm on 02 May 2019 (ADT | SATCON | PGTW advisory), before eventually making landfall in northeastern India at 0230 UTC on 03 May. During its life cycle, Fani moved over warm sea surface temperature values of 29-30ºC — and deep-layer wind shear of only 5-10 knots on 02 May provided an environment favorable for rapid intensification.

Once inland, Fani was in the process of rapidly weakening to a Category 1 storm as it passed over Bhabaneswar (VEBS), and surface wind gusts to 75 knots were reported at that site (below).

A sequence of VIIRS Infrared Window (11.45 µm) images from NOAA-20 and Suomi NPP as viewed using RealEarth (below) showed snapshots of Fani from 19 UTC on 01 May (over the Bay of Bengal) to 07 UTC on 03 May (after landfall).

A comparison of VIIRS True Color Red-Green-Blue (RGB) and Infrared Window (11.45 µm) images from NOAA-20 and Suomi NPP on 02 May (below) showed Fani shortly after it had reached Category 4 intensity.

A toggle between a DMSP-17 SSMIS Microwave image at 1230 UTC and a Meteosat-8 Infrared Window image at 1300 UTC  from the CIMSS Tropical Cyclones site (above) showed the eye and totally closed eyewall of Fani when it was at its peak intensity on 02 May. However, the MIMIC TC product (below) indicated that the eastern portion of the eyewall started to erode as Fani approached the coast and began to undergo an eyewall replacement cycle.

On 30 April, VIIRS DayNight Band (0.7 µm) images (below, courtesy of William Straka, CIMSS) revealed widespread mesospheric airglow waves (reference) within the western semicircle of the storm, along with numerous bright lightning streaks associated with convection south of the storm center.

View only this post Read Less

In a comparison of GOES-17 (GOES-West) Low-level Water Vapor (7.3 µm), Mid-level Water Vapor (6.9 µm), Upper-level Water Vapor (6.2 µm) and “Clean” Infrared Window (10.3 µm) images (above), the Water Vapor imagery revealed an interesting stationary linear boundary — oriented NNW to SSE, near 152-154ºW longitude — over the North Pacific Ocean on 02 May 2019. In addition, note the other linear boundary that propagated from E to W, moving right through the aforementioned stationary boundary (best seen in the 6.19 um Upper-level Water Vapor imagery). There was no evidence of either of these linear features in the corresponding GOES-17 Infrared imagery, or in Visible imagery (not shown). A perfect candidate for the “What the heck is this?” blog category.

One possible explanation for the curious stationary feature was that it resulted from a convergence of flow around the cutoff low to the east and a digging trough approaching from the west. GOES-15 Infrared cloud-tracked Derived Motion Winds from the CIMSS Tropical Cyclones site (below) did show evidence of some converging flow in that region. Derived Motion Winds from GOES-17 were still in the Beta stage, and were not available for display in AWIPS.

View only this post Read Less

On 01 May, GOES-17 (GOES-West) Shortwave Infrared (3.9 µm) and “Red” Visible (0.64 µm) images (above) showed the thermal anomaly (or fire “hot spot”) and dispersion of smoke from the first moderate-size wildfire of 2019 in the Interior of Alaska — the Oregon Lakes Impact Area Fire about 7 miles southwest of Fort Greely. This fire grew from 30 acres to 4000 acres in a 24-hour period, aided by warm daytime temperatures with low relative humidity values and southwest winds late in the day on 30 April (surface data). The Oregon Lakes Impact Area Fire was burning in a remote area just west of the Delta River which was previously burned by the 2013 Mississippi Fire; that area also contained unexploded ordnance dropped by military aircraft during training exercises.

A toggle between Suomi NPP VIIRS Day/Night Band (0.7 µm) and Shortwave Infrared (3.74 µm) images at 1216 UTC or 4:16 am local time (below) revealed the nighttime glow of the fire, along with a more accurate depiction of the size and location of the thermal anomaly.

Although the color enhancements were different, a comparison of Shortwave Infrared images from Suomi NPP (3.74 µm) at 1216 UTC and GOES-17 (3.9 µm) at 1220 UTC (below) demonstrated the advantage of imagery from polar-orbiting satellites at high latitudes. In this example, the 375-meter resolution VIIRS image showed 2 distinct fire hot spots that were not apparent in the lower spatial resolution — 2 km at nadir, decreasing to about 4 km over Alaska — GOES-17 image.

A larger-scale view of GOES-17 Shortwave Infrared and Visible images from 02-04 UTC on 02 May (below) showed the fire as it exhibited its peak 3.9 µm infrared brightness temperature (51.3ºC or 324.5 K at 0210 UTC) and the smoke plume had drifted over 100 miles to the southeast, moving over Beaver Creek, Yukon (CYXQ). While most of the smoke was apparently lofted above the boundary layer, the surface visibility at Fort Greely PABI was briefly reduced to 6 miles at 09 UTC or 1am local time on 02 May. Note the lack of “false cold pixels” adjacent to the warmest 3.9 µm pixels — this is due to a recent change to the GOES-R ABI Band 7 resampler, as detailed in this blog post.

A comparison of Visible and Shortwave Infrared images from GOES-17 and GOES-15 (below) highlighted the improved fire detection and monitoring capability of the new GOES-R series. The higher spatial resolution (0.5 km vs 1.0 km at nadir for Visible, and 2 km vs 4 km at nadir for Shortwave Infrared) and more frequent image scans (10 minutes for GOES-17 Full Disk vs 15-30 minutes for GOES-15 CONUS sector) along with better Image Navigation and Registration (INR) were especially valuable at the higher latitudes of Alaska. For example, the subtle behavior of the fire’s smoke column vertical jump at 2350 UTC was only apparent in the GOES-17 Visible imagery.

Since the fire was also located within the GOES-17 Mesoscale Domain Sector #2, 1-minute imagery provided an even better depiction of the fire’s smoke column vertical jump and downstream smoke transport (below).

View only this post Read Less

GOES-R Advanced Baseline Imagery (ABI) detections must be interpolated from the detector grid on the satellite to a grid that is fixed and geographically referenced. This is accomplished by applying a truncated sinc function in both north-south and east-west directions to the data on the detector grid. Sinc functions include small negative tails adjacent to the large central maximum; for fifteen out of sixteen ABI bands, those subtractions are not detectable. For Band 7, however, the shortwave infrared band at 3.9 µm, the ABI band with the largest dynamic range (and 14 bits of information), the interpolation from detector space to the fixed grid pixel can introduce negative values of radiances and careful observers have seen Cold Pixels Around Fires, the so-called CPAF effect.

An improved interpolation for Band 7 only has been implemented (on 23 April for GOES-16 and on 18 April for GOES-17) in the GOES-R Ground System that reduces the negative tail in the Truncated Sinc function. In the single image above, from GOES-17 at 23:30 UTC on 17 February, the “old” truncated sinc function (denoted ‘Original’ in the image) has generated a falsely cold pixel — white in the greyscale enhancement — off the southeast corner of the warm pixels shown in black.  The cold pixels are not present when the new, improved interpolation scheme is used. Note, however, that the Data Max annotated in the image has cooled by 2K with the improved interpolation;  a fire is nevertheless obvious.

Consider the animation below, for example, (from this blog post on the Cranston fire), that used the ‘old’ interpolation scheme.  Cold pixels (in white) occasionally appear around the periphery the fire (in red) in the center of the image. The new interpolation means that such cold pixels will no longer appear in the data.

The image below shows a fire at 1641 UTC on 29 April 2019, after the CPAF change was implemented into the GOES-R Ground System (two different enhancements are shown). No artificial cold pixels are present. The hottest pixel is 405 K, which would have produced a CPAF under the original truncated sinc kernel.

View only this post Read Less