You did not cross any segments NEW PROBLEM

That would be a GC issue not an Edge issue. GC takes the GPS data from the ride file and then matches it against the segments. It does not take the segment information from the Edge. This way GC can support data from any device even if the device does not support segments.

That would be a GC issue not an Edge issue. GC takes the GPS data from the ride file and then matches it against the segments. It does not take the segment information from the Edge. This way GC can support data from any device even if the device does not support segments.

Hi Alan and thanks for your reply. So GC re-invents the wheel?
Yes I thought might be the case, its why I wasn't too bothered with the first instance and assumed it would sort itself. Which it hasn't.
Because these fw updates invariably necessitate sensor discovery & inputting basic data (seems wholly unnecessary) I'm not too keen to update that often. Case in point is FW 6.46 which I d/l as soon as, but assumed it wouldn't fix much so, left it unused. Now, I see that it fixes segment updates & wonder if this is the issue I have.
I'd always assumed the fit file included segs but maybe not, certainly I had a fit file which was corrupt but had everything except 1 segment which was exceptionally hard to take as I'd beaten a difficult climbing pb by a significant margin - oh the joys of the 1030! If GC shows a continuous route, how did it lose one complete segment? Without segments the 1030 is barely any use to me.

Any idea how to resolve the problem with GC? Oh and Merry Christmas

The FIT does include segment information, but both GC and Strava are masters of their own segment data so both sites look for and compute segment matches. I typically don't use GC segments, but let me switch over to GC segments for a while and see if I get the same issue.

If I can reproduce the issue I will flag it with Garmin, but I suspect that most of the US employees are off until the New Year.

I would recommend saving off that important activity file to your PC. That way you can manually reload it at a later date if needed, by deleting the ride of GC and reloading the activity.

So updating to v6.46 did generate segments on a test ride today. Plan on a bigger ride tomorrow so I'm hopeful. Same problems with gloves, incident detection farcically set-off, had to re link every sensor and connecting to phone tok a very long time >1 min 50secs.
If this has resolved that particular segment / data corruption issue it does beg the question as to how thorough G test these things before release? I suppose with a huge number of unpaid guinea pigs desperate to make the 1030 work and already predisposed two wards expecting rubbish then it really doesn't matter.

All segments properly recorded and used by GC so firmware release was the problem.
Gloves achieved a whole new level of farce today.

Problem has returned.
Today's ride should include 7 segs and yet I'm told I did not cross any segments.
I take back my favourable comments about G finally getting problems solved. with fw7.20
Jinxed or spoke too soon?

And without changing a single thing, lunchtime shows segments in GE
That's the best thing about machines, they are entirely consistent, unless its my Garmon Edge 1030