Thanks to info I found on threads in this forum, I was able to figure out how to obtain and import GPX data to correct the spotty location info from a German ICE train trip. This was a great thing to be able to fix!
I just noticed that in the monthly and yearly views, the map shows both the imported GPX data as well as the original inaccurate data. This is different than in the weekly and daily views, where the original data is hidden in favour of the imported data.
Is there any way to hide the bad data on monthly/yearly view?
Ugh. This one is a bug. The monthly and yearly map views are made from separate data. The original recorded data is “simplified” to reduce the number of map points so that it can all be shoved on the map without using too much memory and forcing the app to be terminated.
But that means that that simplified data needs to be automatically collated periodically and also updated after any changes. And there’s a gap somewhere in that system - that I haven’t yet found - that sometimes leaves outdated versions of the simplified data behind.
Though… the way you describe it, I think I’m having an idea of one possible gap! I don’t think I’d thought of the case of data being “disabled”. Which is what happens when you switch between imported data and data recorded by Arc. The Arc data isn’t deleted, it’s “disabled”, so that it’s still there in the database, available to be turned back on if you ever remove the imported data. I suspect the “simplified items” code is checking for deleted data but not disabled data, which would result in what you’re seeing.
Hmm. I’ll make a note to look at that today. If it is what I think it is, it could be an easy one to fix on my side.
Unfortunately I don’t think there’ll be anything you can do yourself to fix it. It’ll have to be me. But if my hunch is correct, it might be an easy fix and in the next Arc update. Which will be a relief - the occasional weird leftover data in the monthly/yearly views has been annoying me for a long time!
