The plan moving forward is for Xradar to be the primary input/output (IO) tool which was previously implemented in each radar package (Py-ART, wradlib, etc). Once users read in their data using Xradar, they can use accessors, which are connections to other toolkits of the xarray-based scientific Python stack. For example, we plan on implementing a Py-ART accessor, which will enable users to use the full suite of functionality in Py-ART. This enables direct cross-compatibility between libraries, allowing open radar community users to use features in wradlib, without needing to save the file to disk re-read using wradlib. One common ARM data correction task in wradlib, that would be helpful to use within Py-ART, is beam blockage corrections. Xradar reduces the need for duplicated readers, saving files to disk, ultimately reducing the time-to-science. As a single point of IO Xradar will also lessen the burden of maintenance in the different Open Radar Science Packages. Bindings to other programming languages, e,g, C/C++, may also be explored. We will provide updates related to progress on this new tool, highlighting the newest member of the Open Radar Science community.
 - Indicates paper has been withdrawn from meeting
 - Indicates paper has been withdrawn from meeting - Indicates an Award Winner
 - Indicates an Award Winner