[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[McIDAS #CBV-672560]: GOES-18 operational on January 4 at 18Z: Implications for McIDAS

Hi Gilbert,

re:
> So, they used the GOES-18 headers and product ID's (and not GOES-17)
> when they sent it out? 

Since McIDAS doesn't care about the NOAAPort broadcast headers or
LDM/IDD Product IDs, it only needs to understand the information in
the netCDF4 files.  This is true for the L1b image that come from the
GRB and the L2 images that are sent in NOAAPort.  Minor tweaks to
McIDAS code were implemented many months ago that allowed GOES-18 AND
GOES-19 imagery to be recognized (sensor sources, etc.), and we and
you (COD) have been running that code for months.

re:
> Cool. So, I am good. Thanks!

Again, Mike Z knows what he did at the beginning of the GOES-18 interleave
testing to make things work at COD, and I _think_ that whatever changes
he made were eventually superfluous with newer versions of McIDAS-X.
Mike will, of course, know for sure, so it wouldn't hurt to touch
base with him on this!

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: CBV-672560
Department: Support McIDAS
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.