Big discrepancy in climbing data VeloTrack, Isaac, Garmin
Posted: Thu Apr 12, 2018 3:46 pm
I don't expect identical climbing data from my Garmin Edge 1000 and my PowerPod readout in Isaac, but with the addition of VeloTrack on my iPhone, the discrepancy is too large for me to ignore.
On my most recent ride, my Garmin Edge 1000 said I'd climbed 730 meters, while my PowerPod reported it in Isaac as 627 meters. They aren't precision instruments, and I wouldn't write in to complain about a relatively small discrepancy like that. But the GPS Tracker feature, as reported in the VeloTrack app on my iPhone, lists the climb as 1272 meters. That's more than double the Isaac and nearly double the Garmin.
All three are set to record in metric. The Garmin is closest to the official climbs recorded for various rides, and for the elevation change noted on markers on the way up marked mountain roads that have no flat or downhill sections.
Any suggestions for what I may have set wrong in the VeloTrack?
As for the GPS Tracker, I love the Google Maps version of my route. It allows me to examine my power output on rides by exact location, which I find useful in spotting "lazy" sections where I need to work harder.
Thanks,
The Shovel
On my most recent ride, my Garmin Edge 1000 said I'd climbed 730 meters, while my PowerPod reported it in Isaac as 627 meters. They aren't precision instruments, and I wouldn't write in to complain about a relatively small discrepancy like that. But the GPS Tracker feature, as reported in the VeloTrack app on my iPhone, lists the climb as 1272 meters. That's more than double the Isaac and nearly double the Garmin.
All three are set to record in metric. The Garmin is closest to the official climbs recorded for various rides, and for the elevation change noted on markers on the way up marked mountain roads that have no flat or downhill sections.
Any suggestions for what I may have set wrong in the VeloTrack?
As for the GPS Tracker, I love the Google Maps version of my route. It allows me to examine my power output on rides by exact location, which I find useful in spotting "lazy" sections where I need to work harder.
Thanks,
The Shovel