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.
Hello, and thanks for reaching out. Thanks for your time in making these fixes! We won't be making any changes to these older videos when code changes, and we don't currently have a collection of code snippets from past MetPy Mondays available. However, we're hoping to make such a collection available, hopefully as soon as this Summer! This collection should be available on GitHub, and we'd welcome you to keep an eye open and open an issue or make a code change via Pull Request once that becomes available. We'd love to credit you with the fix. In the mean time, feel free to use and share that code in your work and with your colleagues however you'd like. If you're excited to cite MetPy, check out what that looks like here: https://unidata.github.io/MetPy/latest/userguide/citing.html Either way, thanks for letting us know about this. I hope this helps! All the best, Drew > I have made a work around for Google Colab for Gridding METAR Observations > video. It has fixed the problem of not installing wheels for cartopy. It will > crash when you run the first time as installing mamba will restart it. I have > also fixed the problem where the notebook will crash if the altimeter is used > as the variable. I had to remove_observations_below_value 29 inhg. > > > Is there a way I can publish this and give credit to UniData for using the > code? > Ticket Details =================== Ticket ID: UMC-151461 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.