loxodrome
Python bindings for loxodrome. The package surfaces the Rust-backed geometry
handles, geodesic distance/bearing helpers, and Hausdorff variants.
- Setup and publishing live in the repo-level
README.md. - The Typer CLI (
uv run lox info) is a dev-only smoke check to confirm the extension loads.
Shapely interoperability
Shapely is optional. Install the extra if you want to bridge loxodrome points with Shapely:
pip install loxodrome[shapely]
Converters live in loxodrome.ext.shapely and keep imports guarded:
from loxodrome import Point
from loxodrome.ext.shapely import from_shapely, to_shapely
point = Point(12.5, -45.0)
shapely_point = to_shapely(point)
round_tripped = from_shapely(shapely_point)
Point, Point3D, and BoundingBox are supported. Other geometry kinds raise
TypeError, and non-rectangular polygons raise InvalidGeometryError, until
matching kernels land.
Demo notebook
A ready-to-run example lives at experiments/notebooks/loxodrome_usage.ipynb.
Launch it inside the uv-managed environment so imports resolve against the local build:
cd loxodrome
uv sync --all-extras
uv run maturin develop
uv run --with notebook jupyter notebook ../experiments/notebooks/loxodrome_usage.ipynb
For JupyterLab, swap the last line for
uv run --with jupyterlab jupyter-lab ../experiments/notebooks/loxodrome_usage.ipynb.
Metadata
Release files for loxodrome 0.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 | Provenance | Actions |
|---|---|---|---|---|
| loxodrome-0.0.1.tar.gz | 62.4 kB | With provenance | Details for loxodrome-0.0.1.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| loxodrome-0.0.1-cp313-cp313-manylinux_2_28_x86_64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.28+ x86-64 | Details for loxodrome-0.0.1-cp313-cp313-manylinux_2_28_x86_64.whl |
| loxodrome-0.0.1-cp312-cp312-manylinux_2_28_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.28+ x86-64 | Details for loxodrome-0.0.1-cp312-cp312-manylinux_2_28_x86_64.whl |
| loxodrome-0.0.1-cp311-cp311-manylinux_2_28_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.28+ x86-64 | Details for loxodrome-0.0.1-cp311-cp311-manylinux_2_28_x86_64.whl |
| loxodrome-0.0.1-cp310-cp310-manylinux_2_28_x86_64.whl | CPython 3.10 | CPython 3.10 | Linux glibc 2.28+ x86-64 | Details for loxodrome-0.0.1-cp310-cp310-manylinux_2_28_x86_64.whl |
Total release size: 1.9 MB
Release files / loxodrome-0.0.1.tar.gz
| Download URL | loxodrome-0.0.1.tar.gz |
|---|---|
| Size | 62.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
598bf7f07e886d8693af28024ac507707880098ac343c8025ed580ca477f9841
|
|
BLAKE2b-256 checksum How to use checksums |
96a3de1e7078588712b923e37db161a386cb287b3fadcf9ee45188ee10a6ffc2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 17, 2025.
Transparency logRelease files / loxodrome-0.0.1-cp313-cp313-manylinux_2_28_x86_64.whl
| Download URL | loxodrome-0.0.1-cp313-cp313-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 448.6 kB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
2fcf6835690a9f85734f6d02446ce2f73750937c67a172f1b1ba541e1cd8123a
|
|
BLAKE2b-256 checksum How to use checksums |
082dc2af504fb8485372de7c462edae1dc72a664cc4a5da888855146b58ea37c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 17, 2025.
Transparency logRelease files / loxodrome-0.0.1-cp312-cp312-manylinux_2_28_x86_64.whl
| Download URL | loxodrome-0.0.1-cp312-cp312-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 448.5 kB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
e277c4ca59016c9e433ef9e2edb53ace97ce7414e9adbcaf72672dde5fb44688
|
|
BLAKE2b-256 checksum How to use checksums |
000ab583eb843a3a501f58322a3d128c60964ac7ddc2a49c1f23047f3d481ece
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 17, 2025.
Transparency logRelease files / loxodrome-0.0.1-cp311-cp311-manylinux_2_28_x86_64.whl
| Download URL | loxodrome-0.0.1-cp311-cp311-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 451.6 kB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
1e727870a6a3ee21211fdc43c07923f71245d0c6b5b2829810f51c227f36760a
|
|
BLAKE2b-256 checksum How to use checksums |
ad0789b16e98bc8e58089fcdd50406e361df087a314d10f9b6028b5724c4a891
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 17, 2025.
Transparency logRelease files / loxodrome-0.0.1-cp310-cp310-manylinux_2_28_x86_64.whl
| Download URL | loxodrome-0.0.1-cp310-cp310-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 451.7 kB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
fca31cc69bce65da5d817b70ac30eecb132a87da6bca436dbfa6fa310c36dafc
|
|
BLAKE2b-256 checksum How to use checksums |
c869c0dd734909ccd942ef4e089bc6dc6ff49b5e2e41ac2a0665c6e39151b7ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 17, 2025.
Transparency logSecurity for loxodrome 0.0.1
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
All 5 files in this release have been uploaded with provenance metadata.
Attestation for loxodrome-0.0.1.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 Dec 17, 2025.
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.