I have a private place where Arc has ~130 visits recorded. I came back here this week, after about 6 months away, and I can’t get Arc to mark my location as this place.
I only see this place show up as an option for other locations away from this one.
Hmm. Step one will be updating to the App Store build. Build 51 is quite old at this point. Current App Store build is 61 (v1.2.1).
I’m not sure how much has changed in the places system since build 51. But yeah, I think still worth doing that update first and checking again, before we dive into debugging.
Though for the general shape of what you describe… yeah, hard to guess actually. If it were a place with only 1-2 previous visits I can imagine it scoring poorly this time due to the last visit being not recent, and the visit times histograms not matching up. But with 130 previous visits, the model should be well shaped, for good matching.
Ok yeah I’m back to thinking we should get you on the latest App Store build first, then see if it’s still happening the same. Then if still same we could poke about in the Common arrival and Common duration histograms. Maybe there’s some poor scoring due to mismatches in there. Or perhaps some change in GPS data shape is making the new visits fall in different enough location to mess up the matching. Unsure.
But yeah, update to App Store build first, check again, then if still wrong we dig in to testing for specifics.
What I noticed also that if I go the Place, and do show a on map, it shows me the place in a wildly different part of town. Like, over 5km away. I do not see a way to check or edit the place address or coordinates - is that supported for private places?
Yep, private places are identical to ones from Google Places except that you can edit their names. (Can’t edit the names of ones that came from Google Places, yet).
Sounds like there’s been one or more visit assignments to the place that were incorrect visits. Or possibly there’s more than one place with the same name? Though I’d expect that more with a Google Place, like what I sometimes get with a Starbucks or 7-11, and I pick the wrong one, messing those up. For a private place that sounds less likely, given it’s something you’ve intentionally named.
Anyway the solution will be the usual one. Go through the All Visits list, scrolling down slowly until you spot the visit(s) to that place that have been incorrectly assigned, moving its location far away, then correcting those.
Usually it’s easiest to find the incorrect assignments by using the Common Durations view, tapping on bars for durations that make no sense for that place, then tapping through to the list of those visits. That way you can quickly identify and correct the wrong ones, like “this is a cafe, so any visit of more than 2 hours makes no sense and must be wrong”, that sort of thing.
Ok, yeah, confirmed that the street address displayed on the place (it’s only the street and number, that’s all I see) it completely wrong. I don’t know how this worked for two years?
FWIW, this place is in a large nature reserve, and there’s no actual street address here. I thought the place was just tracked by coordinates, but I guess no?
Ok so for all place assignments to be correct but place centre 4km away, that’s mathematically impossible. But there are two possibilities to explore there:
There have been corrections done but the place is still pending update
There are still incorrect visit assignments that have been missed
Well ok there’s a third possibility, that there’s two places with same name. But given this is a private place, and as I said above, that seems the least likely
For possibility 1, let’s check in Debug Info view → Task Queues → Places pending update
If the place is listed in there, you can tap on it to trigger an update now. Then can go back to one of the visits and see whether the place centre has updated sensibly or not.
For possibility 2, I guess the only thing to try there is scrolling down the list slowly, so that the map can update on each page of results. Tedious and frustrating work, I know! But yeah, given the impossibility of what you’re seeing, it might be necessary to do another check.
For possibility 3, I’m guessing you’re in agreement that that one’s the least likely. If there’s two private places with same name, you’d know it.
Same in new app and old. Street addresses are provided by Apple’s reverse geocode service, which is given the place’s coordinates and returns street address, city, country, etc. So it’s all down to what the centre coordinate of the place is. That address is just for display purposes though - it doesn’t have any input into matching places to visits.
Actually, could you send/attach a screenshot showing the place and one/some of the visits on the map? That’d help for me to better visualise what’s going on. Thanks!