This is the non-Supporter LifeMap, which has an activity count limit for certain browsers/devices.
This is the Supporter LifeMap, which adds some features (Activities are filterable by date, individual activity highlighting on hover, each activity is a link, and it’s wildly faster). Each user has two LifeMaps: one that contains private data, and another that contains public data (or is empty if the user is completely private).
How it’s generated
First, it starts at the individual activity level:
Each activity has a series of GPS coordinates that your tracking app records while you’re out on your run/walk. After the activity has been synchronized into CityStrides, there’s a bit of code that collects all of the activity’s coordinates & uses it to generate an “encoded polyline”.
- Explanation of in-browser cache as it relates to the advanced LifeMap
- Explanation of how the site uses browser storage for the regular LifeMap
- Explanation of what the ‘Reset Browser Storage’ button in the Settings page does
- Better explanation of features