issue_comments: 315782686
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/1480#issuecomment-315782686 | https://api.github.com/repos/pydata/xarray/issues/1480 | 315782686 | MDEyOklzc3VlQ29tbWVudDMxNTc4MjY4Ng== | 17701232 | 2017-07-17T15:04:56Z | 2017-07-17T15:04:56Z | NONE | As far as I know I can imagine this is the intended functionality.
I cannot find where this is the case, apart from when using The issue is perhaps more with the example that you present (of only 1 year data) and expected behaviour. Normally groupby('time.month') would be applied to multiple years of data. i.e. group data by month and find the monthly averages for Jan-Dec for 30 years of data, e.g. a climatology. And so in this case it absolutely makes sense to keep the months as 1 to 12, or something similar (perhaps 'Jan','Feb'etc). Applying a datestring of the first day of the month wouldn't make sense because which year would you choose when you have 30 years of data? If you do want a time series of monthly means, then |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
243270042 |