Serving tiles

A map style embeds the MBTiles filename in its tile URLs (/maps/tiles/{tile_set}/{z}/{x}/{y}), so the tile_set segment doubles as a per-version cache key (tiles are cached 24h; styles and TileJSON are never cached).

The catalog

MBTILES_CATALOG is the single source of truth: a space-separated list of every MBTiles filename in /var/lib/db/ that a deploy downloads and serves.

• The service can serve any catalog entry by name. MBTILES_FILENAME and STREETS_MBTILES_FILENAME pick the defaults the style sources point at (both must be listed in the catalog).
• A file whose name starts with osm-woo-land or osm-woo-streets is served with the landcover-* overlay merged in at read time (LANDCOVER_MBTILES_FILENAME); the main combined tileset is not.
• A request for a tile_set not in the catalog returns 404. There is no silent fallback to the main tileset, which would serve wrong-schema tiles and poison the 24h cache under that name's URL.

Because every container serves every catalog entry, a rolling deploy is safe: keep both the old and new filenames in the catalog during the roll and any container (old or new) can serve either name. See Deploying for the rollout.

Endpoints

{z}/{x}/{y} are standard XYZ coordinates; the row is flipped to TMS internally when reading the MBTiles. Tiles are returned Content-Encoding: gzip, Content-Type: application/x-protobuf.