Re: [gembud] C009 added to parameter name in .gem files

• To: "Patrick L. Francis" <wxprofessor@xxxxxxxxx>, "gembud@xxxxxxxxxxxxxxxx" <gembud@xxxxxxxxxxxxxxxx>
• Subject: Re: [gembud] C009 added to parameter name in .gem files
• From: Devin Eyre <Devin.Eyre@xxxxxxxxxxxx>
• Date: Mon, 30 Mar 2020 18:52:58 +0000

Robert Mullenax answered my question.  To get rid of them, I had to add ‘-e 
ENSEXT=0’ to the command line.

From: Patrick L. Francis <wxprofessor@xxxxxxxxx>
Sent: Monday, March 30, 2020 1:51 PM
To: Devin Eyre <Devin.Eyre@xxxxxxxxxxxx>; gembud@xxxxxxxxxxxxxxxx
Subject: Re: [gembud] C009 added to parameter name in .gem files


you might want to take a look at your table files found under:

$GEMTBL/grid/[XXXX].tbl

you may also find this information useful :) :
https://www.unidata.ucar.edu/software/gempak/man/prog/dcgrib2.html


cheers,

--patrick


------ Original Message ------
From: "Devin Eyre" <Devin.Eyre@xxxxxxxxxxxx<mailto:Devin.Eyre@xxxxxxxxxxxx>>
To: "gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>" 
<gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>>
Sent: 3/30/2020 8:55:45 AM
Subject: [gembud] C009 added to parameter name in .gem files

When decoding some ECMWF grib files using dcgrib2, it's adding "C009" after the 
parameter name.  For example, TMPK becomes TMPKC009.  I can rename them back to 
what they should be using gddiag, but I was wondering if it's some field in the 
grib message that can be fixed using grib_set prior to running it through 
dcgrib2.

• References:
  • [gembud] C009 added to parameter name in .gem files
    • From: Devin Eyre
  • Re: [gembud] C009 added to parameter name in .gem files
    • From: Patrick L. Francis