A decade of holidays arrives in the library as one long undifferentiated stream. The information needed to split it into trips is already present, but it is split across two devices: the phone carries GPS and knows where you were, the camera carries the good sensor and knows only when a frame was taken. Neither device alone can file a trip.
Journeys 1.4 joins the two. The phone's positions decide where and when a journey happened, and capture time then pulls in every shot the camera took inside that window.
Trips, not cities
A journey is defined as the span between leaving home and returning, rather than as a cluster of nearby photos. The difference matters on longer trips: a month touring stays one album instead of fragmenting into eight city albums that have to be reassembled by hand afterwards.
Home is derived from your own library rather than configured, and everyday photos are never turned into an album. Several homes across the years are handled, because the address people had in 2016 is usually not the one they have now.
The camera clock problem
A camera left on home time files an afternoon in Rome under the previous evening, which breaks the matching precisely when it is needed most. Journeys measures the offset between camera and phone for the trip and corrects the shots back into place. This is the failure mode I hit most often in my own library, and it is silent, which is what makes it worth handling explicitly.
What the run actually changes
Journeys only creates albums and adds photos that are already in the library to them. Nothing is moved, nothing is deleted, nothing is edited. The worst outcome of a bad run is a folder to drag to the trash. A ledger records every album it created, so a later scan can report what changed since: renamed, photos added or removed, album deleted.
The rest of 1.4 is the surrounding view. A year-at-a-glance heatmap shows when you shot what, with every detected trip marked. Trips take written notes, or spoken ones, which are transcribed on the Mac and kept alongside the audio.
Country names come from boundary data bundled with the app, so no lookup happens at all. One reverse geocode per trip adds a city name. Nothing else leaves the Mac.
Journeys 1.4 is available for macOS.