You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the volume of incidents displayed on the map, the default google "Pin" on the map can become cluttered and subtract value from the map until the user zooms in.
For high density - high level views like the default one implemented, a hotspot / heatmap layer of the data for Google Maps could help solve this issue. There are a few hotspot libraries existing out there that could be leveraged as well as I believe it's available in the Google Maps API. By adding this as a layer, this will not modify the current implementation of the pins, but could "easily" add the functionality to toggle on and off this feature.
The text was updated successfully, but these errors were encountered:
I've used heatmap.js before (http://mycodespace.net/projects/epauvindex/) and the integration was pretty simple. I'll take a look and see what I can come up with. There was a request for this from the Rochester subreddit as well - i just haven't gotten around to implementing everything I've wanted too yet! Thank's for the suggestion!
Due to the volume of incidents displayed on the map, the default google "Pin" on the map can become cluttered and subtract value from the map until the user zooms in.
For high density - high level views like the default one implemented, a hotspot / heatmap layer of the data for Google Maps could help solve this issue. There are a few hotspot libraries existing out there that could be leveraged as well as I believe it's available in the Google Maps API. By adding this as a layer, this will not modify the current implementation of the pins, but could "easily" add the functionality to toggle on and off this feature.
The text was updated successfully, but these errors were encountered: