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

[IDD #TVO-907725]: UNIWISC ingest stopped working

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: [IDD #TVO-907725]: UNIWISC ingest stopped working
  • Date: Thu, 12 Mar 2020 09:09:09 -0600
Hi,

re:
> Thanks Tom!
> Do I need any REQUEST in the ldm.conf if I we want to get it via noaaport?

The UNIWISC (aka MCIDAS) IDD feed is _not_ in the NOAAPort SBN, it is
a datastream that we create here in Unidata.  I figured that you knew
this since the actions you sent along previously are for the MCIDAS
(more properly named UNIWISC) IDD feed.  Assuming you are receiving
the UNIWISC feed, all you need to do is make sure that you are receiving
all of the feed and update your LDM pattern-action file to include the
actions needed to process the new GOES-16/17 imagery.

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: TVO-907725
Department: Support IDD
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.