Skip Navigation

Data Caching For Maps Addresses

Google Maps and Azure Maps APIs have a limit on requests that a registered API key can perform. To reduce the number of requests, the Toolset Maps plugin stores address data as soon as possible.

In the case of the Types Address fields, the data is stored when the field is saved. When you use the Toolset Maps plugin, Views will cache every address that needs to be displayed on a map. There are two reasons for this:

  1. It allows Toolset Maps fast access to the latitude and longitude coordinates. This results in a much better timing than if it fetches the data directly from the Google Maps or Azure Maps APIs, every time the coordinates are needed.
  2. The Google Maps and Azure Maps APIs have a limit on requests coming from a registered API key. This limit is set per day, meaning that you could reach this limit quickly.

Inspecting and Removing the Stored Cached Data

Go to Toolset → Settings,  click the Maps tab, scroll to the Cached data section, and click the Load stored data button. A list of all cached map data appears. The following image shows an example of the Cached data section stored data.

Caching Settings for the Toolset Maps plugin
Caching Settings for the Toolset Maps plugin

You can delete each row individually. In the case of the Types Address fields, the data is stored when the field is saved.

Originally written
December 30, 2015
Updated
June 29, 2020