captnslow wrote:
I generally use my Garmin 810 for most rides and have used most of it's functionality at one time or another. For example, I downloaded the route map for L'Eroica and can use the Garmin for turn by turn navigation throughout the day 'just in case'. Most of the time it has more functionality than I require for a particular ride - but then again so does my smartphone for what I need at any given time. I previously had an Edge 500, but when cycling in distant countries the 810 has given a degree of comfort with the maps and nav features.
I tend to log most of my rides to Strava, and this is where it gets very interesting to those of competitive instincts. The biggest issue with Strava is that it provides "data comparison" sourced from variable devices. I have numerous examples where I have recorded the exact same ride on both my Garmin and my iPhone 6 plus and the data from the iPhone 6 plus provides me with roughly twice the vertical and 10% further distance than the Garmin (although the difference is NOT consistent)
Obviously if I want to do one of Strava's climbing challenges, I'd be logging all my rides from the iPhone! Also equally obvious is that neither the Garmin nor the iPhone are 'accurate'. I suspect that the Garmin is closer to the 'truth' as it's turn by turn nav seems more consistent than say using Google Maps on the iPhone. Google Maps is much more hand when you are truly lost, though...
iPhone stays in my jersey pocket in a Rapha Essential case (too expensive to destroy if I don't stay rubber side down) and the Garmin is attached via a headset mount over the top of my bar stem. Its a bit 'belts and braces' but I've never been let down.
If it's in a pocket not on your back then it doesn't have a full line of sight and gets jiggled around. Do both also use the GLONASS satellites?
Either way you've hit what I always say is a problem with GPS tracking, it is inherently I accurate for tight timings and pinpoint determination. Trees, building all effect it. It's just not that accurate anyway by design and so location movement is guessed using other methods (or should be to check if you actually moved that place or suddenly went faster.)
As for segment, if you see how start and stop works for timings you'll stop arguing who is quickest, especially if it's a few seconds apart. Pointless for short distances.