issues: 146908323
This data as json
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
146908323 | MDU6SXNzdWUxNDY5MDgzMjM= | 821 | datetime units interpretation wrong in special cases | 206773 | closed | 0 | 3 | 2016-04-08T11:55:44Z | 2016-04-09T16:55:10Z | 2016-04-09T16:54:10Z | NONE | 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 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 |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/821/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | 13221727 | issue |