Jupyter Tiler
A Jupyter server extension which provides an API to launch a server to dynamically tile Xarray DataArrays for interactive visualization.
Who is this for?
Intended to be consumed by interactive map libraries for Jupyter, not end-users, e.g.:
- Leafmap
- ipyleaflet
- ipyopenlayers
- More?
What problem does this solve?
For authors of interactive map libraries for Jupyter, providing a dynamic HTTP tile server presents a unique problem: they don't know where Jupyter is running. It could be, for example, running on:
- users' local machines
- a shared JupyterLab instance on an intranet
- an authenticated JupyterHub in a public cloud
The first case is the simplest; when the tile server is running on localhost, the map
viewer running in JavaScript in the user's browser can connect to it.
In the other cases, the map viewer needs a public URL to connect to. The URL of the current JupyterHub instance may not be known. Additionally, a map server running in a Jupyter kernel isn't exposed to the public internet in many cases (for example, when it's running in a Kubernetes pod as part of a JupyterHub). This extension provides dynamic proxying to map servers running in the kernel.
Usage
As a Jupyter interactive map library author, you may implement a method like:
from jupyter_tiler.titiler import add_data_array
class MyMapLibrary:
# ...
def add_xarray_layer(self, da: xr.DataArray):
# Add the layer to the tile server.
# The server will be started the first time this is called.
# A URL that passes through the Jupyter server proxy will be returned:
url = add_data_array(da)
# Add the layer to your map!
self._add_tile_layer(url)
Install
Recommended:
uv add jupyter-tiler
Or:
pixi add jupyter-tiler
For other methods of installation, including pip, conda, mamba, and micromamba, see the installation instructions in the documentation.
From source
uv add git+https://github.com/geojupyter/jupyter-tiler.git#egg=jupyter-tiler
For development instructions, please view the development install instructions in our documentation's Contributor Guide!
Contributing
Please see the Contributor Guide in our documentation!
🚀 Powered by...
Other backends (e.g. xpublish-tiles (earthmover)) may be supported in the future!
✨ Inspired by...
Metadata
Release files for jupyter-tiler 0.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| jupyter_tiler-0.9.0.tar.gz | 236.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jupyter_tiler-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 261.5 kB
Release files / jupyter_tiler-0.9.0.tar.gz
| Download URL | jupyter_tiler-0.9.0.tar.gz |
|---|---|
| Size | 236.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
526e54492ed48f80ae44c5c3b797889d769e10f68e5e95fc359e902f939e0051
|
|
BLAKE2b-256 checksum How to use checksums |
cc202bea67689fab9b98f7f304b8ca82bb721aef4fe2352de44728fb1fc85c4b
|
| 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 1, 2026.
Transparency logRelease files / jupyter_tiler-0.9.0-py3-none-any.whl
| Download URL | jupyter_tiler-0.9.0-py3-none-any.whl |
|---|---|
| Size | 25.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1a0b0a3123a75916c46726c0dca6d42f79f19ec09985eee679bc776afacccfce
|
|
BLAKE2b-256 checksum How to use checksums |
ed7c5eea0db7af52be7d79cba1f6458ce6cdbf5db1f1cf881b9b2add08ec9bc0
|
| 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 1, 2026.
Transparency log