We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.
The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ...
Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.
Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.
Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.
Heatmaps display colors on the map to represent the density of points from a table.
Table of Contents
The table must have a Location column that contains individual points. These can be latitude/longitude pairs in a single or separate columns, geocoded addresses, or KML with <Point> elements.
If all of this is too complicated for you, you can always check alternative software for Google heat map creation which might better suit your needs.
Heatmaps use the Maps API Heatmap layer, so they pull data into the browser before displaying it. This is unlike Fusion Tables feature maps that render map tiles on the server. Because of this, only the first 1,000 rows are mapped. You can add filters to your map to keep the row count under the limit.
Heatmaps of geocoded addresses can be viewed in Fusion Tables but cannot be published. Publishing would extract the geocodes, which is not allowed by the Google Geocoding API’s usage limits.
The HTML/JavaScript generated in the dialog shown with Tools > Publish uses the Fusion Tables API to fetch the rows, parse them for use in the heatmap, and draw the map. If you plan to have more than minimal traffic for the map, you need to get an API key and enter it into the publish dialog’s API key field. That will be included in the generated code.