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/1614#issuecomment-398203726,https://api.github.com/repos/pydata/xarray/issues/1614,398203726,MDEyOklzc3VlQ29tbWVudDM5ODIwMzcyNg==,8204522,2018-06-18T21:36:32Z,2018-06-18T21:36:32Z,NONE,"@shoyer, I assume you are referring to the `keep_attrs` option. Is there a way to persist `attrs` during arithmetic options? I find myself writing a bunch of boilerplate to transfer the wealth of metadata included with most netCDF files.

I realize that adding a module-level or `DataArray` instance-specific `maintain_attrs` configuration flag (as discussed in #131, #988, #1271) could be problematic, but this strikes me as complexity worth adding. The current approach of dropping all metadata (not just units) seems heavy-handed and unintuitive for new/casual users. As you mentioned in #1271, better to have stale metadata than no metadata at all.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503
https://github.com/pydata/xarray/issues/1614#issuecomment-398183428,https://api.github.com/repos/pydata/xarray/issues/1614,398183428,MDEyOklzc3VlQ29tbWVudDM5ODE4MzQyOA==,5225190,2018-06-18T20:23:41Z,2018-06-18T20:23:52Z,NONE,"> are you referring to a different issue? the first post only summarizes some simple proposed rules.

No, just the proposed feature to keep or delete metadata based on the various operations. Is this behaviour already part of the library, and this issue is just to clarify the intended behaviour, or is this a feature proposal?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503
https://github.com/pydata/xarray/issues/1614#issuecomment-397966050,https://api.github.com/repos/pydata/xarray/issues/1614,397966050,MDEyOklzc3VlQ29tbWVudDM5Nzk2NjA1MA==,5225190,2018-06-18T07:32:08Z,2018-06-18T07:32:08Z,NONE,"Also - might I suggest you consider some kind of history tracker as part of the metadata propagation? Perhaps metadata could be saved from each step of a set of operations, so that there is a full paper trail for the set of operations have been applied to the data. It could however get complicated to merge together objects with their own separate histories, especially if they ultimately descend from the same original data set.

This would be very relevant for scientific analyses.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503
https://github.com/pydata/xarray/issues/1614#issuecomment-397965247,https://api.github.com/repos/pydata/xarray/issues/1614,397965247,MDEyOklzc3VlQ29tbWVudDM5Nzk2NTI0Nw==,5225190,2018-06-18T07:28:32Z,2018-06-18T07:28:32Z,NONE,"Hi, this feature would be very relevant to the intended use case of a project I'd like to use `xarray` for. Is the behaviour discussed in the first post implemented anywhere, e.g. in the trunk, for me to play with?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503
https://github.com/pydata/xarray/issues/1614#issuecomment-362624658,https://api.github.com/repos/pydata/xarray/issues/1614,362624658,MDEyOklzc3VlQ29tbWVudDM2MjYyNDY1OA==,5442433,2018-02-02T15:54:41Z,2018-02-02T15:54:41Z,NONE,"I am also interested. In terms of the table from @jhamman I am in principle ok with. However, there could be an option to refer to the original attrs in order to provide provenance even on operations like reduce and arithmetic. The idea here is reproducibility and tractability. Maybe an 'origin' attribute?","{""total_count"": 3, ""+1"": 3, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503
https://github.com/pydata/xarray/issues/1614#issuecomment-343617001,https://api.github.com/repos/pydata/xarray/issues/1614,343617001,MDEyOklzc3VlQ29tbWVudDM0MzYxNzAwMQ==,8204522,2017-11-10T23:50:18Z,2017-11-10T23:50:18Z,NONE,"I'd also suggest that a global [option](http://xarray.pydata.org/en/stable/generated/xarray.set_options.html) of always_keep_attrs=True would be useful. While I understand the logic of dropping units during certain operations, it makes attributes unusable for storing other miscellaneous metadata, e.g. on data provenance. As a recent xarray convert, this behavior has been frustrating.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,264049503