[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20041217: 20041213: Using NAGRIB on grid #221
- Subject: 20041217: 20041213: Using NAGRIB on grid #221
- Date: Fri, 17 Dec 2004 10:55:15 -0700
Luis,
Yes, its manual work. I created the ncarncep1.tbl table for
the reanalysis data sets previously.
You might find that that a good starting point to check
as to what is different in the #131 table.
See the phelp on GBTBLS in nagrib for specifying your own table.
Steve Chiswell
Unidata User Support
>From: address@hidden
>Organization: UCAR/Unidata
>Keywords: 200412171604.iBHG4alI004078
>Steve,
>thanks for the information.
>
>Yes, the GRIB file I have is from the North American Regional Reanalysis
>that has been released by CDC/NCEP.
>
>I did contact Wesley Ebisuzaki and obtained the correct address for the
>table: ftp://ftpprd.ncep.noaa.gov/pub/cpc/wd51we/wgrib/nceptab_131
>This table contains data with (approximately) 255 variables,
>including names and units.
>
>Now, this table has a different format that those in $GEMTBL/grid* and
>this seems to be suggest manual work to have the data in that format.
>Once this is done, I should be able to perform the conversion from
>GRIB into a gridded file for handling with the NAGRIB program of GEMPAK.
>
>Please let me know if I am in the right track and, if this is available,
>any code recommended to simplify the table format conversion.
>
>Luis M Farfan.
>
>* For example: ncarncep1.tbl, wmogrib2.tbl, ncepgrib2.tbl, etc.
>
>
>Quoting Unidata Support <address@hidden>:
>> Luis,
>>
>> Apparently one of the GRIB products you have is using
>> a table 131. Using the GBDIAG parameter for PDS would show
>> you which parameter numbers are beingused for the table 131.
>>
>> The NWS site that provides the NWS local table definitions does
>> not show any updates past table 130:
>> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table2.html
>>
>> However I do find that NCDC references table 131 for reanalysis
>> data rather than the current tables 2, 3, 129 and 130 that we see
>> for realtime data::
>> http://www.ncdc.noaa.gov/oa/documentlibrary/pdf/tddoc/td6175.pdf
>>
>> If you file is reanalysis data, then that document will direct you to
>> the parameter definitions that you would need to create the 131 version
>> tables for your data set::
>> ftp://wesley.ncep.noaa.gov/pub/wgrib/nceptab_131
>> I tried that ftp site this morning and didn't get connected, so you'd
>> have to verify that information yourself.
>>
>>
>> Steve Chiswell
>> Unidata User SUpport
>>
>>
>>
>> >From: address@hidden
>> >Organization: UCAR/Unidata
>> >Keywords: 200412140143.iBE1helI006495
>>
>> >Steve,
>> >I am trying to use the gempak program "nagrib" to convert gridded
>> >data from a GRIB into a GEMPAK file. Since the input file is in
>> >the AWIPS grid #221, I set CPYFIL = #221. However, I find
>> >some problems like the following:
>> >
>> >GEMPAK-NAGRIB> GEMPAK-NAGRIB> Changing center table to cntrgrib1.tbl
>> > Changing vertical coord table to vcrdgrib1.tbl
>> > Changing WMO parameter table to wmogrib131.tbl
>> > [NA -1] The table wmogrib131.tbl cannot be opened.
>> > [NA -1] The table wmogrib131.tbl cannot be opened.
>> >
>> > 1 GRIB messages were read or scanned from the GRIB file:
>> > 20030913_1200_hght_500.grib
>> >
>> > 0 grids were written to the GEMPAK file:
>> > 20030913_1200_hght_500.gem
>> >
>> > Parameters requested:
>> GBFILE,INDXFL,GDOUTF,PROJ,GRDAREA,KXKY,MAXGRD,CPYFIL,
>> > GAREA,OUTPUT,GBTBLS,GBDIAG,PDSEXT.
>> >
>> >I do not see "wmogrib131.tbl" in the directory $GEMTLB/grid and this makes
>> me
>> >think that something is not right with the definition of the grid
>> parameters.
>> >Are you able to provide some assistance to successfully convert this file?
>> >
>> >Thanks, Luis M Farfan.
>> >
>> --
>> ****************************************************************************
>> Unidata User Support UCAR Unidata Program
>> (303)497-8643 P.O. Box 3000
>> address@hidden Boulder, CO 80307
>> ----------------------------------------------------------------------------
>> Unidata WWW Service http://my.unidata.ucar.edu/content/support
>> ----------------------------------------------------------------------------
>> 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.
>>
>
>
>
--
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.