mapbox / mapbox/mapbox-navigation-ios-examples
Custom Route passing in navigation SDK
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 63
- Forks
- 32
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
I am seeking guidance on how to incorporate a custom route into the navigation SDK and effectively utilize the resulting output. Specifically, I have obtained a response from the direction API, containing the desired route information. How can I seamlessly integrate this route data into the navigation SDK for optimal functionality?
I aim to transmit the geometry data obtained from the direction API to the navigation SDK for seamless integration. How can I effectively transfer this geometry information to ensure smooth functionality within the navigation system?
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
No file or test is identified. Start by reviewing the existing iOS navigation examples and the navigation SDK's route-input entry points, then compare them with the Direction API geometry described here. Done should mean the custom geometry is accepted by the SDK and its resulting route can be used for navigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100