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 Gilbert, et. al, I just wanted to jump in to make a comment on something that Gilbert said... re: > I'm also CC'ing Victor on this as well. I forgot, it crashed again when > you started sending the new images across the NIMAGE feed (which have a > serious issue, a buddy of mine reported it already). Anyway... The comment is about "which have a serious issue, a buddy of mine reported it already": The ABI L2 imagery that is now being distributed in the NIMAGE datastream are working flawlessly in AWIPS, McIDAS-X, IDV, McV and MetPy. The issue reported (by Kevin Polston) seems to be a GEMPAK issue only. That is why I drove the inquiry into the GEMPAK area of our inquiry tracking system, not the Datastream portion. That's it from me... > Yes, it is weird, but since it happens so rarely (firewall/network failures) > these days, I never had the chance to see if it still happens with all of the > fixes you did. Alas, it still does... 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: RSN-549334 Department: Support LDM Priority: Normal Status: Open =================== NOTE: All email exchanges with 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.