home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where author_association = "NONE" and issue = 219321876 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

  • darothen 2
  • stale[bot] 1

issue 1

  • Saving to netCDF with 0D dimension doesn't work · 3 ✖

author_association 1

  • NONE · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
493632647 https://github.com/pydata/xarray/issues/1352#issuecomment-493632647 https://api.github.com/repos/pydata/xarray/issues/1352 MDEyOklzc3VlQ29tbWVudDQ5MzYzMjY0Nw== stale[bot] 26384082 2019-05-18T00:21:36Z 2019-05-18T00:21:36Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the stale label; otherwise it will be marked as closed automatically

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Saving to netCDF with 0D dimension doesn't work 219321876
292930254 https://github.com/pydata/xarray/issues/1352#issuecomment-292930254 https://api.github.com/repos/pydata/xarray/issues/1352 MDEyOklzc3VlQ29tbWVudDI5MjkzMDI1NA== darothen 4992424 2017-04-10T12:06:52Z 2017-04-10T12:07:03Z NONE

Yeah, I tend to agree, there should be some sort of auto-magic happening. But, I can think of at least two options:

  1. Coerce to array-like, like you do manually in your first comment here. That makes sense if the dimension is important, i.e. it carries useful metadata or encodes something important.

  2. Coerce to an attribute on the Dataset.

I use workflows where I concatenate things like multiple ensemble members into a single file, and I wind up with this pattern all the time. I usually just drop() the offending coordinate, and save it as part of the output filename. This is because tools like cdo really, really don't like non lat-lon-time dimensions, so that can interrupt my workflow sometimes. Saving as an attribute bypasses this issue, but then you lose the ability to retain any metadata that was associated with that coordinate.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Saving to netCDF with 0D dimension doesn't work 219321876
292926691 https://github.com/pydata/xarray/issues/1352#issuecomment-292926691 https://api.github.com/repos/pydata/xarray/issues/1352 MDEyOklzc3VlQ29tbWVudDI5MjkyNjY5MQ== darothen 4992424 2017-04-10T11:48:37Z 2017-04-10T11:48:37Z NONE

@andreas-h you can drop the 0D dimensions:

python d_ = d_.drop(['category', 'species']) d_.to_netcdf(...)

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Saving to netCDF with 0D dimension doesn't work 219321876

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]);
Powered by Datasette · Queries took 3840.689ms · About: xarray-datasette
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows