Plan ordered stops with notes and a map

Every row has a name, address, and free-text note. Two rows are always kept in the interface, and more can be added or removed above that minimum.

• Names default to Day 1, Day 2, and so on but are editable
• Addresses with fewer than three characters are skipped during geocoding
• Notes are included in the JSON for successfully geocoded stops
• The row order defines the displayed stop order

When at least two stops have coordinates, the preview connects them directly and totals the great-circle length of each straight segment.

• There is no road geometry or travel-time calculation
• There is no automatic reordering or route optimization
• There are no arrival, departure, booking, or schedule fields

Use names such as Museum, Lunch, and Hotel; enter complete addresses; and add concise notes such as ticket time or reservation reference.

• Plot the itinerary and inspect every numbered marker
• Use an external routing service to validate real travel feasibility
• Keep sensitive reservation details out of a browser-session planning tool

Download JSON exports only successfully geocoded stops with order, name, address, note, longitude, and latitude.

• Ungeocoded rows are omitted from the download
• The JSON is a local backup or handoff file, not a public share page
• Refresh clears unsaved component state

There is no explicit stop cap in the interface, but anonymous geocoding permits only 30 uncached requests per minute per requester and caches results for 30 days.

• Keep an all-new anonymous itinerary at 30 or fewer addresses per run
• A normal no-match row remains without coordinates
• A hard request failure can abort the run before the new stop list is committed
• Use the full editor for a saved guide with rich records, sharing, or an eligible embed