Optimize the SQL query determining the built-area tiles per district
The query executed in line 260 in Initializer fails with a timeout for the district FIN-28
, likely due to the large size of the district and the many tiles it encompasses. A possible reason for this is the fact that the query creates an INNER JOIN
with the boundary table to retrieve the boundary for the district. In Finalizer, we use a different technique for a similar problem by first extracting the boundary and then using it in the WHERE
clause of the query. This should be attempted here too.