Just incase anyone isn’t aware, you can get the untiled netcdf files from
Amazon, Google or OCC. These files also don’t appear to have the black pixel
problem. Not as sexy as LDM but a better solution for most folks :)
AWS: https://aws.amazon.com/public-datasets/goes/
<https://aws.amazon.com/public-datasets/goes/>
Google:
https://console.cloud.google.com/storage/browser/gcp-public-data-goes-16
<https://console.cloud.google.com/storage/browser/gcp-public-data-goes-16>
or OCC where we have some more info on working with the data too:
http://edc.occ-data.org/goes16/ <http://edc.occ-data.org/goes16/>
Cheers,
Zac
> On Nov 1, 2017, at 12:30 PM, Daniel Vietor - NOAA Affiliate
> <dan.vietor@xxxxxxxx> wrote:
>
> I've noticed this as well. It was really bad over the weekend. The tiles
> seem to eventually come in but sometimes two hours after the image time. If
> you timeout on compositing the tiles, you end up with a fair number of blank
> areas in the image.
>
> Dan.
>
> On Wed, Nov 1, 2017 at 10:52 AM, Mike Zuranski <zuranski@xxxxxxxxxxxxxxx
> <mailto:zuranski@xxxxxxxxxxxxxxx>> wrote:
> Looks like I did jump the gun and jinxed it. They just reverted these
> changes, scale_factor is back to what is was and the black pixel
> problem has returned.
>
> I get it, non-operational and what have you. Looks like they're still
> changing things; I guess I'll take it as a good sign that it's finally
> being addressed and eventually it'll stay fixed.
>
> ======================
> Mike Zuranski
> Meteorology Support Analyst
> College of DuPage - Nexlab
> Weather.cod.edu <http://weather.cod.edu/>
> ======================
>
>
> On Tue, Oct 31, 2017 at 2:48 PM, Mike Zuranski <zuranski@xxxxxxxxxxxxxxx
> <mailto:zuranski@xxxxxxxxxxxxxxx>> wrote:
> > I hope I'm not jumping the gun too much here, but it appears the black
> > pixel problem has finally been resolved! Watching a loop of visible
> > imagery just now, I noticed a slight change taking place at 17Z today,
> > including a tweak to the scale and no more black pixels. Upon further
> > inspection, the netCDF variable Sectorized_CMI:scale_factor changed
> > from 0.0002442 to 0.00031746 at that time.
> >
> > I'm noticing this change for bands 1, 2 and 3. This also makes the
> > new valid range for the visible bands 0.0 to 1.3.
> >
> > Hooray!!
> >
> > -Mike
> >
> > ======================
> > Mike Zuranski
> > Meteorology Support Analyst
> > College of DuPage - Nexlab
> > Weather.cod.edu <http://weather.cod.edu/>
> > ======================
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx <mailto:ldm-users@xxxxxxxxxxxxxxxx>
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
> <http://www.unidata.ucar.edu/mailing_lists/>
>
>
>
>
> --
> Dan Vietor
> Senior Research Meteorologist
> CIRA, Colorado State Univ
> Aviation Weather Center
> Kansas City, MO
> 816.584.7211
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
