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/1084#issuecomment-339468720,https://api.github.com/repos/pydata/xarray/issues/1084,339468720,MDEyOklzc3VlQ29tbWVudDMzOTQ2ODcyMA==,500246,2017-10-25T20:56:24Z,2017-10-25T20:56:24Z,CONTRIBUTOR,"Not sure if this is related, but pandas commit https://github.com/pandas-dev/pandas/commit/2310faa109bdfd9ff3ef4fc19a163d790d60c645 triggers xarray issue https://github.com/pydata/xarray/issues/1661 .  Not sure if there exists an easy workaround for that one.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,187591179
https://github.com/pydata/xarray/issues/1084#issuecomment-269886866,https://api.github.com/repos/pydata/xarray/issues/1084,269886866,MDEyOklzc3VlQ29tbWVudDI2OTg4Njg2Ng==,6200806,2017-01-01T00:09:26Z,2017-01-01T00:09:26Z,CONTRIBUTOR,">for now I think it makes sense to keep this in xarray proper

I agree.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,187591179
https://github.com/pydata/xarray/issues/1084#issuecomment-265197666,https://api.github.com/repos/pydata/xarray/issues/1084,265197666,MDEyOklzc3VlQ29tbWVudDI2NTE5NzY2Ng==,6200806,2016-12-06T16:30:43Z,2016-12-06T16:30:43Z,CONTRIBUTOR,">I think your basic example is probably already enough to be useful.

Just to be sure we're not mixing Spencers, this was all @spencerkclark's great work! I had no hand in it.

>I think if we were to include string-based indexing, it would be best if it were completely consistent with the DatetimeIndex version.

I agree.

>So ultimately this raises the question, would we want to add just the field accessors to enable group-by operations for now and add string-based selection (and other features like resample) later, or should we put our heads down and work out a solution for partial datetime string based using netcdftime datetime objects?

Maybe an interim solution is for NetCDFTimeIndex to only accept full datestrings, issuing an error message for partial strings explaining that this functionality is forthcoming?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,187591179
https://github.com/pydata/xarray/issues/1084#issuecomment-264916322,https://api.github.com/repos/pydata/xarray/issues/1084,264916322,MDEyOklzc3VlQ29tbWVudDI2NDkxNjMyMg==,6200806,2016-12-05T17:20:13Z,2016-12-05T17:20:13Z,CONTRIBUTOR,">This looks pretty sane to me, though of course it's still missing a few nice things you can do with datetime64 (e.g., reindex and partial datetime string selection).

@shoyer and others, is there a well-defined list of required features that the new index object would need to satisfy in order to be considred for inclusion in xarray?  Are the two that you mentioned must-haves?  Are there others?

Wanting to make sure we're all on the same page in terms of what the target is.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,187591179