MetPy 0.11.0 has been released with a variety of fixes and enhancements. This is the LAST RELEASE to support Python 2.7.
- MetPy's copy of the "viridis" colormap is deprecated. Use it directly from matplotlib instead.
- Deprecated the
isentropic_interpolation; this will be removed in 1.0. Use
ageostrophic_windnow issues a
FutureWarningdue to an impending change to its function signature in 1.0--this will change the signature to
ageostrophic_wind(heights, u, v, f, dx, dy)for better consistency with the rest of the library. To avoid this warning, import the function with
from metpy.future import ageostrophic_wind.
- Deprecated the
Hodograph.plot_colormappedin favor of
intervalsto improve clarity on how to use the argument.
- Removed previously deprecated:
Fixes and Enhancements
- Several SkewT fixes and enhancements, including reworking the transform so that it works in screen space; this helps it work much better on oddly shaped axes. On Matplotlib 3.2, this means that the SkewT maintains sensible data scaling. SkewT by default also now has sensible plot limits.
- MetPy 0.10.x accidentally picked up a hard dependency on CartoPy, this has been removed
- Expanded simplified plotting interface with more documentation and support for
- Several bug fixes for
- No longer require using
.metpy.parse_cf()to activate coordinate identification with XArray
- XArray accessor automatically converts problematic '%' units to 'percent'
- Added unit support in
wind_directionnow supports specifying the convention (either 'to' or 'from') to support oceanographic applications (default remains 'from').
- Improved numerical stability of geopotential<->height calculations
- Added parsing of more combinations of weather symbols
heat_indexnow better matches NWS algorithm
angle_to_directionto convert wind direction in degrees to e.g. 'NE'
- Added control of
@ahuang11, @akrherz, @jthielen, @kgoebber, @leouieda, @mgrover1, @sgdecker, @tjwixtrom, @zbruick, @jrleeman, and @dopplershift contributed code to this release.
For full release notes see the GitHub Release Page.
Let us know if you run into any problems, either at MetPy issue tracker, using firstname.lastname@example.org, or on the python-users list. You can also ask questions using the "MetPy" tag on Stack Overflow.