sudden jump in Activity.getActivityInfo().elapsedDistance when replaying a FIT file

I used my app when riding my bike yesterday and everything displayed fine.

I record sessions in my app, and everything looks fine in the Garmin-History on my watch too.

(I amended the app since the bike ride slightly.)

When I simulate my app now with the device simulator running the FIT file of my bike ride, it runs fine for 11:16 minutes,

Activity.getActivityInfo().elapsedDistance returns 7411.085938 which is correct (7.4 km).

At 11:16, Activity.getActivityInfo().elapsedDistance returns at once 16943838.000000 for some seconds (I don't

remember I halted on my bike), and than goes on accumulating from that random-value on.

Can this jump be a simulator-issue or could it be a bug in my program (I repeat, the app ran ok yesterday) ?

(Or must the app be identical at the time the FIT file is recorded and at the time the FIT file is replayed?)

0 jim_m_58 over 5 years ago

What this sounds like is a GPS drop in the fit file. Check the lat/lon when you see the odd elapsed distance.

0 longtrousers over 5 years ago in reply to jim_m_58

Thanks for your answer.

A GPS drop is what I understand a moment where the lat/lon is lets say on the other side of the earth? And the rest of the

journey is then calculated relative to that position ?

Afterwards the distance was normally increasing every second, but relative to the odd value:

elapsedDistance: 16943838.000000

counter1: 680

elapsedDistance: 16943848.000000

counter1: 681

elapsedDistance: 16943856.000000

counter1: 682

elapsedDistance: 16943866.000000

Strange though that this happens in the FIT file, but it did not happen at the real ride where the very FIT file was recorded.

Anyway, I guess it is a GPS/FITfile issue, and not an error in my app.

0 jim_m_58 over 5 years ago in reply to longtrousers

What you need to do is just record another fit. I have a fit a friend sent me with a GPS drop, where yes, if I play it back, he travels a great distance in a few seconds and then returns. On a real device, the accuracy changes, but that's not reflected in the fit file.