Add analytics to searches
listen to keyup not keypress, so we can capture backspaces
When clicking on a search entry, get the data from the right place, and remove extraneous elements
set lastEvent to search when click on a search result
clearing the search box sets this.searchBoxClear to true
Don't debounce analytics events anymore
Don't set the query in the model, when it doesn't exist
Place the options dropdown in the right place when the search box is showing.
Don't resend event, now they are not being debounced
Don't track keys when enter is typed in the search box
When a forceUpdate happens, the lastEvent was a resize
Ensure that the points are aggregated in chronological order
Only get new points if a relevant value has changed.

So only trigger change events in the event_locations collection if the relevant keys have changed

Only set the model in the router if the appropriate value has changed.
When the highlights change, update the search panel, fetching data if necessary to repopulate the points
update the highlights if necessary after adding an event
Highlight is singular everywhere
pass the submission type, not through the type variable, as analytics overrides this
Only show lines on the map for events in the time range.
set the color for each path segment based on its start time
return distance in metres