issue_comments

Table actions

5 rows where author_association = "MEMBER" and issue = 336371511 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

issue 1

  • Add automatic chunking to open_rasterio · 5 ✖

author_association 1

  • MEMBER · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
808344694 https://github.com/pydata/xarray/pull/2255#issuecomment-808344694 https://api.github.com/repos/pydata/xarray/issues/2255 MDEyOklzc3VlQ29tbWVudDgwODM0NDY5NA== keewis 14808389 2021-03-26T16:19:38Z 2021-03-26T16:19:38Z MEMBER

with #4697 and the fact that this seems to have been included in rioxarray: should we close this?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add automatic chunking to open_rasterio 336371511
514707122 https://github.com/pydata/xarray/pull/2255#issuecomment-514707122 https://api.github.com/repos/pydata/xarray/issues/2255 MDEyOklzc3VlQ29tbWVudDUxNDcwNzEyMg== fmaussion 10050469 2019-07-24T16:36:06Z 2019-07-24T16:36:06Z MEMBER

I'm curious, are there features in rioxarray that could be pushed upstream?

Depends on what the xarray maintainers would like to add. I would definitely like to see the open_rasterio function in rioxarray absorbed back into xarray. Things have just been really slow moving with the other PRs/issues.

Put another way: why don't we put all the logic in rioxarray and make rioxarray an optional dependency of xarray to open rio files?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add automatic chunking to open_rasterio 336371511
514687031 https://github.com/pydata/xarray/pull/2255#issuecomment-514687031 https://api.github.com/repos/pydata/xarray/issues/2255 MDEyOklzc3VlQ29tbWVudDUxNDY4NzAzMQ== mrocklin 306380 2019-07-24T15:43:04Z 2019-07-24T15:43:04Z MEMBER

I'm glad to hear it! I'm curious, are there features in rioxarray that could be pushed upstream?

On Wed, Jul 24, 2019 at 8:39 AM Alan D. Snow notifications@github.com wrote:

I've abandoned this PR. If anyone has time to pick it up, that would be welcome.

I appreciate you staring this! Based on this PR, I added the feature into rioxarray here: corteva/rioxarray#31 https://github.com/corteva/rioxarray/pull/31 (released in version 0.0.9).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/pull/2255?email_source=notifications&email_token=AACKZTHDF5BOUXGTTZ55M3DQBBZRJA5CNFSM4FHJIU5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2WXTEQ#issuecomment-514685330, or mute the thread https://github.com/notifications/unsubscribe-auth/AACKZTDNYY2CK4WV4FBASGTQBBZRJANCNFSM4FHJIU5A . 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add automatic chunking to open_rasterio 336371511
514682988 https://github.com/pydata/xarray/pull/2255#issuecomment-514682988 https://api.github.com/repos/pydata/xarray/issues/2255 MDEyOklzc3VlQ29tbWVudDUxNDY4Mjk4OA== mrocklin 306380 2019-07-24T15:33:10Z 2019-07-24T15:33:10Z MEMBER

I've abandoned this PR. If anyone has time to pick it up, that would be welcome. I think that it would have positive impact.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add automatic chunking to open_rasterio 336371511
401028473 https://github.com/pydata/xarray/pull/2255#issuecomment-401028473 https://api.github.com/repos/pydata/xarray/issues/2255 MDEyOklzc3VlQ29tbWVudDQwMTAyODQ3Mw== mrocklin 306380 2018-06-28T13:08:58Z 2018-06-29T14:00:19Z MEMBER

```python import os if not os.path.exists('myfile.tif'): import requests response = requests.get('https://oin-hotosm.s3.amazonaws.com/5abae68e65bd8f00110f3e42/0/5abae68e65bd8f00110f3e43.tif') with open('myfile.tif', 'wb') as f: f.write(response.content)

import dask dask.config.set({'array.chunk-size': '1MiB'})

import xarray as xr ds = xr.open_rasterio('myfile.tif', chunks=True) # this only reads metadata to start

ds.chunks ((1, 1, 1), (1024, 1024, 1024, 1024, 1024, 1024, 1024, 1024, 1024, 1024, 136), (1024, 1024, 1024, 1024, 1024, 1024, 1024, 1024, 1024, 995)) ```

Also depends on https://github.com/dask/dask/pull/3679 . Without that PR it will use values that are similar, but don't precisely align with 1024.

Oh, I should point out that the image has tiles of size (512, 512)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add automatic chunking to open_rasterio 336371511

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