> Just so you know, the UDUNITS package does assume the first day of the > year at 00:00:00 UTC if additional resolution time-fields are omitted. > This conforms to the ISO standard.
Actually (according to Wikipedia at least) the ISO8601 standard assumes local time if the time zone is omitted. I'm not sure what time information (if any) is inferred if the ISO string omits hours/minutes/seconds (i.e. I don't think 2008-01-01 is inferred to be the same as 2008-01-01T00:00:00Z). But it's important to highlight that UDUNITS does assume midnight UTC if no time is provided. It implies that the temporal resolution is not to be inferred from the length of the UDUNITS time string. Jon -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Steve Emmerson Sent: 18 March 2011 17:14 To: [email protected] Subject: Re: [CF-metadata] udunits handling of fuzzy time units Martin, On 03/18/2011 04:11 AM, Schultz, Martin wrote: > PS: I do disagree with Christopher when he says ''"30 days since 31 Jan 2008" > is perfectly well defined.'' - do you refer to 00 UTC or 12 UTC on 31 Jan > 2008? Or even 00:00 UTC or 01:02:30.3625132 h UTC? OK: if you define an > "oceanographic calendar" (where anything shorter than a day doesn't matter), > you could have a rule that all hours, minutes, seconds, milliseconds, etc. > are mapped onto one value (say 00:00:00 h UTC). But you will need to define > this rule in order to give a meaning to your calendar. Just so you know, the UDUNITS package does assume the first day of the year at 00:00:00 UTC if additional resolution time-fields are omitted. This conforms to the ISO standard. Regards, Steve Emmerson _______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata _______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
