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.
Seth, I looked for the web address you listed below, but no file pgbexample.zip exists. I found your home directory, but it only comtained: Index of /sethmcdoogle Name Last modified Size Description Parent Directory 17-Jan-2001 23:29 - MSDN.gif 19-Oct-2003 12:17 11k SteamValve.jpg 18-Oct-2003 22:22 13k Win32Ed.zip 26-Jan-2003 18:21 5k buttons.zip 10-Mar-2003 23:36 2k exploit.gif 11-Sep-2003 23:57 23k googler.zip 17-Nov-2002 11:24 2k latexperl.zip 16-Oct-2003 21:21 1k notepad_bug.gif 10-Oct-2003 23:53 25k splitter.zip 03-Dec-2002 11:42 2k ymlitecrack.zip 06-Jun-2002 13:56 3k From what you do show however, this is grid #002, a 2.5x2.5 degree global grid, so you should be able to use CPYFIL=#002. The GDS block is omitted from the GRIB (which is really a travestry), so the NAGRIB program cannot create the navigation using CPYFIL=GDS. The location of the GRID projection definition is: > PDS byte 7 (pds.grid_id) = 2 GEMPAK will use #002 from the table $GEMTBL/grdnav.tbl to create the gempak file for the 144x73 CED global grid. See if this gets you going, otherwise, try to repost the data file and I'll download it. Steve Chiswell Unidata User Support >From: "Seth O McDowell" <address@hidden> >Organization: UCAR/Unidata >Keywords: 200310201847.h9KIlMOb021670 >Thanks for the previous help. After running with GDOUTF=list to verify paramet > ers, it still was unsuccessful. Here's GBDIAG=all for an entry in the file. W > hen running with GDOUTF=list, there was no indication as to what projection t > o use? In the diagnostic output, the projection flag is 0, it seems. Maybe it > is a problem with the specified projection and/or latitude & longitude coord > inates? We are not able to tell where the problem is. Any further assistance > you could give would be much appreciated. > >Seth > >Here's a file from the dataset we are trying to use. >http://geocities.com/sethmcdoogle/pgbexample.zip > > 139 2 33 107 691031/1800F000 9950 SGMA UREL > IDS bytes 0 - 4 (GRIB msg id) = GRIB > IDS bytes 5 - 7 (ids.msg_length) = 11910 > IDS byte 8 (ids.edition) = 1 > PDS bytes 1- 3 (pds.length) = 28 > PDS byte 4 (pds.version) = 2 > PDS byte 5 (pds.center) = 7 > PDS byte 6 (pds.process) = 80 > PDS byte 7 (pds.grid_id) = 2 > PDS byte 8 (pds.flag) = 128 > PDS byte 9 (pds.parameter) = 34 > PDS byte 10 (pds.vcoord) = 107 > PDS bytes 11 (pds.level_1) = 38 > PDS bytes 12 (pds.level_2) = 222 > PDS bytes 11-12 (pds.level) = 9950 > PDS byte 13 (pds.year) = 69 > PDS byte 14 (pds.month) = 10 > PDS byte 15 (pds.day) = 31 > PDS byte 16 (pds.hour) = 18 > PDS byte 17 (pds.minute) = 0 > PDS byte 18 (pds.time_unit) = 1 > PDS byte 19 (pds.time_p1) = 0 > PDS byte 20 (pds.time_p2) = 0 > PDS byte 21 (pds.time_range) = 10 > PDS bytes 22-23 (pds.avg_num) = 0 > PDS byte 24 (pds.avg_miss) = 0 > PDS byte 25 (pds.century) = 20 > PDS byte 26 (pds.izero) = 1 > PDS bytes 27-28 (pds.dec_scale) = 1 > PDS EXT FLAG (1-app,0-nc,-1-rep) = 0 > PDS EXT STRING = > GDS bytes 1 - 3 (gds.length) = 32 > GDS byte 4 (gds.NV) = 0 > GDS byte 5 (gds.PV) = 255 > GDS byte 6 (gds.grid_proj) = 0 > GDS bytes 7 - 8 (Nx) = 144 > GDS bytes 9 - 10 (Ny) = 73 > GDS bytes 11 - 13 (La1) = 90000 > GDS bytes 14 - 16 (Lo1) = 0 > GDS byte 17 (flag) = 128 > GDS bytes 18 - 20 (La2) = -90000 > GDS bytes 21 - 23 (Lo2) = -2500 > GDS bytes 24 - 25 (skipped) > GDS bytes 26 - 27 (skipped) > GDS byte 28 (mode) = 0 > GDS bytes 29 - 32 (skipped) > GDS bytes 33 - 35 (skipped) > GDS bytes 36 - 38 (skipped) > GDS byte 39 (skipped) > GDS bytes 40 - 42 (skipped) > GDS bytes 43 - 45 (skipped) > GDS bytes 46 - 48 (skipped) > GDS byte 49 (skipped) > GDS bytes 50 - 52 (skipped) >