Garmin segments not processed: You did not cross any segments.

8880747 said:

Thanks for having a look.

OK, I had a look, zooming to the max both the activity and the segment map, and comparing them. Your track sticks relatively well to the road. The problem is perhaps rather with the track of the original segment that is less accurate, and on some places passes quite a bit off the road. And there are a few places where the deviations of the segment vs your activity are on the opposite sides of the road. It could be perhaps the reason, but to verify it, I'd need to have the orginal activity in the FIT, TCX or GPX file format, so that I can try editing the offending points and try to find, when it starts to fit the Segment.

You could try doing it also. The easiest would be probably working with the GPX file, since there are many tools available for editing GPX tracks. Once you make the activtiy track fitting the segment's track better, you can try importing it as a new test activity, and check whether the segment is then recognized.

I have this same issue as of a couple of weeks ago.

Biked 11.5 mile singletrack, saved the ride. Biked the exact singletrack 10 minutes later. One ride shows 12 segments, the other 8. Now some rides on the same singletrack show 1 segment.

Both rides in Stava show all segments.

Does this have anything to do with Strava requiring paid subscription now to show segments in their app?

Did the algorithm change as part of Garmin's recent compatibility with routes in Strava and Komoot?

Garmin segments enabled.

Data on the web and app are the same.

I have this same issue as of a couple of weeks ago.

Biked 11.5 mile singletrack, saved the ride. Biked the exact singletrack 10 minutes later. One ride shows 12 segments, the other 8. Now some rides on the same singletrack show 1 segment.

Both rides in Stava show all segments.

Does this have anything to do with Strava requiring paid subscription now to show segments in their app?

Did the algorithm change as part of Garmin's recent compatibility with routes in Strava and Komoot?

Garmin segments enabled.

Data on the web and app are the same.

I have this same issue as of a couple of weeks ago.

Biked 11.5 mile singletrack, saved the ride. Biked the exact singletrack 10 minutes later. One ride shows 12 segments, the other 8. Now some rides on the same singletrack show 1 segment.

Both rides in Stava show all segments.

Does this have anything to do with Strava requiring paid subscription now to show segments in their app?

Did the algorithm change as part of Garmin's recent compatibility with routes in Strava and Komoot?

Garmin segments enabled.

Data on the web and app are the same.

Just changed sampling to every second and will see if that helps on the next ride. This has not been an issue in the past.

Both rides in Stava show all segments.

Does this have anything to do with Strava requiring paid subscription now to show segments in their app?

You wrote you see the segments of those rides in Strava. So does it mean you do have the paid subscription?

Biked 11.5 mile singletrack, saved the ride. Biked the exact singletrack 10 minutes later. One ride shows 12 segments, the other 8. Now some rides on the same singletrack show 1 segment.

I'd tell that more likely there is some relation to the accuracy of GPS. If the deviations of individual key points of the activity track differ more than certain thresold from the track of the segemnt, it won't be automatically associated with given segement. I do not know what exactly the threshold is, but from experience it seems to be some distance between 20-40m.

Zoom both the track of the activity, and the track of the segment to the max in two windows side by side (having two monitors is an advantage for that purpose). and compare the deviations all along the route - you may find the offending spots.

I do not have the paid subscription, but read last night that Strava will require paid in order to see segments soon.

The singletrack is only 2 to 3 feet wide, but I'll check the map overlays for GPS deviation. I ride this same singletrack weekly for the last 3 or 4 years.

Just strange how it has never been a problem then in the last 2 or 3 weeks it has major issues. No change in equipment.

Thanks!

Let me add a bit to this, I did the original post.

For me this occured 3 weeks ago. From there on no segment is shown over the whole period of 3 weeks that consisted of  ~700 km of riding.
The roads I passed have about 10 to 30 segments for a total of ~180. I rode those roads before multiple times. I guess 95% showed up overall, at least I rarely did recognize a missing one. Within the last 3 weeks, 0 segments showed up.

You looked at my data .. pretty accurate. That is true for at least 3 rides I looked at, about 350km of road. Each Strava segment always worked in each ride.

Yet, because I rode about 120 km twice, I could do the following experiment.

I added five new segments to the data of one recent tour and tried to match those with 'match new segments' to the tour overlapping with the other one. 

I did not cross any segments still.. according to garmin conect web.

So even to new, accurate data, segments cannot be matched any more.

For me the most likely explanation is that the algorithm changed and cannot match segments any more. Maybe because old segments are not accurate enough anymore for some reason?

Just weird and a bit frustating.

8880747 said:

For me the most likely explanation is that the algorithm changed and cannot match segments any more. Maybe because old segments are not accurate enough anymore for some reason?

Yes, I believe they recently reduced the maximal tolerance of deviations from the predefined segment track. I have re-checked some of my past activities for new segments recently, and some of the segmwents that were previously included, were removed after the re-check. 

The reason is relatively obvious - in many cases there are plenty of paralell roads and trails, and Garmin certainly had a lot fo complaints when segments were inaccurately assigned to activities that were done on a different track.I saw it in the past myself too - for example at running segments in my city, there are segments on the river navigation, as well as on the pavement or road above the navigation (each with different parameters), and often there was a mixup. With the recent change of lower tolerance, the mixup disappeared, with the consequence that at some activities, or at some segments with inaccurate GPS track, the matching is now more sensitive. Unfortunately it is a trade off, and it may be difficult to tune up the parameters so, that it fits all cases.

Anyway, the best you can do, is contacting Garmin Support, and bringing your specific case to their attention. If the number of cases similar to yours overweights the complaints about mixed up segments, they may decide to tune up the parameters again.

Ah very interesting, how did you get that information? That would indeed make sense.

Maybe Garmin should invest a bit in better algorithms and presentation, now that Strava is struggeling and introducing a paywall, it might be easy to make people switch and gain costumerns. (I guess they would rather buy Strava though)

Thanks.