Incorrect distance whilst running using Surge with GPS

[Kathleen75]

When I log a run using my surge with GPS and Map my Run app, there is a discrepancy between the distances, this then means my pace isn't accurate. Why can't surge track distance using GPS which would be accurate? I don't want to have to add my stride length as it alters when running (for instance up and down hills) so it means that my Fitbit surge runs are inaccurate. For me, this defies the purpose of having the surge.

[Cathy419]

Me either 😞


Sent from my iPhone

[MikeF]

If you're using GPS on the Surge,it does calculate the distance from GPS. Thus, entering your stride length will have no impact on the distance in this case.

[Kathleen75]

Thanks MikeF, I'll keep checking as yesterday on my 6 mile run the average pace difference between the two devices was 23 seconds per mile with me having to run further to log a mile on my Fitbit than on map my run. My run distance is always less on my Fitbit. I don't know which one to believe!

[Refslegs]

I also have the same issue with distances

I regular run our local parkrun and i currently running with two devices.

My Garmin shows 5.01K

My Fitbit shows 4.74K

Concidering they are using GPS its quite a difference ;(

[Kathleen75]

So it would look like your Garmin is correct if you're doing a 5k park run - when do you think they'll address this? It's not good is it?



Sent from my iPhone

[Refslegs]

No its not good, i tried looking at setting my stride length but that seemd confusing to set up as in imperial not metric.

I do understand that different devices have different ways to work it out but its quite a large difference. I really dont want to run with two devices.

[Sean_S]

Hi, at first, I had a similar issue with the GPS. The cause of the issue is I always pressed quick start and then started running. For me, it fixed the issue if I waited until the GPS loaded. Otherwise, the run will say it started when the GPS signal is found. (which for me in most cases was 2-3 minutes into my run)

[SunsetRunner]

I have the same issue with my surge. I did a cross country skiing marathon while recording with GPS and the FitBit Apps (doesn't matter if web, mobile or Win10 App) display it as 29 something km's. Interestingly if you export the .tcx file from the web and import it in an app displaying the track (I used BikeXperience which is freely available) the distance was more or less accurate (43km).

Conclusion: The FitBit surge remains a toy. It just does not perform well enough if you want to use it for serious training. The main issues are:

- Very inaccurate heart rate measurement when doing strenuous work outs (have you guys been able to measure heart rates above 170??)

- Data analysis is very limited in standard FitBit apps

- The Surge can not be easily connected to apps which would allow better data analysis

- Activity data captured can only be exported one by one (*.tcx files)

- ...and a ridiculous bug in gps distance calculation (which actually is present since some months)