Until now, an outing recorded by another app entered MushMate one file at a time, from the manual entry. Fine for a few outings. For a season, it is an afternoon gone.

In Traces, the "Import outings" button now takes several GPX files, or a whole .zip archive: your adidas Running account export, or a folder of outings exported from Garmin Connect. Tick the outings, pick the team (dogs, surface, activity, intensity, musher), and import. The list stays open: change the team and import the next batch.

What others see

An outing imported this way is a session like any other: the members of your kennel see it, track included, and it counts in the load of every dog that ran. Same rule as a GPX file imported on its own.

The files themselves never leave your computer: MushMate reads them in the browser and only sends the computed session. The rest of the archive (summaries, photos, the other data of your account) is not read.

What it does not do

The choices we made

One team per batch, not per outing. Picking dogs outing by outing across two years of history brings back the chore we set out to remove. Filter by period, import the outings of one team, then move on to the next. A dog not yet born, or already gone, on the date of a ticked outing is named, and the import waits for you to fix it.

Nothing is dropped silently. An outing on the same day as a session already recorded, within 1 km, arrives unticked and marked "Likely duplicate". Same when two files of the batch tell the same outing, like a walk recorded by both your watch and your phone. You decide.

Our computation counts, not the source app's. Distance, moving time, stops and elevation are computed as for any GPX outing in MushMate, so your sessions compare with each other. The adidas archive carries its own figures; we leave them aside for now, while we check on more outings which one best describes your routes.