[Resolved] Exaggerated amount of Google API Geolocation requests

[Author]

Posts

[Mario Hernandez]

Hello,

we have created a listing directory, available at hidden link

Although having only 937 posts with an address, we have every day a huge amount of API requests to de Geocoding Maps Service (8.641 requests in a week). Geocoding is the process of converting addresses (like a street address) into geographic coordinates (like latitude and longitude), which you can use to place markers on a map, or position the map.

Attached is an image that shows the numbers.

In our site, the API is only used by Toolset maps, and we understand that once the posts have obtained and cached the coordinates, Toolset Maps should not request again to convert the addresses to coordinates to google.

NOTE: We have a daily cron service that will search the custom posts, delete all of them via SQL query and replace them with the updated 937 post from our SQL server export main directory. In each replacement, only a few posts would have changed and the we can be sure that 99.9% of the addresses will not have change at all.

Is normal to see this amount of requests although the addresses have not changed?

Where do you think is the problem here?

I give you access here to two relevant things:

our site admin access (view credentials)

our phpmyadmin access (view in the ftp placeholders).

Thank you for your attention,

we understand that Toolset is a highly low cost resources optimized plugin, we want to clarify the issue,

thanks for the insight,

Best,

Mario

[Christian Cox]

NOTE: We have a daily cron service that will search the custom posts, delete all of them via SQL query and replace them with the updated 937 post from our SQL server export main directory. In each replacement, only a few posts would have changed and the we can be sure that 99.9% of the addresses will not have change at all.
Toolset stores cached geolocation information in a serialized data structure in the wp-options table. As long as the options table remains intact, the cached address geolocation information should remain available and the geolocation API should not be called again. However, if the options table is cleared or the data serialization structure is broken, the addresses must be geocoded again. Is the same API key used for your development site and the live site?