Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve route segments pages for progress tracking #256

Open
pixelspark opened this issue Aug 24, 2024 · 1 comment
Open

Improve route segments pages for progress tracking #256

pixelspark opened this issue Aug 24, 2024 · 1 comment

Comments

@pixelspark
Copy link
Contributor

The route segments overview page could be a great tool for tracking training progress/trends over time. As a runner I would add sprint segments, some longer routes, maybe some with altitude differences, and then I'd like to see how I perform on those to get an idea of my performance on different types of routes.

In addition to the number of matches, I think it would therefore be very useful to show the following information there for each segment in a table:

  • Length of the segment
  • Tempo and/or total times, with link to corresponding workout, for:
    • Most recent attempt
    • Personal record (all time)
    • Personal record (last year)
  • Perhaps some sort of 'spark line' visualisation showing tempo development. Iirc Strava used to show you things like "Upward trend" or "downward trend" if X similar workouts where faster than the last N (probably still exists for paying members).

This info should be grouped (or filtered) by workout type.

The same details mentioned above could of course also be shown on the segment detail page, the spark line could be a larger graph with the same data.

@TheBig-O
Copy link

TheBig-O commented Oct 3, 2024

One additional item that would be a great add is the ability to manually select a route segment. I have several runs that don't show up when reviewing the segment that they should be associated with. My belief is that the start and stop points are just far enough apart that they don't link to the segment. (The rest of the route is a close to the same as it can get without actually stepping in the same footprints.)
If there was a way to add known runs to a specific segment, that would allow us to catch the odd run that is "slightly" different. Another option would be to have a "tolerance" setting to catch more of the runs that match the routes a bit more loosely or stringently. Though, a tolerance setting might be much harder to accomplish.
I find that I use the route segment page a lot to compare my performance and really like the information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants