stadiamaps / stadiamaps/ferrostar
Starting navigation in the middle of the route tries to snap to the first Step and is immediately off route
- Dominant language
- Kotlin
- Stars
- 419
- Forks
- 81
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
I work on a custom navigation solution with very specific needs. It is a pre-calculated route which can be started without internet connection. Sometimes the driver is not at the beginning of the route, but somewhere on it.
But this navigation engine always assumes the navigation session always starts on the first _Step_, but we need it to start anywhere on the route. _MapboxNavigation_ (even the old one) can handle it.
I think this is the part that is causing this behavior. It gets the first _Step_ and then snaps to it:
https://github.com/stadiamaps/ferrostar/blob/abb3bde981634335726d5ffb3aac453576cdcda1/common/ferrostar/src/navigation_controller/mod.rs#L110-L118
If it is modified to check which _Step_ is the closes and than snap to it, it should handle both cases: starting at the beginning or in the middle.
Sadly, I don't know Rust to modify it
Contributor guide
Assessment
This issue has not been assessed yet.