My activity should have matched more than 9 segments. Is this number the maximum? Is there a way to dismiss/ignore some segments in order to prioritize other segments?
My activity should have matched more than 9 segments. Is this number the maximum? Is there a way to dismiss/ignore some segments in order to prioritize other segments?
There is a count limit or a computation time limit for segments (after they changed, that it only checks new activities for segments automatically).
But this limit is much higher then that - it bugs during…
The problems is not the number of segments. Garmin Segments have less tolerance for deviations from the segment track than at Strava, so if the GPS track does not match the segment track well, they won…
There is a count limit or a computation time limit for segments (after they changed, that it only checks new activities for segments automatically).
But this limit is much higher then that - it bugs during a long run around / through whole major city with plenty of segments.
On short runs it should be ok.
And no, you can't uncheck segments of other users.
And if segments were created after an activity, then you need manually re-scan for segments.
The problems is not the number of segments. Garmin Segments have less tolerance for deviations from the segment track than at Strava, so if the GPS track does not match the segment track well, they won't be matched. Garmin Segments are the most picky about the starting point - in fact you can be perfectly on the right track, but if the last keypoint of the recorded track is more than some 15m before the starting point of the segment, and the next point more than some 15m after it, then they will not be matched. It happens especially easily when the starting point of the segment is on a stright line, and when you use the "smart GPS recording". Using the mode "Every second recording" and/or slowing down at the starting point (or turning around) will help.
Well, possible reason may be, that Garmin does some kind of re-sampling of the track, when creating a segment from it, skipping some keypoints, it considers redundand, and adding others instead of them. In some cases, it can lead to deviations bigger than the tolerance. You coul only confirm or exclude it, if you zoom both tracks (the original, and the segment) to the max, and verify each keypoint (and especially the starting point). If there is a bigger difference than those ~15m, then it is the reason.
Open them in two different windows, side by side