GrADS and grib2

[Mike Fiorino]

Dear Steve,

I'm actually working this issue...

there is a working wgrib2 program and I will be prototyping a grads
interface inside wgrib2, see:

http://www.cpc.ncep.noaa.gov/products/wesley/wgrib2/

I'm working on a windows xp box and cygwinX; have been able to compile fine.
the good thing about wgrib2 is that it's relatively easy to add functions
without having to hack all parts of the code.  adding grib1 output might not
be too bad...  hope to have something in the next month.

Best /R Mike

> -----Original Message-----
> From: GRADSUSR at LIST.CINECA.IT
> [mailto:GRADSUSR at LIST.CINECA.IT] On Behalf Of Masters.Steve
> Sent: Friday, January 20, 2006 2:37 PM
> To: GRADSUSR at LIST.CINECA.IT
> Subject: GrADS and grib2
>
> From the latest NCEP "jifmemo" announcing current and future plans...
>
> "1.  The moratorium on changes at the NWS Telecommunications
> Operations Center (TOC) is expected to end in mid to late
> February.  As soon as the moratorium is lifted NCEP will
> begin the transition from GRIB1 to GRIB2, by placing
> duplicate GRIB2 files on the TOC FTP server.  Both sets of
> data will remain on the TOC FTP server for a minimum of 180 days. "
>
> It looks like NCEP may soon be pushing more model files to
> grib2 to save space and bandwidth. The GFS half-degree grids
> are already in grib2.  While a grib2->grib1 converter is
> available, getting it to compile and run is "challenging" at
> best on most platforms.  Is there any work being done (or
> already done) for grads to read grib2?  I note that there is
> not yet an operational (or even beta) wgrib2 program.
>
>
> Steve Masters   masters.steve at ensco.com
> ENSCO, Inc.
> Melbourne, FL USA
>
> The information contained in this email message is intended
> only for the use of the individuals to whom it is addressed
> and may contain information that is privileged and sensitive.
> If the reader of this message is not the intended recipient,
> you are hereby notified that any dissemination, distribution
> or copying of this communication is strictly prohibited. If
> you have received this communication in error, please notify
> the sender immediately by email at the above referenced
> address. Thank you.
>