issue_comments

Table actions

4 rows where issue = 146975644 and user = 206773 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • forman · 4 ✖

issue 1

  • value scaling wrong in special cases · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
208719528 https://github.com/pydata/xarray/issues/822#issuecomment-208719528 https://api.github.com/repos/pydata/xarray/issues/822 MDEyOklzc3VlQ29tbWVudDIwODcxOTUyOA== forman 206773 2016-04-12T05:54:43Z 2016-04-12T05:54:43Z NONE

Fantastic, thanks!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   value scaling wrong in special cases 146975644
208339095 https://github.com/pydata/xarray/issues/822#issuecomment-208339095 https://api.github.com/repos/pydata/xarray/issues/822 MDEyOklzc3VlQ29tbWVudDIwODMzOTA5NQ== forman 206773 2016-04-11T13:21:25Z 2016-04-11T13:21:25Z NONE

With h5py the data is read correctly too.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   value scaling wrong in special cases 146975644
208243175 https://github.com/pydata/xarray/issues/822#issuecomment-208243175 https://api.github.com/repos/pydata/xarray/issues/822 MDEyOklzc3VlQ29tbWVudDIwODI0MzE3NQ== forman 206773 2016-04-11T09:10:41Z 2016-04-11T09:10:41Z NONE

Ok, I'll submit a netCDF issue then.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   value scaling wrong in special cases 146975644
208214490 https://github.com/pydata/xarray/issues/822#issuecomment-208214490 https://api.github.com/repos/pydata/xarray/issues/822 MDEyOklzc3VlQ29tbWVudDIwODIxNDQ5MA== forman 206773 2016-04-11T08:02:30Z 2016-04-11T09:08:34Z NONE

Just found that the valid_min/valid_max attributes are not directly part of the CF convention but the NUG convention and applying to byte only according to CF Section 2.2 Data Types

All integer types are treated by the netCDF interface as signed. It is possible to treat the byte type as unsigned by using the NUG convention of indicating the unsigned range using the valid_min, valid_max, or valid_range attributes.

As for for #821, Panoply shows the correct values for the same file: 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   value scaling wrong in special cases 146975644

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]);