issue_comments: 474601105

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/521#issuecomment-474601105 https://api.github.com/repos/pydata/xarray/issues/521 474601105 MDEyOklzc3VlQ29tbWVudDQ3NDYwMTEwNQ== 6628425 2019-03-19T21:59:08Z 2019-03-19T21:59:08Z MEMBER

Thanks -- in looking at the metadata it seems there is nothing unusual about the 'd2' dimension (in normal circumstances we should be able to decode N-D variables to dates, regardless of their type).

My feeling is that the issue here remains the fact that cftime dates do not support year zero (see the upstream issue @rabernat mentioned earlier: Unidata/netcdf4-python#442). That said, it's surprising that dropping the 'time_bounds' variable seems to be a workaround for this issue, because the 'time' variable (which remains in the dataset) still has units with a reference date of year zero.

If you don't mind, could you provide me with two more things? - What the time coordinate looks like after your workaround in https://github.com/pydata/xarray/issues/521#issuecomment-474580481 - What the traceback looks like if you try to open the file normally, e.g. ds = xr.open_dataset('some_CESM_output_file.nc')?

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