-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
datetime units interpretation wrong in special cases #821
Comments
This may be related to #545 Likely this is due to numeric overflow of some sort in our datetime decoding function. This is the internal function that handles decoding dates if you're interested in digging into this: |
Thanks, I'll give it a try. |
After some testing I found the problem. The single value of the time coordinate is wrong in the files. So it is a file content problem not a problem in the software. Therefore I'll close this issue. However, Panoply displays the time information correctly and I found out why: Panoply correctly interprets the
Details are in Section 7.1 Cell Boundaries |
Hi there,
I have a datetime issue with a certain type of (CF-compliant!) netCDF files orginating from the ESA CCI Sea Surface Temperature project. With other climate data, everthings seems fine.
When I open such a netCDF file, the datetime value(s) of the time dimension seem to be wrong. If I do
I get
The time dimension is
and the time value is
915192000
. Therefore the correctly interpreted time value must be2010-01-01T12:00:00
which is 1981-01-01 00:00:00 plus 915192000 seconds.Here is the link to the data: ftp://anon-ftp.ceda.ac.uk/neodc/esacci/sst/data/lt/Analysis/L4/v01.1/2010/01/01/20100101120000-ESACCI-L4_GHRSST-SSTdepth-OSTIA-GLOB_LT-v02.0-fv01.1.nc
I'm not sure whether this is actually a CF-specific issue with which xarray doesn't want to deal with. If so, could you please give some advice to get arround this. I'm sure other xarray lovers will face this issue sooner or later.
Thanks!
-- Norman
The text was updated successfully, but these errors were encountered: