A long trip produces a trail of updates: a message from the road, a map observation, another checkpoint, and a revised guess about arrival. My cross-country trip page brings those pieces into one readable timeline.
The project in the jeremy folder records a completed journey from California to the Cleveland area. It combines a route map, checkpoints, progress information, segment summaries, and an arrival result. It is a retrospective dashboard built from recorded observations, not a live tracking service that is still following the trip.
One feature I particularly like is the data key. The page distinguishes direct reports, shared-map observations, estimates, and values calculated from those observations. Those categories keep a convenient chart from making every point look equally certain.
The segment table also distinguishes elapsed progress from driving speed. An average that includes an overnight stop or a visit can be much lower than the speed of the vehicle while moving. Labeling that difference makes the information easier to interpret.
The final record allows an arrival estimate to be compared with what actually happened. That is useful feedback for the assumptions behind a trip model, especially when stops and changing plans are part of the journey.
For this article, the point is the structure rather than anybody’s exact address or minute-by-minute movements. A public example can explain the timeline without republishing those personal details.
This project shows how a one-off family question can become a small data-presentation exercise: collect observations, preserve their origin, and make the uncertainty visible alongside the progress.