Reshape a route after you have drawn it
Itineraries gain a draft and a published version, segments can be merged, split, inserted, grouped, and switched between routing engines, and itineraries can be duplicated.
Itineraries now have a draft and a published version. Editing changes only the draft, so a course can be reworked in the open; share links, embeds, and the tiles they render keep serving the last published snapshot until you publish again. An itinerary that has never been published is not reachable from a share link or an embed. Publishing is refused while a collaborator is still editing any part of the itinerary.
Segments can be reshaped after they are drawn. Merge two neighbours that share a routing engine, split one in two at a point you click on the route, or insert a new segment between two neighbours or before the first. The chain renumbers itself and stays continuous.
A segment's routing engine can be switched between smart routing and freehand. Going from freehand to smart routing snaps the drawn line to the trail network while keeping the original start and end points, and reports a clear error when the line cannot be routed.
Neighbouring segments can be collected into a group that shows a single name, color, and speed on the elevation profile. The segments themselves are untouched and stay individually editable, which suits a course that dips into a freehand line for a few hundred meters where no trail is mapped.
The itinerary query returns an itinerary's segment groups as groups, and each segment names the group it belongs to through groupId. Groups are flat rather than nested, so the ordered segment chain stays the primary structure and a run is resolved by matching the ids. An itinerary with no groups returns an empty list.
analyzeGeometry and directions now return the trailDifficultyInfo stretches they compute. The field was on the schema but missing from the queries the MCP server and AI agents issue, so the analysis was calculated and then dropped before it reached a caller.
Itineraries can be duplicated, optionally into another organization, choosing which segments and waypoints to carry over. The kept segments must stay a continuous run, so only the ends of the remaining route can be dropped.
Clicking a segment on the map opens it for editing, the same as clicking its row in the list. A segment a collaborator is already editing stays inert.
The mode field on the segment update request has been removed. It was accepted and silently ignored, so a request that set it never changed the segment's routing engine. Changing the engine is now its own operation.