mapbox / mapbox/mapbox-navigation-ios
Purpose of RouteController unclear
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 918
- Forks
- 326
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
**Mapbox Navigation SDK version:** 0.39
If I wanted to have turn-by-turn directions textual and visual shown on a map without using the NavigationViewController, rather an instance of NavigationMapView and some labels for the directions, is it still necessary to use a `RouteController`? In the past, I subscribed to various _alerts_ and on that basis triggered a new request and re-route but in the new versions of the API it's unclear to me what's actually required and what isn't. I'm using the `NavigationService` and observe it for `progressDidChange` and `routeControllerDidReroute` notifications and show the routes on the MapView accordingly. In essence, I need to show a route on a map, show an instruction in a label and if the user doesn't follow the current route, re-route and show the new route on the map etc.
Thank you,
Aodh.
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 Guides and examples, API reference, and example app linked in the issue, then compare the roles of NavigationService, RouteController, NavigationViewController, and NavigationMapView. Done means documenting which components are required for displaying routes and instructions, observing progress and rerouting, and presenting updated routes without NavigationViewController.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100