It sounds like there are different grids included in this that have different
spacing. If you give it a name for the gempak files that include the grid,
such as data/gempak/model/navgem/YYYYMMDDHH_@@@.gem, the @@@ will be replaced
by the grid number, and you should get all of them decoded.
________________________________
From: gembud-bounces@xxxxxxxxxxxxxxxx <gembud-bounces@xxxxxxxxxxxxxxxx> on
behalf of Smith, Neil R <n-smith2@xxxxxxxxxxxxx>
Sent: Wednesday, March 2, 2016 9:49 AM
To: gembud
Subject: Re: [gembud] navgem in GEMPAK7
Is no one plotting the navgem?
Anyone remember what the incompatible navigation issue is about?
On Feb 29, 2016, at 5:20 PM, Smith, Neil R
<n-smith2@xxxxxxxxxxxxx<mailto:n-smith2@xxxxxxxxxxxxx>> wrote:
What's the key to ingesting navgem?
I'm using
FNMOC (^US058.{4}-GR1mdl\.0018_0056_.{5}.{4})(.{4})(.{6})(.*)
PIPE /unidata/ldm/decoders/dcgrib2 -d
data/gempak/logs/dcgrib2_navgem.log
-e GEMTBL=/unidata/gempak/NAWIPS/gempak/tables
but getting screwy plotting results, and ingest log file entries like
160229/1637[DCGRIB 1] Grid navigation 56 incompatible with file
data/gempak/model/fnmoc/navgem/2016022918f045_navgem.gem
This is GEMPAK7 and ldm 6.12.5
-Neil
_______________________________________________
gembud mailing list
gembud@xxxxxxxxxxxxxxxx<mailto:gembud@xxxxxxxxxxxxxxxx>
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
