Don't pan as much

[iandees]

When I was playing around with getting this to run directly on Chromecast, panning between edits every few hundred milliseconds bogged down the Chromecast and made it restart. The panning can even cause problems on slower desktops/laptops, too.

It would be nice to cluster edits together and have the browser center on a bounding box that shows a cluster of edits without panning between each edit. For bonus points, when we have a bunch of ways to draw inside the viewport we could try drawing them all at the same time.

[iandees]

One thought is to use k-means clustering to group the ways (via their bounding boxes) into clusters. We would pan to each bounding box cluster and show the data in that bounding box without panning.

There would have to be some fiddling to figure out what the right number of clusters vs. how big to make the bounding boxes (so we could still see the changes), but it would certainly lead to less panning.