issue_comments

Table actions

1 row where issue = 782440858 and user = 53100696 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

  • ohiat · 1 ✖

issue 1

  • Opening a tiff with scale_factor/add_offset attrs then saving as zarr and opening causes a UFuncTypeError · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
760459257 https://github.com/pydata/xarray/issues/4784#issuecomment-760459257 https://api.github.com/repos/pydata/xarray/issues/4784 MDEyOklzc3VlQ29tbWVudDc2MDQ1OTI1Nw== ohiat 53100696 2021-01-14T20:32:48Z 2021-01-14T20:32:48Z NONE

I haven't found anywhere where geotiffs are meant to follow cf-conventions and the HDF from which the geotiff was generated doesn't seem to have the scale_factor/add_offset metadata. I think the change that should be made is that when loading a zarr or anything else that is expected to follow CF conventions a type check (and possible type cast) is made before trying to apply scale_factor and add_offset

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Opening a tiff with scale_factor/add_offset attrs then saving as zarr and opening causes a UFuncTypeError 782440858

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