paulmach
Joined 14 years ago
Joined 14 years ago
We're not considering opening the data. But we are working with cities to help improve their bike infrastructure
http://bikeportland.org/2014/05/01/odot-embarks-on-big-data-...
I couldn't get the styles I wanted with mapbox so I just defaulted to google.
I've also built another tool, Slide, to help use this data for faster editing, see http://labs.strava.com/slide/
I've looked into a couple of these cases and it's friends "coming by for a ride" or them stopping at their house mid ride.
I'm working on further eliminating these points by just not included "stopped" points. I've also tried doing some image processing to remove these hot spots but have had mixed results.
An overlay would be nice, but there is a version for both running and riding.
It's not updated on every upload, but pretty much the complete dataset.
Maybe unnecessarily complicated, but it does provide really good local normalization. You also get cool looking shading like in this location http://labs.strava.com/heatmap/#16/-121.76487/38.49134/gray/...
The data is aggregated into a quad tree based on number of GPS points in each pixel. Tiles are then served on the fly using Go and C using CGO.
Cloudfront tackles most of the load, but the load balanced i2.xlarge instances can do about 300 tiles a second.