I’m not sure I understand correctly. Are you saying that tilemaker doesn’t do any feature merging, but you do, so OSMF tiles are much lighter for users than the ones I can generate with tilemaker?
tilemaker does do feature merging, but you should configure it in the json config file. See combine_below and combine_polygons_below in tilemaker/docs/CONFIGURATION.md at master · systemed/tilemaker · GitHub
Thanks for pointing out these options ! I tested the impact of combine_xx options starting from the configuration in shortbread-tilemaker: removing all feature merging increased the weight by only 3%. Does it mean that the merging options in shortbread-tilemaker have not been optimized at all ? (I noticed for example there is no combine_polygons_below options defined) Where can I find the merging options used for OSMF tiles for comparison ?
I noticed that the tiles are served (and transfered to the user) without compression, could you please confirm this ?
- is it a server configuration choice you made ?
- is it a limitation of the protocol or the MVT Content-Type ?
- is it a constraint to allow minutely updates ?
- is it because feature merging already compressed the tile ?
(I’m not a network expert and I apologise if these questions are naive)
I’ve fixed the Fastly config and they should now be compressed. Most browsers will be served brotli compressed tiles.