Connected GPS bike ride distance is inaccurate

[VikSteps]

Hi all

I'm having a problem with my Blaze and bike rides, it's reporting under the actual distance by quite some margin.

This morning I rode into work and used my Blaze, a Garmin watch and running the Endomondo app on my phone, these were the distance results:

Garmin: 19.4 km

Endomondo: 19.2 km

FitBit: 15.5km !! (using same phone as connected GPS source)

The map of the route looks good so I don't understand why it's so off even with GPS smoothing. There is one section where I enter a tunnel and lose GPS for about 1km but I don't see a GPS spike in the map.

This contrasts with when I use Connected GPS with a Run, it's a bit over distance but never out by a huge amount, usually 100 metres over a 10km distance.

Does anybody have any tips on getting this a lot more accurate?

Also a Strava question, if I use Strava - will FitBit sync back HR data within the same time period? 

thanks!

[VikSteps]

I will need to try what @Dries and @MayLeaBee have done and start my next exercise from the Fitbit app. I don't see the correct distance in Strava, I get whatever comes out from Fitbit 😞

https://www.strava.com/activities/1125383086 17.6km

https://www.strava.com/activities/1124615365 18.5km

https://www.strava.com/activities/1123816106 16.9km

Usually it varies -1km from Garmin but the 16.9km one is around 2km under. Previously I exported the route from FitBit's website and recalculated the distance in another tool and it comes out correct, this leads to me to believe the underlying data is correct but the calculation is not.

Also note @Colinm39 has reported behaviour in the southern hemisphere of over reporting further up this thread.

[whoopsiedoodle]

I have a Blaze and use Connected GPS with my iPhone.

Same issue. I bike the same short route every day that I’ve been able to for the past few weeks. The distance should be about 10.5 miles. It tends to underreport the distance if I go faster, I’ve noticed. There are no GPS gaps in my maps, and the only deviation would be by maybe 20 feet. 

 So why are the maps above near half a mile in difference?

[Rtopz]

This is definitely still an issue, even with charge2 using phone GPS...Fitbit app is wrong.  I have a bike computer that measures the distance using the wheel size and a magnetic sensor.  Pretty standard setup for bikes...and Fitbit is calculating down by 15% of the actual mileage.  Useless...

[MSMacedo]

Hi people!

It is still an issue. I noticed that last week, and then I review several of my bike rides and the distance recorded is absolutely meaningless. For instance:

-on Dec/30th I rode 14Km and Fitbit recorded 8.1Km

-on Dec/31st I rode 27Km and Fitbit recorded 7.5Km

-on Jan/6th I rode 13Km and Fitbit recorded  1.3Km (!!!)

All of those exercises were outdoors, clear sky.

I noticed that the path shown on the map of the Fitbit site is accurate, tracking the path correctly.

I'm using the Fitbit Blaze + iPhone 7. iOS and Fitbit app all updated.

If, at least, there was means to edit the exercise and correct the distance, it would help while a definitive solution is not available.

What can be done to correct this?  

[Fharmstrong]

I ride with many people who use other tracking devices. They all register about the same distance every time. My Ionic is the laughing stock and always way underestimates distances. For example,  this morning we rode eight-plus kilometres. My Ionic registered 6. I will not buy another Fitbit unless this is fixed, and this is my third. Fix this, Fitbit. This is ridiculous. 

[Fharmstrong]

Yep. That sums up the issue