Why does an imported run show implausible values (pace too fast, wrong splits)?

Every now and then a run shows up in Trait with values that can't be right: a kilometre in 2:30 min, a pace that differs significantly from your watch, or strange splits. Here we explain why that happens.

What Trait gets from your watch

Watches and third-party providers essentially only deliver raw data to Trait: GPS coordinates and a timestamp per data point. Trait calculates pace, kilometre splits and much more itself. There are typical stumbling blocks along the way:

• Fluctuating resolution: Sometimes there are 2 seconds between two data points, sometimes 0.2 seconds – and points are often missing altogether.
• Missing pauses: Often the data doesn't include the fact that you stopped at a traffic light on the way. Then there's a gap between gross and net time that Trait has to detect itself. This can lead to a differing duration or pace.
• GPS jumps: If your position jumps briefly, mathematically it looks like a sprint – resulting in unrealistically fast splits or even wrong personal bests.

Trait does its best to interpret this data sensibly. Nevertheless, there are always some sessions with implausible values. In most cases this is a problem with the data delivered and not a bug in the app.

What you can do

• Correct distance and duration: Tap the run in the Calendar → edit. This works for all running activities.
• Wrong personal best: correct it via “Enter your own personal bests”.
• Don't worry: A single session with odd values won't mess up your plan or your paces – the paces are calibrated via your Checkout ratings and the heart rate analysis, not via individual splits.