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/406#issuecomment-97896201,https://api.github.com/repos/pydata/xarray/issues/406,97896201,MDEyOklzc3VlQ29tbWVudDk3ODk2MjAx,2443309,2015-04-30T17:48:47Z,2015-04-30T17:48:47Z,MEMBER,"My thoughts exactly.  The original post mentioned `netcdftime` so I thought it would be beneficial to point that out.  For standard calendards using Python/Numpy datetime objects, microsecond precision is preserved.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,72145600
https://github.com/pydata/xarray/issues/406#issuecomment-97892365,https://api.github.com/repos/pydata/xarray/issues/406,97892365,MDEyOklzc3VlQ29tbWVudDk3ODkyMzY1,2443309,2015-04-30T17:38:15Z,2015-04-30T17:38:15Z,MEMBER,"As a small side note, netcdf4-python doesn't exactly support microseconds.  There is a known precision issue that ends up giving `netcdftime` a minimum time precision of seconds: https://github.com/Unidata/netcdf4-python/issues/321
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,72145600