mapbox / mapbox/mapbox-navigation-android
ViewportDataSource framing on cloverleaf and windy road
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
Cutting to track implementation of ideas from https://github.com/mapbox/mapbox-navigation-android/pull/4916 and https://github.com/mapbox/mapbox-navigation-android/pull/4664. The MapboxNavigationViewportDataSource does not take into account a type of the maneuver, or the shape of the geometry ahead when trying to frame that geometry.
This can lead to situations when on a cloverleaf ramp or on a windy road we're constantly zooming in and out in following mode as the bearing of the vehicle changes.
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 by reading MapboxNavigationViewportDataSource and the approaches described in pull requests #4916 and #4664. Trace how maneuver type and the geometry ahead affect following-mode framing. Done means cloverleaf ramps and windy roads no longer cause repeated zooming in and out as vehicle bearing changes.
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