The
▦ Planner button overlays the itinerary on the map — click anywhere off it (or Esc) to
dismiss. Click any card or dot to
highlight it (Esc clears). The
+ on an Options card commits
the next leg; click a
connector between Choices to insert mid-trip;
⇄ replaces,
✕
removes — nothing is ever truncated, illegal legs flag red and stay yours to mend. Leg distances and
drive times are now
OSRM-routed between properties (an ≈ marks the few legs that still fall
back to crow-fly × 1.25); the disc remains a crow-fly reach approximation — deliberately geometric.
On the disc: the dashed-radius number is its
crow-fly reach in miles; the number in the
bright band is the
road-mile window a good next stop should spend (55–100% of the leg,
toward Santa Barbara).
Any place can be a stop, and every stop names its leg. Each leg carries
+ Add a stop here. Click it and one drawer opens under that leg: a search box, and under
it the catalog properties that actually fit between those two stops. Type a name or an address —
a hotel, a spa, a national park, a friend's house — and the matches join the same list. Nothing
opens by itself, and only one leg is ever open.
Your catalog answers on the first keystroke, offline. The two search services answer about half a
second after you stop typing, because one of them asks for no more than a request a second; Enter
searches immediately rather than waiting. Whatever you pick goes into
that leg — the search
used to sit above the whole planner and drop its result at the gap that cost the fewest miles,
which is a guess. It no longer guesses.
+ Add puts it
straight into the itinerary, at the gap that costs the fewest road miles;
○ Map only drops
it on the map as a ⌂ dot for later. A match the search is unsure of is labelled
low
confidence rather than quietly presented as the answer, and a property already in the catalog
is committed as that entry — with its stars and booking details — not as a copy.
Your own catalog is searched first — instantly, with no network at all — because the two
properties no public geocoder can find are both already in it: the Blackberry Farm resort is not
in OpenStreetMap under any name, and Post Ranch Inn is filed there as an ordinary residential
building. A catalog hit is committed as the catalog entry, stars and booking link included.
Then two search services are asked, not one, because neither finds everything: Nominatim reads
street addresses well but re-derives the street name and so loses some houses entirely; Photon
keeps the raw address tags and finds those, but cannot interpolate a house number. The better
answer wins. OSRM then measures the real road miles of the legs the new stop touches. None of it
is needed for anything else on this page; if a service is unreachable the stop still works and
its legs fall back to crow-fly × 1.25, marked ≈ — with a
↻ re-measure offered so one bad
moment on the network does not leave a leg on the estimate for good.
Routes save locally. The plan you are looking at autosaves and is in the URL;
☆ Save route
keeps as many named routes as you like
in this browser (clearing site data deletes them, and
no other device sees them), and
⤓ Plan writes a
.vquest file you can keep or send.
The 24-day itinerary is already packed as one —
download it here, then
⤒ Load it.
It carries no departure date of its own, so the brief assumes today and says so — set your
real one in
Depart and every date moves with it.