xuepy
Xue (雪) weather bundles for Python: the decoder, and an experimental native encoder — the Xue Rust crate through PyO3.
A .xue file packs one variable of a global forecast run as quantized
single-byte planes with temporal residual prediction and per-plane Zstandard,
so a browser can animate a 240-hour run frame by frame. docs/format.md in the
repository is the normative specification. Since 2026-09-15 the service
publishes the same bundles as Zarr v3 stores (docs/zarr-profile.md) rather
than .xue files, which xarray reads without this package; the decoder here
still reads every .xue, and the encoder still writes one as the
intermediate the store is derived from.
Installing
pip install xuepy
Linux wheels are manylinux_2_39 (Ubuntu 24.04+, Debian 13+) and macOS is
arm64 only. There is no sdist: building from source needs GDAL, libclang and
cmake, and an unsupported platform is better served by a clear "no matching
distribution" than by a confusing build failure.
Decoding
Bundle is the same reader the browser runs through wasm, so a bundle that
decodes here decodes there. A plane comes back as the uint8 NumPy array of
quantized codes the shader would have uploaded to an R8 texture; the
metadata's quantization block turns it back into physical values.
import xue
bundle = xue.Bundle.open("tmp2m.xue")
plane = bundle.decode(variable_id=1, frame_offset=24) # uint8, width * height
codebook = bundle.metadata["variables"][0]["quantization"]
celsius = codebook["offset"] + plane * codebook["scale"]
bundle.frame_offsets, bundle.unit_seconds and bundle.metadata describe
the time axis and the grid. Reconstruction is checked against the CRC-32 the
encoder wrote, so a corrupt file raises rather than returning wrong numbers.
Encoding
Experimental, and held to the Python reference pipeline by byte-for-byte identical output on every source it supports — GFS, ECMWF, GFS surface flux, and the CMA radar mosaic.
report = xue.convert_bin(["data/raw/gfs.2026082006"], "out/", model="gfs")
A build writes one Zarr v3 store per bundle (out/tmp2m.zarr, …) by
default; container=True writes each bundle's .xue beside it, and
zarr=False, container=True the .xue alone (what earlier releases wrote
by default).
The stages are also exposed on their own — quantize, encode_residual,
decimate, encode_poster, write_store — taking and returning NumPy
arrays.
What is in the wheel
Its own minimal GDAL: the GRIB and netCDF drivers, the OpenJPEG codec the
GRIB driver needs for JPEG 2000-packed records (GFS-Wave), and nothing else,
with GDAL's and PROJ's data directories beside it, because the GRIB driver
cannot read a band without them. Eight shared libraries rather than the 227 a
distribution GDAL pulls in, all permissively licensed, with their notices in
xue/licenses/. Nothing needs to be installed alongside it and no environment
variable needs setting.
See docs/encoder.md
for how it is built and what it is measured against.
1 maintainer
Metadata
1 maintainer
Release files for xuepy 0.40.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xuepy-0.40.0-cp314-abi3-manylinux_2_39_x86_64.whl | CPython 3.14 | abi3 | Linux glibc 2.39+ x86-64 | Details |
| xuepy-0.40.0-cp314-abi3-manylinux_2_39_aarch64.whl | CPython 3.14 | abi3 | Linux glibc 2.39+ ARM64 | Details |
| xuepy-0.40.0-cp314-abi3-macosx_11_0_arm64.whl | CPython 3.14 | abi3 | macOS 11.0+ ARM64 | Details |
Total release size: 47.8 MB
Release files / xuepy-0.40.0-cp314-abi3-manylinux_2_39_x86_64.whl
| Download URL | xuepy-0.40.0-cp314-abi3-manylinux_2_39_x86_64.whl |
|---|---|
| Size | 17.9 MB |
| Tags | CPython 3.14 Linux glibc 2.39+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
c48e954b22f7b653ea961fd40dfe2910521b8a4fc3b438b4771d79b469f65975
|
|
BLAKE2b-256 checksum How to use checksums |
8e3ae2854258742c3a9a7b4ceea632c2d630fd1c94828ff95861148ae8d9c0a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 15, 2026.
Transparency logRelease files / xuepy-0.40.0-cp314-abi3-manylinux_2_39_aarch64.whl
| Download URL | xuepy-0.40.0-cp314-abi3-manylinux_2_39_aarch64.whl |
|---|---|
| Size | 16.8 MB |
| Tags | CPython 3.14 Linux glibc 2.39+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
c6a22b1be063725f6ad67ceba9e9b0cd595c2e48cebfbe50de88eb263542a1e2
|
|
BLAKE2b-256 checksum How to use checksums |
7e7836b0e54d3240167d7c7baae439442fd42dc378e99419f51d8d3be8f4daf0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 15, 2026.
Transparency logRelease files / xuepy-0.40.0-cp314-abi3-macosx_11_0_arm64.whl
| Download URL | xuepy-0.40.0-cp314-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 13.1 MB |
| Tags | CPython 3.14 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9ccbfd4c8a05c19a9b4d113de4570a1a87833a6399ed9dc1fdac77d1f7c30ffe
|
|
BLAKE2b-256 checksum How to use checksums |
df259469f30ef04ca24ab56c46e1ca557445d6e588b91c9f389449263bf5828b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 15, 2026.
Transparency log
