issue_comments: 454531015

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/issues/2649#issuecomment-454531015 https://api.github.com/repos/pydata/xarray/issues/2649 454531015 MDEyOklzc3VlQ29tbWVudDQ1NDUzMTAxNQ== 6628425 2019-01-15T20:02:18Z 2019-01-15T20:02:18Z MEMBER

This was an internal bug in xarray introduced in version 0.11.2, which through #2651 should be fixed in the next release. Probably the cleanest way to work around it for now would be to temporarily downgrade to xarray 0.11.0.

If there is something in xarray > 0.11.0 that you need, another option would be to install the master (unreleased) version of xarray, which includes the bug fix in #2651.

Finally, a cruder workaround (if you want to stick with xarray 0.11.2) in the case that time is encoded with the UTC time zone (and not some other time zone) would be to drop the time zone from the units encoding, e.g. with the example file shared above: ``` In [1]: import xarray

In [2]: ds = xarray.open_dataset('example.nc')

In [3]: ds.time.encoding['units'] Out[3]: 'seconds since 1970-01-01T00:00:00+00:00'

In [4]: ds.time.encoding['units'] = 'seconds since 1970-01-01T00:00:00'

In [5]: ds.to_netcdf('out.nc') ```

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   396063731