matched-activities

Group Strava runs by route similarity using polyline decoding or start and end coordinate signatures to identify repeated routes and display pace progression trends. This allows you to compare performance across the same routes over time.

Polyline similarity matches repeated running activities by decoding route data into coordinate signatures and clustering runs that share the same path. It evaluates geometric similarity to form groups with a minimum number of occurrences for reliable pace tracking.

Yes, you can analyze pace progression for Strava run groups within a configurable time window. The analysis operates exclusively on Run activities, filtering data by your specified dates to calculate and report pace trends for matched routes.

The best way to export grouped Strava activity data for downstream training analytics is using the CLI JSON output. It provides structured route grouping and pace progression data while gracefully handling missing tokens and persisting coaching observations to memory.

Yes, route grouping handles missing Strava API tokens and incomplete activity data gracefully. The system recovers from common errors automatically, ensuring that missing data does not interrupt the pace progression analysis or the JSON output generation.

A valid matched activity group requires a minimum number of occurrences configured by the user. This threshold ensures that pace progression analytics are only reported for routes repeated enough times to generate meaningful training insights.