RasterIO errors about rio-tiler

[vincentsarago]

👋 Hi @zags, thanks for opening this issue.
can you try to do

$ export CURL_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt

as explained in rasterio/rasterio#1289 and #19 ?

Please feel free to close if it solve your issue.

[zags]

Setting the following fixes it for landsat:

os.environ["AWS_REQUEST_PAYER"] = "requester"
os.environ["CURL_CA_BUNDLE"] = "/etc/ssl/certs/ca-certificates.crt"

I'm still getting the error for sentinel.

sentinel2.tile("S2B_tile_20180803_22JER_0", 11825, 18895, 15)

RasterioIOError: '/vsis3/sentinel-s2-l1c/tiles/22/J/ER/2018/8/3/0/preview.jp2' does not exist in the file system, and is not recognized as a supported dataset name.

[vincentsarago]

@zags this is an platform specific, do you have gdal installed, how did you installed rasterio ?

can you try gdalinfo /vsis3/sentinel-s2-l1c/tiles/22/J/ER/2018/8/3/0/preview.jp2 ?

[zags]

I do have gdal installed and rasterio was installed via PIP.

gdalinfo tells me

ERROR 15: AWS_SECRET_ACCESS_KEY configuration option not defined
gdalinfo failed - unable to open '/vsis3/sentinel-s2-l1c/tiles/22/J/ER/2018/8/3/0/preview.jp2'.

I have ~/.boto and ~/.aws/config files with my keys

[vincentsarago]

This is a configuration problem (not a rio-tiler issue). I'm really sorry. checkout http://boto3.readthedocs.io/en/latest/guide/configuration.html it might help.

[zags]

The RioTiler issue is the completely undecipherable error messages. If it's an authentication problem, this should be reflected in the resulting error

[vincentsarago]

I understand but that's a GDAL/Rasterio error.
Noticing that it might be updated with the work currently happening on rasterio/rasterio#1429

[zags]

Fixing the GDAL configuration does not solve this problem. GDAL then gives:

ERROR 4: /vsis3/sentinel-s2-l1c/tiles/22/J/ER/2018/8/3/0/preview.jp2: No such file or directory

/vsis3/sentinel-s2-l1c/tiles/22/J/ER/2018/8/3/0/preview.jp2 is being generated by RIO-tiler.