[Resolved] New google policies vs. calls made by Toolset Maps
This thread is resolved. Here is a description of the problem and solution.
Problem:
New google policies vs. calls made by Toolset Maps
Solution:
we are aware of those new Google API changes about the billing changes and limit of request. We already filed feature request to our Devs to make Toolset maps plugin compatible with those new changes.
This support ticket is created 6 years, 6 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
1) Can you explain which aspects of the Toolset Maps would generate a call that begins to count against an api limit - and then, which api limit so we know the available volume/etc.
2) Also, for things like markers - does quantity of markers (or any other specific usage beyond a 'map view') have any impact vs. the limits?
Hello. Thank you for contacting the Toolset support.
Yes - we are aware of those new Google API changes about the billing changes and limit of request. We already filed feature request to our Devs to make Toolset maps plugin compatible with those new changes.
Our Devs are on it to implement it but it may take some time. Please note that there is no ETA on it. Please check our blog to get latest updates:
=> https://toolset.com/blog/
I understand that you may be making some changes in the near future... but I am trying to understand how it is impacted *now* with the current methods Toolset maps is using...
If you could recheck my questions in more detail, I would appreciate it. I will try to shorten them a bit to clarify what I am asking:
1) Which aspects of the Toolset Maps currently would generate a call that begins to count against an api limit?
2) Does quantity of markers (or any other specific usage beyond a 'map view') have any impact vs. the limits?
We are about to launch something with a number of maps and a lot of markers, generated via filters. And so, we are very interested in the current condition.
1) Which aspects of the Toolset Maps currently would generate a call that begins to count against an api limit?
=> Toolset Maps JS loads GeoCoding API to make a call. It will make one call per address. But, it caches, so once it has an address, it won't ask the API any more.
2) Does quantity of markers (or any other specific usage beyond a 'map view') have any impact vs. the limits?
=> ) It does have an impact, but it's very limited, since we cache the address got from API. Queries potentially have a bigger impact.
Google offers 40,000 calls to geocoding API for free monthly. Most users will not use that much.
1. Can you tell me, when it caches - is that on a per user / session basis or for the site in general? And how often does it recache?
2. I presume the map itself is a call with every new page load?
We have ~200 possible markers (over 4 different maps representing different areas - so not all displayable at one time - but each with filter lookup) - and on current (non-wordpress) site, average around 600-700 visitors/day - so the details are very important. The current site about to be replaced uses a different map system (not google) - so kind of a bummer to see this announcement lol.
1. Can you tell me, when it caches - is that on a per user / session basis or for the site in general? And how often does it recache?
=> It will cached the address for the site in general, and keeps indefinitely - it is not very likely that the latitude and longitude of an address will change as lat and long should be unique to specific address.
2. I presume the map itself is a call with every new page load?
=> It will cache the each new address first time and then if map loaded it will check in cache and if address available in cache it will not make a API call but use the address available in cache.
Hi so it seems good news related to address / marker calls then - thank you. ?
I have one more clarification:
When I ask about the map itself being a call upon page load, I am referring to the following google pricing chart.
hidden link
There are 3 sections, Maps, Routes and Places
The last one, 'Places' - it seems the Call being made by Toolset Maps is 'Geolocation' and so we can see the 40,000 Call limit here.
So then, there is also 'Maps', and here it is referring to Loads. So it seems when a map itself is loaded, one of these map types is being used. So can you tell me, which one is being used? I am guessing 'Static Street View' but not sure. And confirm then that each time a page is loaded (or reloaded) with such map it is a 'Load' against the specified limit? I imagine this is not something that can be cached unfortunately?
The last one, 'Places' - it seems the Call being made by Toolset Maps is 'Geolocation' and so we can see the 40,000 Call limit here.
=> Well - I already confirm with you that Toolset maps uses GeoCoding API (that also shared same number 40000 calls per month) as you can see with my previous reply here:=> https://toolset.com/forums/topic/new-google-policies-vs-calls-made-by-toolset-maps/#post-875396
So then, there is also 'Maps', and here it is referring to Loads. So it seems when a map itself is loaded, one of these map types is being used. So can you tell me, which one is being used? I am guessing 'Static Street View' but not sure. And confirm then that each time a page is loaded (or reloaded) with such map it is a 'Load' against the specified limit? I imagine this is not something that can be cached unfortunately?
==> Basically we are using Dynamic Maps API to load the maps.
It seems that Google has change the API names, so I raised the related query in front of our Devs and I will get in touch with you with all accurate information as soon as I know more.
Ok. So it is the 28k loads. I wonder if the 'Static Map' could be an end user option (such as, for certain outputs this could be an alternate option) given that it affords 100k?? but of course I do not know the functional difference as it relates to Toolset Map output.
I ask on Static, because in the bigger picture, obviously we are not getting 28k loads and also 40k calls - as both will be working together towards the single allowed $$ credit :-(. So it is important to understand every call / load implication. Fortunately your address caching seems to really limit that requirement, so I hope it plays out that way. Clearly *any* cache opportunity in this case is a game changer for anyone using maps as a key element with enough traffic.
