You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New tilequeue commands have been added to help deal with common issues:
status returns information about whether the tile is present in storage, the tiles-of-interest (TOI) list and the in-flight list. This can help diagnosing issues with bad or stale tiles being returned.
stuck-tiles lists tiles which are present in storage but not in the TOI. These might be causing problems, since they will not be updated. delete-stuck-tiles takes the list output by stuck-tiles and deletes them.
Database queries are now per-table rather than per-layer. This can help efficiency slightly, as the database may be able to optimise the number of blocks read from disk into a single pass. However, the main reason was to prepare for RAWR tiles, which are collected into per-table files.
Added support for RAWR tiles. These serialise the data for several tables into one static file, which can then be used to render tiles without needing further access to the database, which should allow it to scale more easily.
Added support for 4x4 metatiles, with optional "1024px" size tile.
Tilequeue process now logs in JSON format. This allows the use of some more advanced query features of the AWS CloudWatch system.
Added support for building a Docker image of tilequeue.
There are alternative, configurable implementations of the TOI, including all and none. The multiple queue job dispatcher can be configured to route based on TOI membership. These changes together mean it's possible to configure the cluster to run in "global build" mode, where all tiles are rendered, but the TOI decides priority, and in the normal mode, where only tiles in the TOI are rendered.
Details
Use pypi for mapbox-vector and edtf packages. See #219.
Update output props processing for normalized SQL. See #221.
Create source metadata based on query results. See #222.
Use consistent precision for different sizes of MVT tile. Previously, all had been 4096 coordinates per tile (a.k.a. "extent"), now the 256px are 4096, 512px are 8192, and so on. See #304.
Add batch-enqueue command to start AWS Batch jobs to render tiles, and batch-process command which is run in a single instance of an AWS Batch job. See #315.