vsifile
Documentation: https://vincentsarago.github.io/vsifile/
Source Code: https://github.com/vincentsarago/vsifile
Description
Experiment using Rasterio/GDAL Python file opener VSI plugin https://github.com/rasterio/rasterio/pull/2898/files
Future version of rasterio will accept an custom dataset opener:
opener : callable, optional
A custom dataset opener which can serve GDAL's virtual
filesystem machinery via Python file-like objects. The
underlying file-like object is obtained by calling *opener* with
(*fp*, *mode*) or (*fp*, *mode* + "b") depending on the format
driver's native mode. *opener* must return a Python file-like
object that provides read, seek, tell, and close methods.
Install
You can install vsifile using pip
python -m pip install -U pip
python -m pip install -U vsifile
or install from source:
git clone https://github.com/vincentsarago/vsifile.git
cd vsifile
python -m pip install -U pip
python -m pip install -e .
Usage
from vsifile import VSIFile, FileReader
src_path = "tests/fixture.cog.tif"
with VSIFile(src_path, "rb") as f:
assert isinstance(f, FileReader)
assert hash(f)
assert "FileReader" in str(f)
assert not f.closed
assert f.header_cache
assert len(f.header) == 32768
assert f.tell() == 0
assert f.seekable
b = f.read(100)
assert len(b) == 100
assert f.header[0:100] == b
assert f.tell() == 100
_ = f.seek(0)
assert f.tell() == 0
_ = f.seek(40000)
assert f.tell() == 40000
b = f.read(100)
assert f.tell() == 40100
# fetch the same block (should be from LRU cache)
_ = f.seek(40000)
b_cache = f.read(100)
assert f.tell() == 40100
assert b_cache == b
b = f.get_byte_ranges([100, 200], [10, 20])
assert len(b) == 2
assert len(b[0]) == 10
assert len(b[1]) == 20
assert f.tell() == 220
With Rasterio
import rasterio
from vsifile.rasterio import opener
with rasterio.open("tests/fixtures/cog.tif", opener=opener) as src:
...
Caches Configuration
Header Cache
vsifile uses DiskCache to create a persistent File Header cache (TTL: Time To Live cache).
By default the cache will be cleaned up when closing the file handle, you can change this behaviour by setting VSIFILE_CACHE_DIRECTORY="{your temp directory}" environment variable.
Settings:
- VSIFILE_CACHE_DIRECTORY: Diskcache directory (defaults to
None) - VSIFILE_CACHE_HEADERS_TTL: Time to Live of each object in the cache, in seconds (defaults to
300) - VSIFILE_CACHE_HEADERS_MAXSIZE: Maximum size of the cache, in Bytes (defaults to
5120000000)
Block Cache
vsifile has a second layer of cache for the blocks (non-header read) based on cachetools.
Settings:
- VSIFILE_CACHE_BLOCKS_TTL: Time to Live of each object in the cache, in seconds (defaults to
300) - VSIFILE_CACHE_BLOCKS_MAXSIZE: Maximum size of the cache, in number of items (defaults to
512)
Note: you can disable cache by setting: VSIFILE_CACHE_DISABLE=TRUE
Other Configurations
- VSIFILE_INGESTED_BYTES_AT_OPEN: Bytes ingested when opening a file (header) (defaults to
32768)
Contribution & Development
See CONTRIBUTING.md
Changes
See CHANGES.md.
License
See LICENSE
Metadata
Release files for vsifile 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| vsifile-0.6.0.tar.gz | 9.0 kB | With provenance | Details for vsifile-0.6.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vsifile-0.6.0-py3-none-any.whl | Python 3 | none | any | Details for vsifile-0.6.0-py3-none-any.whl |
Total release size: 20.2 kB
Release files / vsifile-0.6.0.tar.gz
| Download URL | vsifile-0.6.0.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8156864fc5b8eb76c61cbdf8967ae578bee2e4f15ed462f60e8c8d50d4ad06da
|
|
BLAKE2b-256 checksum How to use checksums |
f898d6052680bb5dd724fe5f6de281697e4c473afe879beb860295ba37a6a03e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 28, 2026.
Transparency logRelease files / vsifile-0.6.0-py3-none-any.whl
| Download URL | vsifile-0.6.0-py3-none-any.whl |
|---|---|
| Size | 11.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
793bfe0c70645ec6e13136a49125c392d8a2580246d16a7e9ae344ceb71b0f7c
|
|
BLAKE2b-256 checksum How to use checksums |
55eabcf1f75f454df746d4bbb3d890252aac08b63271c6bd38984e623d07ec99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 28, 2026.
Transparency logSecurity for vsifile 0.6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for vsifile-0.6.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.