issues: 199218465

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
199218465 MDU6SXNzdWUxOTkyMTg0NjU= 1195 Bug in dateconversion? 14314623 closed 0     4 2017-01-06T15:25:03Z 2017-01-09T14:27:18Z 2017-01-09T14:27:18Z CONTRIBUTOR      

I noticed an undesired behavior in xarray when using xarray.open_dataset:

running the following in version 0.8.2-90-g2c7730d: import xarray as xr fid = 'dt_global_allsat_msla_uv_20140101_20140829.nc' ds = xr.open_dataset(fid) ds.time gives

<xarray.DataArray 'time' (time: 1)> array(['2013-12-31T19:00:00.000000000-0500'], dtype='datetime64[ns]') Coordinates: * time (time) datetime64[ns] 2014-01-01 Attributes: long_name: Time standard_name: time axis: T

Note the hour is 19, I also encountered files with 20. Since the time in the .nc file is given in 'days since', the expected output would be 00.

Indeed when running version 0.8.2 the output is: <xarray.DataArray 'time' (time: 1)> array(['2014-01-01T00:00:00.000000000'], dtype='datetime64[ns]') Coordinates: * time (time) datetime64[ns] 2014-01-01 Attributes: long_name: Time standard_name: time axis: T Any idea what could cause this?

Sample file used in the example can be found here: https://ufile.io/077da

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1195/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed 13221727 issue

Links from other tables