❤️ First Time Contributors

Welcome to Iris! 😊

This is a permanent pinned issue dedicated to our lovely first time contributors and those new to Iris, keen to get involved.

We'd really love to hear from you, so checkout our GitHub Discussions. Ask a question, share an idea, ask for help, tell us what we could do better or simply say `"Hi!"

https://carpentries-incubator.github.io/geospatial-python/ is a good course that uses rioxarray. Could add a link to it in https://corteva.github.io/rioxarray/stable/getting_started/getting_started.html

When there are no data available for a particular date range from IGRA2, it would be very helpful to the users to include the range of data that is actually found in the file. This will require actually calculating the min/max date, but we are already scanning through all of them so it shouldn't be too much more effort.

Any chance to implement comfit?
If not, how to get exponential fitting with implemented functions in GDL?

Describe the bug
The documentation unit tests have identified two badly named sections in the docstrings

To Reproduce
Go to the doc tests in any of the recent PRs.

Expected behavior
Only have UserWarnings for the Note section.

Desktop (please complete the following information):

• OS: ubuntu
• Other details about your setup that could be relevant - GitHub Actions

The -Wmaybe-uninitialized GFortran option will list many variables that may be used before initialized. While several of these warnings are likely false positives, that is most likely due to the branching done in the code causing certain, unlikely paths (and sometime error paths) that do not initialize the variable. These cases need to be evaluated, and if possible corrected.