Skip to main content

pixelworld-pipeline

The offline geo pipeline of pixelworld: real elevation, land cover, roads and buildings in, gridded world packages out. A region spec (YAML) says where, at what scale and with what data; pixelworld build turns it into a package the viewer (the npm package pixelworld) draws.

pip install pixelworld-pipeline        # or: uv tool install pixelworld-pipeline
pixelworld build region.yaml --out my-world

In a checkout of the repository, from pipeline/:

uv sync                                                    # once
uv run pixelworld check ../worlds/jerome/region.yaml       # validate a spec, offline
uv run pixelworld build ../worlds/jerome/region.yaml --out ../fixtures/_try/jerome
uv run pixelworld view ../fixtures/_try/jerome             # serve a package, print the viewer URL
uv run pixelworld --help                                   # every command, the exit codes
  • Making a world of your own place: docs/worlds.md, a walkthrough with Jerome, Arizona as the example, and the reference of every spec key (pixelworld reference prints it).
  • How the pipeline works: docs/architecture.md §4–6: the spec, the stages, the warp.
  • The package it writes: docs/world-format.md.
  • Data sources (terrain, land cover, the map, building facts and the rest, built in or your own) and the Python API (pixelworld_pipeline.build(spec)): docs/plugins.md.
  • Data and licences: docs/data-sources.md.

Exit codes: 0 done; 1 the package was written but its road report found problems; 2 the spec or command line is invalid; 3 the build failed (a download, or a bug) and the output was left as it was.

Downloads are cached in pipeline/.cache/, or in $PIXELWORLD_CACHE, which several checkouts can share.

Development: uv run pytest (offline), uv run ruff check . && uv run ruff format --check .. The spec schema is src/pixelworld_pipeline/schema.py; after changing it, uv run pixelworld reference --write ../docs/worlds.md (a test checks the two agree).

Metadata

Release files for pixelworld-pipeline 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pixelworld-pipeline 0.1.0
File Size Uploaded Provenance Actions
pixelworld_pipeline-0.1.0.tar.gz 336.5 kB Without provenance Details for pixelworld_pipeline-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for pixelworld-pipeline 0.1.0
File Interpreter ABI Platform Actions
pixelworld_pipeline-0.1.0-py3-none-any.whl Python 3 none any Details for pixelworld_pipeline-0.1.0-py3-none-any.whl

Total release size: 579.2 kB

Release files / pixelworld_pipeline-0.1.0.tar.gz

Download URL pixelworld_pipeline-0.1.0.tar.gz
Size 336.5 kB
Tags Source
SHA-256 checksum
How to use checksums
6b942735abf8f31a28cc8f40e099c30ebdab01ee1f5f5a5faa717ae0ce736c58
BLAKE2b-256 checksum
How to use checksums
778e0d3baa1addbbb08b6d9de5c0a39b85e30e27e8e2cbbd3400a45cf7e95901
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / pixelworld_pipeline-0.1.0-py3-none-any.whl

Download URL pixelworld_pipeline-0.1.0-py3-none-any.whl
Size 242.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
62c464941666593d68ac80f746a6bc7d3d7fe34a36b943b162f8577b8510b2c1
BLAKE2b-256 checksum
How to use checksums
0cc7d4ddb821ab43ea32ac95a3b3d0219b8141a573f6247399be2b037a154435
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for pixelworld-pipeline 0.1.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page