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-451681899,https://api.github.com/repos/pydata/xarray/issues/2649,451681899,MDEyOklzc3VlQ29tbWVudDQ1MTY4MTg5OQ==,1217238,2019-01-05T18:59:23Z,2019-01-05T18:59:23Z,MEMBER,"For reference, the issue here appears to be that the time variable's `units` attribute specifies a timezone:
```
	int64 time(time) ;
		time:standard_name = forecast_reference_time ;
		time:long_name = initial time of forecast ;
		time:units = seconds since 1970-01-01T00:00:00+00:00 ;
		time:calendar = proleptic_gregorian ;
```

And here is the relevant description from [CF conventions](http://cfconventions.org/cf-conventions/cf-conventions.html#time-coordinate):
> The reference time string (appearing after the identifier since) may include date alone; date and time; or date, time, and time zone. ...
> 
> Note: if the time zone is omitted the default is UTC, and if both time and time zone are omitted the default is 00:00:00 UTC.

Given that xarray uses timezone agnostic `np.datetime64` and `cftime.datetime` objects, it does seem like the best course of action here is to decode dates to UTC and then remove the timezone.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,396063731