We’ve been pretty busy polishing up the new Garmin Push API, but we still made a little time to add some small but helpful features.
Projected finish time
If you’ve ever run a marathon, you’ve probably wondered: “If I had run the second half as fast as my first half, what would my time have been?”
Well, now you can. Just highlight a section of your pace graph on the bottom of your By Run page. And, of course, you can do the same for any segment of any distance run.
Stryd power meter support
We’re now importing running power from the Stryd power meter. Power meters are cool because they tell you how much energy you’re using instead of how fast you’re running. If you run faster but your power goes down, that means that you’re running more efficiently, and improving running efficiency is how you can see some of the biggest gains in performance. Power meters are also cool for trail runners, because they are unaffected by hills. Top athletes run fast down hills and slow up hills, but their power and heart rate stay mostly flat.
We’ve added an option to correct the elevation for runs where the elevation looks a bit (or a lot) wonky. The data available for this correction comes from satellite topography, so the resolution is not wonderful. If you run over a bridge, it’ll show you running across the river. If you run through a tunnel, it’ll show you running up and over the top of the tunnel. GPS-based elevation data is, in general, pretty terrible and only a few lucky people have barometric altimeters (woop iPhone 7!), so there’s a lot of messed up elevation data out there. Using this option can be a big improvement.
After correcting the elevation, you can also click the bad elevation tag again to remove the elevation data.