mapbox / mapbox/mapbox-navigation-ios
Feature Request: Allow for custom options on difficult turns or other roads users want to avoid
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 918
- Forks
- 326
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
One of my users told me that there is a very tight turn near his address, which he wants to avoid. However, Mapbox keeps navigating him over that point, as it seems to be seconds faster. I noticed that Waze allows users to give more detailed feedback on the map, similar to the contribution tool Mapbox provides, but with more settings. One of the things users can give feedback on is a tight turn, which is to be avoided. Doing that in the Waze app will seemingly make the navigation avoid this part of the route for future calculations.
Now think about that: The Navigation Route Options could include a custom list of waypoints a user wants to avoid. Imagine a tight turn he does not like, a second entrance to his property that he does not want to use, or a road he does not like because it is in bad condition. The user could set those in the app, and the app could then provide such points to the Navigation Request using the Navigation Options object to make sure they influence the navigation response. It seems like an easy implementation for Mapbox, yet a powerful tool for developers to customize the experience. Also, feedback on tight turns could be added to the contribution tool, making those available for other drivers as well.
Edit: As can be seen in the Screenshot provided, you can even set a priority to some routes, so not only a negative factor but also a positive factor.

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The request mentions Navigation Route Options, the Navigation Request, and the contribution tool, but names no files, tests, or concrete entry point. Start by locating those APIs and reviewing how route preferences are represented. The scope and completion criteria need maintainer clarification, including whether avoidance points and positive priorities are both required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100