Okay so I think that I can update the GRIB specific options using rio warp ie: rio warp 1000_500_thick.grb 1000_500_thick_new2.grb --format GRIB --profile BAND_1_PDS_PDTN= with BAND_1_PDS_PDTN being a

Hi All, I just listed an issue on the main github log. https://github.com/mapbox/rasterio/issues/1659 If anyone could take a look I would be very grateful. Kind Regards, Amine

Hi Shane, I think I understand now. BAND_1_PDS_PDTN isn't a tag, it's a "creation option". You can apply these at the time you open a dataset for writing like with rasterio.open("file.grb2", "w",

Ah I see, I was confused then just because these come up when you "rio insp" and then "src.tags(1)", these creation options show up under the tags for band1. That's very helpful so thanks for the

Hi Amine, I think you have made in error in pasting code into the GitHub issue. The code you've given will fail at dataset = memfile.open because you haven't assigned memfile yet. The message you see

We were discussing whether it would be possible to use `gdalbuildvrt` on several cloud-optimized GeoTIFF and obtain something that behaves like one big COG (which would be awesome to serve up large

Hi Dion, I encountered the same result couple month ago and couldn't get it to work. I asked Evan about it and see his answer here

Huh, interesting. So only birds-eye overviews of VRTs should be expensive, which is to expected. Did you observe that in your tests? Did you ever go further and experiment with external overviews for

Hi Sean, the issue is that I am writing functions where the output is often a rasterio dataset. I don't know if this can be accomplished using a with statement: function open_raster(filename):

Dear All, I am quite sure that there used to be extensive online documentation in the following website: https://rasterio.readthedocs.io/en/stable/api/rasterio.transform.html What happened to it?

Hi Amine, The following will work if you are calling the two functions in the same module. with open_raster('raster.tif') as dataset: # this gives you an implicit Env around the contained

Dear Sean, I am slightly confused. You state the following: I have two issues with the above statement: Why are you closing the file if it is inside the with block? I thought one of the advantages

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

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

Hi all, I'm new at this, more of a computer vision person than a developer, so please bear with me.... I see the behavior I'm about to describe running pip-installed rasterio (1.0.22) on my Mac (OSX

Dear Rasterio contributors ;-) I installed the latest version of GDAL 2.4.1 with PROJ4 version 6 and I'm seeing this message "proj_create: init=epsg:/init=IGNF: syntax not supported in non-PROJ4

I reinstalled rasterio and it fixed itself. I think it was caused by environment variables

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

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

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