Hey Matt, Love the new version! However, I noticed on the place I have labeled ‘Home’ which is my house, the app shows a bogus address! I can’t find anyplace to correct this address. Am I missing something? Thanks, Mark
Hi Mark! Glad you’re liking the new app
Me too. The old one feels like a rusty antique now in comparison.
For the street address, how wrong is it?
Those get set once, then can’t be edited and don’t get updated. So if the first “reverse geocode” lookup got a not great answer, that’s what we’re stuck with. But if it’s annoyingly off enough that it’s a genuine bother, we can think through some options for how to improve that flow. I know I’d be annoyed if for example it was the neighbour’s address across the road, and every time I saw it I was thinking “not them!” ![]()
Hey Matt,
Thanks for getting back so promptly!
The address is about a quarter mile away from where I live.
The address is correct in the old version. So that’s weird! Actually never even knew that it had the actual address listed in the old app until I checked!
This screen shot is from the original app
This is the new app
I also noticed that when in the old app, you could tap on the map in this view and the box would minimize so you could see the full map. That does not happen in the new version. I used that a lot to verify locations, can that be corrected?
On another topic. Does the original Arc app and the Arc Recorder app still need to be installed and running for the Arc Timeline 4 to function properly?
Thanks!
Mark
Aah, this one is different than I thought then! This is a case of the place having some incorrect visit assignments. The place thinks its centre is way off somewhere else, and also that it has a massive radius. Which means there’s some visits assigned to it that shouldn’t be.
Tap through to … actually, 3008 visits is a lot to sift through. Might be best to try to track down the incorrect one(s) by the histogram views rather than “Total visits”. Although that might be a challenge too.
Perhaps could start by tapping on “Total visits”, then scroll down the list slowly so that you can see the map view update. That’ll show you the visits currently visible in list view, so that you can easily spot the one (or more) that aren’t where they should be.
Then you can tap on those ones and correct their place assignment. Which will then automatically fix your home place’s centre and radius.
Oh, although it won’t fix its street address. Damn. that’s only set once. That’s on me to fix that one. I’ve already filed a ticket for it (BIG-470).
Ah the old app used a non-standard interaction there (tapping the map) while the new app uses the more iOS standard interaction, which is swiping the content sheet down from the top area (like the title area, with the nav buttons).
You can do that in any view that’s got that content sheet (ie anything in the timeline tab). You can swipe the content sheet down to minimised, but also swipe it up to nearly full screen, for when you want to see more of the timeline or details view and don’t care about the map.
I’d keep them still installed and running for now. Technically once you’re on the new app and you’re happy with it, you don’t need the old ones anymore. But I’m leaning more cautious on that one just because I don’t want to fully commit to “delete all the old things!” just yet ![]()
Oh and Arc Recorder will make a comeback at some point in the next few months, repurposed as a fallback recorder for the new app instead of the old.
The new app is much more stable/reliable than the old, so it doesn’t need Arc Recorder as much. Data gaps are much less likely. But… when we do get data gaps that still sucks. So if Arc Recorder is there to catch those then that’ll be great. So yeah, at some point there’ll be an Arc Recorder update that switches it over to being the fallback buddy for new app instead of old.
Hey Matt,
Thanks for the explanation.
How do I view the histogram? If it’s what I think it is, all the locations for the “home” place are on the correct location on the map, just the address is wrong. There are some bogus locations marked as “home” and I’ve tried to correct the ones I can find, but that doesn’t remove them from history, ie, they still will try to auto populate for my home place occasionally.
These are the Common duration, Common arrival, Common leaving views.
In those views you can tap on the bar chart bars and then below that tap on the row that takes you to viewing all the visits that match that bar. This is super useful for quickly finding visits that don’t match the place at all. Like, for your local cafe an arrival time of 2am is probably a definite incorrect assignment, and ditto a 12 hour visit duration.
But for home places those histogram views are less useful. For home, any duration from 1 minute to 7 days could be appropriate. And ditto any arrival or leaving time throughout the day. So filtering by those things is less useful for finding the incorrect visit assignments.
Your first screenshot from the old app shows a very large place radius. Which means there’s definitely some incorrect visit assignments that’ve been confirmed. (Only confirmed visits are used for place centre and radius calculations). So they’re in there somewhere!
Unfortunately I think the only reliable way to find them will be to scroll down the Total visits view, page by page, waiting for the map to update after each page. That’s going to be a slow process given there’s over 3000 visits! And given the old app is showing that large radius, it could be some quite old visits that were incorrectly assigned. Might take a while to find ![]()
If this were my data I’d probably do it over a period of days, not try to hunt them all out in one go. Will take too long, be too tedious. And once you correct any wrong assignments it’ll take a few hours for the change to land anyway. The place stats get updated while the app is in background, as a scheduled housekeeping task. So the radius and centre won’t update immediately.
So yeah, I’d page down the visits list until I find something wrong, fix that, then leave it for a day or whatever. Then come back later and try to hunt out some more.
Once the place stats have updated, and the radius is back down to appropriate size, the auto assignment will go back to making sane choices. But yeah, while that radius remains that large the place ranking and auto assignment will continue to make occasional bad choices.
Anyway let me know how it goes! It’ll almost certainly be a bit of a slog, but it’ll get there in the end, once you find them. I’ve occasionally had to do this with some of my own home places. The process does work, it’s just potentially a long one ![]()
Hey Matt,
I did scroll through the list, went back 4 years! Some bogus locations, but not a ton. Our property is 5 acres, and it looks like the app shows a lot of different locations around our property as “home”, which is correct. I’m not too worried about that! I would be happy with the ability to just edit the address that is listed for a particular place!
I have noticed bogus addresses on other places as well, like our favorite restaurant. It shows the restaurant at two different locations one in front of the mall it’s in and the other one behind the mall in a neighborhood! The old app didn’t show the actual address when confirming a location, just the name. So no wonder the app is confused!
It would be nice to be able to edit those bogus addresses or at least be able to merge them with the correct address.
Thanks for all your help!
Mark
Ah, this changes my read considerably! In that case… yeah agree, that place radius on the map could well be correct. Sounds like I sent you down a cleanup path that possibly wasn’t necessary. Sorry about that!
So the question is then what to do about the wrong street address…
Ok so we’ve been planning some future feature work for fleshing out the Places system a bunch more. This feels like it could fit in under that umbrella. I won’t go into the details of the broader plans yet (we’re still fleshing them out), but the ticket number for being able to override the street address is BIG-519 - just filed now. Locked in!
I think the intent will be that the Place Edit view will be where this happens. Makes the most natural sense. That’s where we already edit the place names for private places.
For place merging, this one’s already filed and planned. Ticket number is BIG-153, high priority, and one of the upcoming feature releases.
Hey Matt,
No need to apologize! You actually taught me a lot about what the app can do by my going through the process, so all’s good! ![]()
I’ve been using Arc since Moves went away, many years ago. It still amazes me that you are so responsive! You really seem to be passionate about what you build and want to make sure everyone is getting the most out of the app.
I’ll keep a lookout for all the new features!
Thanks again for all your assistance!
Peace, Mark
Just another thought…
In the old version of the app my “home” address is correct! For some reason it just did not transfer to the new app.
Here is a screen shot from the older app this morning (it’s still running):
This is the correct address! So I don’t know if it was just something with the transfer of info from the old to new app that may have caused the issue! ![]()
![]()
Hah. Thanks! Yeah I’m a big user of the app too. It’s my job, but it’s also an app I genuinely care about and get massive personal value out of too.
So while yeah I’m here on the forum to provide customer support, I’m also pretty invested in the features and directions and so forth on a personal level ![]()
Ah! Curious. Ok I think what’s happened is that address did copy over to the new app, but then the new app updated it later.
The new app has city and country fields for Places, which the old app didn’t (used by the Places tab, and also searchable in search view). So the new app does “reverse geocode” lookups for all of the migrated places, even if they’ve already got street address filled in. It wants to fill in city and country too. And then while it’s at it it updates the street address from the reverse geocode results. On the assumption that it should be a more correct value than the old one.
But in your case the new value wasn’t more correct. Oops.
I’m thinking the app’s behaviour there was technically correct, but in this case bad luck that the result was worse than the old one. And that leaves us with the solution being still BIG-519 - the ability to manually override the street address that reverse geocode came up with. Which… lemme check again… Yeah that’s filed for v1.2, a task in amongst the various Place system improvements we’ve got planned. Not too far away, if all goes well!


