Dan Rademacher

One challenge with an address search approach is that we are not actually including all ~20-30k Intersections in the app, but only the 500 most dangerous over last 36 mos....

Regarding this: >Question: Would this feature replace the existing "intersections" in "filter by boundary"? Or just augment it? I don't see this replacing the "500 Worst Intersections" as we have...

@postfalk: Can we assume then that _everything_ other than Layers and Rasters will be represented in the Observations table in some way?

Hmm, Eric split that menu out as a separate repo for reuse and it looks like that's for sure set here: https://github.com/stamen/legend-layer-menu/blob/5e6427e00016812096a7f1c717b3f41025373e3e/src/legend-layer-menu.js#L40 which gets pulled into your code on build...

markercluster.js is a potential solution: http://leaflet.github.io/Leaflet.markercluster/example/marker-clustering-realworld.388.html When markers are in the same location, they do this:  https://github.com/Leaflet/Leaflet.markercluster