Register vector tile label features first when all tiles are fetched #60361
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.
This is a follow up on #60346, where the problem is described in more detail.
Problem
When rendering a map from a vector tile service, tiles are fetched asynchronously. Once a tile is fetched, its features are registered for labeling. However, the order in which the label features are registered can change depending on the order in which tiles are fetched. This results in inconsistent labeling.
Solution
Rather than registering label features when an individual tile is fetched, tiles are stored in a map. Once all tiles have been fetched, they are registered for labeling in order by tile id.