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

[McIDAS #TVR-927190]: GOES-16 ADDE Data Access

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [McIDAS #TVR-927190]: GOES-16 ADDE Data Access
  • Date: Mon, 18 Sep 2017 11:28:46 -0600
Hi Fred,

er:
> Yes, I will agree to not publishing the images or basing any decisions on the 
> data.

Very good.

re:
> I am concerned about getting the software ready for the November operational 
> date.
> I plan to initially just get the current products transitioned to the GOES-16 
> data
> format.  Then we will experiment with increasing the space and time 
> resolution to
> see how our system will stand up to the increased communications speeds, data 
> storage
> requirements, and data processing requirements.

I understand.

re:
> NESDIS is planning a suite of new products from GOES-16.  Do you know how 
> these
> will be made available (NESDIS server, NOAAport, or relayed through UNIDATA)?

A set of Level 2 products are already flowing in NOAAPort, and we are
relaying them in the LDM/IDD NOTHER feed.

Comments:

I have been developing an ADDE server for the ABI images that are being
sent in NOAAPort, but I suspended development to see what the effects
of the current test (run by NOAA, not us) of not remapping most of the
sectors being sent (e.g., CONUS, Puerto Rico and Mesoscale-[12]) like
they have been doing.  What I saw on Friday after the unremapped images
started being sent convinced me that I needed to resume my ADDE development.

My previous examination of the format of the L2 products being sent in
NOAAPort strongly suggested that my new server would not be needed to
serve/use these L2 products; the core McIDAS v2017 ones should work.

As soon as I finish my ADDE server development for the NOAAPort delivered
ABI images, I will be releasing Unidata McIDAs-X v2017.  The other thing
that could delay this a bit is SSEC's intention of releasing an
addendum to their v2017 sometime very soon.

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: TVR-927190
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.