Tracker optimisation focus #5967
Merged
Conversation
This file contains 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
|
🎉 Ta-daaa, freshly created APKs are available for bccb67e: arm64-android |
nirvn
force-pushed
the
tracker_optimisation
branch
2 times, most recently
from
a12dff9 to
4371639
Compare
|
@m-kuhn , did you give this a try? Can we merge? |
nirvn
force-pushed
the
tracker_optimisation
branch
from
4371639 to
d8c652c
Compare
Not yet, it says "WIP" in the description :-) |
m-kuhn
reviewed
Feb 4, 2025
|
@m-kuhn , oups! :) fixed the description, and about to fix your review. Thanks. |
nirvn
force-pushed
the
tracker_optimisation
branch
from
d8c652c to
a4471cc
Compare
m-kuhn
reviewed
Feb 4, 2025
…hen replaying against a point layer
nirvn
force-pushed
the
tracker_optimisation
branch
from
a4471cc to
bccb67e
Compare
m-kuhn
approved these changes
Feb 4, 2025
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.
This PR implements a number of strategies to optimize tracking playback when returning from a long period of time when QField was set in the background or the phone was locked.
For line and polygon layers, this makes replaying hours of captured positions near instantaneous.
For point layers, the speed is significantly improved, yet as every position will lead to a completely new feature being added (inc. unique value checks, default value expression calculation, etc), the time required to playback the position can take longer. To that end, we now have a busy indicator overlay to tell the user an ongoing operation is happening.
Overall, it makes using background tracking for long period of time much, much more efficient.