I am wondering what the difference is between 'Recorded Speed' and Calculated 2D' speed as produced from my Garmin Virb Elite. I see two separate categories and two separate gauges in the G-Metrix section when I am creating or editing a video. I do not use any external speed sensor on my bicycle. Both categories of gauge show speed data, but the recorded speed is always significantly slower that the calculated speed.
Here's an excerpt of a post from Falagar, who is a VIRB Edit Developer, where he sheds some light on the differences:
The point of adding this was to give users more flexibility, and allow them to choose if they want to use recorded speed (what the FIT file says how fast you were), 2D calculated (we calculate speed from position, might be useful in case the FIT speed is inaccurate for whatever reason) or 3D calculated (for events with fast changes of altitude).
Since your file won't have data from a wheel speed sensor or a barometric altimeter, I'd trust calculated 2D speed over the rest.
Hello I made a test using my Gopro Session with Strava on iphone 7 (which I believe is equipped with built-in Gyroscope). When I added the GPX file to my video the altitude looks fine but the speed was innacurate both calculated or recorded (even when the bike is stopped the speed is not zero). In some sections of the video there is no reading at all. I guess I need to do more tests and see. If anyone had already same issue you are welcome to comment :-) Cheers
