External Distance Matrices

Upload pre-computed distance matrices to maps.solvice.io/table/upload-table and reference them by ID in your VRP requests for faster processing and custom traffic patterns.

Basic Configuration

Configure different distance matrices for different times of day:

{
  "jobs": [
    {"name": "delivery-1", "location": {"latitude": 51.1279, "longitude": 17.0485}},
    {"name": "delivery-2", "location": {"latitude": 51.1350, "longitude": 17.0600}}
  ],
  "resources": [{
    "name": "driver-1",
    "category": "CAR",
    "shifts": [{
      "from": "2025-01-01T08:00:00Z",
      "to": "2025-01-01T18:00:00Z"
    }]
  }],
  "customDistanceMatrices": {
    "profileMatrices": {
      "CAR": {
        "6": "matrix-car-morning-rush",   // slice starting at 6 (06:30-09:30)
        "12": "matrix-car-midday",        // slice starting at 12 (12:00-14:30)
        "16": "matrix-car-evening-rush"   // slice starting at 16 (16:30-19:30)
      }
    }
  }
}

Time Slice Keys

Each key under a vehicle profile is the start hour of a time slice. Only these keys match a slice:

Key	Slice	Period
`6`	Morning rush	06:30 - 09:30
`9`	Morning	09:30 - 12:00
`12`	Midday	12:00 - 14:30
`14`	Afternoon	14:30 - 16:30
`16`	Evening rush	16:30 - 19:30
`20`	Night	20:30 - 06:30

A key that is not one of 6, 9, 12, 14, 16 or 20 (for example 8) matches no slice, so its matrix ID is never used.

With a routing engine that does not vary travel time by departure time (the default OSM engine, and TOMTOM_REAL_TIME), only the 20 slice is read. Provide the matrix under "20" in that case.

Matrix Upload

Upload your distance matrix to get an ID:

{
  "coordinates": [
    [4.9, 50.2],   // [longitude, latitude]
    [4.8, 50.4]
  ],
  "durations": [
    [0, 1976.1],
    [2010.2, 0]
  ],
  "vehicleType": "CAR",
  "departureTime": "2025-01-01T08:00:00"
}

Then reference the returned matrix ID under the key of the time slice that the departure time falls in (08:00 is in the slice starting at 6):

{
  "customDistanceMatrices": {
    "profileMatrices": {
      "CAR": {
        "6": "matrix-id-from-upload-response"
      }
    }
  }
}

Multi-Vehicle Configuration

Different vehicle types can use different routing matrices:

{
  "customDistanceMatrices": {
    "profileMatrices": {
      "CAR": {
        "6": "car-early-commute",
        "9": "car-midday-traffic",
        "16": "car-evening-rush"
      },
      "TRUCK": {
        "6": "truck-early-delivery",
        "12": "truck-midday-routes"
      }
    }
  }
}

API Reference

object

required

Map of vehicle profiles to time slice configurations. Keys are vehicle categories (CAR, TRUCK, BIKE). Each profile maps a time slice start hour (6, 9, 12, 14, 16 or 20) to a matrix ID.

string

Optional URL for custom matrix service endpoint

Platform

VRP API

Fill API

External Distance Matrices

External Distance Matrices

Basic Configuration

Time Slice Keys

Matrix Upload

Multi-Vehicle Configuration

API Reference

​External Distance Matrices

​Basic Configuration

​Time Slice Keys

​Matrix Upload

​Multi-Vehicle Configuration

​API Reference

External Distance Matrices

Basic Configuration

Time Slice Keys

Matrix Upload

Multi-Vehicle Configuration

API Reference