After showing Claude my two export directories it provided me with the following report. Is there any way to update the missing place names, etc?
Pasting the markdown into this field munged it a bit, if you find it difficult to read please see your email for the original .md file.
Thank you!
Bill
Summary. 98% of the old visits (15,195) have a match in the new export. Of those, 4,457 have a different name:
- 2,250 had a real place name in the old app and are now Unnamed Visit.
- 429 were changed to a different named place.
- 264 were generic before (Unknown Place, Brief Stop) and now have a name.
————————
1. Place names lost in migration (highest priority)
2,250 visits that were linked to a named place in Arc App are exported as Unnamed Visit by Arc Timeline. They cover 749 distinct places.
Year Visits that lost a name
2016 2
2018 503
2019 1,003
2020 190
2022 10
2023 173
2024 67
2025 158
2026 144
- Nov 2018 – Nov 2019 is almost entirely unnamed in the new export. In calendar 2019, 1,292 of 1,306 visits are Unnamed Visit.
- Places used heavily for years lost their link completely. Examples:
- the user’s Home place: 458 visits between 2018-08-29 and 2026-03-20
- a rented apartment: 117 visits, every one of them for 2018-12-22 → 2019-01-08
- several workplaces: 54–78 visits each in 2018–2020
- Likely cause: the visit → place link was dropped during import for places that were last edited or created in that era. The coordinates survive, so the places could be re-linked automatically.
2. Visits re-linked to the wrong place
The new export attaches some visits to a nearby place, often a transit station, instead of the place they were linked to before. The worst cases:
Old place New place Visits Notes
Home a nearby street-address place 68 2025-12-28 → 2026-03-23. Home was effectively split in two.
Home nearby subway station 21 Workplace nearby subway station
6
Includes 2026-03-20 15:14–15:49Z
Serviced apartment (Minami-Azabu)
a different serviced apartment
3
Arrival night 2026-03-24/25
Language school
nearby JR station
5
2026
Share house
neighborhood place
6
2026
A restaurant
three different nearby places
27
2026
Place renames such as Ottomanelli’s → Ottomanelli & Sons (39 visits) look like expected venue-data updates and are not included here.
Place-matching seems to prefer busy nearby venues, especially stations, over the place the user had already confirmed for that visit. User-confirmed place assignments should survive migration.
3. Days dropped
The old export has visits or tracks on these 6 days. The new export has nothing for them:
2019-11-26, 2019-11-27, 2022-11-27, 2024-12-08, 2025-12-27, 2026-02-13
The new export has 2 days the old one doesn’t: 2026-01-30, 2026-01-31.
4. Visits re-segmented in Jan–May 2026
Between Jan and May 2026, about 270 old visits have no match in the new export and about 290 new visits have no match in the old. Most of these fall in March–April. It looks like the new app re-processed this period and cut the visits differently.
5. Bad track segments
Start (UTC)
Type
Length in export
Problem
2026-03-24 13:09
airplane
21,049 km
JFK → HND stored as one segment of about twice the real length. New export’s 2026 flight total is 23,225 km vs 12,228 km in the old export.
2023-05-28 11:34
airplane
31,457 km
HND → SFO. The real distance is about 8,300 km.
2024-10-26 19:09
bogus
6,294 km
Starts and ends in Manhattan. Present in both exports.
2014-06-11, 2014-06-20, 2014-11-17, 2014-11-19, 2015-03-09, 2015-11-18
walking
207–4,639 km
Flights typed as walking, at 366–5,965 km/h. Present in both exports.
2019-04-10 23:59; 2022-10-16 19:45–20:09
unknown
867 km; 5 pieces
Flights left unclassified.
GPS jitter in the airplane segments inflates distance generally. Filtering out points with a large accuracy radius would help.
6. New recordings aren’t classified
Arc Timeline exports 624 track segments with no (4,549 km) for Mar–Sep 2026. That starts with the switch to Arc Timeline. The old app classified this same period (mostly train and metro for Mar–May 2026).
7. Duplicate waypoints
The weekly export has about 595 duplicate entries: same name and same timestamp, listed more than once.