issues

Table actions

4 rows where repo = 13221727, state = "closed" and user = 3217406 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date), closed_at (date)

type 2

state 1

  • closed · 4 ✖

repo 1

  • xarray · 4 ✖
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 laliberte 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 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 xarray 13221727 issue
195832230 MDExOlB1bGxSZXF1ZXN0OTgxNzAxNDE= 1165 Set a default _FillValue of NaN for float types laliberte 3217406 closed 0     16 2016-12-15T15:20:16Z 2017-09-28T13:20:12Z 2016-12-16T03:11:06Z CONTRIBUTOR   0 pydata/xarray/pulls/1165

This PR attempts to solve #1163 by systematically including a default _FillValue of NaN whenever the user do not explicitly specify a FillValue. The idea is that third party software should work properly in these situations and if they don't then it is a bug on their side.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1165/reactions",
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
197364558 MDExOlB1bGxSZXF1ZXN0OTkyMzg4NzQ= 1181 Add mention of in breaking change about default fill value laliberte 3217406 closed 0     1 2016-12-23T12:51:39Z 2016-12-23T17:25:41Z 2016-12-23T17:25:37Z CONTRIBUTOR   0 pydata/xarray/pulls/1181

Quick PR to attribute credit to Frederic Laliberte for the default fill value in the .to_netcdf() method.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1181/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
195576963 MDU6SXNzdWUxOTU1NzY5NjM= 1163 User warning / more transparent _FillValue interface for .to_netcdf() laliberte 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 NaNs 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 xarray 13221727 issue

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [active_lock_reason] TEXT,
   [draft] INTEGER,
   [pull_request] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [state_reason] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
);
CREATE INDEX [idx_issues_repo]
    ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
    ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
    ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
    ON [issues] ([user]);