Better handling of duplicates

Feature Requests
1

Unfortunately I still get duplicates sometimes. Ideally that would be managed by me and the way I connect source devices, but the reality is there will always be the case of duplicates as I hack together different fixes to cover gaps in various ecosystems (long story, but I can’t fix it my end).

This is how a duplicate appears. It would be great if some simple logic was applied to see if an activity already exists, and either not accept the second activity, or merge them (as already happens with Strava and Garmin I think?)

The logic could just look at the timestamps and duration, and if there is a match of over 90%, then don’t accept the second activity (for example).

Screenshot_20250422-220624
Screenshot_20250422-2206241080×1813 258 KB

2

But which source do you prefer? I dual record my indoor rides with Rouvy and Wahoo and these would match your criterias. But one want to use the rouvy activity, as it has GPS data, another one will use Wahoo data.
So you must prioritise the sources. If I sync to Strava there will be two activities too.

1 Like
3

Being able to choose which is kept would be a great option, but I’d also be happy to just keep the first one.

Or… merge them. Fill any gaps in the first with data in the second.

Note this is slightly different than dual recording… these duplicates have the exact same originating source.

4

What I wanted to say: One day I want to keep my first source, the next day maybe the second source. So maybe hard to resolve this issue automatically.

But one question: Why don’t you use a filter, e.g. not downloading from TPV, or not downloading Virtual Rides from Suunto?

1 Like
5

It would probably help with virtual rides, but not in this example:

Ride on Karoo, which gets sent to intervals.icu

Duplicate from Suunto also comes through

If I filter out rides from Suunto, that’s a problem for when I do use Suunto to record a ride (which happens now and again for various reasons)