Charley,
Make sure you are decoding using the dcgrib2 program from 5.9.4 and not 5.7.3.
As I mentioned before, NCEP changed one byte of the grib headers that changed
the F000 meaning to an analysis time - so the 5.7.3 version would be decoding
these initial times as YYMMDD/HHNN rather than YYMMDD/HHNNf000.
You should be able to see the grid times in the file if you fill out the
entries in gdinfo rather than leaving blank.
Try
GDATTIM = fall
GLEVEL = all
GVCORD = all
GFUNC = all
or:
at the gdinfo prompt type: restore defaults/gdinfo
Steve Chiswell
Unidata User Support
On Mon, 2007-02-19 at 15:48 -0800, Charley Knoderer wrote:
Hi,
Here's the listing I get off of gdinfo:
GEMPAK-GDINFO>l
GDFILE = 07021918_nam_212.gem
LSTALL = YES
OUTPUT
GDATTIM = all
GLEVEL
GVCORD
GFUNC
GEMPAK-GDINFO>r
GRID FILE: 07021918_nam_212.gem
GRID NAVIGATION:
PROJECTION: LCC
ANGLES: 25.0 -95.0 25.0
GRID SIZE: 185 129
LL CORNER: 12.19 -133.46
UR CORNER: 57.29 -49.39
GRID ANALYSIS BLOCK:
ANALYSIS TYPE: BARNES
DELTAN: 4.000
DELTAX: -9999.000
DELTAY: -9999.000
GRID AREA: 11.00 -154.00 62.00 -48.00
EXTEND AREA: 11.00 -154.00 62.00 -48.00
DATA AREA: 11.00 -154.00 62.00 -48.00
Number of grids in file: 9210
Maximum number of grids in file: 29999
[GDU 2] Did not find any matching grids.
Parameters requested: GDFILE,LSTALL,OUTPUT,GDATTIM,GLEVEL,GVCORD,GFUNC.
To add further confusion to the matter, we have one machine running
gempak 5.7.3 and it displays the first time period in nmap, but only the
first time period. On a separate machine, we are running gempak 5.9.4
and reading the decoded grib from 5.7.3 and nmap will not read these
files at all.
Any suggestions?
Thanks,
Charley
