Re: Occasional "not recognized as a supported file format" errors when reading from S3
thank you very much for the detailed assessment. I think this already sheds some light on some of the problems.
To answer your questions:
- The /vsis3/ identifiers are correct and work most of the time, we only see these errors from time to time.
- This is just a default read from a private S3 bucket. I don't know which protocol boto (or GDAL?) uses under the hood.
- In the first case, there is indeed multithreading involved, so this is a hot lead. I will have a look at the documentation as soon as I can find it somewhere :) It working most of the time would of course suggest some sort of race condition.
In the second case, the setup is actually more complicated. We experimented with "cloud-optimized" VRT files, that we created by
1. gdalbuildvrt on many small-ish COG
2. gdaladdo on the resulting VRT into an external .vrt.ovr file
We could then serve these COG mosaics up as a single dataset via Terracotta, but apparently the read from the VRT would fail when we zoomed in too far.
Thank you for your time!
On 24/05/2019 20.49, Sean Gillies via Groups.Io wrote: