issue_comments

Table actions

4 rows where issue = 318950038 and user = 601025 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

issue 1

  • Default chunking in GeoTIFF images · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
398214607 https://github.com/pydata/xarray/issues/2093#issuecomment-398214607 https://api.github.com/repos/pydata/xarray/issues/2093 MDEyOklzc3VlQ29tbWVudDM5ODIxNDYwNw== ebo 601025 2018-06-18T22:24:18Z 2018-06-18T22:24:18Z NONE

On Jun 18 2018 4:03 PM, Fabien Maussion wrote:

Has a default GeoTIFF chunk been implemented?

No, unfortunately.

ok. Maybe the overall chunking issue has been sorted. I will try to look into this and see what is working now related to this issue.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Default chunking in GeoTIFF images 318950038
398183774 https://github.com/pydata/xarray/issues/2093#issuecomment-398183774 https://api.github.com/repos/pydata/xarray/issues/2093 MDEyOklzc3VlQ29tbWVudDM5ODE4Mzc3NA== ebo 601025 2018-06-18T20:24:53Z 2018-06-18T20:24:53Z NONE

one of the issues related to this has been closed. Has a default GeoTIFF chunk been implemented?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Default chunking in GeoTIFF images 318950038
387058496 https://github.com/pydata/xarray/issues/2093#issuecomment-387058496 https://api.github.com/repos/pydata/xarray/issues/2093 MDEyOklzc3VlQ29tbWVudDM4NzA1ODQ5Ng== ebo 601025 2018-05-07T13:07:16Z 2018-05-07T13:07:16Z NONE

that would definitely work for me.

On May 7 2018 6:43 AM, Zac Hatfield-Dodds wrote:

With the benefit of almost a year's worth of procrastination, I think the best approach is to take the heuristics from #1440, but only support chunks=True - if a decent default heuristic isn't good enough, the user can specify exact chunks.

The underlying logic for this issue would be identical to that of

1440, so supporting both is "just" a matter of plumbing it in

correctly.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Default chunking in GeoTIFF images 318950038
385463527 https://github.com/pydata/xarray/issues/2093#issuecomment-385463527 https://api.github.com/repos/pydata/xarray/issues/2093 MDEyOklzc3VlQ29tbWVudDM4NTQ2MzUyNw== ebo 601025 2018-04-30T17:07:43Z 2018-04-30T17:07:43Z NONE

Most of the standard internal chunked (or what I believe to be called 'tiled' by the GIS community) is 256x256 (see: http://www.gdal.org/frmt_gtiff.html TILED=YES BLOCKXSIZE=n and BLOCKYSIZE=n). This is used when viewing images within a given region of interest or window. You can really tell the difference in speed between the tiled and stripped images (which has a blocksize 1x<width>).

@mrocklin, I agree that we might want to aggregate some number of them, but we would need to get some automation up front and sort out how we want to determine the expansion. Adding to the #1440 discussion mentioned, there will likely be advantage in increasing the block sizes in given directions.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Default chunking in GeoTIFF images 318950038

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