SMF·WANDERLOG-PRO
Can a prompt replace Wanderlog Pro?
Travel & outdoors — collaborative trip itinerary planning
Exhibit tracking slip
Verdict
A trip itinerary is a list of places with dates, and the useful computation — travel time between consecutive stops, whether a day is overpacked — is a routing call and some arithmetic. That is a weekend. The two gaps are the standard ones: several people editing the same plan while messaging each other about it, and place data with hours, photos and ratings, which comes from a commercial maps API you now pay for directly.
Exhibit A — The prompt
Received on31.07.2026Build a day-by-day trip planner where travel time between stops is computed rather than guessed.
Data model: a trip has dates and a base location; a day has an ordered list of stops; a stop has a place, a planned arrival, a duration and notes. Places are stored once per trip and reused, with coordinates, an address and your own notes.
The computation that makes it worth using: between consecutive stops on a day, call a routing engine for travel time by the mode you set for that leg, and lay the day out as a timeline. When the stops plus the travel plus the durations exceed the hours you said you would be out, flag the day as overpacked and show by how much. That single number is the thing people get wrong when planning a holiday, every time.
Add opening-hours awareness: store hours per place, either typed in or from the OpenStreetMap opening-hours tag, and warn when a planned arrival falls outside them or within thirty minutes of closing.
Import places from a GeoJSON export or a pasted list of names to geocode. Export the trip as GeoJSON, as `.ics` with one event per stop, and as a printable day sheet.
For collaboration, do the honest simple version rather than the hard one: the trip file lives in a shared git repository or a synced folder, edits are made by one person at a time, and the tool shows a diff of what changed since you last looked. It is worse than concurrent editing and it does not lose anyone's work.
Do not build live multi-user editing on a first pass. Concurrent editing with ordering and offline clients is a genuinely hard problem, and a half-working version loses the plan someone spent an evening making.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 real-time collaborative editing, which is how couples and groups actually plan
- B.2 place data with opening hours, photographs and ratings out of the box
- B.3 importing a whole itinerary from a saved map list in one click
- B.4 offline access to the plan and its maps on the road
- B.5 the mobile apps and shared expense tracking
Exhibit C — Why people still pay: real-time collaboration and place data
Six dollars a month so that two people in two cities can rearrange the same Tuesday without sending each other screenshots.
Questions
Can I export my Wanderlog trips?
Partly. Wanderlog exports an itinerary to a calendar and to a printable view, and place lists can be extracted from the shared view. There is no clean structured export, so expect to rebuild anything complicated by hand.
Where does place data come from?
OpenStreetMap through Nominatim and Overpass covers coordinates, addresses and opening hours for a great many places, free within its usage policy. Photographs and ratings do not exist there — for those you would pay a commercial maps API directly, which is one of the costs Wanderlog absorbs.
What does it cost to run?
A few dollars a month for hosting. Routing against a self-hosted engine or a free-tier API is effectively free at trip-planning volumes.
What is the one thing that does not survive the rebuild?
Planning together. The moment two people want to move the same afternoon around while talking about it, a shared file with a diff view is visibly the wrong tool.
Related tools
Receipt