issue_comments

Table actions

3 rows where issue = 291485366 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

author_association 2

issue 1

  • Option to make DataArray.transpose also transpose coords · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
398484964 https://github.com/pydata/xarray/issues/1856#issuecomment-398484964 https://api.github.com/repos/pydata/xarray/issues/1856 MDEyOklzc3VlQ29tbWVudDM5ODQ4NDk2NA== shoyer 1217238 2018-06-19T17:43:07Z 2018-06-19T17:43:07Z MEMBER

Honestly, we could probably consider the DataArray behavior to be a bug. In general DataArray methods should work exactly like Dataset methods on a Dataset with a single data variable. (In fact, this is how we implement many DataArray methods.)

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Option to make DataArray.transpose also transpose coords 291485366
398481880 https://github.com/pydata/xarray/issues/1856#issuecomment-398481880 https://api.github.com/repos/pydata/xarray/issues/1856 MDEyOklzc3VlQ29tbWVudDM5ODQ4MTg4MA== NicWayand 1117224 2018-06-19T17:33:03Z 2018-06-19T17:33:03Z NONE

Also hitting this issue. (Use case: formatting netcdf files for some R code that does not have labeled indexing... ugh). Thanks @phausamann for the work around. Default transposing of coods makes sense to me.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Option to make DataArray.transpose also transpose coords 291485366
361303126 https://github.com/pydata/xarray/issues/1856#issuecomment-361303126 https://api.github.com/repos/pydata/xarray/issues/1856 MDEyOklzc3VlQ29tbWVudDM2MTMwMzEyNg== shoyer 1217238 2018-01-29T16:32:09Z 2018-01-29T16:32:09Z MEMBER

To be honest, I'm not sure skipping coordinates was actually intentional. In most cases, I suspect transposing coordinates simply doesn't matter because either (1) there are no multi-dimensional coordinates or (2) xarray usually doesn't care much about dimension order (so it doesn't matter).

I would support adding a transpose_coords argument, but we should also consider switching the default behavior in the future to transpose_coords=True.

Anyone else have opinions on this API?

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Option to make DataArray.transpose also transpose coords 291485366

Advanced export

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

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);