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/1931#issuecomment-367417542,https://api.github.com/repos/pydata/xarray/issues/1931,367417542,MDEyOklzc3VlQ29tbWVudDM2NzQxNzU0Mg==,1217238,2018-02-21T18:09:07Z,2018-02-21T18:09:07Z,MEMBER,"Xarray should certainly be raising an informative error message earlier rather than only when writing these files to disk. It should not be possible to create coordinates with inconsistent dimension sizes.

I would hesitate to drop coordinates associated with core dimensions that appear in both the input and output, because there are definitely functions that *do* preserve dimension identity, e.g., for a ufunc that normalizes across a dimension, e.g., `centered_in_time = xr.apply_ufunc(lambda x: x - x.mean(axis=-1), ds, input_core_dims=[['time']], output_core_dims=[['time']])`.

I think your ""Case 2: Specifying a new output dimension name"" should be the recommended pattern here. This already removes all coordinates associated with the input core dimensions (since they are not specified on outputs), so you can simply rename the output dimensions to achieve your desired result, e.g., `dr_out2.rename({'x_new': 'x'})`.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,298834332