issues

Table actions

4 rows where state = "closed", type = "pull" and user = 3924836 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 1

  • pull · 4 ✖

state 1

  • closed · 4 ✖

repo 1

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
1639815690 PR_kwDOAMm_X85M2xOo 7671 Delete built-in rasterio backend scottyhq 3924836 closed 0     0 2023-03-24T17:55:50Z 2023-03-29T17:31:27Z 2023-03-29T17:31:26Z MEMBER   0 pydata/xarray/pulls/7671

Following up on #5808, which deprecated XR.open_rasterio in favor of rioxarray this PR finally removes open_rasterio() entirely 2 years later!

Closes #2314, closes #2535, closes #3489, closes #3776, closes #4655, closes #5207 (either outdated or ‘wontfix’ in favor of rioxarray)

Maybe closes:

3921

Discussion closure (mark answer as ‘use rioxarray discussions’?):

5840, #6485, #7327

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/7671/reactions",
    "total_count": 2,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 2,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
473142248 MDExOlB1bGxSZXF1ZXN0MzAxMzY4NjIw 3162 changed url for rasterio network test scottyhq 3924836 closed 0     10 2019-07-26T02:06:20Z 2019-07-31T00:28:53Z 2019-07-31T00:28:46Z MEMBER   0 pydata/xarray/pulls/3162

fix failing rasterio network test by simplifying test and using same image url as rasterio library test suite - [x ] Closes #3083

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3162/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
387123860 MDExOlB1bGxSZXF1ZXN0MjM1NjgyMjk4 2589 added some logic to deal with rasterio objects in addition to filepaths scottyhq 3924836 closed 0     14 2018-12-04T05:13:33Z 2019-07-05T23:13:49Z 2018-12-23T19:02:53Z MEMBER   0 pydata/xarray/pulls/2589

…h strings

  • [x] Closes #2588
  • [x] Tests added (for all bug fixes or enhancements)
  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API (remove if this change should not be visible to users, e.g., if it is an internal clean-up, or if this is part of a larger project that will be documented later)
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2589/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
412645481 MDExOlB1bGxSZXF1ZXN0MjU0ODA3NTgz 2782 enable loading remote hdf5 files scottyhq 3924836 closed 0     9 2019-02-20T21:51:02Z 2019-03-16T00:36:12Z 2019-03-16T00:35:58Z MEMBER   0 pydata/xarray/pulls/2782

Enable loading remote hdf5 files. Will require h5py>2.9.0 and some changes to https://github.com/shoyer/h5netcdf. I've current just made a quick hack change to backends/api.py, so further tests are needed. Pinging @jhamman, @mrocklin, and @rabernat for thoughts on this.

Here is a short notebook demonstrating how this works: https://gist.github.com/scottyhq/790bf19c7811b5c6243ce37aae252ca1

  • [x] Closes #2781
  • [x] Tests added
  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2782/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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