issues
2 rows where repo = 13221727, state = "open" and user = 2444231 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at ▲ | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
578427969 | MDU6SXNzdWU1Nzg0Mjc5Njk= | 3853 | Custom Table when opening GRIB Files | pgierz 2444231 | open | 0 | 8 | 2020-03-10T08:58:42Z | 2022-04-27T14:34:02Z | NONE | Hello, I'd like to open some old-school Grib files from one of our climate models. I'm using the
So, would it somehow be possible to provide a code table to be used when opening grb files? I have files next to my output where the codes are stored. An example is below. I can imagine something like:
Would this be difficult to implement? Cheers, Paul
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/3853/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | issue | ||||||||
894498459 | MDU6SXNzdWU4OTQ0OTg0NTk= | 5332 | Progressbar for groupby operations? | pgierz 2444231 | open | 0 | 2 | 2021-05-18T15:19:19Z | 2021-05-19T01:27:55Z | NONE | I recently learned that Would it be simple to implement something similar in Xarray? The documentation seems to read as if the groupby is heavily inspired by pandas. Is your feature request related to a problem? Please describe. No, everything works as expected, this would just be a "quality of life" improvement. Describe the solution you'd like The implementation in tqdm states:
I suppose something similar would need to be implemented in Xarray, and then we might be able to copy the tqdm logic. Describe alternatives you've considered I could loop over whatever dimension I have and make my own progress bar, but that seems like defeating the purpose of groupby. |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/5332/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray 13221727 | issue |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issues] ( [id] INTEGER PRIMARY KEY, [node_id] TEXT, [number] INTEGER, [title] TEXT, [user] INTEGER REFERENCES [users]([id]), [state] TEXT, [locked] INTEGER, [assignee] INTEGER REFERENCES [users]([id]), [milestone] INTEGER REFERENCES [milestones]([id]), [comments] INTEGER, [created_at] TEXT, [updated_at] TEXT, [closed_at] TEXT, [author_association] TEXT, [active_lock_reason] TEXT, [draft] INTEGER, [pull_request] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [state_reason] TEXT, [repo] INTEGER REFERENCES [repos]([id]), [type] TEXT ); CREATE INDEX [idx_issues_repo] ON [issues] ([repo]); CREATE INDEX [idx_issues_milestone] ON [issues] ([milestone]); CREATE INDEX [idx_issues_assignee] ON [issues] ([assignee]); CREATE INDEX [idx_issues_user] ON [issues] ([user]);