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/1352#issuecomment-292930254,https://api.github.com/repos/pydata/xarray/issues/1352,292930254,MDEyOklzc3VlQ29tbWVudDI5MjkzMDI1NA==,4992424,2017-04-10T12:06:52Z,2017-04-10T12:07:03Z,NONE,"Yeah, I tend to agree, there should be some sort of auto-magic happening. But, I can think of at least two options:

1. Coerce to array-like, like you do manually in your first comment here. That makes sense if the dimension is important, i.e. it carries useful metadata or encodes something important.

2. Coerce to an attribute on the Dataset.

I use workflows where I concatenate things like multiple ensemble members into a single file, and I wind up with this pattern all the time. I usually just `drop()` the offending coordinate, and save it as part of the output filename. This is because tools like `cdo` really, really don't like non lat-lon-time dimensions, so that can interrupt my workflow sometimes. Saving as an attribute bypasses this issue, but then you lose the ability to retain any metadata that was associated with that coordinate.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,219321876
https://github.com/pydata/xarray/issues/1352#issuecomment-292926691,https://api.github.com/repos/pydata/xarray/issues/1352,292926691,MDEyOklzc3VlQ29tbWVudDI5MjkyNjY5MQ==,4992424,2017-04-10T11:48:37Z,2017-04-10T11:48:37Z,NONE,"@andreas-h you can drop the 0D dimensions:

``` python
d_ = d_.drop(['category', 'species'])
d_.to_netcdf(...)
```","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,219321876