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/2288#issuecomment-412410121,https://api.github.com/repos/pydata/xarray/issues/2288,412410121,MDEyOklzc3VlQ29tbWVudDQxMjQxMDEyMQ==,1217238,2018-08-13T05:12:05Z,2018-08-13T05:12:05Z,MEMBER,"> Is there a way in xarray to associate these three arrays in a DataArray so that slicing is handled automatically but also not put the arrays in the coordinates? 

Not yet, unfortunately, but this is what https://github.com/pydata/xarray/pull/2302 is trying to solve.

> I could always add this logic myself to geoxarray's version of to_netcdf.

I think this would be the preferred approach.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,341331807
https://github.com/pydata/xarray/issues/2288#issuecomment-405420045,https://api.github.com/repos/pydata/xarray/issues/2288,405420045,MDEyOklzc3VlQ29tbWVudDQwNTQyMDA0NQ==,1217238,2018-07-17T00:18:58Z,2018-07-17T00:18:58Z,MEMBER,"> But I guess that is intended behavior and if the crs is a coordinate then joining things from different projections would not be allowed and raise an exception. However that is exactly what satpy wants/needs to handle in some cases (satellite datasets at different resolutions, multiple 'regions' of from the same overall instrument, two channels from the same instrument with slightly shifted geolocation, etc).

I think it would make more sense to think about using multiple `xarray.Dataset` objects for these use cases, possibly in some sort of hierarchical collection. The notion of `xarray.Dataset` is pretty closely tied to a single grid. The discussion in https://github.com/pydata/xarray/issues/1092 is definitely worth reading.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,341331807