Clustering and Hexbin

Dense point layers are hard to read at overview zooms. Tamaat precomputes two summary artifacts so the map stays responsive.

Clustering

When clustering is enabled on Standard, Category, or Range symbology and the cluster rollup is ready:

1. Open the layer symbology controls.
2. Enable clustering for the point layer.
3. Optionally choose a Color by field that appears in the cluster style manifest.
4. Zoom in and out — cluster bubbles stay color-stable because style props are baked into the cluster tiles.

Cluster artifacts rebuild when the layer data revision changes, not when you only change palette or opacity.

Hexbin

Hexbin mode uses stored H3 rollups (not live point scans):

1. Switch the layer visualization to hexbin.
2. Wait until hexbin rollup status is ready and matches the current data revision.
3. Zoom to change H3 resolution; the map remounts the hexbin tile source for the active resolution.

While a rollup is building or stale, Tamaat shows base points instead of fake bins.

When tiles refresh

Clustering and hexbin rebuild on edit session close, not on every feature save. See Edit Session and Tile Rebuild.

Common errors

• No clusters appear — confirm the layer is points, clustering is enabled, and cluster_rollup_status is ready for the current revision.
• Hexbin controls are dimmed — the rollup is still building or stale; keep working on points until the update finishes.
• Median unavailable — stored hexbin rollups do not support median yet; choose count or another supported statistic.

FAQ

Do style-only changes rebuild clusters?
No. Palette and Color by changes recompile MapLibre paint from the existing manifest.

Can I use clustering in heatmap or hexbin mode?
No. Clustering mounts only in default vector visualization modes.