Fix "Elevation Correction doesn't work" #21691
Merged
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.
Fix Summary
This pull request addresses the issue described in #21418.
Problem Description
The issue occurred exclusively for tracks recorded manually via Trip Recording and did not affect tracks created with Plan Route or exported from navigation routes.
The root cause was point duplication in tracks, resulting in a mismatch between the number of points in GPX tracks and segments in the editing context. This problem is described in detail here and here.
Analysis and Fix
Testing
Elevation correction
output_360x800_alt.mp4
output_360x800_video3.mp4
Save as a new "simplified track"
output_360x800_video2.mp4
output_360x800_video4.mp4
Outcome
The functions now work correctly after the changes, and the bug described in the Issue has been successfully resolved.