I'm having trouble understanding the flow of commands needed to produce metatiles.
tileserver runs successfully, serving tiles from either tile store (local folder via tilequeue process) or directly from postgres.

From what I understand (and please correct me where I'm wrong):

• once data is in postgres, there are 2 flows:

  1. zoom <= 10
  2. zoom > 10

• for zoom <= 10, the tiles generation would be either with batch or on-demand to generate, store (in s3 or similar) and serve as is, via cdn and use caching (cdn or redis) where appropriate

• for zoom > 10, rawr files needs to be created from which the tiles will be generated

rawr tiles, from what I gather, are created via its own queue (differnet from the tilequeue process queue) and are seeded from the TOI?

• what command(s) are needed to generate them? tilequeue rawr-process produces a admin_areas relation does not exist and tilequeue-rawr-seed-toi explodes after some tiles due to the assert len(coords) == 1

I noticed a (undocumented) command for metatile and meta-tile-low-zoom which seems to fit the process described above but these command are a per tile commands, and do not read from a queue (which I'm not sure how the queue is populated, and by what logic and by who)

thanks