issue_comments
6 rows where issue = 392361367 and user = 4806877 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Adding mask to open_rasterio · 6 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 867648515 | https://github.com/pydata/xarray/pull/2618#issuecomment-867648515 | https://api.github.com/repos/pydata/xarray/issues/2618 | MDEyOklzc3VlQ29tbWVudDg2NzY0ODUxNQ== | jsignell 4806877 | 2021-06-24T13:44:33Z | 2021-06-24T13:44:33Z | CONTRIBUTOR | I'm fine with this being closed. TBH I had totally forgotten about it :grimacing: |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Adding mask to open_rasterio 392361367 | |
| 487052582 | https://github.com/pydata/xarray/pull/2618#issuecomment-487052582 | https://api.github.com/repos/pydata/xarray/issues/2618 | MDEyOklzc3VlQ29tbWVudDQ4NzA1MjU4Mg== | jsignell 4806877 | 2019-04-26T13:15:40Z | 2019-04-26T13:15:40Z | CONTRIBUTOR |
Do you mean write a test to do this, or just check it locally? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Adding mask to open_rasterio 392361367 | |
| 487046879 | https://github.com/pydata/xarray/pull/2618#issuecomment-487046879 | https://api.github.com/repos/pydata/xarray/issues/2618 | MDEyOklzc3VlQ29tbWVudDQ4NzA0Njg3OQ== | jsignell 4806877 | 2019-04-26T12:56:10Z | 2019-04-26T12:56:10Z | CONTRIBUTOR | Yeah I have some time to finish it up. Looking back at it now it seems like |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Adding mask to open_rasterio 392361367 | |
| 448641329 | https://github.com/pydata/xarray/pull/2618#issuecomment-448641329 | https://api.github.com/repos/pydata/xarray/issues/2618 | MDEyOklzc3VlQ29tbWVudDQ0ODY0MTMyOQ== | jsignell 4806877 | 2018-12-19T15:45:04Z | 2018-12-19T15:45:04Z | CONTRIBUTOR | I did as @snowman2 suggested but filled the mask with nans at the end. Since it is now using rasterio directly this should address @fmaussion's concern about |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Adding mask to open_rasterio 392361367 | |
| 448633729 | https://github.com/pydata/xarray/pull/2618#issuecomment-448633729 | https://api.github.com/repos/pydata/xarray/issues/2618 | MDEyOklzc3VlQ29tbWVudDQ0ODYzMzcyOQ== | jsignell 4806877 | 2018-12-19T15:24:28Z | 2018-12-19T15:24:28Z | CONTRIBUTOR | Hmm. Do we really want a np.masked_array or do we just want an array with np.Nans in it? I prefer nans, but I guess the downside is type conversion for ints? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Adding mask to open_rasterio 392361367 | |
| 448629146 | https://github.com/pydata/xarray/pull/2618#issuecomment-448629146 | https://api.github.com/repos/pydata/xarray/issues/2618 | MDEyOklzc3VlQ29tbWVudDQ0ODYyOTE0Ng== | jsignell 4806877 | 2018-12-19T15:11:49Z | 2018-12-19T15:11:49Z | CONTRIBUTOR | I was wondering if we should just pass the mask option to rasterio like that. I'll try it out. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Adding mask to open_rasterio 392361367 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 1