I've never actually been into it, just scraped past it loads of times, but Strava/Veloviewer originally credited the tile as visited because one of the GPS records cut a corner through it (leading me to ignore it for years). VV added the 'tile recalculation' feature to improve the accuracy for these scenarios and it's triggered automatically when you click on a particular activity. It's mainly intended to give people extra 'missing' tiles but inevitably it can remove some too - and that's what happened when I inadvertently clicked on a ride from years ago recently. There's more detail here..
... I guess it's quite common as I ended up with 4 of these examples after I recalculated everything. This Ealing one is just the only one I haven't gone back to get yet (thanks Covid!).
I've never actually been into it, just scraped past it loads of times, but Strava/Veloviewer originally credited the tile as visited because one of the GPS records cut a corner through it (leading me to ignore it for years). VV added the 'tile recalculation' feature to improve the accuracy for these scenarios and it's triggered automatically when you click on a particular activity. It's mainly intended to give people extra 'missing' tiles but inevitably it can remove some too - and that's what happened when I inadvertently clicked on a ride from years ago recently. There's more detail here..
https://blog.veloviewer.com/explorer-tile-calculation-updates/
... I guess it's quite common as I ended up with 4 of these examples after I recalculated everything. This Ealing one is just the only one I haven't gone back to get yet (thanks Covid!).