NOTE: The decoders mailing list is no longer active. The list archives are made available for historical reasons.
Beth,
I was in meetings all yesterday afternoon, ugh...
Anyway here the setup need to get the CONDUIT feed for the one degree
grid. At first it might be easier to get the raw files then set up a pqact
entry to decode the one degree.
For the ldmd.conf file add lines: like:
exec "pqact -f CONDUIT|SPARE /opt/ldm/etc/pqact.conduit"
request CONDUIT "MT.avn_CY" <upstream LDM node>
Then make a file etc/pqact.conduit with the entry:
NMC2 ^/afs/.nwstg.nws.noaa.gov/ftp/(.*) !(.*)/(.*)/(.*)/(#.*)/(.*)/(.*)/(.*)/
(.*)!
FILE -close data/pub/raw/conduit/\1/\2_\3_\4_\5_\6_\7_\8_\9
This should make a file structure similar too:
/local/ldm/data/pub/raw/conduit/SL.us008001/ST.opnl/MT.avn_CY.12/RD.20040528/PT.
grid_DF.gr1/fh.0012_tl.press_gr.onedeg
% cd to that dir
Then you could decode the data:
grib_ncep_AVN_#003_200405281200_F012_U-GWD_sfc
If you do a notifyme the results should look like:
% notifyme -vl - -f CONDUIT -p "MT.avn_CY" -o 3600000
May 28 15:23:19 notifyme[25675]: 130404 20040528152311.874 CONDUIT 231
/afs/.
nwstg.nws.noaa.gov/ftp/SL.us008001/ST.opnl/MT.avn_CY.12/RD.20040528/PT.grid_DF.g
r1/fh.0000_tl.press_gr.onedeg
!grib/ncep/SPEC_SSI_AVN/#003/200405281200/F000/PRES/tropopause! 000231
If you want to directly decode the data, put a pqact entry in pqact.conduit
NMC2 ^/afs/.nwstg.nws.noaa.gov/ftp/MT.avn_CY.(..)/RD.(........)
PIPE decoders/gribtonc etc/gfs-1.0x1.0_3.cdl
data/decoded/netcdf/GRIB/\2\1_/gfs-1.0x1.0.nc
I haven't checked out the entry, could be an error. You could modify the
entry to only decode certain products. Some of the products are missing
from the gfs-1.0x1.0_3.cdl, you could run gribtocdl to find them and then
add them to gfs-1.0x1.0_3.cdl. If you make a complete cdl, I would like
to have it for the distribution.
Thanks,
Robb...
On Mon, 24 May 2004, Beth Hall wrote:
Robb -- Thanks for the quick reply. Yes, the 211 grid has constant coordinates, but not in the latitude/longitude coordinate system. The Dx and Dy are not in degrees, but ground/kilometer distance. Therefore, I am looking for what the lat/lon coordinate is at each constant kilometer distance. Even the corner lat/lon coordinates you provided indicate that there is not a constant _degree_ Dx or Dy. On a slightly separate note, we are really interested in the 1-degree GFS forecasts (we are currently downloading them daily from the ftp site) through the Unidata feed. In a past email, you said that the 1-degree grids are only available through the CONDUIT and not the NOAA port. So, how do we get the CONDUIT? Why isn't it available through the NOAA port, if I can ftp the data? Thanks for all of your help, Beth On Mon, 24 May 2004, Robb Kambic wrote: > On Fri, 21 May 2004, Beth Hall wrote: > > > Robb -- > > > > Thanks for the advice on the CDL's. You mentioned how to use most of the > > CDL's except for the gfs_211.cdl. This one is of most interest to me > > since it seems to be for a much higher resolution (80 km) than the others > > and still shows the forecast data. However, I'm having a hard time > > knowing what the actual lat/lon coordinates are for this 80 km grid. Is > > Beth, > > The coordinates are constant. > > Lat/lon values of the corners of the grid > (1,1) 12.190N, 133.459W > (1,65) 54.536N, 152.856W > (93,65) 57.290N, 49.385W > (93,1) 14.335N, 65.091W > > Here's the basic info on all the grids at: > > http://www.nco.ncep.noaa.gov/pmb/docs/on388/tableb.html > > Actually http://www.nco.ncep.noaa.gov/pmb/docs/on388 give the details of > parameters, etc too. > > Other info: > > http://www.nco.ncep.noaa.gov/pmb/docs/headers/awpgfs/#TABLEGP > > > Robb.... > > > this, perhaps a separate file that would specify this information, for I > > don't think I need it for every dataset I want to use -- it should stay > > fairly constant, right?? > > > > Thanks, > > Beth Hall > > > > On Fri, 7 May 2004, Robb Kambic wrote: > > > > > On Thu, 6 May 2004, Unidata Support wrote: > > > > > > > > > > > ------- Forwarded Message > > > > > > > > >To: support-decoders@xxxxxxxxxxxxxxxx > > > > >From: "Beth Hall" <bhall@xxxxxxx> > > > > >Subject: netCDF Decoders - Sun UNIX - CDLs > > > > >Organization: DRI > > > > >Keywords: 200405070023.i470NhxJ020678 netCDF decoders gribtonc CDL > > > > > > > > Institution: Desert Research Insitute > > > > Package Version: decoders-3.0.3 > > > > Operating System: Sun UNIX > > > > Hardware Information: Sun > > > > Inquiry: I'm trying to access data from the ldm feed, partiticularly > > > > the GFS data. I feel very lost, but finally found the gribtonc > > > > command. I originally used the gfs_211.cdl file, but it gave me no > > > > lat/lon coordinates, just x and y. > > > > > > Beth, > > > > > > No lat/lon are given because of rounding errors, no accurate values. The > > > lat/lon are mainly for human information. > > > > > > > > > > > > With this cdl, the ncdump -h said > > > > there were 21 records (I'm assuming this refers to the forecasts, > > > > themselves). > > > > > > Your correct the records are for forcast times: > > > > > > valtime_offset = 0, 6, 12, 18, 24, 30, 36, 42, 48, 54, 60, 66, 72, 78, > > > 84, 90, 96, 102, 108, 114, 120 ; > > > > > > > > > I did some web searching and found that there were other > > > > CDLs including a 1 degree CDL. > > > > > > The 1 degree grids are only on the CONDUIT feed, not the standard NOAAPORT > > > feed. > > > > > > > > > I tried it along with the > > > > gfs_21-24.cdl, gfs_25-26.cdl, and the gfs_37-44.cdl. Several of those > > > > actually have the lat/lon coordinate information, but now show 0 > > > > records (no forecast data?). > > > > > > Maybe you don't have the correct pqact entries, here's the ones we are > > > using. Remember the white spaces are tabs between the parts of the > > > entries. > > > > > > # GFS model on global 5.0 x 2.5 degree grids > > > HRS ^H.[A-D]... .... (..)(..).*/m(SPEC62MRF|MRF) > > > PIPE /usr/local/ldm/decoders/gribtonc > > > etc/gfs_21-24.cdl > > > data/pub/decoded/netcdf/GRIB/(\1:yyyy)(\1:mm)\1\2_gfs_21-24.nc > > > > > > # GFS model on global 5.0 x 5.0 degree grid > > > HRS ^H.[EF]... KWB. (..)(..) > > > PIPE /usr/local/ldm/decoders/gribtonc > > > etc/gfs_25-26.cdl > > > data/pub/decoded/netcdf/GRIB/(\1:yyyy)(\1:mm)\1\2_gfs_25-26.nc > > > > > > > > > # GFS model on thinned grids, interpolated to global 5.0 x 2.5 regular > > > grid > > > HRS ^H.[I-P]... KWB. (..)(..).*(/mAVN|/mSSIAVN) > > > PIPE /usr/local/ldm/decoders/gribtonc > > > -q "lin,dlat=2.5,dlon=5.0" etc/gfs_37-44.cdl > > > data/pub/decoded/netcdf/GRIB/(\1:yyyy)(\1:mm)\1\2_gfs_37-44.nc > > > > > > I know the data must be there, but clearly > > > > don't understand what these different CDLs are doing, which one I > > > > > > The cdl file are templates for making the NetCDF files, the number > > > designation at the end of the cdl refers to the grib sections ie 21-24 > > > that are stitched together to form the whole grib file. > > > > > > Robb... > > > > > > > should use, and which ones give me the lat/lon coordinate information. > > > > Can you help? Thanks. > > > > > > > > -- > > > > NOTE: All email exchanges with Unidata User Support are recorded in the > > > > Unidata inquiry tracking system and then made publically 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. > > > > > > > > ------- End of Forwarded Message > > > >
============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research rkambic@xxxxxxxxxxxxxxxx WWW: http://www.unidata.ucar.edu/ ==============================================================================
decoders archives: