Don't calculate Pokestops, Gyms and Spawnpoints for larger areas automatically.

[Cronick]

As for someone that has decided to scan my home-country fully for routes.

When your polygons get over a certain size and complexity. It just takes forever to calculate the values for Pokestops, Gyms & Spawnpoints in the polygons, and puts the database up for a task that it's not happy about 😄

My suggestion would be to implement some sort of sweetspot by area size, or just a simple settings option to don't calculate these automatically when clicking on a polygon.

So instead you can click on an icon to get the values, instead of pushing a task to the database everytime you click on a polygon.

[TurtIeSocks]

I suspect that if we only add this limitation to spawnpoints then the other 2 queries will be fast enough that it shouldn't matter. (I believe it's a promise.all so the other 2 are likely always waiting for spawnpoints.)

[Cronick]

I suspect that if we only add this limitation to spawnpoints then the other 2 queries will be fast enough that it shouldn't matter. (I believe it's a promise.all so the other 2 are likely always waiting for spawnpoints.)

That could be an option as well yeah. Havn't look much into what query was taking the resources other then killing them, when I click on a polygon by mistake and overloads the database 😅

[lenisko]

I think I shared this idea, but possible only within my mind.... 😶

I saw it like a value field with sane default, if area is lower than X km2 pull the data automatically. Otherwise, add a button like mentioned in post above.