@ChrisBarker-NOAA I think we need to go ahead and embrace the mess that quite a few data producers and users are happily using. We can provide an "almost-as-easy" alternative (do you mean the string or binary time stamps?), but there's a large base of producers and users that would need to switch methods, software packages that would need to add a new way of dealing with time, and legacy datasets that have no path forward for being given a better specification of what exactly is in their time variables. (Which could be handled with an attribute edit if we provide a calendar for their use case.)
-- 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/148#issuecomment-436027057
