@ChrisBarker-NOAA This topic is only about real-world calendars. There are three different model calendars already - **`360_day`**, **`noleap`** (aka **`365_day`**), and **`all_leap`** (aka **`366_day`**). I think the model people have all they need. They can also use the current **`julian`**, **`gregorian`**, and **`proleptic_gregorian`** calendars if they so choose. They don't (shouldn't?) ever need to deal with leap seconds unless they are trying to match up against observational data, and even then I don't think many (any?) models have time resolutions where leaps seconds would matter.
-- 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-435444047
