Data issue with tomtom provider in some areas "Cannot retrieve costs from matrix service"

Hi

We’re getting errors in certain US areas using the TomTom data provider that we weren’t previously e.g. Texas and Iowa which was working before Christmas. I’ve been using data based in Ireland and there’s no issue there.

Sample request:

{
  "vehicles": [
    {
      "vehicle_id": "car_1",
      "type_id": "car",
      "shifts": [
        {
          "shift_id": "shift_1",
          "start_address": {
            "location_id": "690_1138",
            "lon": -103.622274,
            "lat": 30.111646,
            "name": "Service A"
          },
          "earliest_start": 1641805200,
          "latest_end": 1641835800,
          "return_to_depot": false
        }
      ]
    }
  ],
  "vehicle_types": [
    {
      "type_id": "car",
      "profile": "car",
      "consider_traffic": false
    }
  ],
  "services": [
    {
      "id": "690_1138",
      "name": "Service A",
      "address": {
        "location_id": "690_1138",
        "lon": -103.622274,
        "lat": 30.111646
      },
      "duration": 2700,
      "priority": 2
    },
    {
      "id": "690_47",
      "name": "Service B",
      "address": {
        "location_id": "690_47",
        "lon": -104.278262,
        "lat": 29.724477
      },
      "duration": 2700,
      "priority": 2
    }
  ],
  "configuration": {
    "routing": {
      "calc_points": true,
      "consider_traffic": false,
      "network_data_provider": "tomtom",
      "return_snapped_waypoints": false
    }
  }
}

Response:

{
  "message": "Cannot retrieve costs from matrix service",
  "hints": [
    {
      "message": "Cannot find the following locations: start location (lon: -103.622274, lat: 30.111646) of vehicle 'car_1:shift-id:shift_1'",
      "details": "PointNotFound"
    },
    {
      "message": "Cannot find the following locations: service location (lon: -103.622274, lat: 30.111646) of service '690_1138'",
      "details": "PointNotFound"
    },
    {
      "message": "Cannot find the following locations: service location (lon: -104.278262, lat: 29.724477) of service '690_47'",
      "details": "PointNotFound"
    },
    {
      "message": "Connection between locations not found: [ start location (lon: -103.622274, lat: 30.111646) of vehicle 'car_1:shift-id:shift_1'], [ start location (lon: -103.622274, lat: 30.111646) of vehicle 'car_1:shift-id:shift_1']",
      "details": "ConnectionNotFound"
    },
    {
      "message": "Connection between locations not found: [ start location (lon: -103.622274, lat: 30.111646) of vehicle 'car_1:shift-id:shift_1'], [ service location (lon: -103.622274, lat: 30.111646) of service '690_1138']",
      "details": "ConnectionNotFound"
    },
    {
      "message": "Connection between locations not found: [ start location (lon: -103.622274, lat: 30.111646) of vehicle 'car_1:shift-id:shift_1'], [ service location (lon: -104.278262, lat: 29.724477) of service '690_47']",
      "details": "ConnectionNotFound"
    }
  ],
  "status": "finished"
}

Changing network_data_provider from “tomtom” to “openstreetmap” gives a successful response.

Can you confirm that the coordinates like
https://graphhopper.com/maps/?point=30.111646%2C-103.622274
are the intended locations you need? The are not really close a road (>300m) and the road is only a track. So it seems the coordinates do not really fit.

These errors are appearing in some of our older QA test files. Upon further investigation, we can see that any time the error occurs that there is a point in the schedule request that is several hundred meters from road so we don’t think this will be a major problem in production since most user points will have originated from a good geocoder.

Still, we’ve used these files with Google and Azure routing with no problem and GraphHopper also works when the data provider is set to OSM so the inconsistency isn’t ideal. Is there a lower distance threshold in play when using the tomtom data provider?

We can have a look. Do you have examples in the US or Europe where our TomTom data results in the same differences?

Here are two other points from our sample data:

https://graphhopper.com/maps/?point=45.866779%2C-100.732804
https://graphhopper.com/maps/?point=43.077468%2C-91.214105

It’s not great sample data. They are a good distance from the road. We’re not overly concerned about it now but, as I said, the inconsistency with the GH OSM network as well as our previous providers (Google, MS Azure) isn’t ideal.

This should be fixed next week.

1 Like
Powered by Discourse