Hi Jim:
Thanks for explaining some of the details of TAI and UTC time standards.
Obviously Im not much of an expert on them. What I am 99 44/100 % sure of
is that udunits uses 60 seconds per minute no matter what, as does
joda-time, which the netcdf-java library uses. So thats what I mean by
Maik,
I'm far from an expert on this, but doesn't this depend entirely on how
you choose to count your seconds? If you declare your time as 'seconds
since epoch', then it seems to me that it would be perfectly fine (and
perhaps most appropriate) to use exact seconds as defined by
Hi Jim
I see where the potential for mismatches when using time values with
unexpected encoding means that we should provide a way to declare what
kind of time-since-epoch values are used in a particular time variable.
And that's exactly the problem. The CDF website summarizes it quite
Hi Maik:
Unfortunately, CF references the udunits package which is no longer being
developed, at least for date/time coordinates.
udunits does not support leap seconds.
your best bet is to add an auxiliary time coordinate which uses leap
seconds, eg TAI. your specialized software can use that
From: John Caron ca...@ucar.edu
Sent: Wednesday, July 16, 2014 5:59 PM
To: Maik Riechert maik.riech...@arcor.de
Cc: cf-metadata@cgd.ucar.edu
Subject: Re: [CF-metadata] Date/time and leap seconds
Hi Maik:
Unfortunately, CF references the udunits package which is no longer
