Well, it's over six months since swapping over from MotionBased, and of the three basic pieces of data I require from a GPS, Garmin Connect is still only reporting one of these correctly. I need:
o DISTANCE - that's fine;
o TIME - this is often overstated, as GC doesn't report MOVING TIME - essential for runs, rides etc interrupted for any reason (regrouping, traffic lights, etc etc);
o ELEVATION - hugely variable and erratic - MotionBased's correction algorithm was fine on this.
Surely this situation has gone on for long enough now - can you please get these previously-correct (in MB) data elements to be reported correctly as top priority, before adding in any more GC features? Two out of three basic pieces of data being wrong this long after the migration is a very poor score. :(