Spark 3 inaccurate pace, accurate avg pace
edited January 24
In areas with tree cover I get wildly inaccurate pace readings, but avg pace is not affected. Are they measured/calculated differently?
Average pace has a lot more data to average over so you are not seeing the dips in pace. Under trees you are probably losing satellite coverage momentarily so the watch is detecting it as you being stopped, dropping the pace. When looking at the average a second or two of lost signal will not impact it like it will for the "instant" pace.
I hope this helped answer your question. If so, please mark it as a solution so others can look for it if they have the same question.
Hmm, avg. pace is reasonably accurate over 1 km splits under the same circumstances, so shouldn't it be doable to improve pace accuracy with some smart(er) programming? As it is it's pretty useless.
Welcome and support
Maps and Services
RoadTrips by TomTom
Community Knowledge Base