This method adds an array of data points H.data.heatmap.IDataPoint to the heat map. The heat map provides a visual representation of these data points. Note that there is a significant performance cost to adding and removing data, once an overlay has been created. This is related to the rendering engine and tile caching. If you wish to add data after the tiles have been created, the cache must be cleared and all tiles need to be recreated. For this reason, heat maps should not be used to create fast animations.

This method adds an array of data points H.data.heatmap.IDataPoint to the heat map. The heat map provides a visual representation of these data points. Note that there is a significant performance cost to adding and removing data, once an overlay has been created. This is related to the rendering engine and tile caching. If you wish to add data after the tiles have been created, the cache must be cleared and all tiles need to be recreated. For this reason, heat maps should not be used to create fast animations.

As new data can invalidate the already generated tiles, those tiles should be removed form the tile cache. Use the argument opt_hardReload to change the mode determining how those tiles are removed. Two modes are supported:

hard: This mode immediately removes the cached tiles from the tile cache and forces the provider to re-fetch the tiles. Currently cached tiles are not used for rendering.

soft: This mode only marks tiles as invalid and requests the tiles to be re-fetched at the earliest opportunity. The provider does not invalidate the cache immediately in this case. This means that cached tiles can still be rendered while the updated tiles are fetched.