WALKING MapMatching issue

Inizia riproducendo la richiesta Java mostrata nell’issue, usando MapboxMapMatching.builder con PROFILE_WALKING, le coordinate fornite e le opzioni indicate. Confronta il relativo matching e i passaggi con la demo di Directions, quindi verifica se la discrepanza viene esposta dalla Java API o si verifica nel servizio sottostante. Il lavoro è completo quando sono disponibili una causa confermata e una risoluzione documentata e attuabile.

We are working on a app that uses the mapmatching api. We seem to have some problems when it comes to walking matchings/steps. Many of the roads dont seem to be included when matching with this profile. Is there any way that I can add these roads to the walking profile so it matches the points correctly like in the example Directions demo?

This behaviour only seems to be an issue when using the WALKING profile.

Some additional info:

    Point point1 = Point.fromLngLat(6.525440, 52.115350);
    Point point2 = Point.fromLngLat(6.526132, 52.115345);

    waypoints.add(point1);
    waypoints.add(point2);
    
    Locale locale = new Locale("nl_NL");
    Arrays.fill(radiuses, 50.0);
    
    MapboxMapMatching client = MapboxMapMatching.builder()
            .accessToken(Objects.requireNonNull(Mapbox.getAccessToken()))
            .geometries(DirectionsCriteria.GEOMETRY_POLYLINE)
            .profile(DirectionsCriteria.PROFILE_WALKING)
            .overview(DirectionsCriteria.OVERVIEW_FULL)
            .coordinates(waypoints)
            .language(locale)
            .steps(true)
            .roundaboutExits(true)
            .bannerInstructions(true)
            .tidy(false)
            .radiuses(radiuses)
            .build();

Result:

Expected result: