issue_comments

Table actions

4 rows where issue = 1128759050 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 3

author_association 3

issue 1

  • Be able to override calendar in `open_dataset`/`open_mfdataset`/etc OR include another calendar name · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1077728973 https://github.com/pydata/xarray/issues/6259#issuecomment-1077728973 https://api.github.com/repos/pydata/xarray/issues/6259 IC_kwDOAMm_X85APNbN kthyng 3487237 2022-03-24T15:03:50Z 2022-03-24T15:03:50Z NONE

What?! Whoa I did not know about the preprocess option and it looks really powerful! I have been getting the derived datasets to work but I think this would do the job in a more simple and easy-to-understand way. I will give it a try.

intake-xarray should now work with open_mfdataset — I added this as an option, though it's probably not in a release yet.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Be able to override calendar in `open_dataset`/`open_mfdataset`/etc OR include another calendar name 1128759050
1077043912 https://github.com/pydata/xarray/issues/6259#issuecomment-1077043912 https://api.github.com/repos/pydata/xarray/issues/6259 IC_kwDOAMm_X85AMmLI dcherian 2448579 2022-03-24T04:00:52Z 2022-03-24T04:00:52Z MEMBER

You could do the same correction with the preprocess kwarg to open_mfdataset (which can handle a single file). But if intake only uses open_dataset we could consider adding preprocess to open_dataset

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Be able to override calendar in `open_dataset`/`open_mfdataset`/etc OR include another calendar name 1128759050
1035604231 https://github.com/pydata/xarray/issues/6259#issuecomment-1035604231 https://api.github.com/repos/pydata/xarray/issues/6259 IC_kwDOAMm_X849uhEH kthyng 3487237 2022-02-10T22:39:16Z 2022-02-10T22:39:16Z NONE

Thanks @d70-t for the idea! I haven't tried out the derived datasets capabilities in intake, but I'll give them a try. Sounds like they could be pretty powerful.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Be able to override calendar in `open_dataset`/`open_mfdataset`/etc OR include another calendar name 1128759050
1034098265 https://github.com/pydata/xarray/issues/6259#issuecomment-1034098265 https://api.github.com/repos/pydata/xarray/issues/6259 IC_kwDOAMm_X849oxZZ d70-t 6574622 2022-02-09T19:05:44Z 2022-02-09T19:05:44Z CONTRIBUTOR

This sounds like it could theoretically be handled using intake derived datasets. To be fair, derived datasets are probably still in their early stages. But the basic idea would be to apply arbitrary transformations to a dataset after it has been opened (e.g. with decode_cf=False) and represent the outcome of this transformation as an entry in the catalog. A suitable transformation function might be something like: python def fix_calendar(ds): ds.time.calendar = "proleptic_gregorian" return xr.decode_cf(ds) ... but maybe it is still more convenient or useful to handle it in xarray directly (e.g. I don't know if stac has a similar approach).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Be able to override calendar in `open_dataset`/`open_mfdataset`/etc OR include another calendar name 1128759050

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