[gdal-dev] VSI sidecar and sibling file lookup

[Sean Gillies]

Thanks for the tip, Thomas!

On Thu, Feb 15, 2024 at 9:45 AM thomas bonfort <thomas.bonfort at gmail.com>
wrote:

> Hi Sean,
> I believe/recall this is very driver dependent. Some drivers will look for
> their sidecars in the provided sibling files list returned by
> VSISiblingFiles, whereas others will unconditionally try to open well-known
> sidecar names they will have computed from their own name. IIRC I added
> VSISiblingFiles so that some vsi backends (namely object storage based
> ones) could explicitly return an empty list of sibling files in order to
> prevent drivers to emit a subsequent Readdir() (which might break drivers
> that require sidecar files to work, but speeds up those where sidecar files
> are optional and not used in a cloud-storage environment (namely cogs) )
>
> On Tue, Feb 13, 2024 at 6:12 PM Sean Gillies via gdal-dev <
> gdal-dev at lists.osgeo.org> wrote:
>
>> Hi all,
>>
>> It's not clear to me from reading
>> https://gdal.org/user/virtual_file_systems.html if VSI sidecar and
>> sibling file lookup works in general, by design, or whether it's an
>> implementation detail of the standard VSI filesystems ("vsizip", "vsicurl",
>> etc.).
>>
>> More specifically: if I have a "/vsipyopener/foo.tif" object, do drivers
>> always look for other files at paths precisely relative to that one? Does
>> this vary among drivers?
>>
>

-- 
Sean Gillies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240216/1732055b/attachment.htm>