In case it's useful, the "wgrib2" package:
http://www.cpc.ncep.noaa.gov/products/wesley/wgrib2/
can read both grib1 and grib2 and write both NetCDF3 and NetCDF4 files.
-Rich
On Thu, Mar 28, 2013 at 4:40 PM, Lynnes, Christopher S. (GSFC-6102)
<christopher.s.lynnes@xxxxxxxx> wrote:
>
> On Mar 28, 2013, at 4:06 PM, Russ Rew wrote:
>
>> Hi Chris,
>>
>>> I see that the netcdf-java API can read GRIB data, which produces nice
>>> capabi
>>> lities like the ability to read GRIB into Panoply and (I presume?) TDS.
>>>
>>> Does the netCDF C API have this capability? (I guess I'm hoping to sneak
>>> GRI
>>> B capability into C/C++ based tools like nco and Hyrax through the API back
>>> d
>>> oor, so to speak.)
>>>
>>> If not, any plans to add this to the C API?
>>
>> APIs built on the netCDF C library, which include C, Fortran, Python and
>> C++ libraries, have support for OPeNDAP client access. That means
>> programs built on such APIs can read from an OPeNDAP server that serves
>> GRIB data. Such programs are DAP clients and by opening with a URL
>> rather than a local file name, they can access GRIB files, aggregations,
>> subsets, and other features supported by the Unidata Common Data Model
>> software.
>>
>> There are no current plans to provide netCDF C support for directly
>> accessing local GRIB files.
>>
>> --Russ
>
> Yeah, we're using the OPeNDAP trick now, but were looking for a higher
> performance mechanism, i.e., reading directly off disk...will check direct
> disk converters instead, like ncl...
> --
> Dr. Christopher Lynnes NASA/GSFC, Code 610.2 phone: 301-614-5185
>
>
> _______________________________________________
> netcdfgroup mailing list
> netcdfgroup@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
--
Dr. Richard P. Signell (508) 457-2229
USGS, 384 Woods Hole Rd.
Woods Hole, MA 02543-1598
