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
The Android calculation of the current wayname was originally ported directly from the iOS logic.
mapbox/mapbox-navigation-ios#2635 tracks a performance improvement for this functionality that can be very significant for maps with many polyline segments. The Android algorithm should fix this issue as well.
The Android calculation of the current wayname was originally ported directly from the iOS logic.
mapbox/mapbox-navigation-ios#2635 tracks a performance improvement for this functionality that can be very significant for maps with many polyline segments. The Android algorithm should fix this issue as well.
I believe the corresponding code is here:
mapbox-navigation-android/libnavigation-ui/src/main/java/com/mapbox/navigation/ui/map/WaynameFeatureFilter.java
Line 99 in cc93c3d
The calculation of this LineSlice should be done outside of the double for-loop since it doesn't change.
The text was updated successfully, but these errors were encountered: