-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Map Matching #659
Comments
cc: @osana for visibility on any required MAS changes. |
I opened individual tickets on what needs to happen in Mapbox Java to unblock this. |
Upstream tickets in Mapbox Java:
|
This missing params were added to Mapbox Matching Builder in mapbox/mapbox-java#718 |
This is being addressed in mapbox/mapbox-java#705 |
|
mapbox/mapbox-java#759 and mapbox/mapbox-java#764 have been merged. Are we good to close here @danesfeder? |
@Guardiola31337 Yep, map matching support was released with MAS |
The Map Matching API now supports a
waypoints
url parameter (Project-OSRM/osrm-backend#4732):By setting
waypoints=0,<coordinates.length-1>
, the response will return a route with a single leg similar to a normal directions route, and will allow for turn-by-turn navigation along a custom route.In theory, you should be able to start navigation with a custom route as with the following:
However, as commented above, we'll need to update a few things in order for this to work (mostly in MAS):
waypoints
property toMapboxMapMatching.Builder
roundaboutExits
,voiceInstructions
,bannerInstructions
toMapboxMapMatching.Builder
MapMatchingMatching
to aDirectionsRoute
to pass into MapboxNavigationcc @mapbox/navigation-android @cammace @coxchapman
The text was updated successfully, but these errors were encountered: