Sean Gillies

@vincentsarago Rasterio's raison d'être is to be the best Python API for using classic raster data. Not in terms of absolute performance or number of features or format support (it's...

@groutr that would be one way to go, but I'm also interested in addressing the larger-than-memory mosaic problem, so I'm thinking about using a VRT, not an in-memory dataset: https://github.com/rasterio/rasterio/issues/2700....

Sure, decoupling makes sense to me. The `show()` function has its origin in allowing quick plotting of a dataset from within the `rio insp` command: ``` $ rio insp tests/data/RGB.byte.tif...

I sorta wonder if xarray.plot isn't what folks are using these days to plot data? Still, I'm leaving this open.

@geowurster to really make this work we're going to need more access to GDAL's [DriverManager](http://www.gdal.org/classGDALDriverManager.html) than is available in the C API, perhaps using an extension module written in C++....

we've got a workaround for rio-info, so pushing this to post-1.0.

Still a problem for 1.0.5, but work arounds exist. Priority: low.

We should still do this!

@groutr I'm not much in favor of growing the windows API except where we would use new methods to make rasterio's code better or to radically improve usability for common...

Dataset.read has more features than ReadRaster and more overhead. Sample_gen has gained some optimizations since this ticket was opened, but we're still calling dataset.read for each sample point. Now that...