Sean Gillies

Closed by #1427. Work on other modules shall be tracked in new tickets.

@daniel-j-h GDAL's resolution of WMS tiles is hidden by its API and is not available to rasterio. We don't know exactly which tiles it has requested or retrieved and we...

@ldesousa show_hist is unsophisticated and requires the entire dataset to be loaded into memory. In your case, your dataset is ~62 GB, too large. Hence the error. I'm marking this...

@danilobellini yes, it should be possible by extending 1) the profile property and 2) the keyword arguments of `rasterio.open()` and the dataset class constructor. I think it's reasonable to expect...

This one is pretty complicated in fact and will have to wait until after 1.0.

@HarryDolan indeed, very related.

@eseglem read-only, at first. The win here is being able to read a small fraction of the dataset's bytes to get metadata or an overview level. My hypothesis is that...

@mothersup thanks for the report. I can confirm the discrepancy. @rouault rasterio's fillnodata takes a band from an in-memory dataset with no nodata set and a mask identifying which pixels...

@rouault thanks! Was the number of smoothing iterations not related after all? I think it wasn't, because I saw a discrepancy between the two approaches even with no smoothing. I'm...

@rouault sorry, false alarm on my part. The patch resolves the discrepancy completely as far as I can see. ### gdal ```python >>> from osgeo import gdal >>> import numpy...