mapbox / mapbox/mapbox-navigation-android
Optimise callout placement
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
Current reference implementation of callouts (#1339) shows the callout based on the location of the middle step of the route. First improvement to this system would be to take the full geometry of the route and calculate a center point of this geometry. Second improvement would involve not overlapping callouts and not showing callouts close to overlapping geometries.
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
Start with the callout reference implementation described in issue #1339 and trace how placement currently uses the route's middle step. Define and implement placement based on the full route geometry, then address overlapping callouts and callouts near overlapping geometries; done means these placement cases are handled without obscuring route geometry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100