Specifying mbtiles layer in tessera conf?

[afrigeri]

Is there a way to specify the mbtiles vector_layer into tessera conf? Or, do I have to specify it somewhere else, i.e. on the client? Thanks.

[mojodna]

Not at the moment, though I've been considering a way to augment / override the TileJSON that's already generated.

Tessera passes through the TileJSON provided by a source, mbtiles in this case. If index.json isn't including vector_layer entries, it's because the metadata in the MBTiles archive is also lacking it. The best solution is to overwrite the metadata in the MBTiles archive with a more complete description of what's present (sorry, I don't have any good tips on doing this).

How did you produce the MBTiles archive?

[afrigeri]

Thanks for the reply! I've made the mbtiles with tippecanoe, with 38 layers corresponding to 38 geojson files - the final mbtiles is about 2Gb - for that reason I was thinking about using layers. Of course the backup solution is to produce 38 different mbtiles, with a tessera config - but I have a bunch of these vector files to serve (more than 1000).

[mojodna]

Yeah, layers seem like they would make sense.

Rather than treating tessera as a standalone server with a complicated configuration that needs to be kept in sync, you could try using it as a library and handle the layer management in code.

fp-tiler does this to dynamically tile rasters (where the slug matches a snapshot id).

sm2 is another example.