manby
Vector tiles, fast
The same tiles as tippecanoe, eight to eighteen times faster, in less memory. From GeoJSON, FlatGeobuf, CSV or Geobuf.
On a Snapdragon X Elite with 12 cores, median of three runs, against tippecanoe 2.82.0. The tiles are the same. On the roads and the tracts to z12, much of tippecanoe's time goes to its SQLite step on this machine's compressed disk. The commands, and the same benchmarks on macOS
Use it as you use tippecanoe
manby takes tippecanoe's options, so a tippecanoe command works with manby in its place.
manby -zg --drop-densest-as-needed -o places.pmtiles places.geojsontippecanoe's tiles
manby makes the tiles tippecanoe makes, for every option it supports. All 188 of tippecanoe's expected test outputs match, from GeoJSON and from Geobuf.
Every core, all the time
The features stay in memory, sorted once. The tile pyramid is made on every core at once, big tiles are split across threads, and oversized tiles are retried on data already in memory.
Less memory
On every benchmark manby's peak memory is below tippecanoe's, on macOS and on Linux, and less than half of it for the points on a Mac.
Larger than memory
With --memory-budget, 40 million points (5.6 GB) take 79 seconds in 1.1 GB on a Mac, where tippecanoe takes 652 seconds and 10 GB.
tile-join too
manby join merges, joins, filters and converts tilesets like tile-join, with the same tiles, two to thirty-five times faster.
PMTiles directly
PMTiles archives are written directly, without the SQLite database tippecanoe goes through. MBTiles and directories of tiles work too.