This feature is configurable via .json input, without the need for code customization and is available for both the Marketplace app and Platform. You can find a list of all available features here.
This how-to guide assumes you already completed the get started with vehicle routing tutorial.
| Field name | Required | Data type | SI Unit | Defined on | Example | Configurable via defaults |
|---|---|---|---|---|---|---|
start_location | No | location | NA | vehicle | {"start_location": {"lon": 1.23, "lat": 4.56}} | ✅ |
end_location | No | location | NA | vehicle | {"end_location": {"lon": 1.23, "lat": 4.56}} | ✅ |
Traditional vehicle routing problems require a depot where a route starts and ends. On the other hand, open vehicle routing problems (OVRP) do not specify an ending location for a vehicle, for example. You can specify the start_location and end_location on a vehicle.
These features are independent of each other, so you could solve vehicle routing problems by configuring the same start_location and end_location, or OVRPs by omitting one or both.
Here is an example input defining an assortment of locations for vehicles. A sample output obtained after solving the problem is also shown.