I've seen that happen when I import a track that I had created in other software as opposed to recorded with a GPS. IN addition, Runalyze will refuse to import a track that lacks speed data.
The reported stats remain correct despite the "sliced and diced" appearance of the track (that I attribute to some sort of visual rendering error).
|