[conduit] [CONDUIT #MWI-895819]: LDM CONDUIT gfs sfluxgrb files

Hello everyone,

Per the response below from Unidata User Support, I would like to ask the 
community if there would be any objections to adding the new sfluxgrb files to 
the CONDUIT LDM feed? After the GFS data change, we (DRI) needs both the pgrb2 
and sfluxgrb files in order to perform our WRF runs. It would be preferred by 
all in our group to continue using the LDM system, which is great, to acquire 
all of the necessary data instead of relying on wget scripts. Please respond 
back to this with any questions or concerns you may have and hopefully this 
additional data can be added.

Thanks

Matthew R. Sgambati
HPC and Visualization Systems Analyst
Desert Research Institute
2215 Raggio Parkway
Reno, NV 89512
Phone: +1-775-673-7662
Email: Matthew.Sgambati@xxxxxxx

-----Original Message-----
From: Unidata CONDUIT Support [mailto:support-conduit@xxxxxxxxxxxxxxxx]
Sent: Monday, August 7, 2017 9:44 AM
To: Matthew Sgambati <Matthew.Sgambati@xxxxxxx>
Cc: Matthew Sgambati <Matthew.Sgambati@xxxxxxx>; 
support-conduit@xxxxxxxxxxxxxxxx
Subject: [CONDUIT #MWI-895819]: LDM CONDUIT gfs sfluxgrb files

Hi Matthew,


...

> I was wondering if/when the gfs sfluxgrb files
> (gfs.t12z.sfluxgrbf00.grib2, etc) are going to be added to CONDUIT?
>
> We can get them through the ftp site
>
> ftp://ftp.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/gfs.2017072112
>
> but would prefer to use ldm with CONDUIT.

New content is added to CONDUIT when there is solid support for that content 
from the CONDUIT using community.  Adding or removing content to CONDUIT is not 
something that we can do unilaterally as NOAA/NCEP is actually in charge of the 
processes that create the content.

I think that the best course of action is for your to send out an email to the 
conduit@xxxxxxxxxxxxxxxx email list voicing your desire for the addition of the 
sfluxgrb products to the data stream and asking other CONDUIT users if they 
support this addition.  If there is widespread support for the addition, we can 
work with NCEP to get the addition into the pipeline.

...

Cheers,

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


Ticket Details
===================
Ticket ID: MWI-895819
Department: Support CONDUIT
Priority: Urgent
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.



PUBLIC RECORDS NOTICE: In accordance with NRS Chapter 239, this email and 
responses, unless otherwise made confidential by law, may be subject to the 
Nevada Public Records laws and may be disclosed to the public upon request.
  • 2017 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the conduit archives: