NOAA / NWS's Meteorological Development Laboratory
Degrib (NDFD GRIB2 Decoder)
Subject: degrib version 0.90
Date: Thu, 12 Dec 2002 13:04:41 -0500
Organization: DOC/NOAA/NWS - National Weather Service
To: Arthur Taylor
You all have the unique distinction of being registered on my degrib
mailing list (all 8 of us) (I'd like to welcome rdale, rwb, and Clark
Safford to the list). Since you are a member, you get this email...
Please let me know if you want to unregister.
I have just finished version "0.90" (last one was "0.85" on 11/20/2002)
New to this release:
1) Moved the web site from 188.8.131.52/degrib/ to
2) Fixed a number of minor bugs, including a correction for the naming
3) Introduced a -Unit option which allows one to output the data in F
instead of K. Use "-Unit english" for F, Knots, inches, "-Unit metric"
for C, m/s, m. Use "-Unit none" to get no unit conversion... (Useful if
the people who packed it didn't actually store a temperature in K like
they are supposed to). The default is now "-Unit english"
4) Handled a major bug with the Windows version... For second order
differencing the FORTRAN code needs an automatic array on the order of
2.8 megs. However the code on a PC was compiled with 2 megs of stack
space. It crashes (only on the PC). After some dead ends I finally
realized that I could use the option "-Wl,--stack,4000000" in my
makefile to get gcc to grab 4 megs of stack space. The code works now.
The following currently only affects the command line version:
5) Added a "-msg all" or "-msg 0" option to convert all the messages in
6) Added a "-namePath" option to allow one to use the -nameStyle but
store the files in a different directory.
7) Added a "-nameStyle 3" option (A new nameStyle to be compatible with
8) Added a "-P" option to allow one to probe a given lat/lon point in
all the messages in the file. It does this by linearly interpolating
the surrounding cells to that point. May want to do a nearest neighbor
instead. Also the -pntFile option is not working yet.
9) As always, tested on PC, Linux, HP-Unix, and AIX-Unix. Although I
may have missed something in my testing, it should at least compile, and
run for some of the test cases.
What this means to you... Your current tcldegrib should work fine. It
is, however, using one of the dead ends that I traversed, and you don't
have the -P option (command line only), so although it should function
fine, you might want the current release.
What this means to you... I again have compiled current versions in
~taylor/degrib/bin on rainbow (HP-GDP), in ~taylor/degrib/bin on bd10
(linux), and in /nfsuser/g06/we25at/degrib/bin on Suitland's IBM. So
again, you shouldn't need to download the code or compile it yourself.
Did my suggestions about ArcView help with regards to your "one solid
If you are using the MS-Windows version, then I would definitely
recommend .90 over any of the earlier releases, mainly because of item