> @hrajagers said: However CF inherits most of them [attributes] from the > NetCDF User Guide which explicitly states that they should be stored as > character arrays (see NUG Appendix A) So, is it then up to CF to allow > strings here?
Yes, NUG Appendix A literally allows only **`char`** type attributes. My sense is that proponents believe that **`string`** type is compatible with the intent of the NUG, and also **`strings `** have enough advantages to warrant departure from the NUG. Personally I think **`string`** type attributes are fine within collaborations where everyone is ready for any needed code upgrades. For exchanged and published data, **`char`** type CF attributes should be preferred explicitly by CF. -- 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-407937736
