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

Re: 20061018: Changes to CONDUIT data stream

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: Re: 20061018: Changes to CONDUIT data stream
  • Date: Fri, 20 Oct 2006 11:17:52 -0600
Tyler,

The GRIB2 files will have '#000' as the grid number in the data
themselves rather than #252 as the GRIB1 data do.

The bottom of the web page you mention below showes an example pattern
for all GRIB2 RUC (which are the 20km files) as "prod/ruc2a.*grib2".


Steve Chiswell
Unidata User Support

On Fri, 2006-10-20 at 13:01 -0400, Tyler Allison wrote:
> > http://www.unidata.ucar.edu/data/conduit/ldm_idd/ruc2_files.html
> 
> According to the above file it looks like I should be able to grab ruc
> #252 grib2 files with the following ldmd.conf line:
> 
> request CONDUIT "(grib2.*#252)" [ldm server]
> 
> yet I don't see any grib2 data.
> 
> if I change the line to:
> 
> request CONDUIT "(grib.*#252)" [ldm server]
> 
> I would presume that I would see grib1 and grib2 data...I see grib1 coming
> through...but not grib2.
> 
> Did I do something wrong?
> 
> -Tyler
> 
> 
> 
> 
> ===============================================================================
> To unsubscribe conduit, visit:
> http://www.unidata.ucar.edu/mailing-list-delete-form.html
> ===============================================================================
-- 
Steve Chiswell <address@hidden>
Unidata