osrm-backend icon indicating copy to clipboard operation
osrm-backend copied to clipboard

Published 20 hours ago • verified publisher icon Project-OSRM

No corresponding entry in matchings for a tracepoint

Open alexanderzatko opened this issue 1 year ago • 1 comments

Issue

I am using a docker OSRM container on my server, with a slightly modified profile, based on "foot". When running the query below, I get a tracepoint (No.18) that refers to a particular matching with indices 1 and waypoint 4. However, that "address" does not exist in the matchings section. I assume here that the waypoint_index of a tracepoint refers to a leg in the corresponding matchings entry.

http://nabezky.sk:5000/match/v1/foot/polyline(gwolHwnr%7BBxEnAqDg%40%7CDKkFc%40dEkAnE%40%7CArFfGS%7EElBjElElDtFfDxF%60DnHlCyErD%7ECpDjH%7EA%7CFfDtEpAvGfBvI%5CjLaE%60%40_C_H%7DDbFrC%7EI%7CElInDaF_DkIeEcJcCnKzB%60FjCfElC%7DDcA%7DG%7ECiGyCmNuFqGqHzIt%40rIjAnIdC%60HpD%60GlChGjA%60IDbIvA%7CAhBb%40)?steps=true&geometries=geojson&overview=full&annotations=false&timestamps=1675865963;1675865995;1675866091;1675866124;1675866204;1675866339;1675866387;1675866435;1675866483;1675866531;1675866579;1675866627;1675866675;1675866723;1675868033;1675868066;1675868098;1675868129;1675868161;1675868224;1675868256;1675868304;1675868336;1675868368;1675868400;1675868432;1675868464;1675868496;1675868527;1675868559;1675868591;1675868623;1675868639;1675868671;1675868687;1675868719;1675868751;1675868783;1676368639;1676368655;1676368671;1676368687;1676368704;1676368720;1676368736;1676368752;1676368768;1676368864

Steps to reproduce

  1. install Docker version 24.0.6, build ed223bc
  2. install the OSRM-backend container version: v5.26.0
  3. download the slovakia.pbf from http://download.geofabrik.de/europe/slovakia.html
  4. use the groomer.lua profile attached to this issue
  5. run the query provided above

Specifications

I am running the docker on an Ubuntu 22.04.3 vps, with 8 GiB RAM, 176.71 GiB free SSD groomer.lua.zip

alexanderzatko avatar Sep 11 '23 16:09 alexanderzatko

I found out that routing from point 18 I mention above was impossible, due to a profile clause restricting routing on certain types of highways. After removing the restriction routing through that section works ok.

However, the mismatch I describe in this report is still puzzling and looks like a bug to me.

alexanderzatko avatar Sep 12 '23 06:09 alexanderzatko