Yeah this is an ongoing problem that’s worsened since iOS started becoming a massive liar about location data accuracy. And it’s especially troublesome for frequent travellers (myself included!), due to Trust Factor requiring at least one day’s cleanup work before becoming useful. It’s not much use if you only stay in one place for a few days at a time.
Bit of a tangent: The problem with building new UI to fix the symptoms when there’s a way to fix the underlying problem is that it makes it unnecessary to fix the underlying problem. The user is left with new UI and UI steps to perform periodically (albeit more convenient and efficient than the previous) when they really shouldn’t have to do any work at all. The new should-be-unnecessary UI becomes normalised, and the underlying problem gets forgotten.
In terms of improved UI though, I think there’s a case to be made that efficiency improvements to the existing confirm/correct flows could be made that would have general applicability, not just “gloss over this data problem” applicability. So I’m still open to those options too.
In this case it’s the underlying recorded location data that’s the problem. iOS tells massive lies about data accuracy (eg reporting 10 metre accuracy when the data is 100+ metres away), which then breaks the filtering and smoothing maths, causing these nonsense drifting items to clutter up the timelines. So the “correct” fix is at Apple’s end, and the next best fix is some way of LocoKit being able to identify the lies immediately, without having to wait for user feedback and calculation of Trust Factors.
Anyway, in terms of possible UI improvements, I think one that could make life a bit easier is to have the long press menu on timeline items offer up a shortlist of type correction options. Like for those airplane items in your screenshot, if you long pressed on them the options menu that appeared could show the top 4-5 type matches, for quick correction. You could long press, select “stationary”, and job done.
I’ve actually already got that task in my “Today” list. Though unfortunately “today” is a misnomer, and instead means “stuff I’d like to start on today, but almost certainly won’t get to”. But anyway, it’s one that I’m hopeful will get into an update in the not too distant future.
For fixing the underlying problem, I still spend time every day cogitating on that. It’s a problem that affects me too, due to travelling to different cities each month then spending the first few days (or worse) cleaning up a new mess, until Trust Factor takes over.
I don’t have any credible ideas yet for that though - it’s a hard problem. The only way that we as humans know the data is wrong is because we know where we really physically are or were. Machine learning / AI can’t do that.