Elapsed time and stops
Times include stops between the checkpoints. The finish difference compares each attempt with the reference. The same distance can be at a different place on the ground, for example after a detour.
Segment analysis
Compare repeated routes between map checkpoints.
Place checkpoints on the map. MTL Explorer finds every track that passed through them and compares your attempts.
Compare a repeated section.
Choose activities, place ordered zones, and select exact attempts for comparison or replay.
Results
Inspect every matching attempt.
Browse matching activities and select the attempts you want to compare. Open a result to inspect its visits, graphs, and map position.
- Compare repeated climbs, descents, trail sections, or commutes.
- Keep the source activities in the private archive.
- Use the same segment again as new tracks are imported.
Comparison
Review timing and effort together.
Compare time, speed, and heart rate between the same checkpoints. The attempt marked R is the reference. The first chart shows how far ahead or behind each attempt was at the same distance.
Move along a chart to see the matching spot on the map. Ghosts show where the other attempts were when the reference reached that spot.
Open Replay here starts a replay of the attempts at that spot.
Check what the timing can support.
Comparing times needs tracks with timestamps. Recordings also differ in how often they saved a position.
Gaps and missing times
Gaps or missing timestamps can leave an attempt without a time. A missing time is not zero.
Zone placement matters
Large checkpoints can match a different part of a track than you expect. Check the result on the map and add checkpoints in between if needed.
Graphs depend on available data
Speed needs positions and times; elevation needs recorded heights. Power and energy are estimates. Heart rate needs data from the optional Google Health connection.