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.
Mike - well, I will admit I am a little disappointed by some of your findings. And the need to address will be sometime after Monday, but there are some errors in the coding: FTTN41 is definitely a TAF, which should be coded IDS|DDPLUS. IUPT02 should be a BUFR, and thus HDS. Or profiler . . . I will need to capture one. I knew the Redbook was coded incorrectly - it actually should be NGRAPH, but am not surprised it is HDS. GRIB2 should always be NGRID, but there are a few on NMC that get a feedtype of HDS . . . shouldn't but do. To answer your question, we may need to do a thorough analysis in near real-time with data on Monday, and make adjustments. Folks may see a hit on bandwidth usage, and it is unfortunate . . . but I completely agree with the philosophy of the data realignment, we may some pains for a short period. Sorry I don't have more, but I do think using the subset filters instead of ANY will help a little. - Stonie Cooper, PhD Software Engineer III NSF Unidata Program Center University Corporation for Atmospheric Research I acknowledge that the land I live and work on is the traditional territory of The Pawnee, The Omaha, and The Otoe. Ticket Details =================== Ticket ID: NFA-100528 Department: Support LDM Priority: Normal Status: Open =================== NOTE: All email exchanges with NSF 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.