Supporting GDAL Virtual File Systems would allow xtensor to access files located in compressed archives (zip, tar), on the network (http, https, ftp), and in the cloud (AWS S3, Google Cloud Storage, Microsoft Azure, Alibaba Cloud OSS, OpenStack Swift Object Storage, Hadoop File System), and more (standard I/O, in-memory, etc.).
The GDAL API uses C FILE-like objects, not streams as in our IO handlers, so I guess we should also provide dump/load functions that operate on such objects.
This is part of an effort to implement a Zarr driver in GDAL using xtensor-zarr.
Supporting GDAL Virtual File Systems would allow xtensor to access files located in compressed archives (zip, tar), on the network (http, https, ftp), and in the cloud (AWS S3, Google Cloud Storage, Microsoft Azure, Alibaba Cloud OSS, OpenStack Swift Object Storage, Hadoop File System), and more (standard I/O, in-memory, etc.).
The GDAL API uses C
FILE-like objects, not streams as in our IO handlers, so I guess we should also provide dump/load functions that operate on such objects.This is part of an effort to implement a Zarr driver in GDAL using xtensor-zarr.