Gps sample rate and noise adding to wrong distance and times.
I posted something in feedback before seeing this but I figured I would past it in here too.
""Hi, Ive spent a lot of time trying gps logging apps this week, and though I want to use Strava, I cant get past how noisy the gps data comes out compared to Runkeeper, Nike+ and even my old Garmin Quest. For the most part I think it is great that Strava samples as fast as they do for especially fast activities, but because of the limitation of phone gps consistency, it is all over the place and adds the extra vectors for a total of .1 to .2 miles per mile. So while my garmin, runkeeker, and Nike+ all say the distance was 2.3 miles, Strava is saying it is 2.5 or more just because of the added noise. This could be easily fixed by just collecting 3 or 4 data points and averaging some of the data I would imagine, or perhaps even just lower the sampling rate? Would it possible to add an adjustable setting in the Android app to affect this? I tried the Strava Snap site but because some of the area I was traveling didnt have a trail to snap to, it does not work. I attached some pictures of the other apps reckoning of position data that was recorded at the same time with Strava(same walk) to compare vector lengths and over all smoothness. Nike and Runkeeper were on the same phone simultaneously with Strava while the Garmin Quest was on its own. The first Pic is Nike+(green)over Strava(purple). The second pic is Runkeeper over Strava. The third pic is Strava(purple) over the Garmin track. Notice how short the vectors are for the Strava output.Notice in the first pic how much longer the vectors are than the Strava vectors in the 3rd pic(almost 4 to 1). Also, the Nike+ and Runkeeper were almost identical in output. Perhaps and averaging or longer sampling interval would reduce some static and make the distance accurate? Thanks