A small problem with the displayed track statistics for merged tracks:
Sometimes I forget to activate the track recording at the start of a tour and do this only after, for example, 0,56 km.
I then create the first 0,56 km with the route planner and then merge the two tracks. The part with the route planner logically does not contain any time values.
The merged total track then contains the correct total distance (e.g. 20,93 km, of which 20,36 km was recorded and 0,56 km was created with the route planner). The altitude profile is also correct.
However, nonsense is displayed for the track time: 469238:54:07.
Likewise with the pace: 1344958:37
I know that Locus cannot calculate correct values in this case. However, it would be more elegant if then nothing or 0,0 is displayed than such fantasy numbers.
Screenshot 1 shows the statistics of a recorded tour. Length 20.36 km.
The first 560 m are missing and were created with the route planner.
Screenshot 2 shows the statistics of the merged track (20.93 km).
(Such nonsensical values always occur when a recorded track and a track created with the route planner are merged).
Sometimes I forget to activate the track recording at the start of a tour and do this only after, for example, 0,56 km.
I then create the first 0,56 km with the route planner and then merge the two tracks. The part with the route planner logically does not contain any time values.
The merged total track then contains the correct total distance (e.g. 20,93 km, of which 20,36 km was recorded and 0,56 km was created with the route planner). The altitude profile is also correct.
However, nonsense is displayed for the track time: 469238:54:07.
Likewise with the pace: 1344958:37
I know that Locus cannot calculate correct values in this case. However, it would be more elegant if then nothing or 0,0 is displayed than such fantasy numbers.
Screenshot 1 shows the statistics of a recorded tour. Length 20.36 km.
The first 560 m are missing and were created with the route planner.
Screenshot 2 shows the statistics of the merged track (20.93 km).
(Such nonsensical values always occur when a recorded track and a track created with the route planner are merged).