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
First of all, thank you for the amazing work on the flutter_mapbox_navigation package. It’s been incredibly helpful for integrating turn-by-turn navigation in Flutter apps.
I would like to request a feature to display custom polygons on the map, similar to how polylines are supported. This would be extremely useful for visualizing zones such as danger areas, delivery zones, geofences, or service coverage areas while navigating.
Use case:
• Show highlighted risk zones on the navigation map.
• Define delivery or service boundaries visually.
• Enhance the UI by dynamically rendering polygonal overlays based on user data.
If it’s not currently feasible to implement directly, it would also help to know if there’s a recommended workaround using native code or if this is planned in future versions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! 👋
First of all, thank you for the amazing work on the flutter_mapbox_navigation package. It’s been incredibly helpful for integrating turn-by-turn navigation in Flutter apps.
I would like to request a feature to display custom polygons on the map, similar to how polylines are supported. This would be extremely useful for visualizing zones such as danger areas, delivery zones, geofences, or service coverage areas while navigating.
Use case:
• Show highlighted risk zones on the navigation map.
• Define delivery or service boundaries visually.
• Enhance the UI by dynamically rendering polygonal overlays based on user data.
If it’s not currently feasible to implement directly, it would also help to know if there’s a recommended workaround using native code or if this is planned in future versions.
Thanks again for the awesome work! 🙏
Beta Was this translation helpful? Give feedback.
All reactions