Suggestion/request for segments

[Mountaingoat1]

Hello!

Let me suggest a different way to handle segments, one that was used in Sporttracks 3 (desktop version).

Let the user select a start and endpoint on a map, plus as many points in between as they want (or none). Set the recognition zone to 30 meters to account for gps innacuracy (if you pass the segment starting and ending point within a radius of 30 meters the activity will be matched against the segment). This is not the way Strava handles segments, but it would offer so much more freedom and less problems with matching.

Also one could add a "segment center" in the menu, where you can choose segment and then get your results there with all the data you want (avg. time, watt, hr, etc etc).

I hope this sounds like a good idea :-)

[Ale Martinez (Please don't email or cc me)]

El domingo, 19 de julio de 2020, 12:11:22 (UTC-3), Mountaingoat1 escribió:

Also one could add a "segment center" in the menu, where you can choose segment and then get your results there with all the data you want (avg. time, watt, hr, etc etc).

Using current versions it is possible to create a chart like this in Trends using R or Python.

The attached example shows the identified segments in the Date Range selected on the sidebar, ordered by name then Duration (so the segments stay together),

with these metrics: Distance, Elevation_Gain, Average_Speed, Average_Power, Average_Heart_Rate, VAM and date to identify the ride.

Metrics are in a list at the script beginning, so they are easy to add/remove.

Segments can be filtered in the same way, but this is likely not that practical.

Format can be customized looking at Plotly/Pandas the documentation.

Since it is a Python chart the easiest way to use it is with current v3.6 snapshots since they include Python, just enabling Python in Preferences with Python Home empty and restarting GC should allow to use the chart without Python knowledge.

[Mountaingoat1]

I'll check it out, thanks!

[Ale Martinez (Please don't email or cc me)]

The attached version is similar, but has some formatting for easy viewing: Duration in hh:mm:ss, precision set to 1 for most of the metrics and 0 for HR, removed "_" from metrics names