mapbox / mapbox/mapbox-navigation-android

Route arrived without covering route, if source and destination coordinates are nearby.

Open
#3,597 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
651
Forks
321
PR merge metrics
No merged PRs in 30d

Description

Scenario: Get a UTurn route on same straight street.

User starts from point A ( left side point of a street), moved towards end of street, Point B, make a right UTurn on same street, towards Point C, reaches the start of street but on right side, at point D

Route is - A->B->C->D

Preview
A -------------------------------------------B
(Same street - UTurn)
D--------------------------------------------C

**API Request**

**https://api.mapbox.com/directions/v5/mapbox/walking/-87.632965,41.903986;-87.632965,41.905703;-87.633065,41.905703;-87.633065,41.903986?access_token=""&geometries=polyline6&overview=full&steps=true&voice_instructions=true&banner_instructions=true&waypoints=0%3B3**

**Android API:**
**Mapbox Navigation SDK version:**

### Steps to trigger behavior

1. User starts from point A ( left side point of a street)
2. Moved towards end of street, Point B
3. Make a right UTurn on same street, towards Point C
4. Reaches the start of street but on right side, at point D

### Expected behavior

Route should stay on map till user cover the whole route, from start to destination.

### Actual behavior

As soon as user reaches source coordinate, Route Rrived event fires. Mapbox navigation assumes route arrived as source and destination are nearby on same street. Without covering route (covering whole street), route arrived event fires without covering route.

**Is there a way to tell mapbox that until user navigates on whole route, mapbox should not fire route arrive event, even if user arrives at destination without navigating on direction route???**

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 supplied walking directions request and the A-to-D U-turn scenario in the Android SDK. Review the route-arrival behavior involved in this flow and the existing comments for context. Done means arrival is not reported before the full route has been navigated, or the supported way to configure that behavior is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.