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
198742089,MDU6SXNzdWUxOTg3NDIwODk=,1192,Implementing dask.array.coarsen in xarrays,3217406,closed,0,,,19,2017-01-04T15:59:50Z,2019-02-01T16:07:52Z,2019-02-01T16:07:52Z,CONTRIBUTOR,,,,"Would it make sense to implement the [dask.array.coarsen](http://dask.pydata.org/en/latest/array-api.html#dask.array.coarsen) method on xarrays?

In some ways, ``coarsen`` is a generalization of ``reduce``.

Any thoughts?","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/1192/reactions"", ""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue
195576963,MDU6SXNzdWUxOTU1NzY5NjM=,1163,User warning / more transparent _FillValue interface for .to_netcdf(),3217406,closed,0,,,3,2016-12-14T16:23:05Z,2016-12-23T05:44:00Z,2016-12-23T05:44:00Z,CONTRIBUTOR,,,,"Since many tools (for example ``cdo``) do not work well with ``NaN`` values, the default missing value setting for the ``.to_netcdf()`` method is not well-suited to enable optimal data reuse.

One option would be to add a ``fill_value=NaN`` option to ``.to_netcdf()`` and output a warning message whenever ``NaN``s are written to netCDF: ``'The data being written to netCDF includes missing values (NaN) that are often not easily handled by other netCDF softwares. It is strongly encouraged to coerce missing data to a valid yet large floating point value (for example, 1e20 for float) by calling .to_netcdf(..., fill_value=1e20)'.``","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/1163/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue