Matched route stops before end of trip


I am trying to use graphhopper in version 6.0 to match a route with pedestrian and bike profiles. In both cases, I have no failure on the server side, but the matched route is very short and doesn’t follow all the trip nodes.

I have tried several weighting options (shortest, fastest and short_fastest) and I always get a very small matched route compared to the one I am trying to match.
Here is a screeshot of the foot profile output (red= original trip, green=matched route):

Here are my profiles:

    - name: car
      vehicle: car
      weighting: shortest
    - name: bike
      vehicle: bike
      weighting: shortest
    - name: foot
      vehicle: foot
      weighting: short_fastest

    - profile: car
    - profile: bike
    - profile: foot

and the gpx data:

<?xml version="1.0" encoding="UTF-8"?>
<gpx xmlns="" xmlns:xsi="" xsi:schemaLocation="" version="1.1" creator=" --">
      <trkpt lat="48.86400042111182" lon="2.3607843371469666">
      <trkpt lat="48.86400042111182" lon="2.3607843371469666">
      <trkpt lat="48.86355691455583" lon="2.3547411840491885">
      <trkpt lat="48.86073482698218" lon="2.3530194642553046">
      <trkpt lat="48.862741253038955" lon="2.335490834124835">
      <trkpt lat="48.86689310416586" lon="2.323124376331279">
      <trkpt lat="48.86671810266022" lon="2.323062929002894">

Do you have any ideas as why this happens or how I could debug ?

Another question, I don’t understand why it doesn’t go down the street indicated in blue.

Thanks a lot for your help.

Any ideas on the reason of this malfunction?

For foot I can reproduce this. See the created issue here.

Thank you very much for your answer. However, I still cannot make it work even with the bike profile.

Which weighting method did you use?
Do the weighting methods influence map matching?
Which gps accuracy did you use, what is the default ? It would be good to be able to specify accuracy point by point since it can vary along the track.

Thank you.

Powered by Discourse