March 2nd, 2026
Release Date: January 25, 2026
Issue: Elevation profile displayed incorrect maximum values (~140m) instead of actual GPX elevation data (~700m for Signal de Botrange)
Root Cause: Chart was reconstructing elevation from gradient percentages, accumulating floating-point errors across thousands of segments
Fix:
Added startElevation and endElevation to segment data during route analysis
Modified elevation profile calculation to use actual GPX elevation values instead of reconstructing from gradients
Impact: Y-axis now displays correct elevation values matching GPX source data
User Action Required: None - existing routes automatically work after update (GPX data is re-parsed on route load)