netcdf

As far as I know, there's no way to see what options are enabled.

It'd be nice to add either xr.get_options or xr.show_options or xr.options so that users can see what is enabled.

I think it would be nice to have a one-line description under each option

"arithmetic_join": "outer"
    controls DataArray/Dataset alignment in binary operations.

❤️ 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.

See #601 . Was done for CW_BGROUP

Is your feature request related to a problem? Please describe.
It can be necessary to pull out the instrument sampling rate from data. In principle this should be easy but data gaps, instrument turn on/off, etc. can potentially frustrate this determination.

Describe the solution you'd like
It may be necessary for calc_res in utils.time to support different averaging methods for da

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.