LAZrs provides Python bindings for `laz-rs`, a high-performance Rust implementation of LAZ (Laszip) compression and decompression. Its primary role is to serve as an optional, multi-threaded backend for other Python libraries, such as `laspy`, enabling them to efficiently read and write LAZ data. The library is currently at version 0.8.1, with releases tied to updates of its underlying Rust core.
pip install lazrsNo compatibility data collected yet for this library.
LAZrs primarily functions as a high-performance backend for other libraries like `laspy`. This quickstart demonstrates how `laspy` leverages `lazrs` for transparent LAZ file compression and decompression. When `lazrs` is installed, `laspy` automatically uses it for LAZ processing, providing multi-threaded performance. There is no direct high-level API for `lazrs` for file operations; it's consumed implicitly by compatible libraries.
Consider `laszip-python` as an alternative backend for `laspy` if waveform data is critical. Install `laspy` with `pip install laspy[laszip]`.
Use a higher-level library like `laspy` (installed with `laspy[lazrs]`) for reading and writing LAZ files. `lazrs` will be used automatically by `laspy` for performance.
When upgrading, thoroughly test existing code. Consult the `laz-rs-python` GitHub repository's commit history for changes if unexpected behavior occurs.
Ensure `lazrs` is installed using `pip install lazrs` and that you are running your script in the correct Python environment where it was installed.
Try updating `pip` (`python -m pip install --upgrade pip`) or explicitly specifying an older `lazrs` version that might have compatible wheels for your platform. If pre-built wheels are consistently incompatible, you might need to compile `lazrs` from source by ensuring you have Rust and the necessary build tools installed, then running `pip install lazrs` which will attempt a source build.
Inspect the .laz file for corruption or non-standard formatting. If possible, try decompressing the file with another LAZ utility to verify its integrity. If the file is valid, consider reporting the issue to the `lazrs` (or `laspy` if used as a backend) developers with a sample of the problematic data.
As a workaround, ensure the .laz file is not empty when you start appending. Write at least one dummy point during the initial file creation or ensure it contains some valid data before any append operations. The core issue would require a fix in the `lazrs` or `laspy` library.
No dependency data recorded yet.