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 there, > We are on NWS AWIPS Build 20.3.2-55 of CAVE. Python 3. DAF version is > unknown but I could reach out to someone else for more on that. The > following text... > > METARraw BBXX KDAB 0912/ 99336 11304 41/// ///// 10244 20210 40187 > 53010 7//// 8//// 22200 0//// 2//// 80220 > > ...is the output from the Python application from which all other METARs > are behaving properly (i.e. KLEE METAR included in previous email). All of > the METAR data is treated the same by the Python application, which is why > it is confusing that KDAB is the only site not behaving as expected. Below > you will find a screenshot of the application, in addition to a readout of > the METAR for KDAB: It sounds like you're using a version of AWIPS provided by the national weather service. We only support our (Unidata's distribution) of AWIPS. You might want to contact whoever distributes the version you have, and whoever is running the EDEX you're connected to. --Shay Carter She/Her/Hers AWIPS Software Engineer UCAR - Unidata If you're interested, please feel free to fill out a survey about the support you receive: https://docs.google.com/forms/d/e/1FAIpQLSeDIkdk8qUMgq8ZdM4jhP-ubJPUOr-mJMQgxInwoAWoV5QcOw/viewform Ticket Details =================== Ticket ID: XFF-584221 Department: Support AWIPS 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.