NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

Re: [conduit] problems with NAM 104/255 CONDUIT files

Hi David,
I checked the contents of the GRIB2 file at NCEP and everything looks ok. I then converted it back to GRIB1 format using our converter (non Unidata) and the resulting data look find for PMSL as well. There are two records for PMSL right at the beginning of this file. The first record is the NAM (or Eta) model reduction (GRIB1 ID=130). The second record is the traditional reduction (GRIB1 ID=2). Are you having problems with both of these? 

Brent

David Ovens wrote:

CONDUIT users and Gembuds,

As you know, the CONDUIT data feed recently dropped the NAM 104 grids
in GRIB1 format.  We are receiving the 90-km NAM grids in GRIB2 format
under the following pqact entry:

 CONDUIT          /nam\.t(..)z\.grbgrd.*grib2

Most everything looks fine; however, when I convert these files to
GEMPAK using dcgrib2 from 5.9.4, 5.10.3, or 5.10.4, the PMSL field is
all fouled up. The following URL shows what I get for a 'CINT=0' setting: http://www.atmos.washington.edu/~ovens/2007110600_badpmsl.gif 

Here's how I decoded the file:

 $GEMEXE/dcgrib2 -d - 2007110600_nam104.gem < \
 /home/disk/data/conduit/nam.20071106/nam.t00z.grbgrd00.tm00.grib2

I suspect this is a problem with the GRIB2 file (my first guess) or
the way GEMPAK is decoding the sea-level pressure field.

Does anyone have a fix for this yet?

Thanks,

David
  • 2007 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the conduit archives: