Need to figure out a way to make them useful, and not too busy

Right now, it's not possible to see street names. In order to have a text string follow a LineString like one expects on a map, MapBox requires LineStrings. However, we're using MultiLineStrings because the data in the shapefiles is all chopped up into each segment along a block (basically, any point where two roads intersect).

Possible solutions:

1. Merge all MultiLineStrings into LineStrings. This would require some way to determine which points are "close enough" to be merged. There's shapely.ops.linemerge (discussion on StackOverflow), though that would require more work because a) I'm not sure how precise the overlapping points are, and b) there are certainly discontiguous street segements. So we'd probably end up with more streets.
2. Hope that MapBox starts supporting string labels for MultiLineString. 😬
3. Add a popover to the existing street MultiLineStrings, presumably using the hover trick.

3 is the most plausible solution.

Provide a way for users to highlight issues with an ED

• Map picker (z-index)
• Opacity
• Show/hide map layer

Add an easy way to get back out to the overview

Key things:

• Change the year picker to a popup button when width is sufficiently small
• Put the info panel below (maybe in a drawer?) on a phone

• EDs
• Metros
• Roads

When a user successfully searches and picks a result, she should be taken there. This implies that we need the road layer. #7