opengeos /geolibre-rust
whitebox_next_gen geospatial tools (plus new GeoLibre tools) compiled to WebAssembly (WASI) for in-browser use in GeoLibre
★ 299⑂ 34👁 4⑃ 327● 308▤ 44
+0
Daily
299
stars
34
forks
4
watchers
327
prs
308
issues
44
releases
README
geolibre-rust
A pure-Rust geospatial toolkit for GeoLibre,
built on opengeos/whitebox-wasm
(the WASM-ready fork of
whitebox_next_gen) and
compiled to WebAssembly. It is a superset of whitebox-wasm: everything that
package offers, plus new GeoLibre-authored tools.
The published npm package (geolibre-wasm) ships two layers:
- Browser library (. export, wasm-bindgen) -- typed in-memory APIs for
GeoTIFF/COG read+write, projections, vector, LiDAR, and topology
(GeoTiffReader, CogBuilder, CogStream, ...). Same surface as
whitebox-wasm.
- Tool runner (./tools export, WASI) -- the whitebox tool registry plus
GeoLibre's own tools, run over an in-memory /work filesystem via
@bjorn3/browser_wasi_shim.
No server, no GDAL, no native install. Use it from JavaScript (npm
geolibre-wasm) or Python (PyPI geolibre-wasm). New tools live in the
geolibre-tools crate and are registered alongside whitebox's, so GeoLibre sees
them through the same interface as the built-ins.
Try it in the browser
demo/index.html is a self-contained page that loads every tool manifest,
renders a parameter form for whichever tool you pick, and runs it on a sample DEM
(or your own GeoTIFF) entirely in the browser via the WASI runner.
bash
./build.sh once, to produce npm/geolibre-cli.wasm and npm/tools.mjs
./demo/serve.sh serve on http://localhost:8000 (pass a port to override)
Open the printed URL, filter the tool list, fill in the auto-generated form, and
click Run to see the exit code, stdout, output files, and a download link.
serve.sh stages the runtime (npm/tools.mjs, npm/geolibre-cli.wasm) and the
sample raster (examples/sample.tif) next to the page in a temp directory, so the
repo's demo/ stays clean; Ctrl-C stops the server and cleans up.
Self-host with Docker
The same demo ships as a container image so you can host it yourself. The image
is a static site (nginx) — every tool still runs in the visitor's browser, so
there's no server-side compute, GDAL, or database.
Pull the published image with Docker Compose:
bash
docker compose up -d serves on http://localhost:8080
Or build and run it straight from source (needs only Docker — the Rust/WASM
toolchain lives inside the build):
bash
docker build -t geolibre-rust .
docker run --rm -p 8080:80 geolibre-rust
Images are published to ghcr.io/opengeos/geolibre-rust on each release (and on
v tags); :latest tracks the most recent release. To build from source via
Compose instead of pulling, uncomment build: . in docker-compose.yml.
Architecture
crates/geolibre-wasm wasm-bindgen browser library - geolibre_wasm{.js,_bg.wasm,.d.ts} (npm ".")
crates/geolibre-cli WASI tool runner - geolibre-cli.wasm + tools.mjs (npm "./tools")
crates/geolibre-tools new Tool impls (raster_normalize, ...), registered by geolibre-cli
JS (browser/Node) WASI binary (geolibre-cli.wasm)
----------------- --------------------------------
tools.mjs Top issues
Discussions
#5Initial release0 comments · 2026-06-19#1Welcome to geolibre-rust Discussions!0 comments · 2026-06-17
Latest release
v1.8.2 v1.8.2 2026-11-12What's Changed build(deps): bump wbspatialstats from 6d88aaa to dab6e43 by @dependabot[bot] in https://github.com/opengeos/geolibre-rust/pull/612 build(deps): bump wbtopology from 6d88aaa to dab6e43 by @dependabot[bot] in https://github.com/opengeos/geolibre-rust/pull/613 build(deps): bump wbvector from 6d88aaa to dab6e43 by @dependabot[bot] in https://github.com/opengeos/geolibre-rust/pull/614 build(deps): bump wblidar from 6d88aaa to dab6e43 by @dependabot[bot] in https://github.com/opengeos/geolibre-rust/pull/615 build(deps): bump the actions-minor-patch group across 1 directory with 2