[Resolved] With Toolset Maps caching of coordinates, does displaying maps still count towards Google API use?

[Author]

Posts

[webD-3]

Our customer (historyinyourownbackyard.com) is running into issues where he's exceeding the new threshold Google threw at us out of nowhere, and his site is starting to display the over-quota error message. Shouldn't caching help prevent him from hitting the 28,000 limit? It does appear all his map points are cached, but he's still exceeding the threshold?

[webD-3]

I updated his key to a new one, so the error is gone at the moment, but we are still wanting a better understanding of the caching situation. It seems like it should only hit Google rarely with caching?

Also, have you guys considered integrating with leaflet, since it's an opensource/free system?

[Nigel]

Hi there

The caching mechanism reduces requests but it doesn't eliminate them, by any means.

When you enter an address the coordinates are looked up and cached, and these cached coordinates are used when filtering by distance, for example, and when maps are displayed these coordinates are used for the markers rather than addresses, which would need converting to coordinates, but dynamic maps still count as hits on the API for every page visit.

The only alternative is to create static maps, to create maps with required markers directly in Google and then embed these static maps on your site, there are no API implications from doing this.

When Google announced the pending price increases we added support for Microsoft Azure maps which has more generous/cheaper allowances, though you would need to verify and monitor that for yourself.

We have plans to add OpenStreetMap as a source (which leaflet uses), but no fixed timetable for when work on that will begin, so I can't give you any estimates I'm afraid.

[webD-3]

Thanks for the info, Nigel.

[Tinsterman]

I have the same problem with a client. What solution did you go with in the end? I am thinking of switching to Azure