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.
Brian, The Lambert projection code is part of the GEMPAK libraries, and not specific to dcgrib2. The routine is $GEMPAK/source/gemlib/gb/gblamb.c which is available in the source code distribution. The dcgrib2 program is in the source distribution under $NAWIPS/unidata/ldmbridge/dcgrib2. If you want to send me a single (or small) example of your grib, I can pass it through the debugger and see where things are getting fouled. Steve Chiswell Unidata User Support >From: Brian Jamison <address@hidden> >Organization: UCAR/Unidata >Keywords: 200412031643.iB3GhWlI024668 >Hi Steve, > >> Brian, >> >> Since this is not grid #252, that value should be set to 255 >> just for correctness, but since the dcgrib2 decoder will use the GDS >> when present, that shouldn't be your problem here. >> >> One possibility is that the Lo1 angle is not in the range 0 to 360, >> eg your wgrib output shows 520. Can you change this to a more >> conventional 260? That way, the (Lo1 - Lov) difference in >> computing the upper right point should be in the correct distance. > >I don't know of an easy way to "edit" a grib file to change this >value. I wasn't the person that created these grib files, so it's >not easy for me to re-create them with this change, either. > >Would it be possible to get the code for creating the dcgrib2 >executable, so I can make the changes to handle the 520 >value? > > >Brian > > -- NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.