On the string encoding issue, CF data can be currently stored in two file formats: [NetCDF Classic](https://www.unidata.ucar.edu/software/netcdf/docs/file_format_specifications.html), and [HDF5](https://support.hdfgroup.org/HDF5/doc/H5.format.html). String encoding information cannot be directly stored in the netCDF Classic format and the spec defines a special variable attribute `_Encoding` for that in _future implementations_. The values of this attribute are not specified so anything could be used.
In the HDF5 case, string encoding is an intrinsic part of the HDF5 string datatype and can only be ASCII or UTF-8. Both `char` and `string` datatypes in the context of this discussion are stored as HDF5 strings. This effectively limits what could be allowed values of the (future) `_Encoding` attribute for maximal data interoperability between the two file formats. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/141#issuecomment-407760311
