stt-build
The CLI that builds SpatioTemporal Tiles (STT) datasets. It reads a
GeoParquet file with a WKB geometry column (or separate lon/lat columns)
plus a timestamp column — or, behind opt-in cargo features, a live
PostGIS or DuckDB query — tiles the features across zooms and
temporal buckets, and writes the packed format: a dataset directory of
manifest.json, one index/<blake3>.sttd directory object, and
content-addressed packs/<blake3>.sttp objects (immutable,
forever-cacheable). Simplification, temporal LOD pyramids, summary tiers
(H3/Quadbin), coordinate/attribute quantization, and per-tile budgets are
all flags away.
Internal implementation crate of
spatiotemporal-tiles: this is the tiler/encoder library (the facade'sbuildmodule). Thestt-buildCLI ships with the facade:Database inputs stay feature-gated (
postgres/duckdb) on both the library and the facade.
Example
# Auto-tuned build (zoom range + temporal bucket picked by stt-optimize):
# Trajectories with simplification and a temporal-LOD pyramid:
# Straight from PostGIS (--features postgres), no export step:
-o foo.stt strips the extension and produces foo/{manifest.json,index/,packs/}.
Pass --publish for a deploy-ready build (zstd 19).
Relation to the other crates
Encoding, packing, and the directory come from stt-core;
--auto calls into stt-optimize;
stt-generate shells out to this binary for every bundled
dataset; stt-serve reuses the same per-tile encoder to
serve tiles on the fly; gate outputs in CI with
stt-validate.
Docs
License: MIT.