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

[CONDUIT #RLV-675697]: [! INFO !] Conduit Data Feed

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: [CONDUIT #RLV-675697]: [! INFO !] Conduit Data Feed
  • Date: Tue, 30 Nov 2010 17:04:51 -0700
Hi Paul,

re:
> I had a question about the Conduit Data Feed.  Are we (NWS) allowed to
> subscribe to the Conduit Data feed from NCEP?

If your question is if you can subscribe to the CONDUIT feed from the
top level redistribution sites at the WOC, then I honestly don't know.
You should contact Becky Cosgrove or the NCEP Data Flow team and
ask them directly:

Rebecca Cosgrove <address@hidden>
address@hidden

If, on the other hand, you are asking if you can subscribe to the CONDUIT
feed from a site in the Unidata IDD, then the answer is yes, this can be
arranged.

re:
> If so, what would be needed
> to get this setup for us to begin ingesting the Conduit Data Feed.

In any case, you would need to do the following:

- setup an account on a *nix (Unix/Linux) machine in which you would
  run the LDM.  By convention this would be the user 'ldm'.

- register with the Unidata website: http://www.unidata.ucar.edu

- download the current version of the LDM from our website (v6.8.1)
  to the HOME directory of the LDM

- unpack, build, and install the LDM in the 'ldm' account

- edit the ~ldm/etc/ldmd.conf file to add the appropriate REQUEST lines
  for the CONDUIT data.  We recommend a five-way split request to maximize
  the transfer of the data to your machine.

  For instance, here are example request lines for the Silver Springs and
  Boulder WOC machines for all CONDUIT products:

# CONDUIT from SSMC (Silver Springs WOC)
request CONDUIT "[09]$" ncepldm1.woc.noaa.gov
request CONDUIT "[18]$" ncepldm1.woc.noaa.gov
request CONDUIT "[27]$" ncepldm1.woc.noaa.gov
request CONDUIT "[36]$" ncepldm1.woc.noaa.gov
request CONDUIT "[45]$" ncepldm1.woc.noaa.gov

  -- OR --

# CONDUIT from Boulder WOC
request CONDUIT "[09]$" ncepldm4.woc.noaa.gov
request CONDUIT "[18]$" ncepldm4.woc.noaa.gov
request CONDUIT "[27]$" ncepldm4.woc.noaa.gov
request CONDUIT "[36]$" ncepldm4.woc.noaa.gov
request CONDUIT "[45]$" ncepldm4.woc.noaa.gov

  If you end up feeding from a machine in the Unidata IDD, then you
  would replace the machine name in the actions above with the one
  that is setup to allow you to request the data (we will provide
  you with the name of the machine to feed from if you can not
  feed from one of the WOC locations).

re:
> Thank you for your time and great service.

No worries.

Please keep us informed about your interactions with Becky and/or the
NCEP Data Flow team.

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: RLV-675697
Department: Support CONDUIT
Priority: Normal
Status: Closed