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/6806#issuecomment-1188305230,https://api.github.com/repos/pydata/xarray/issues/6806,1188305230,IC_kwDOAMm_X85G1BlO,35968931,2022-07-18T21:00:29Z,2022-07-18T21:00:29Z,MEMBER,"> I'm curious to see if in that specific case using a custom index for staggered grid coordinates wouldn't work as an alternative solution. The alignment rules are pretty strict (same index type + same sequence of coordinate names & dims). Not 100% sure if that applies in the xgcm case, but in theory it would raise an error regardless of the join method if you try to align objects that have broadcastable coordinates with incompatible indexes.

This is on my to-do list to think about really hard :sweat_smile: 

I think one problem would be that sometimes a different grid position implies a different length coordinate array, e.g. ""outer"" vs ""center"" is larger by one element.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1308371056