This is partly a backend issue, the backend times out if the data request is too large. Essentially, for the global zoom levels like zoom = 0, the backend will try to render all the aggregationlayer polygons in one tile. This is not practical and leads to timeouts.
30s is a hard limit from aws api gateay, which is the service we use to distribute the api. So we can't change that.
On the frontend, we can reduce these errors by adding a minimum zoom level constraint on the protobuffer layers that renders the aggregation areas. This should be easy by using the minZoom property on the layer. See
This is partly a backend issue, the backend times out if the data request is too large. Essentially, for the global zoom levels like zoom = 0, the backend will try to render all the aggregationlayer polygons in one tile. This is not practical and leads to timeouts.
30s is a hard limit from aws api gateay, which is the service we use to distribute the api. So we can't change that.
On the frontend, we can reduce these errors by adding a minimum zoom level constraint on the protobuffer layers that renders the aggregation areas. This should be easy by using the
minZoomproperty on the layer. Seehttps://leafletjs.com/reference-1.7.1.html#tilelayer-minzoom
Sentry Issue: TESSELO-AUTO-2