MetPy is a collection of tools in Python for reading, visualizing and performing calculations with weather data.
MetPy follows semantic versioning in its version number. With our current 0.x version, that implies that MetPy's APIs (application programming interfaces) are still evolving (we won't break things just for fun, but many things are still changing as we work through design issues). Also, for a version 0.x.y, we change x when we release new features, and y when we make a release with only bug fixes.
We support Python >= 3.6 and currently support Python 2.7.
NOTE: We are dropping support for Python 2.7 in Fall 2019. See here for more information.
Need help using MetPy? Found an issue? Have a feature request? Checkout our support page .
- Source code repository: https://github.com/Unidata/MetPy
- HTML Documentation : http://unidata.github.io/MetPy
- Unidata Python Gallery: https://unidata.github.io/python-gallery/
- Issue tracker: http://github.com/Unidata/MetPy/issues
- "metpy" tagged questions on Stack Overflow: https://stackoverflow.com/questions/tagged/metpy
- Gitter chat room: https://gitter.im/Unidata/MetPy
- Say Thanks: https://saythanks.io/to/unidata
Other required packages:
- Numpy
- Scipy
- Matplotlib
- Pint
Python 2.7 requires the enum34 package, which is a backport of the standard library enum module.
There is also an optional dependency on the pyproj library for geographic projections (used with CDM interface).
See the installation guide for more information.
We want everyone to feel welcome to contribute to MetPy and participate in discussions. In that spirit please have a look at our code of conduct.
Imposter syndrome disclaimer: We want your help. No, really.
There may be a little voice inside your head that is telling you that you're not ready to be an open source contributor; that your skills aren't nearly good enough to contribute. What could you possibly offer a project like this one?
We assure you - the little voice in your head is wrong. If you can write code at all, you can contribute code to open source. Contributing to open source projects is a fantastic way to advance one's coding skills. Writing perfect code isn't the measure of a good developer (that would disqualify all of us!); it's trying to create something, making mistakes, and learning from those mistakes. That's how we all improve, and we are happy to help others learn.
Being an open source contributor doesn't just mean writing code, either. You can help out by writing documentation, tests, or even giving feedback about the project (and yes - that includes giving feedback about the contribution process). Some of these contributions may be the most valuable to the project as a whole, because you're coming to the project with fresh eyes, so you can see the errors and assumptions that seasoned contributors have glossed over.
For more information, please read the see the contributing guide.
The space MetPy aims for is GEMPAK (and maybe NCL)-like functionality, in a way that plugs easily into the existing scientific Python ecosystem (numpy, scipy, matplotlib). So, if you take the average GEMPAK script for a weather map, you need to:
- read data
- calculate a derived field
- show on a map/skew-T
One of the benefits hoped to achieve over GEMPAK is to make it easier to use these routines for any meteorological Python application; this means making it easy to pull out the LCL calculation and just use that, or re-use the Skew-T with your own data code. MetPy also prides itself on being well-documented and well-tested, so that on-going maintenance is easily manageable.
The intended audience is that of GEMPAK: researchers, educators, and any one wanting to script up weather analysis. It doesn't even have to be scripting; all python meteorology tools are hoped to be able to benefit from MetPy. Conversely, it's hoped to be the meteorological equivalent of the audience of scipy/scikit-learn/skimage.