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.
Nilsson, GEMPAK does not handle the rotated lat/lon grid projection. It will decode the GRIB message, but the gbltln.c routine does not process any of the added navigation information from the stretching or rotation terms). The -12 message you are receiving I believe results from invalid navigation that results when trying to create the output grid file. Steve Chiswell Unidata User Support > Hi, > > I have a problem using Nagib on a grib file with a raotated lat/lon grid > (projection no 10): > > GEMPAK-NAGRIB>d > GBFILE GRIB data file name sw.grb > INDXFL GRIB index file name > GDOUTF Output grid file sw.grd > PROJ Map projection/angles/margins|dr > GRDAREA Area covered by grid > KXKY Number of grid points in x;y > MAXGRD Maximum number of grids 200 > CPYFIL Grid file whose navigation is to GDS > GAREA Graphics area > OUTPUT Output device/filename T > GBTBLS Input GRIB decoding tables > GBDIAG GRIB diagnostic elements > PDSEXT Y or N, add PDS extension if fou NO > OVERWR Overwr flag YES > GEMPAK-NAGRIB>r > Changing center table to cntrgrib1.tbl > Changing vertical coord table to vcrdgrib1.tbl > Changing WMO parameter table to wmogrib133.tbl > Changing center parameter table to smhigrib133.tbl > Creating the GEMPAK grid file... > [NAGRIB -12] Error creating GEMPAK grid file. > > > 0 GRIB messages were read or scanned from the GRIB file: > sw.grb > > > 0 grids were written to the GEMPAK file: > sw.grd > > > Parameters requested: > GBFILE,INDXFL,GDOUTF,PROJ,GRDAREA,KXKY,MAXGRD,CPYFIL, > GAREA,OUTPUT,GBTBLS,GBDIAG,PDSEXT,OVERWR. > > Running Nagrib with diagnostics shows: > > IDS bytes 0 - 4 (GRIB msg id) = GRIB > IDS bytes 5 - 7 (ids.msg_length) = 37112 > IDS byte 8 (ids.edition) = 1 > PDS bytes 1- 3 (pds.length) = 28 > PDS byte 4 (pds.version) = 133 > PDS byte 5 (pds.center) = 82 > PDS byte 6 (pds.process) = 130 > PDS byte 7 (pds.grid_id) = 255 > PDS byte 8 (pds.flag) = 192 > PDS byte 9 (pds.parameter) = 101 > PDS byte 10 (pds.vcoord) = 102 > PDS bytes 11 (pds.level_1) = 0 > PDS bytes 12 (pds.level_2) = 0 > PDS bytes 11-12 (pds.level) = 0 > PDS byte 13 (pds.year) = 6 > PDS byte 14 (pds.month) = 12 > PDS byte 15 (pds.day) = 21 > PDS byte 16 (pds.hour) = 6 > 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) = 0 > PDS bytes 22-23 (pds.avg_num) = 0 > PDS byte 24 (pds.avg_miss) = 0 > PDS byte 25 (pds.century) = 21 > PDS byte 26 (pds.izero) = 0 > PDS bytes 27-28 (pds.dec_scale) = 0 > PDS EXT FLAG (1-app,0-nc,-1-rep) = 0 > PDS EXT STRING = > GDS bytes 1 - 3 (gds.length) = 42 > GDS byte 4 (gds.NV) = 0 > GDS byte 5 (gds.PV) = 255 > GDS byte 6 (gds.grid_proj) = 10 > GDS bytes 7 - 8 (Nx) = 189 > GDS bytes 9 - 10 (Ny) = 199 > GDS bytes 11 - 13 (La1) = -8200 > GDS bytes 14 - 16 (Lo1) = 0 > GDS byte 17 (flag) = 128 > GDS bytes 18 - 20 (La2) = 11600 > GDS bytes 21 - 23 (Lo2) = 18800 > GDS bytes 24 - 25 (skipped) > GDS bytes 26 - 27 (skipped) > GDS byte 28 (mode) = 64 > 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) > > Any clue what the problem is? > > /Regards Bengt <<sw.grb>> > > Ticket Details =================== Ticket ID: BEM-969521 Department: Support GEMPAK Priority: Normal Status: Closed