How should we handle boundless reads?

[kylebarron]

How should async-geotiff be handling boundless reads? Should they be opt-in/opt-out? What should the default be?

I just encountered a failing test in #82 where the overview has a tile size of 512x512 but the image is only 256x256:

IFD
    Id      Size           BlockSize     Decimation
    0       512x512        512x512       0
    1       256x256        512x512       2
    2       128x128        512x512       4

The array comparison with rasterio failed because rasterio auto-cropped the result to 256x256 (setting boundless=False) by default.

[kylebarron]

#82 sidestepped the question for now by just using boundless=True in the rasterio read call

[kylebarron]

Boundless reads should be the default

You don’t want users to have to think about where tile is in the image and implement different logic if tile is in middle of image or at the borders

And boundless reads work well with the array/mask interface because you just mask out the area out of bounds.

from @geospatial-jeff