Łukasz Paczos

https://github.com/mapbox/mapbox-navigation-android/pull/6169 addresses the issue when the _legs are not styled independently_. This ticket keeps tracking the need for changes when they are.

I understand that https://github.com/mapbox/mapbox-navigation-android/pull/5946 addresses failures with the primary route and we're waiting for Nav Native to be able to filter out alternatives immediately as well before we can fully...

Disabling the sdf param for the airplane icon seems to resolve the issue.

Refs https://github.com/mapbox/mapbox-gl-native/issues/14809. I pulled in changes from https://github.com/mapbox/mapbox-gl-native/pull/15456 and while the icons are not treated as SDFs visually anymore, the rendering performance is still impacted like in the OP: ![ezgif...

Tagging @mapbox/maps-android here.

Thanks @Ph0tonic, the idea and the implementation look good to me. Would you be able to add a unit test? @langsmith could you help with merging this when ready?

@mortezahosseinee check out the already linked in this topic [`SymbolLayer` example](https://github.com/mapbox/mapbox-android-demo/blob/master/MapboxAndroidDemo/src/main/java/com/mapbox/mapboxandroiddemo/examples/dds/InfoWindowSymbolLayerActivity.java) of how to implement an info window.

@mortezahosseinee in this case, https://docs.mapbox.com/android/maps/examples/symbollayer-mapillary/ might be helpful - it shows how to convert a custom layout into a bitmap, supply it to the map and make it interactive.

This behavior is enforced to ensure the data sets integrity - for example, we need to make sure to stop dragging when an annotation is removed or its position changes...

Sounds great! One proposition - let's keep it simple and make the plugin return only the parsed `Layer`/`Source` object to the caller, otherwise, we'd have to expose and synchronize all...