Re-join RoboPacer

It’s a gap in data: you’re in one place at one time, then nothing, then continuing the ride later in a different place. It’s not a straight line even though Strava chooses to visualize it that way instead of leaving a gap in the track.

I believe the .fit file also contains a running accumulated distance measurement which of course should not change while going through the warp zone, but I think Strava might actually have made a design choice to ignore that and instead recalculate the distance based on the individual waypoints.

Ah.

Ooo, that makes it sound awesome! (insert evil laugh)