Daryl,
The NGRID GRIB2 files being broadcast over NOAAport do not have a grid
number included within the data, so the default grid umber that dcgrib2
will use without a file name is 255 in a pattern @@@. However, I do
provide a set of GFS actions in the $NAWIPS/ldm/etc/templates directory
that provide individual actions with output names for the GFS grid2
sectors, rather than what you are using:
# GRIB2 GFS
# AWIPS grids
# Grid #212 CONUS 40km: ^[LM].R... KWBC
# Grid #160 Alaska 47.5km: ^[LM].G... KWBC
# Grid #254 Pacific 40km: ^[LM].O... KWBC
# Grid #161 Puerto Rico 0.5 degree: ^[LM].T... KWBC
NGRID ^[LM].R... KWBC
PIPE decoders/dcgrib2 -m 20000 -d
data/gempak/logs/dcgrib2_GFS2conus.log
-e GEMTBL=@GEMTBL@
data/gempak/model/gfs/YYYYMMDDHH_gfs212.gem
#
NGRID ^[LM].G... KWBC
PIPE decoders/dcgrib2 -m 20000 -d
data/gempak/logs/dcgrib2_GFS2alaska.log
-e GEMTBL=@GEMTBL@
data/gempak/model/gfs/YYYYMMDDHH_gfs160.gem
#
NGRID ^[LM].O... KWBC
PIPE decoders/dcgrib2 -m 20000 -d
data/gempak/logs/dcgrib2_GFS2pacific.log
-e GEMTBL=@GEMTBL@
data/gempak/model/gfs/YYYYMMDDHH_gfs254.gem
#
NGRID ^[LM].T... KWBC
PIPE decoders/dcgrib2 -m 20000 -d
data/gempak/logs/dcgrib2_GFS2puertorico.log
-e GEMTBL=@GEMTBL@
data/gempak/model/gfs/YYYYMMDDHH_gfs161.gem
Steve Chiswell
Unidata User Support
On Tue, 2007-01-09 at 12:22 -0600, Daryl Herzmann wrote:
Hi,
So I was poking around on my machine today looking at all the fancy GFS
data we graciously and reliably get via the IDD.
$ ls -l 2007010900*
-rw-rw-r-- 1 zmfritz student 3315716 Jan 8 22:08 2007010900_gfs201.gem
-rw-rw-r-- 1 zmfritz student 5135876 Jan 8 22:08 2007010900_gfs202.gem
-rw-rw-r-- 1 zmfritz student 3979268 Jan 8 22:08 2007010900_gfs203.gem
-rw-rw-r-- 1 zmfritz student 52307972 Jan 8 22:38 2007010900_gfs211.gem
-rw-rw-r-- 1 zmfritz student 25583108 Jan 8 22:15 2007010900_gfs213.gem
-rw-rw-r-- 1 zmfritz student 84425732 Jan 8 22:37 2007010900_gfs225.gem
-rw-rw-r-- 1 zmfritz student 417772548 Jan 8 22:40 2007010900_gfs255.gem
-rw-rw-r-- 1 zmfritz student 51909124 Jan 8 21:51 2007010900_thin.gem
All of these fancy files appear in my $GEMDATA/model/gfs after being
processed by GEMPAK5.9.4
Wow, that GFS255 file is big. "What's inside it?" I wondered. So I fire
up 'gdinfo'
GRID FILE: 2007010900_gfs255.gem
GRID NAVIGATION:
PROJECTION: STR
ANGLES: 90.0 -105.0 0.0
GRID SIZE: 65 65
LL CORNER: -20.83 -150.00
UR CORNER: -20.83 30.00
Hmmm, those corners look strange for latitude. So I poke at Garp_defaults
and datatype.tbl to attempt to get it in Garp. Ewwww, garp no likey
either.
So I wonder how the gfs255 file came to be. Ah, yes. dcgrib2 on my LDM
box with this entry:
HRS|NGRID ^.*
PIPE dcgrib2 -d data/gempak/logs/dcgrib2.log
-e GEMTBL=/home/gempak/nawips/gempak/tables
oooo, a log file! Looking at it, I see lots of messages like this.
[32020] 070109/1146[DECODE_GRIB2 -4] TMPK [070109/1200F066] 60:30 PDLY 137
102
[32020] 070109/1146[DCGRIB 1] Grid navigation 137.000000 102.000000 CED
incompatible with file data/gempak/model/gfs/2007010912_gfs255.
So I wonder some more :) I then asked The Google and he had very few hits
on "GFS 255". Anybody cure my puzzlement?
daryl
--
Steve Chiswell <chiz@xxxxxxxxxxxxxxxx>
Unidata
