Error fetching altitudes, elevation API daily request quota exceeded, spawn point failures

[Jabsu]

I mentioned these briefly on another thread, but I decided to make a new issue to get more visibility.

I've been getting these errors since the "# consecutive failures on #, will treat as an unknown from now on" errors surfaced (about a month ago, maybe?), though I don't know if they're related. Before those spawn point failures, the elevation API quota was never exceeded and there wasn't any altitude errors either.

There shouldn't be anything wrong in my configuration, but it's strange no one else has mentioned having the quota exceeded and/or the altitude errors. I've tried to lower the ALT_PRECISION, no luck there.

The spawn point failures are somewhat problematic too, as they slowly grow the unknown spawns value, which in the end will make the workers restless. Luckily I do have more than enough workers to compensate for this.

I'm using polygons as boundaries, MySQL as database. Known spawns are usually around 2000, though it varies a lot. I have 484 workers. Skipped stays at 0 until the unknown spawns value grows too high.

[DavePlater]

I've been having it for about a month too. I think it was the cause of not getting IV data for a bunch of my accounts too. I just got annoyed and commented out my google API key and turned off encounters. Cleared up my logs just fine as best I can tell.

[Jabsu]

Thanks for the reply, now I at least know I'm not the only one with this problem. I'm probably going to do the same as you. The altitude error spam is pretty annoying, indeed.