Hi,
after reading
http://cdf.gsfc.nasa.gov/html/leapseconds_requirements.html I'm a bit
confused on how CF handles times for the netcdf world. It seems as if
the 'seconds since' convention is basically POSIX time in regards to how
leap seconds are handled. Quoting wiki " Due to its handling of leap
seconds, it is neither a linear representation of time nor a true
representation of UTC". This means that any dataset with <= 1 second
resolution which covers the moment a leap second happens will have a
problem encoding the time using the existing units convention.
I first posted this issue on the netcdf4-python tracker:
https://github.com/Unidata/netcdf4-python/issues/280
Is this an issue which was discussed before and is there any solution?
Cheers
Maik
_______________________________________________
CF-metadata mailing list
[email protected]
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
