Remove redundant tiles in MBTiles
527
A MBTiles introspection tool for optimizing and verifying MBTiles files.
You need Python 2 or Python 3 installed on your system.
git clone https://github.com/lukasmartinelli/optimize-mbtiles.git
cd optimize-mbtiles
pip install -r requirements.txt
If you are using tilelive-vector or a tile server like tileserver-php which supports maskLevel you can save a lot of redundant data in your MBTiles file by backfilling missing high zoom levels with data from low zoom levels. This approach is used at osm2vectortiles to decrease the size of the MBTiles downloads.
Check if a file contains any removable redundant subpyramids.
./optimize.py check <mbtiles_file> -z=<mask_level> [--scheme=<scheme>]
You get back a list of all optimizable subpyramids.
8/125/188 OPTIMIZABLE
Once you know your file contains redundancy you can remove the unnecessary tiles. Removing subpyramids will gain a lot of space in big files since you no longer need to store all the references to the binary image data. If you render vector tiles of the entire wolrd to a file with 70GB this can decrease the size by over 12GB.
./optimize.py remove <mbtiles_file> -z=<mask_level> [--scheme=<scheme>]
Check if a file contains any tiles larger than 500KB.
./verify.py size <mbtiles_file> -s=500000
You get back a list of all tiles larger than 500KB.
14/8024/12095 506 KByte
14/8025/12095 1.1 Mbyte
Given you have a MBTiles file you want to verify that that
all tile data for the XYZ subpyramid 8/125/188 down to zoom level 14 is present.
./verify.py missing <mbtiles_file> 125 188 -z 8 -Z 14
Given you have a MBTiles file you want to verify that only the exact
tile data of the XYZ subpyramid 8/125/188 down to zoom level 14 is present.
Any additional data is treated as redundant.
./verify.py redundant <mbtiles_file> 125 188 -z 8 -Z 14
tilelive-vector supports the powerful concept of mask level.
To avoid requiring many duplicate or empty vector tiles to be generated at high zoom levels, the backend source can specify a
maskLevel. If a vector tile is not initially found at somez > maskLevel, Vector will issue an additional request to the backend using the parent tile of of the request atmaskLevel. This allows a lower zoom level to backfill high zoom levels.
If each descendant tile in the entire subpyramid 8/100/101 has the same binary
data as 8/100/101 we can remove all descendants. A request to 9/200/202 will
then receive the data from 8/100/101 without the need of duplicating the data
across multiple zoom levels.

Content type
Image
Digest
Size
254 MB
Last updated
over 10 years ago
docker pull lukasmartinelli/optimize-mbtiles