cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

The Hub is now in read-only mode as we make improvements to the Hub experience. More information is available here.

Jagged GPS recording with iPhone 13 mini

jdujic
Shkhara

My shiny new iPhone 13 mini has apparent issues with jagged GPS tracks, consistently adding some 2-5% to the total route length. For an illustration, check out the two runs of mine: the first from August recorded with iPhone 8, and the second from October with 13 mini:

https://www.strava.com/activities/7584918073

https://www.strava.com/activities/8025639130

The two tracks are supposed to be identical, and the physical difference should not exceed 20 m. Yet, the first shows up as 5.10 km, and the second as 5.31 km (therefore, making me appear faster than I am 😉). If you zoom in, you can notice the recording **bleep**-zagging, while the track is of course perfectly smooth.

While this is probably not a Strava issue, does anyone have an idea how I can possibly fix this?

As a feature request idea, Strava could probably implement some route smoothing by default for estimating distances. At least for faster activities such as cycling and running, it should smooth out such pesky gremlins.

1 ACCEPTED SOLUTION

Hi @jdujic

Thanks for getting back to us. Our Support Team would be happy to work with you to investigate this further.

Please submit a support ticket and somebody will be in touch.


Jane (she/her)
STRAVA | Community Hub Team

View solution in original post

12 REPLIES 12

Hi @Jane

It took a while to test it, but no, it did not solve the problem. I believe the problem is not in GPS as such, but in the algorithm how a gpx track is recorded and noise analyzed. Noise is immanent to GPS recording, but my particular GPS sensor seems to be more noise-prone, and it simply shows up in the traces.

There is, however, a well-known "noise cancelation" algorithm for GPS tracks known as Kalman filter. An excellent explanation and implementation can be found e.g. here. However, it seems that it is not implemented on Strava side either, and it should, at least as an option to post-process the data.

I've just tested Strava's "Correct distance" option on my recent hike, reported as 15.69 km by my iPhone (the correct distance is some 15.10 km, as previously measured by two separate smartphones), and it made a mess out of it, "correcting" it to 16.98 km. It seems something is seriously wrong there. A properly implemented Kalman filter can only shorten the reported distance, as it filters out all the wobbling, yet I've only seen the option increasing the total distance.

As a workaround for my problem, I ordered a Garmin watch as a present for my upcoming birthday. 😉 And I carry my old phone to my runs (hiking distance is of lesser concern).

Hi @jdujic

Thanks for getting back to us. Our Support Team would be happy to work with you to investigate this further.

Please submit a support ticket and somebody will be in touch.


Jane (she/her)
STRAVA | Community Hub Team

jdujic
Shkhara

A similar issue has been reported at

https://www.reddit.com/r/Strava/comments/k8n1t9