Visual trip maps for routes, itineraries, and movement planning

Travel & Routing lets a user enter where they want to go from and to, choose the travel mode, and generate a visual route map. It is intentionally simple right now: build a route, preview it on the OpenStreetMap / MapLibre map, copy the GeoJSON, and use the visual as a planning or sharing artifact.

What it does

Enter a start and destination for a plane, train, ship, car, or walking route. Atlasemoji geocodes the places, builds route geometry, and draws the trip on the map with visual styling for each transport mode.

Synthetic route vs observed tracking

A planned route is a visual route. It is not proof that a vehicle, aircraft, vessel, train, or person actually moved along that path. Observed tracking requires a real signal such as phone location, scanner pings, aircraft telemetry, vessel AIS, EDI/API events, or another trusted source.

Why it uses OpenStreetMap

The Travelers map uses MapLibre with OpenStreetMap-compatible basemaps. That keeps the Travel & Routing experience separate from the main Google map and preserves the existing Travelers map behavior.

Importing an itinerary

Paste a confirmation email, itinerary text, reservation note, or route description. The importer tries to find usable stops and route legs. For best results, paste the original confirmation section instead of a long forwarded thread.

Sharing the result

The home panel can copy route GeoJSON and the map stage can attempt a browser image snapshot. If the browser blocks canvas export because of map tile security, use the full Travelers map or a normal browser/OS screenshot.

Operational examples

A sales team can show a proposed delivery route. A field team can explain a site visit plan. A logistics team can sketch a vessel, air, rail, or road movement. A travel coordinator can share the route with friends, colleagues, or customers before live tracking exists.

How this can grow

The same visual pattern can later connect to consented phone pings, DataSynch manifests, geofences, aircraft or vessel feeds, carrier events, dispatch workflows, CRM notes, and exception handling. The current version is the visual planning layer, not the full tracking system.