Version Handling in `to_odim`

[kmuehlbauer]

• xradar version: 0.1.0
• Python version: 3.11
• Operating System: Linux

Description

• The output to_odim is currently assuming ODIM_H5 V2.2. We should discuss how we want to enable output of V2.3 and V2.4 and possible further versions. One problem with that was raised by @egouden in https://github.com/openradar/xradar/pull/97#issuecomment-1460451436.
• A second issue with to_odim is the capability of handling source identifiers. This should be discussed too, how to align that with our internal structure. See discussion around this comment https://github.com/openradar/xradar/pull/96#issuecomment-1455058568.

[egouden]

The ODIM writer is now fully compatible with ODIM 2.2 (2014), which is good !

The main interest of ODIM 2.4 (2021) is the definition of some mandatory metadata, useful for data assimilation in NWP.

We could keep only 2.4, because it is cheaper and the format is backward compatible.

We could also release quickly 2.4, by focusing on the mandatory metadata.

Some mandatory metadata in 2.4 might not be available in our WMO model (which is a merging of ODIM and CFRADIAL2). I do not think this is an issue. The missing information can be provided as parameters, like the source parameter in 2.2.