Rebuilding Strava's Global Heatmap
medium.com
medium.com
You can see the burning man "city" moves slightly each year creating an "echo" in the data.
https://labs.strava.com/heatmap/#13.49/-119.20399/40.78672/h...
Also, some people appear to have biked to the Farallone's https://labs.strava.com/heatmap/#12.41/-122.97170/37.71310/h...
This is neat =)
https://labs.strava.com/heatmap/#11.86/-118.45498/42.54408/h...
Alvord lake/desert in Eastern OR
For example:
Level 16 on the old heatmap: http://globalheat.strava.com/tiles/cycling/color3/16/33705/2... Level 16 on the new heatmap (empty tile): https://heatmap-external-b.strava.com/tiles/ride/blue/16/337...
1) Internal representation for building/serving: For vector, the data would have to be aggregated in some way otherwise it would be way too slow (for example, tiles having 10 million or more lines). How exactly to do that vector aggregation is a real challenge. If there is a good solution I'm not aware of it.
2) End product quality: everything is ultimately rasterized on the viewer's monitor. So if upstream resolution is high enough vector doesn't have any advantage here.