From 708f5428968b7c1526f257b683d0146ef5dae418 Mon Sep 17 00:00:00 2001 From: Martin Kagamino Lehoux Date: Tue, 25 Aug 2026 11:32:57 +0200 Subject: Make mountain pass and web consumers take ride components instead of a whole Ride rideBounds, nearestCrossing and DetectCrossings now accept the coordinate, distance and elevation component slices they read. LoadMountainPassesAroundRide takes the coords slice only. Web ride view builders and the official climb creation path iterate ride components (Coords, Distances, Elevations) rather than per-index accessors on Ride. --- rideanalysis/analysis.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'rideanalysis') diff --git a/rideanalysis/analysis.go b/rideanalysis/analysis.go index 55f77b8..5e08e65 100644 --- a/rideanalysis/analysis.go +++ b/rideanalysis/analysis.go @@ -59,7 +59,7 @@ func Analyze(parsed ride.Ride, passes []mountain_pass.MountainPass, officialClim return a.Segment.StartIndex() - b.Segment.StartIndex() }) result.Climbs = climbs - for _, crossing := range mountain_pass.DetectCrossings(parsed, passes, passCrossingRadiusM, passCrossingElevationToleranceM) { + for _, crossing := range mountain_pass.DetectCrossings(parsed.Coords(), parsed.Distances(), parsed.Elevations(), passes, passCrossingRadiusM, passCrossingElevationToleranceM) { result.Crossings = append(result.Crossings, crossing) } return result -- cgit v1.3