Race GPS erratic behaviour with poor coverage
-
Hello, there is definitely a problem with the GPS accuracy with my Race when there is poor coverage. I saw that behaviour several times in the past, but few days ago I could compare directly the tracks recorded by my Race and the Race S of my wife. It happens that when I’m in poor GPS coverage, as into a building, the position recorded by my Race become wildly incorrect, resulting also in an overestimation of the walked distance (+550 m), and of the speed (21.6 km/h max!), while the Race S seems to be not affected by the problem, see figure: Race (left), Race S (right).
I don’t know if this is caused by a less performing GPS module in the Race or in a different data processing. Anyway, I’m hoping a fix could be found to reduce that randomic behaviour in a future firmware update.
-
My understanding is that the Race and the Race S use identical hardware and identical firmware so the only difference will be the antenna design and whether both watches have the same gps data file sync’d to them.
-
@far-blue said in Race GPS erratic behaviour with poor coverage:
My understanding is that the Race and the Race S use identical hardware and identical firmware so the only difference will be the antenna design and whether both watches have the same gps data file sync’d to them.
They were both synced before the activity, in fact the overall track is very similar, the problem arises when the signal is weak. It seems strange that the smaller Race S has a better antenna. I’m wondering if this a common problem for the Race model, or just of mine. If common, maybe an appropriate filtering of the GPS data could minimize the effect.
