issues: 297780998
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
297780998 | MDU6SXNzdWUyOTc3ODA5OTg= | 1917 | Decode times adds micro-second noise to standard calendar | 145117 | closed | 0 | 5 | 2018-02-16T13:14:15Z | 2018-02-26T10:28:17Z | 2018-02-26T10:28:17Z | CONTRIBUTOR | Code Sample, a copy-pastable example if possibleI have a simplified NetCDF file with the following header: ```bash netcdf foo { dimensions: time = UNLIMITED ; // (366 currently) x = 2 ; y = 2 ; variables: float time(time) ; time:standard_name = "time" ; time:long_name = "time" ; time:units = "DAYS since 2000-01-01 00:00:00" ; time:calendar = "standard" ; time:axis = "T" ; ... } ``` I would expect xarray to be able to decode these times. It does, but appears to do so incorrectly and without reporting any issues. Note the fractional time added to each date.
Problem descriptionDays since a valid date on a I know that xarray has time issues, for example #118 #521 numpy:#6207 #531 #789 and #848. But all of those appear to address non-standard times. This bug (if it is a bug) seems to occur with a very simple and straight forward calendar, and is silent, so it took me 2 days to figure out what was going on. Output of
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/1917/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | 13221727 | issue |