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.
>From: Mai Nguyen <address@hidden> >Organization: National Center for Hydro-Meteorological Forecasting of Vietnam >Keywords: 200312020023.hB20N4p2027742 IDD LDM Linux Mai, >Our site is now ready for two way nslookup. Please >check it again. Forward and reverse name lookup now look good for met_research3. >We've tried to used only those variables which have >standard ID as in wmogrib2.tbl, and also created file >name dwdgrib2.tbl as nagrib required when checking the >center number. But the results are still negative, >which means that the error should be somewhere else. The test we ran here was to use the Unidata GEMPAK grib decoder, dctgrib2, to decode the original GRIB file you had under ldm/VNdata. It worked fine, and we were able to display the data in GEMPAK. We wanted to alert you to the conflict that you would eventually run into when redefining names for parameter numbers less than 128. Can you tell us where your new GRIB file is so we can decode it using the Unidata GEMPAK GRIB decoder? >Thanks and bye for now. >Best regards, Mai. Cheers, Tom -- 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.