@JimBiardCics said: > I'm curious to know if the NUG authors looked at this section in light of > allowing `string` type.
No, the NUG has NOT been systematically reviewed with respect to the `string` type or other enhanced data model features. Clearly, the NUG should support the use of enhanced data model types and features (with appropriate cautions about backward compatibility and broad usability) and leave further restrictions to conventions. So, NUG Appendix A should probably clarify that the values of those attributes are strings that can be encoded in netCDF-3 as `char` arrays and in netCDF-4 as either `char` arrays or `string` type. The Unidata netCDF group will work on updating the NUG (with user community input) in the fairly near-term. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/141#issuecomment-408563187
