Conversation
- Add missing mountain-pass Overpass query and styling params to the Multi Mountain renderer (previously only mountain huts were fetched) - Fix a distance-computation asymmetry in GpxTrack.load() where the cumulative distance used a different point order than gpxpy's own length_3d(), breaking coherence on simplified/curvy tracks - Drop unplaceable text labels instead of crashing the whole poster when too many labels are packed into a small area - Fix Profiling bypass-queue leaking across worker-process calls after an exception, which caused an unrelated error on the next upload Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0188FvAtgW3nmYx88h9EBKcp
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
GpxTrack.load(): the cumulative distance usedprev_point.distance_3d(point)while gpxpy's ownlength_3d()usespoint.distance_3d(prev_point)— since gpxpy's flat-earth formula depends on theselfpoint's latitude only, the mismatch grows with segment length and broke the coherence check on simplified/curvy tracksProfiling's bypass queue leaking across worker-process calls after an exception, which caused an unrelatedBypass queue named 'Parallel' is already seterror on the next upload attempt in the same reused worker processTest plan
GpxTrack.load()coherence check passes on 5 real-world multi-day GPX tracks (previously failing by up to ~2.5 m) after the distance-order fix@profile_parallel-decorated call that raises no longer blocks a subsequent call in the same process🤖 Generated with Claude Code
https://claude.ai/code/session_0188FvAtgW3nmYx88h9EBKcp