# ANN: wradlib 2.0

**URL:** <https://openradar.discourse.group/t/ann-wradlib-2-0/324>\
**Category:** Announcements\
**Tags:** xradar, wradlib\
**Created:** [September 28, 2023, 6:25pm UTC](https://openradar.discourse.group/t/ann-wradlib-2-0/324 "2023-09-28T18:25:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kmuehlbauer](https://yyz2.discourse-cdn.com/free1/user_avatar/openradar.discourse.group/kmuehlbauer/32/439_2.png) [@kmuehlbauer](https://openradar.discourse.group/u/kmuehlbauer)\
**Post date:** [September 28, 2023, 6:25pm UTC](https://openradar.discourse.group/t/ann-wradlib-2-0/324/1 "2023-09-28T18:25:27Z")

</div>

Dear Community,

I’m really happy to announce the release of wradlib 2.0 🚀 . As written in [ANN: wradlib 2.0.0 release candidate](https://openradar.discourse.group/t/ann-wradlib-2-0-0-release-candidate/301) this was a major undertaking from moving the xarray reading capabilities to [xradar — xradar 0.4.0 documentation](https://docs.openradarscience.org/projects/xradar/en/stable/) to close integration of wradlib processing functionality into [Xarray documentation](https://docs.xarray.dev/en/stable/index.html).

It was taken care of keeping numpy based processing available and exposing existing and new wradlib functionality by [Extending xarray using accessors](https://docs.xarray.dev/en/stable/internals/extending-xarray.html). Please check the [migration-guide](https://docs.wradlib.org/en/latest/migration.html) for any unexpected changes.

We’ve got the docs back into the main repo 📄 , revisited the docstrings, checked links 🔗 and cross-references and also worked 👷‍♂️ over the code with lint and style tools. Finally, the build system 🏗 was moved to a [pyproject.toml](https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/) only build using [Hatch](https://hatch.pypa.io/latest/).

Over at [GitHub - wradlib/wradlib-notebooks: wradlib jupyter notebooks](https://github.com/wradlib/wradlib-notebooks) the wradlib tutorials and examples got a major overhaul and are almost everywhere using the new xarray based processing. From my personal experience this is kind of a game changer: clean code, easy access to the xarray ecosystem and to cloud ready ☁ processing frameworks, like [Dask — Dask documentation](https://docs.dask.org/en/stable/).

Check out the [latest documentation](https://docs.wradlib.org/en/latest/index.html). We are always happy 😍 to receive contributions in any form, as there is still much work ahead.

See you around,  
Kai  
On behalf of all wradlib developers and contributors

---

<div class="post-metadata">

**Author:** ![mgrover1](https://yyz2.discourse-cdn.com/free1/user_avatar/openradar.discourse.group/mgrover1/32/7_2.png) [@mgrover1](https://openradar.discourse.group/u/mgrover1)\
**Post date:** [September 29, 2023, 1:54pm UTC](https://openradar.discourse.group/t/ann-wradlib-2-0/324/2 "2023-09-29T13:54:50Z")

</div>

Congrats @kmuehlbauer !! This is so exciting!! Amazing work!