Grouped routes
With RouteQ, you can build routes in which orders are grouped closer to each other or localized in a certain area. To do this, use the options.proximity_factor and options.global_proximity_factor options.
| Option | Description |
|---|---|
proximity_factor |
Routes are built taking into account the distance to the nearest orders. This option helps build routes with closer distances between neighboring orders. In practice, such routes are more resistant to changes in order time windows: when the order receipt time is postponed, the courier can drive to the next order and then return to the previous one. |
global_proximity_factor |
Routes are built taking into account the distance to the last order. This option helps build geographically grouped routes. Use sequence post-optimization together with this option. You can also group orders around a so-called point of attraction. |
Options can take a value between 0 and 10, where 0 means no order grouping, and 10 means maximum order grouping. The recommended value range is from 0 to 1. Higher values may negatively affect solution metrics: mileage, route time, or the number of couriers.
If you need to group some of the route's orders, but not others (like when delivering in the center and on the outskirts of the city), you can selectively disable proximity_factor and global_proximity_factor. To do this, open the Orders sheet and set false in the use_in_proximity field for orders that don't need to be grouped further.
By default, building grouped routes takes into account the location of all depots. To exclude intermediate depots from the grouping process, open the Depot sheet and set false in the use_in_proximity field for such depots.
To learn more about grouping options, see the Grouped routes case.
Example 1
cost.km = 8 (the default value), and the proximity_factor and global_proximity_factor values are set to zero. The routes are optimal in mileage, but geographically stretched and not localized in any area.
API request (JSON) ⋅ API response ⋅ View on map
Example 2
The same as example 1, but the proximity_factor value is increased to 0.5. Routes are built so that neighboring orders are closer to each other.
API request (JSON) ⋅ API response ⋅ View on map
Example 3
The same as example 1, but the global_proximity_factor value is increased to 0.5 and the post_optimization option is enabled. The routes are geographically grouped.
API request (JSON) ⋅ API response ⋅ View on map
Example 4
You need to deliver 40 orders. Grouping options apply to all orders. The algorithm builds flexible and compact routes for three vehicles.
API request (JSON) ⋅ API response ⋅ View on map
Example 5
The same as example 4, but for orders outside the Moscow Automobile Ring Road, the use_in_proximity field is set to false so they aren't included in grouping. As a result, the algorithm combines "long-distance" orders and offers routes for two vehicles instead of three.
API request (JSON) ⋅ API response ⋅ View on map