We should move the data to the open-radar-data package. This will make the package more lightweight.

Adam mentioned wanting to gather new contributors for this project and one thing that can happen when bringing in a lot of new people is differences in coding style or ability. It may be of interesting to the maintainers of this project to consider using pre-commit to encourage consistent code style and quality:

https://pre-commit.com/

These configs can definitely get crazy, but I feel that in the end they benefit projects more than the time they take to setup. You can even enable pre-commit.ci to automatically run checks for pull requests:

https://pre-commit.ci/

You can find examples in the various examples on the above sites, but I find it useful to look at other projects using pre-commit:

• https://github.com/pytroll/satpy/blob/main/.pre-commit-config.yaml
• https://github.com/dask/dask/blob/main/.pre-commit-config.yaml
• https://github.com/pydata/xarray/blob/main/.pre-commit-config.yaml

Just an idea. Feel free to close this.

Installed /usr/local/lib/python3.10/dist-packages/importlib_metadata-7.0.1-py3.10.egg
error: click 8.0.3 is installed but click>=8.1 is required by {'dask'}

radar_plot_vpt.pro

Would like to kindly suggest making a release to see how far it gets within conda-forge/staged-recipes#24910

radar_get_beam_pattern.pro

Want to follow suit like ACT and get this added.

get_radar_profile.pro

radar_plot_scatter.pro

We need to add a function to dealias velocity for VPT data.

We'd (Iowa State) like to use this package, but the matplotlib < 3.5 pin is a bit problematic. I couldn't find an issue here documenting the issues with that or 3.6 matplotlib?