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

[CONDUIT #UDU-273265]: CONDUIT data.

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 #UDU-273265]: CONDUIT data.
  • Date: Mon, 28 Apr 2008 17:37:20 -0600
Hi again Carlos,

I have it on expert authority that:

  The grib2 version of data always labels the grids #000 as that is the
  designation in the data that the grid is self describing. There is no 
provision
  in grib2  for both a grid number and a section 3 definition (unlike grib1).

  So, Carlos will have to use  #000, or wildcard that section.

At the bottom of the CONDUIT web page:
http://www.unidata.ucar.edu/data/conduit/ldm_idd/gfs_files.html

is:

LDM patterns for selected processing

 ...

# Pipe all GFS Grid #002/#003 to decoder (note includes new NCEP file NAMES)
CONDUIT (ST.opnl/MT.gfs|prod/gfs.*pgrb[^2])
        PIPE    decoder
 ...

You should follow this example to process the grid 3 grids.



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