- Activity must pass close to segment start
- Activity must pass close to segment end
- Do not deviate from exact path of segment
- Additionally, the segment is based off the original activity's GPS. If your device, or the device that was originally used to create the segment, is suffering from GPS inaccuracy it can cause the segment to not register properly. While Garmin Connect will automatically adjust for some of this inaccuracy, it is still possible that an activity will not be matched to a segment correctly.
My questions based on the above:
Q1: Wouldn't my Segment GPS data *exactly* match the activity from which it was created? Assuming yes, wouldn't I be likely to be ranked on that segment I just created, especially if only 4 or 5 other users' activities are found to match that segment?
Q2: I have observed that my *subsequent* Activities *after* the date I created my Segment seem to match and I was ranked. Does this mean Garmin Connect's Segment feature is not going through my past Activities data... just analyzing Segments against Activities *after* whose create date is after? (i.e.: ...not even the past Activity on which the Segment was created?!).
I find it unlikely that an Activity track that I repeat almost exactly every week for years, fails to match the Segment GPS data for any of those historical Activities; a Segment created from one of those Activities... but, then matches the next immediate Activity on first date after the Segment was created. Is this a bug?
Sample Test:
I created a Segment from the Elevation Map on and Activity created way back in Jan of 2013. None of the dozens of Activities that I ran almost weekly on that same path registered, yet, one Activity that I ran this past weekend (after I created the Segment) finally matched and got ranked. Shouldn't Garmin Connect at least register and rank the Activity from which the Segment was created? (in this case, the Jan 2013 Activity?)
Thank you in advance for any insights / observations / advice other fellow Garmin Connect Segment users may have!
David J.