This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
James, To isolate the grid 211 (Q) grids, you need to modify your pattern: >HRS ^[YZ]..... KWB. ([0-3][0-9])([0-2][0-9]).*(/mAVN|/mSSIAVN) To: HRS ^[YZ].Q... KWB. ([0-3][0-9])([0-2][0-9]).*(/mAVN|/mSSIAVN) There are about 5 AVN projections on NOAAport, and if you don't use the grid specifier in the pattern, or if you don't use the @@@ template in the file name which is replaced by the grid number in the file name, then you can get conflicts where the file is created using the projection of the first grid that comes across the feed. All subsequent grids that don't match the projection would be thrown away. So, if a grid 213 (H) avn came in first, then that would be the projection of the file. SInce the H grid is 95km STR, it would cover roughly the same area as the Lambert 80km grid 211, but the content of what grids are distributed in each projection are somewhat different based on AWIPS needs in the NWS. I provided Devin with the lasted dcgrib source that has many updates and additional grid projections that can be decoded since the 1997 copy that you were running. Let me know if the above pattern isolation and the dcgrib update don't solve your problem. You should probably check the gdinfo projection information of the AVN file in question and see which of the AVN data sets created the file. The dcgrib updates since the 1997 version you had now add the @@@ an ### templates so that the various model projections can be written to appropriate files, so a pattern like: HRS ^[YZ].*/mNGM dcgrib PACK YYMMDDHH_ngm_grid@@@.gem Would produce separate filesfor grid211, grid 201, grid 207, grid 213 etc. Similarly, ### is replaced by the model number, eg NGM=039, however, AVN and SSIAVN are different model numbers, so its not likely that MRF/AVN would want to use that option, but ruc, ngm, eta etc can be identified uniquely by the model number. Steve Chiswell Unidata User Support >From: address@hidden (James Murakami) >Organization: . >Keywords: 199904271904.NAA22608 >Hi Steve Chiswell: > >Does the NOAAport distribution of AVN (grid 211) still >contain files of 6 hr precipitation and omega (for various >levels)? > >We've stopped receiving the above data. The AVN gempak decoded >files are now about one-third as large as early last week. > >As you probably know, somehow our GRIB decoder started "acting >wacky" (Devin Kramer is our programmer). Only the ECMWF and NGM >grids were getting decoded. We're getting other data decoded >again, but the AVN files seem incomplete. Here's our pqact.conf >for the AVN data-- > ># AVN model output decoded into yymmddhh_avn.gem (#211 grid) ># >HRS ^[YZ]..... KWB. ([0-3][0-9])([0-2][0-9]).*(/mAVN|/mSSIAVN) > PIPE /unidata/ldm/gempak/bin/dcgrib_ncsu -v > -d /gempak/logs/dcgrib.log > -g /unidata/ldm/gempak/gempak5.4/tables > PACK /gempak/data/hrs/YYMMDDHH_avn.gem > > >I'd hate to resort to the "thin" grids for plotting charts for >the contiguous U.S. > >James > > > >James Murakami >Staff Meteorologist/Student Affairs >Department of Atmospheric Sciences >University of California, Los Angeles >405 Hilgard Ave. >Los Angeles, CA 90095-1565 > > > e-mail: address@hidden >telephone: 310-825-2418 > Fax: 310-206-5219 >