20040629: DGEX.

DGEX is model 115, transmitted on GRIB 185 (eg grid designator "E")
from KWBD.

The GRIB2 format does not provide the "185" grid number unlike GRIB1,
so if other domains are used, it will likely need a pqact pattern
matching on the A(1) (of TTAAii) and an explicit file name. But
the following will be the generic entries.
! DGEX
007   x   115       185    data/gempak/model/dgex/YYYYMMDDHHfFFF_dgex.gem  1000
007   x   115       @@@    data/gempak/model/dgex/YYYYMMDDHHfFFF_dgex.gem  1000

I have found that the grib2 decoding can barf if the dvbs feed is garbled, so
have put extra checks in the g2_info return block in dcgrib2.

I plan on putting the grib2 eta218 and dgex into individual FFF files
and using the config/datatype.tbl entry to match, otherwise,
these files get big (and the .5 degree AVN as well) and harder to
work with.

Steve Chiswell
Unidata User Support




>From: Stonie Cooper <address@hidden>
>Organization: Planetary Data, Incorporated
>Keywords: 200406291221.i5TCLtWb029790

>Steve,
>
>Welcome back . . . hope it was a vacation and not something work related.
>
>Do you happen to have DGEX entries for gribkey.tbl based on the new data on 
>the DVB-S segment of NOAAPort?  Wes's wgrib is not setup for JPEG2000 GRIB2, 
>yet, so it would take a code effort to decode the PDS and figure out where 
>the data should go.  I also noticed that some of the fields are not 
>referenced in the various grid tables when I run dcgrib2 by hand on the data. 
>  
>Just curious - trying to save doing rework if someone there had already done 
>the work.
>-- 
>Stonie R. Cooper
>Planetary Data, Incorporated
>(402) 727-6599
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.