Geospatial · Geocoding and routing

Optimize stops

Puts stops in the visiting order with the least total travel time or distance on the road, for one or several vehicles.

Also known as: Route optimization, delivery route

How it works

Pick the Latitude and Longitude columns of the stops, a Travel mode (Car by default, or Bike, Walk or Truck) and the Routing tiles. Optimise by chooses the cost to minimise, Time (the default) or Distance. Route shape sets the ends: Open path starts at the first input row and ends anywhere, Fixed start + end also pins the last input row as the end, and Round trip (return to start) closes the loop. Vehicles (1 by default) splits the stops across several routes; Capacity per vehicle (optional) with a Demand column (optional) keeps each route within a load.

Every input column is kept, and the node appends vehicle, visit_order, leg_distance_m, leg_duration_s, cumulative_distance_m and cumulative_duration_s. If an input column already uses one of those names the new one gets a numeric suffix.

Inputs and outputs

Inputs

  • data — Table

Outputs

  • data — Table

Settings

The Attributes panel of Optimize stops, as in the app: the controls work, but nothing runs — there is no data behind it.

The same settings, as the Assistant writes them
{
  lat: string
  lon: string
  costing: "auto"|"bicycle"|"pedestrian"|"truck"
  optimizeBy: "duration"|"distance"
  routeShape: "open"|"fixed-ends"|"round-trip"
  vehicles?: number
  capacity?: number
  demandColumn?: string
}

lat/lon are the stop columns. Keeps every input column and appends the optimised visiting order (vehicle, visit_order, leg/cumulative cost). Never emit tile-set ids or paths — the app selects the installed tile set itself.

Example

A van must deliver 30 parcels and return to the depot, which is the first row. Set Route shape to Round trip (return to start), Optimise by to Time and Travel mode to Car, then Sort by visit_order for the driver's sheet.