Metro’s route went crazy after recent update
Also another problem is that I created two private places with different names by accident at the same place, but there doesn’t seem to be a way to delete private places?
Hi @dyang886, two separate things here, so let me take them in turn.
The metro route. This is underground-train territory. In 1.3.0 we put real work into improving how underground train lines get recorded (BIG-150), but it depends on the line itself producing at least roughly-usable raw location data underground, and that varies a lot between cities and lines. Yours is actually the first report we’ve had of an underground trip coming out this messy since that 1.3.0 work, so it’s genuinely valuable feedback.
What would help most: how often does this happen for you? Every metro trip, a particular line, or a one-off? The more we know about how reliably it makes this kind of mess, the better we can judge whether there’s something specific to dig into.
Deleting private places. You’re right that there’s no direct delete. Places are meant to clear themselves once they fall out of use, but ones near where you spend time are deliberately kept around for future re-use — so a duplicate at a regular spot tends to stick rather than disappear. The proper fix for your case is place merging, which is planned (BIG-153 — resolving duplicate places by merging them). In the meantime, if you reassign the accidental place’s visits to the correct one, the stray just sits harmlessly and won’t get picked for new visits.
Every metro so far since update, 2 to be exact, before the update it has a straight line, which I’d say should be a safe fallback if your new system can’t process on meaningful data
1 Like
I have seen this jaggedness occasionally in the new update, but not often, and nowhere as bad as what you have experienced.
It decided to turn east around 86 St. The old Arc Timeline 3 doesn’t do this. But most of the time this seems okay. I think it’s still better than 1.2.x.
1 Like
@dyang886 @trackerminerfs — thanks both, this is genuinely useful field data.
@dyang886, “every metro since the update” is the key detail — a consistent case is far more useful to us than a one-off. A clean straight-line fallback turns out trickier than it sounds (we can’t reliably separate good underground fixes from noise at recording time), but you’ve flagged a real shortcoming on noisy lines and we’re playing with some ideas that could help. Filed as BIG-607 — no timing yet, but your every-trip Shanghai case is exactly what we’d tune against.
@trackerminerfs, yours actually looks largely right — that one jump near 86 St is the same root, just an isolated blip rather than a whole-route version, and the kind of thing those same ideas would smooth. Good to hear it’s net better than 1.2.x for you. Both reports are on BIG-607.