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/2064#issuecomment-381975937,https://api.github.com/repos/pydata/xarray/issues/2064,381975937,MDEyOklzc3VlQ29tbWVudDM4MTk3NTkzNw==,1197350,2018-04-17T12:34:15Z,2018-04-17T12:34:15Z,MEMBER,"I'm glad!

FWIW, I think this is a relatively simple fix within xarray. @xylar, if you are game, we would love to see a PR from you. Could be a good opportunity to learn more about xarray internals.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,314764258
https://github.com/pydata/xarray/issues/2064#issuecomment-381725478,https://api.github.com/repos/pydata/xarray/issues/2064,381725478,MDEyOklzc3VlQ29tbWVudDM4MTcyNTQ3OA==,1197350,2018-04-16T19:44:00Z,2018-04-16T19:44:00Z,MEMBER,But this issue raises an important basic point: we might want different behavior for variables in which `concat_dim` is already a dimension vs. variables for which it is not.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,314764258
https://github.com/pydata/xarray/issues/2064#issuecomment-381722944,https://api.github.com/repos/pydata/xarray/issues/2064,381722944,MDEyOklzc3VlQ29tbWVudDM4MTcyMjk0NA==,1197350,2018-04-16T19:35:12Z,2018-04-16T19:35:12Z,MEMBER,"> so you're fooling xarray into not including the time dimension in your non-time variables by making them coordinates in the above example?

Exactly. They *are* coordinates. Those variables are usually related to grid geometry or constants, as I presume is `refBottomDepth` in your example.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,314764258
https://github.com/pydata/xarray/issues/2064#issuecomment-381717472,https://api.github.com/repos/pydata/xarray/issues/2064,381717472,MDEyOklzc3VlQ29tbWVudDM4MTcxNzQ3Mg==,1197350,2018-04-16T19:15:19Z,2018-04-16T19:15:19Z,MEMBER,"👍 This is a persistent problem for me as well.

I often find myself writing a preprocessor function like this
```python
def process_coords(ds, concat_dim='time', drop=True):
    coord_vars = [v for v in ds.data_vars if concat_dim not in ds[v].dims]
    if drop:
        return ds.drop(coord_vars)
    else:
        return ds.set_coords(coord_vars)
ds = xr.open_mfdataset('*.nc', preprocess=process_coords)
```

The reason to drop the coordinates is to avoid the comparison that happens when you concatenate coords.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,314764258