You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when you arrive at an intersection the state machine in common usually moves you forward to the next step. This makes sense as you're geographically on the edge of the next step. However, this can be confusing when you look down and see instructions for the next maneuver when you still haven't progressed through the intersection.
The Question:
When has the user actually completed the maneuver?
Short term idea is to add an index padding param to the step advance, where we can delay the route step update n indexes. Note this may need to only be for visual instructions, as the snapping and other tools use the RouteStep's coordinates.
Long term, map matching support.
The text was updated successfully, but these errors were encountered:
Currently when you arrive at an intersection the state machine in
common
usually moves you forward to the next step. This makes sense as you're geographically on the edge of the next step. However, this can be confusing when you look down and see instructions for the next maneuver when you still haven't progressed through the intersection.Short term idea is to add an index padding param to the step advance, where we can delay the route step update
n
indexes. Note this may need to only be for visual instructions, as the snapping and other tools use theRouteStep
's coordinates.Long term, map matching support.
The text was updated successfully, but these errors were encountered: