Minor refactoring of route line view #5631
Closed
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.
Description
Recently a customer asked for additional optimization around the process of selecting alternative routes. The rendering when redrawing long routes seemed longer than in the SDK's previous release. Although most of the rendering time is on the map side, this PR rearranges some of the calls to emphasize setting the line sources to get that process happening as early as possible. At the same time the calls to recalculate traffic gradients are executed on a background thread in parallel. This is a minor optimization. The bulk of the optimization is being explored on the map side.
Screenshots or Gifs