Edouard Goudenhoofdt

This is not an easy discussion and it would be nice to hear from other people including CfRadial2 developers ;-) We should probably keep the current implementation because it is...

This is a known tricky issue. 1) _Undetect It is an optional attribute in [FM301](https://github.com/wmo-im/CF-NetCDF/blob/main/standard/fm-301/fm301.adoc). It is defined as follow: "Indicates an area (range bin) that has been radiated but...

For UBYTE, the default _FillValue is 255. If this is a valid maximum value for a given format (e.g. Rainbow), one could replace 255 by 254 while setting 255 as...

This is actually a more general issue on the definition of special values in our data model. Is missing value "undetect" or "no valid data" or both? I think this...

It seems there is an ODIM version of the data indeed. There is already a reader for ODIM radial data in xradar. For 2D ODIM products, you can use [this](https://corteva.github.io/rioxarray/stable/)....

Thank you @kmuehlbauer for the suggestion. I am wondering if an automatic option based on the file metadata would be interesting.

I think reading the nominal angles should be the default for all readers for several reasons: - it follows the philosophy of ODIM and CFRADIAL2 - the actual physical quantity...

For example, viewing all dataset variables. If one loops over data_vars, one also gets the metadata variables.

What about using attributes to store these ancillary variables?

There are actually 3 types of sweep variables: - observed variables - ancillary variables related to one or more observed variables - metadata variables related to the sweep itself Accessing...