This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi John, Can you re-send the GDLIST input and output? The attached grid files isn't necessary, when your previous email came in the files were removed. I am looking over here for missing data -9999 or 0 values at the meridian but not seeing any. I am using the 1 degree GFS grib2 files from NCEP NOMADS ftp server to check. -Michael > We haven't heard back about this issue - any further assistance you can > provide? > > Thanks. > > John > > -----Original Message----- > From: John Manobianco [mailto:address@hidden] > Sent: Saturday, November 02, 2013 9:14 AM > To: 'address@hidden' > Subject: RE: [GEMPAK #ZTH-407575]: GEMPAK nagrib issue > > Michael, > > I tried this exercise using the same command on a recent GSF data set > (gdas.t00z.pgrbf00.grib2) with the following command > > dcgrib2 dummy.grd < gdas1.t00z.pgrbf00.grib2 > > However, I still get a missing column of data at the 0 deg meridian (figure > attached). > > I've also attached the GEMPAK file and the GDLIST output showing text data. > > Perhaps this issue is related to the compiler (ifort v11.1 ) and operating > system characteristics (uname -a) on the machine where I'm running GEMPAK. > > Linux ens00ib 2.6.18-371.1.2.el5 #1 SMP Tue Oct 22 12:51:53 EDT 2013 x86_64 > x86_64 x86_64 GNU/Linux > > Thanks. > > John > > -----Original Message----- > From: Unidata GEMPAK Support [mailto:address@hidden] > Sent: Friday, November 01, 2013 3:37 PM > To: address@hidden > Cc: address@hidden > Subject: [GEMPAK #ZTH-407575]: GEMPAK nagrib issue > > Hi John, > > For decoding grib 1 and 2 files, I always recommend using the program > "dcgrib2" rather than "nagrib". > > Unidata added dcgrib2 to the NAWIPS/GEMPAK package some years ago; it was > developed to be more robust than the NAGRIB program created by NCEP. > > I downloaded a 1.0 deg global GFS file and decoded it with the command > "dcgrib2 gfs.gem < gfs.t12z.pgrbf12.grib2" > > I then plotted the 500mb temperature field using > > GAREA = -21;-150;-21;30 > PROJ = STR/90;-105;0 > GDFILE = gfs.gem > GDATTIM = last > GLEVEL = 500 > GVCORD = pres > GDPFUN = tmpf > TYPE = f > FINT = 5 > FLINE = 30-7 > > This to confirm that when using dcgrib2 there are no missing data along the > boundaries. See attached image. > > > -Michael > > > > Good Morning, > > > > I am using nagrib (v.6.8.0) to decode GFS 1 x 1 deg global data (360x181) . > > The settings are as follows > > > > GBFILE = avn.2012102300f00.grib2 > > > > INDXFL = > > > > GDOUTF = dummy.grd > > > > PROJ = > > > > GRDAREA = > > > > KXKY = > > > > MAXGRD = 3000 > > > > CPYFIL = #3 > > > > GAREA = > > > > OUTPUT = f > > > > GBTBLS = wmogrib2.tbl;ncepgrib2.tbl;vcrdgrib1.tbl;cntrgrib2.tbl > > > > GBDIAG = > > > > PDSEXT = no > > > > OVERWR = no > > > > > > The resulting GEMPAK file has missing values along the 0 meridian > > (from -90N to 90N) but is fine everywhere else (example attached). > > > > With nagrid, it doesn’t matter which field I look at as they all have > > this issue (which also shows up using GDLIST). > > > > nagrid will not write the grids to a GEMPAK file using any other > > setting except CPYFIL=#3 (for example CPYFIL=GDS, GAREA=GRID). > > > > Thanks. > > > > John Manobianco > > > > John Manobianco > > Vice President/Business Development > > > > MESO, Inc. > > > > 185 Jordan Road > > > > Troy, NY 12180-7611 > > > > (518) 283-5169 > > > > address@hidden > > > > http://www.meso.com > > > > > > Good Morning, > > > > I am using nagrib (v.6.8.0) to decode GFS 1 x 1 deg global data (360x181) . > > The settings are as follows > > > > GBFILE = avn.2012102300f00.grib2 > > > > INDXFL = > > > > GDOUTF = dummy.grd > > > > PROJ = > > > > GRDAREA = > > > > KXKY = > > > > MAXGRD = 3000 > > > > CPYFIL = #3 > > > > GAREA = > > > > OUTPUT = f > > > > GBTBLS = wmogrib2.tbl;ncepgrib2.tbl;vcrdgrib1.tbl;cntrgrib2.tbl > > > > GBDIAG = > > > > PDSEXT = no > > > > OVERWR = no > > > > > > The resulting GEMPAK file has missing values along the 0 meridian > > (from -90N to 90N) but is fine everywhere else (example attached). > > > > With nagrid, it doesn’t matter which field I look at as they all have > > this issue (which also shows up using GDLIST). > > > > nagrid will not write the grids to a GEMPAK file using any other > > setting except CPYFIL=#3 (for example CPYFIL=GDS, GAREA=GRID). > > > > Thanks. > > > > John Manobianco > > > > John Manobianco > > Vice President/Business Development > > > > MESO, Inc. > > > > 185 Jordan Road > > > > Troy, NY 12180-7611 > > > > (518) 283-5169 > > > > address@hidden > > > > http://www.meso.com > > > > > > Ticket Details > =================== > Ticket ID: ZTH-407575 > Department: Support GEMPAK > Priority: Normal > Status: Open > > Ticket Details =================== Ticket ID: ZTH-407575 Department: Support GEMPAK Priority: Normal Status: Open