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/3349#issuecomment-565600745,https://api.github.com/repos/pydata/xarray/issues/3349,565600745,MDEyOklzc3VlQ29tbWVudDU2NTYwMDc0NQ==,6628425,2019-12-13T20:39:21Z,2019-12-13T20:39:21Z,MEMBER,"Excellent, looking forward to seeing it in a PR!","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,499477363
https://github.com/pydata/xarray/issues/3349#issuecomment-565462443,https://api.github.com/repos/pydata/xarray/issues/3349,565462443,MDEyOklzc3VlQ29tbWVudDU2NTQ2MjQ0Mw==,6628425,2019-12-13T14:33:53Z,2019-12-13T14:33:53Z,MEMBER,"If I understand correctly, `pd.to_numeric` (and its inverse) works because it always uses 1970-01-01T00:00:00 as the reference date.  Could we do something similar when working with cftime dates?

Within xarray we typically convert dates to numeric values (e.g. when doing interpolation) using `xarray.core.duck_array_ops.datetime_to_numeric`, which takes an optional `offset` argument to control the reference date.  Would it work to always make sure to pass 1970-01-01T00:00:00 with the appropriate calendar type as the offset when constructing the ordinal x-coordinate for `polyfit`/`polyval`?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,499477363