html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/2093#issuecomment-398214607,https://api.github.com/repos/pydata/xarray/issues/2093,398214607,MDEyOklzc3VlQ29tbWVudDM5ODIxNDYwNw==,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}",,318950038
https://github.com/pydata/xarray/issues/2093#issuecomment-398183774,https://api.github.com/repos/pydata/xarray/issues/2093,398183774,MDEyOklzc3VlQ29tbWVudDM5ODE4Mzc3NA==,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}",,318950038
https://github.com/pydata/xarray/issues/2093#issuecomment-387058496,https://api.github.com/repos/pydata/xarray/issues/2093,387058496,MDEyOklzc3VlQ29tbWVudDM4NzA1ODQ5Ng==,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}",,318950038
https://github.com/pydata/xarray/issues/2093#issuecomment-385463527,https://api.github.com/repos/pydata/xarray/issues/2093,385463527,MDEyOklzc3VlQ29tbWVudDM4NTQ2MzUyNw==,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}",,318950038