Devin,
I've noticed this since we first started getting the imagery back in April. The
problem is that the ABI instrument returns reflectance values that are greater
than 1 (up to 1.25 or so) but the processing software that remaps the images
and sends out over NOAAPort is currently clipping them at 1 and assigning any
higher values a missing/out of range value (which unfortunately is zero)
My quick and dirty solution is replacing all 0 values in the image with 1's,
since I'd rather see white in the middle of storms, at the expense of the dark
(night) areas being white. The only time it really ended up being an issue was
with the total eclipse, which progressed across the country in brilliant white
on my images.
Supposedly this was going to be fixed in July, but so far it has not. Someday
hopefully.
Pete
<http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>--
Pete Pokrandt - Systems Programmer
UW-Madison Dept of Atmospheric and Oceanic Sciences
608-262-3086 - poker@xxxxxxxxxxxx
________________________________
From: ldm-users-bounces@xxxxxxxxxxxxxxxx <ldm-users-bounces@xxxxxxxxxxxxxxxx>
on behalf of Devin Eyre <Devin.Eyre@xxxxxxxxxxxx>
Sent: Monday, October 2, 2017 9:56 AM
To: ldm-users@xxxxxxxxxxxxxxxx
Subject: [ldm-users] no-data values in GOES-16 in visible imagery
I have seen that there are frequently no-data values in the middle of
high-reflectivity areas in the visible imagery. How are you dealing with this
when creating graphics?
