Right now we mark and display every known pin near the user. However, sometimes it is less important to know precisely where cameras are, and more important to know where areas of high and low surveillance are. To this end we should develop a "surveillance heatmap", similar to the following:
This map will have to be calculated by the client based on pin locations. The heatmap display (and calculations) should be an option in UI settings.
This may require extensive code additions, or it may be trivially provided by the mapbox API already, and would therefore be a slight update.
Note: That link is to mapbox.js - there's probably an equivalent for Java/Objective-C, but I haven't run into it yet.
This isn't particularly useful until we have a lot of cameras, so it will probably be on the back-burner until after OSM integration. If someone is excited and wants to hop in and implement this though, then by all means.
Right now we mark and display every known pin near the user. However, sometimes it is less important to know precisely where cameras are, and more important to know where areas of high and low surveillance are. To this end we should develop a "surveillance heatmap", similar to the following:
This map will have to be calculated by the client based on pin locations. The heatmap display (and calculations) should be an option in UI settings.
This may require extensive code additions, or it may be trivially provided by the mapbox API already, and would therefore be a slight update.
Note: That link is to mapbox.js - there's probably an equivalent for Java/Objective-C, but I haven't run into it yet.
This isn't particularly useful until we have a lot of cameras, so it will probably be on the back-burner until after OSM integration. If someone is excited and wants to hop in and implement this though, then by all means.