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, This sounds like a bug in MetPy. Would you be able to open an issue at https://github.com/Unidata/MetPy/issues/new ? It'd be helpful to include/attach a copy of the data that's producing the error. Thanks, Ryan > I am using the MetPy ver0.9.2. > > > address@hidden> wrote: > > > Thank you for your reply. > > > > address@hidden> wrote: > > > >> Hello, > >> > >> There was a recent issue relating to this. What version of MetPy are you > >> running? You can check by running this from the command line: > >> > >> python -c "import metpy; print(metpy.__version__)" > >> Ticket Details =================== Ticket ID: LUY-822187 Department: Support Python Priority: Low Status: Closed =================== 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.