Hi, Correct, those dataset creation options need to be passed into rasterio.open(). One way to do that is to add to your metadata dict below metadata["profile"] = "GeoTIFF" Any extra keyword argument

If you are creating a GeoTIFF it is possible that no XML file will be written. As Even Rouault explains in https://lists.osgeo.org/pipermail/gdal-dev/2010-May/024522.html, the PAM file is only created

Hi, Can you tell us how you installed rasterio? If you installed one of the binary wheels from PyPI (which I built), you may be out of luck. I haven't paid any attention to making sure that they have

Dion, Jonas: There is a new report in the FIona tracker that may be related: https://github.com/Toblerity/Fiona/issues/761. There I advised turning on CPL_CURL_VERBOSE=YES to see more details about th

Hi Erick, I'm not familiar with Lustre and only slightly familiar with the details of GDAL's netCDF driver. I think, since the problem manifests with gdalinfo as well as rasterio programs, that the be

I found the VRT multi-threading guidance at https://gdal.org/drivers/raster/vrt.html#multi-threading-issues. It moved during the site migration. This smells like a GDAL bug to me, perhaps a manifestat

Hi Shane, It looks like your feature geometries extend beyond the extent of your raster, yes? In that case, crop can create an extra row or column of pixels, which will be empty. This seems like a bug

Alan: the function does indeed write to a new file with blocksizes set appropriately. Javier: the TIFF spec states that tile width (and this goes for height, I presume) must be a multiple of 16. Neith

Thank you for providing a complete example of your code and the ArcMap error message. Without those details, it can be hard to provide help. When you open the files for writing, there is one thing mis

The VRT_SHARED_SOURCE option only affects the connection pool within the VRT driver code and that's not relevant to your code as far as I can see. A single opened rasterio dataset cannot be safely use

Hi Vincent, Can you explain what processes produced those images? What program produced the blurry one and what program produced the non-blurry one? Which resampling algorithms were used? Yes, you can

Hi, If you pass a Python file object opened in "r" mode to rasterio.open, the contents will be read and stored in a MemoryFile. See https://github.com/mapbox/rasterio/blob/master/rasterio/__init__.py#

rio-calc does indeed read the entire file. The requirement to use it on files too large to fit in memory hasn't come up before. Modifying it to work on only one (or several, using a thread or process

For GeoTIFF (at least), the photometric creation option is different from the color interpretation that we can get/set using the GDAL API. The file's layout and compression strategy is influenced by t

Hi Shane, Before Rasterio 1.0, the project did record creation options in a custom tag (metadata) namespace. We discovered problems when converting from GeoTIFF to other formats: creation options are

Hi Ed, Can you try the following variation on your first command? $ rio color -j 1 uint16_image.tif uint16_brightened.tif gamma RGB 1.5 --co photometric=RGB Note the addition of "--co photometric=RGB"

Hi all, In the Rasterio quickstart guide I've added some links to API documentation. For example, see the "open()" link under the 2nd code block in https://rasterio.readthedocs.io/en/latest/quickstart

Vincent, We haven't been testing with PROJ 6. It might work. This commit https://github.com/mapbox/rasterio/commit/c5b0d911994ade823a7b5a969071c2c1bd860a11 should address the error message printed to

This issue has been resolved. Check the project issue tracker's recently closed issues for details.

Amine, I'm sorry about the confusion. I would rather not comment on the structure of your application. Your original question was about the warnings being printed in your shell, yes? I pointed out tha