mapbox / mapbox/mapbox-java

WALKING MapMatching issue

Open
#1,331 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

jira-sync-complete
Dominant language
Java
Stars
438
Forks
117
PR merge metrics
No merged PRs in 30d

Description

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:
directions-correct

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Java request shown in the issue, using MapboxMapMatching.builder with PROFILE_WALKING, the supplied coordinates, and the stated options. Compare its matching and steps with the Directions demo, then trace whether the discrepancy is exposed by the Java API or occurs in the underlying service. Done means a confirmed cause and a documented actionable resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.