Android: Enable synchronous updates for NavigationPuckOverlay GeoJSON source#931
Merged
ianthetechie merged 1 commit intoJun 30, 2026
Conversation
Contributor
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Enable synchronous GeoJSON updates for the Android
NavigationPuckOverlaysource.The navigation puck source contains a single point feature with the current position and bearing. This is a small, frequently updated, latency-sensitive source, so it is a good fit for MapLibre Compose's
GeoJsonOptions(synchronousUpdate = true)(see maplibre/maplibre-compose#761 and maplibre/maplibre-native#3968).Motivation
The navigation puck should visually track position and bearing updates with as little latency as possible during active navigation. Applying this update synchronously avoids the extra async source update delay for this very small in-memory GeoJSON source.
Notes
This is intentionally limited to the navigation puck source. Larger GeoJSON sources such as routes, shape collections, or clustered data should continue using the default asynchronous update path to avoid hurting frame performance.
Testing