Skip to content
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

Step Progression Improvement. #363

Open
Archdoog opened this issue Nov 19, 2024 · 0 comments
Open

Step Progression Improvement. #363

Archdoog opened this issue Nov 19, 2024 · 0 comments
Labels
bug Something isn't working core Related to the Rust core

Comments

@Archdoog
Copy link
Collaborator

Archdoog commented Nov 19, 2024

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.

@Archdoog Archdoog added bug Something isn't working core Related to the Rust core labels Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working core Related to the Rust core
Projects
None yet
Development

No branches or pull requests

1 participant