Surge GPS Accuracy

[SteveGTR]

As posted in other threads, my new Surge watch doesn't even come close to being accurate. I've been running with both the Surge and my Andriod phone's MapMyRun app. Here are the pictures from both on the same 5-mile run:

Surge:

MapMyRun:

[HeliosJim]

What, you didn't run through that water?

[steveeJ]

I was about to create a thread with a very similar comparison of a route recorded by Surge and Endomondo (phone GPS) when I saw yours. The Surge measured 4.1 km vs 3.6 km from my phone.

I'm honestly quite surprised by the GPS inaccuracy. The wrong distance is the result of a totally sidetracked route record. This hasn't been an issue with any of my phones for many years so I was hoping Fitbit has figured this out too.

It would be great if the Fitbit team informed us if this can be fixed in software or if the hardware is at fault here.

Regards

Stefan

[Jamesfp]

I've had the same issue on runs where my phone has not had a problem tracking the location.

The first occasion Fitbit tracked me accurately apart from being about 100metres offline - so it had me running through rivers etc.

Secondly (will try and attach a pic) the signal was clearly lost for a period. My phone tracked me no problem.

I've had issues like this with strava and run keeper before that but they sorted out the tracking years ago it seems. Also, strava appears to somehow 'clean' the run and will work out there has been an issue with the gps and correct itself.

Does Fitbit do this? I'd have thought it would be a requirement for a gps tracker. Are there updates in the system - I've seen there have been improvements but any further ones due in early 2016??

The tall buildings/tree area excuse doesn't hold much water these days as I've seen and experienced a huge improvement in other trackers which happened a long time ago. Any info would be great! Thanks

[OkieRunner87]

 I never used to have problems with my Surge GPS--it was always accurate. Lately (last few weeks), it's been screwing up for about the first mile or so. It'll follow the general track of which directions I've been running, but will place me about 1/2 mile south of my actual location. Eventually, it catches up with itself, and the remainder of the GPS data for my run will be spot on. I do a lot of out-and-back running routes over my lunch break, and the overall distance is always accurate to within 0.1 miles. It's just the actual placement of the route that's wrong for the first part of the run.

I've tried waiting a bit after it says it has a GPS lock before starting my run, but that doesn't seem to do any good. Hoping FitBit comes up with a good solution soon!

[SteveGTR]

My last run was like this also. I waited for the GPS and started the run. When I looked at the map, the path was much more accurate, but it had me starting in an adjacent neighborhood.