Hi all, The rasterio 1.1.5 wheels on PyPI include GDAL 2.4.4 and a patched PROJ 4.9.3. Neither of these versions are supported anymore. Recently I have heard from users and contributors would like to

Hi, How did you install rasterio? If you got it with `pip install rasterio` you will have installed a wheel file that includes GDAL 2.4.4 and data files and which will be incompatible with the GDAL 3.

Hi Daryl, We're testing rasterio's trunk against GDAL 3.1.2 here: https://travis-ci.org/github/mapbox/rasterio. We are not currently checking the 1.1.x branch, but in my experience there are no proble

Hi, It looks like your input.tif may have lossy compression applied, and the output will have the same compression by default. You might try rio mask --overwrite --crop in.tif out.tif --geojson-mask m

Hi, If your original raster's georeferencing did not involve rotation, and if the merged raster has the same origin (upper left corner) as the original, you can reuse the original raster's transform p

Hi, Your usage of the affine transform affine_transform * (r-1, c-1) is incorrect. You must swap the order of the tuple indexes to get the correct results because mathematically speaking (x', y') = af

Apologies for the late reply. There may be a bug, yes, but there are more likely sources of trouble. Can you explain more about how you are installing the rasterio package on GCP and how you are confi

You're welcome. It's unfortunate that we don't have a more informative message from GDAL that we can raise to users. "No such file or directory" is too opaque.

Hi Tom, I don't use netcdf files with GDAL often and have never tried to write a netcdf file to vsimem. It could be that there is a combination of creation or config options required that I don't know

Hi Thomas, I think Denis found the root of the problem and we have a fix at https://github.com/mapbox/rasterio/pull/1938 that will be a part of the 1.1.5 release. Thank you for the test cases and for

Hi all, Rasterio 1.1.4 has been released. Here are the changes: https://github.com/mapbox/rasterio/blob/master/CHANGES.txt#L4 Here are the distributions on PyPI https://pypi.org/project/rasterio/1.1.4

Hi, I've only now remembered (not being a regular jp2 user) that JPEG2000 is a create-copy format (see https://gdal.org/drivers/raster/index.html) and as such is not suited for uses cases like with ra

Hi, Dataset files can be accessed from multiple threads, but the dataset objects returned by rasterio.open can only be used by a single thread at a time. This is a constraint that we get from GDAL. Yo

Since there's no JP2 specific code in MemoryFile and things work with the GeoTIFF driver, I suspect there's a subtle bug involving the vsimem system and one of the JP2 drivers. It would be useful to t

Hi, I can't say for sure about the time differences because I don't know much about your data files or your computer. However, know this: GDAL's I/O system caches blocks of raster data in memory, the

Correct, the dataset's shape is not the same as the shape of dataset.read().

Hi Kyle, Dion: Thank you for the details. Dion, can you say a little more about reads not being thread-safe? It's intended that we can call GDAL's RasterIO functions in different threads concurrently

Hi Vincent, Thanks for the update. This situation points out a downside of using the warped VRT: it abstracts everything (network, reprojection, caching) and makes diagnosing problems difficult.

Hi, First of all, I'm not very familiar with rio-tiler. Hopefully, Vincent will help us out. A constant time regardless of the amount of overlap suggests to me that your source files may lack the prop

Hi Greg, Do you see a bare "proj_create_from_database: datum not found" or do you see ERROR 1: PROJ: proj_create_from_database: datum not found as in https://github.com/OSGeo/gdal/issues/2321? Which s