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.
Hi again Robert, Just a quick note to let you know that I have been running the ADDE GRIB (GRIB 1) server on my 64-bit Fedora Core 5 machine since yesterday afternoon. I followed the steps you outlined in the first message of this thread for setting up the MySQL database, etc. As soon as 'gribadmin latest' showed that GRIB1 messages were being processed, I turned off DMGRID decoding and started setting up ADDE datasets using direct GRIB access. Everything is working nicely for me _except_ that not all of the AMPS fields are being processed correctly. I have not (yet) made an inventory of which fields are not displayable, so I have no guidance for you on what to expect when you hit the ice. Along these lines, I would appreciate you developing an inventory (list) of which fields are processed correctly and which are not. I will then use grib messages from the 'not' list to improve the GRIB decoding/serving in McIDAS. Have fun in Antarctica! Cheers, Tom **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: JIN-832252 Department: Support McIDAS Priority: Normal Status: Closed