So now that [string variables have landed](https://github.com/cf-convention/cf-conventions/pull/140), I want to bring some attention to this issue again. Some updates I've learned about:
* Because strings are allowed in variables, some are assuming that string attributes are allowed by CF 1.8, especially because [Appendix A](http://cfconventions.org/Data/cf-conventions/cf-conventions-1.8/cf-conventions.html#attribute-appendix) uses the word "string" instead of... text? whatever `nc_get_att_text()` returns... * This is now being used as a "CF-1.8" conforming recommendation from [PODAAC](https://podaac.jpl.nasa.gov/) for [pinniped data](https://github.com/oceandatainterop/nc-eTAG/blob/master/nc-eTAG_Archival_Template.cdl). * I personally see use of string arrays as having extreme utility for lists of peoples names (mostly ACDD attrs), flag definitions, and anything else that is currently "white space separated" in the CF standard. -- 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-598851406 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
