Coorx
Coorx implements object-oriented linear and nonlinear coordinate system transforms. Optionally, coorx also keeps track of a graph of coordinate systems (such as a scene graph) that are connected by transforms, allowing automatic mapping between coordinate systems.
- A collection of different types of coordinate system transform classes with unit test coverage
- Easy methods for mapping coordinate data through these transforms
- Transform composition and simplification
- Transforms intelligently map data types including numpy arrays, lists, etc.
- Automatic generation of composite transforms from a coordinate system graph
- Coordinate arrays that know which coordinate system they live in to handle automatic mapping
- Using named coordinate systems, coorx warns you wnen you try to map data through the wrong transform
- Automatic conversion of (some) transforms between ITK, Qt, scikit-image, and vispy
Installation
To install the package from PyPI, use the following command:
pip install coorx
Usage
Scale and translate 2D coordinates:
import numpy as np
from coorx import STTransform
coords = np.array([
[ 0, 0],
[ 1, 2],
[20, 21],
])
tr = STTransform(scale=(10, 1), offset=(5, 5))
print(tr.map(coords))
Compose multiple transforms together:
import numpy as np
from coorx import STTransform, AffineTransform, CompositeTransform
coords = np.array([
[0, 0, 0],
[1, 2, 3],
[-10, -200, -3000],
])
tr1 = STTransform(scale=(1, 10, 100))
tr2 = AffineTransform(dims=3)
tr2.rotate(90, axis=(0, 0, 1))
tr3 = CompositeTransform([tr2, tr1])
print(tr3.map(coords))
Local CI
To run GitHub Actions workflows locally with act, first build the runner image once:
docker build -t coorx-act-runner -f .github/act-ubuntu.dockerfile .github/
Then run act as normal; .actrc maps ubuntu-latest to this image.
Todo
- import bilinear, SRT transforms from pyqtgraph
- import coordinate system graph handling from vispy
- make coordinate system dimensionality explicit
- unit tests against ITK output
Credit
Coorx is adapted from code originally written for VisPy (vispy.org), inspired by the nice transform classes in ITK, and maintained by the Allen Institute for Brain Science.
Metadata
Release files for coorx 2.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| coorx-2.0.1.tar.gz | 41.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| coorx-2.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 87.6 kB
Release files / coorx-2.0.1.tar.gz
| Download URL | coorx-2.0.1.tar.gz |
|---|---|
| Size | 41.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e89e931bd2e970506bbdd0fffe1f6c845ddffa17244d96eacb3035db2e87df4
|
|
BLAKE2b-256 checksum How to use checksums |
8c24b98ad87d85160449059205ed751f24ea4f06cd1ca506669aac7002c3ebb9
|
| 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 21, 2026.
Transparency logRelease files / coorx-2.0.1-py3-none-any.whl
| Download URL | coorx-2.0.1-py3-none-any.whl |
|---|---|
| Size | 45.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b2d169a455a30d51843277e71aa8c9f368cd7c06f861c271ac6fc001ae6da9b3
|
|
BLAKE2b-256 checksum How to use checksums |
7571d1f76d16d0fa3bdf1b9bf9c881ad782acc8f7c8eb8f070294fe6dbcc8541
|
| 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 21, 2026.
Transparency log