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

20040622: Gempak - Linux - ECMWF Grib Tables

Ron,

The attatchment of table128 parameters did not come through.
I'd welcome it if you have it. I don't have any un-free ECMWF data
(the very limited parameters I have are all parameter numbers <128,
so referenced from the WMO table).

Steve Chiswell
Unidata User Support


>From: "Ron McTaggart-Cowan" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200406222142.i5MLgPsY020872

>--=_d56a6177918d39bc0f579b72cb09fc6a
>Content-Type: text/plain; charset="ISO-8859-1"
>Content-Transfer-Encoding: 7bit
>
>Institution: SUNY Albany Earth and Atmospheric Sciences
>Package Version: current
>Operating System: Linux
>Hardware Information: n/a
>Inquiry: hi - we ran into some minor trouble decoding ERA40 data to GEMPAK fil
> es ... it seems that the parameter/unit mapping table for V128 of the ECMWF G
> rib Table 2 ($GEMTBL/grid/ecmwfgrib128.tbl) is a direct copy of the NCEP V2 t
> able (ncepgrib2.tbl) which doesn't map particularly well to the ECMWF gribbin
> g conventions.
>
>We took the Grib information directly from the ECMWF Grib description and made
>  a new version of the ecmwfgrib128.tbl which seems to properly convert the ER
> A data.  I've included a copy of the table file.  I tried to stick, as much a
> s possible, to the naming conventions that I found in the other GEMPAK table 
> files.  If I'm not way off base on the problem and if you find the new table 
> file acceptable, it would be handy to have it in future versions of GEMPAK to
>  ease the decoding of std format ECMWF data.
>ron
>
>
>--=_d56a6177918d39bc0f579b72cb09fc6a
>Content-Type: application/octet-stream
>Content-Transfer-Encoding: base64
>Content-Disposition: attachment; filename="ecmwfgrib128.tbl"
>
>
>--=_d56a6177918d39bc0f579b72cb09fc6a--
>
--
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.