Frankly, I always thinking giving more context will help especially with the python binding logging gdal errors to stderr and you have to figure out how to do that. However, in my case I guess it was

I found my problem. I had extra double quote from a copy paste around for this env var CPL_VSIL_CURL_ALLOWED_EXTENSIONS=".TIF,.ovr,.jp2,.tif" which I was setting via .env file and referencing it in th

This the log I getting when the rio command with verbose curl. Not seeing specific http connection errors. $ CPL_CURL_VERBOSE=YES rio -vvv info http://oin-hotosm.s3.amazonaws.com/59c66c5223c8440011d7b

I am having a strange rasterio issue where if I build rasterio docker image from osgeo/gdal:ubuntu-small-latest as the base image and run it as docker-compose up, the rio fails to open any http based

@Sean I am building a Docker image with the requirements.txt file set to rasterio==1.0.15. Do I have to do anything specific to get the 1.0.15-1 wheels for Docker image running on Linux?

@Sean Just tested 1.0.15, GS support works great! Thanks... Madhav

Great! I am good for now through local rasterio 1.0.14 packaging but happy to test out GS support again once rasterio 1.0.15 is out.

@Sean I think something is not right with the PyPI distribution of rasterio 1.0.14. I did pip install rasterio into a clean virtualenv and it installed rasterio. See the pip show rasterio output: rio

I setup rasterio 1.0.14 and try to do a rasterio.open with gs:// url and I get following error. I did set GOOGLE_APPLICATION_CREDENTIALS to json key file. What am I missing? >>> import rasterio >>> im

Wow! This is awesome! I made similar changes to add GS support locally. I will pull 1.0.14 and see if all GCS related workflow works as expected in my Kubernetes cluster. Thanks! Madhav

I didn't build gdal but I am using the base gdal image from quay.io/mojodna/gdal:v2.3.2. s3 access is working perfectly fine. If GDAL was not built SSL, AWS S3 wouldn't have worked correct? Also is th

Hi I forked and am trying to add support for rasterio and rio to handle files on Google Cloud Storage. I made changes to path.py and added remote schemes to include gs:// type urls similar to AWS S3 s