> The CF calendar attribute specifies the calendar for the reference timestamp > and other timestamps, and the rules for converting between timestamps and > time coordinates. This seems convenient and clear to me. We just need to add > the new ones for (proper) UTC, TAI and GPS, I think.
and a new one for this use case -- the current "gregorian" is NOT the same thing. It often (maybe mostly) is, but it is actually ambiguous with regard to leap seconds, and we need to keep that. Also, once we have the new "calendars", it should not be used for this use case, and should only be used with "metrical" values :-) -- 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-437157449
