issues: 219692578

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
219692578 MDU6SXNzdWUyMTk2OTI1Nzg= 1354 concat automagically outer-joins coordinates 3404817 closed 0     8 2017-04-05T19:39:07Z 2019-08-07T12:17:07Z 2019-08-07T12:17:07Z CONTRIBUTOR      

I would like to concatenate two netCDF files that have float64 coordinate variables. I thought the coordinate values were the same, but in fact they differ by something in the order of 1e-14.

Using open_mfdataset or concat to merge the datasets, I get a completely different output shape than the two input files have.

This is because concat is somewhere performing an outer join on the coordinates. Now I am wondering where else in my workflows this might happen without my notice...

It would be awesome if there was an option to change this behaviour on concat, open_mfdataset, and auto_combine. I would actually rather make these functions fail if any dimension other than the concatenation dimension differs.

Note: This could also be a special case, because ```python

(ds1.lon == ds2.lon).all() <xarray.DataArray 'lon' ()> array(True, dtype=bool) whilepython (ds1.lon.values == ds2.lon.values).all() False ```

Maybe an interface change could be considered together with that discussed in #1340?

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1354/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed 13221727 issue

Links from other tables