In the world of tactical cycling, distance is not a straight line on a flat map. Most consumer-grade cycling apps treat the Earth as a plane (Euclidean geometry), which leads to significant errors in distance and slope calculation. Geodesic Accuracy is the practice of measuring distance over the Earth's ellipsoidal surface.
BikeScout implements 100% Geodesic Accuracy to ensure that when we report a 15% gradient "Wall", it is physically accurate, whether you are riding at the Equator or the high latitudes of the Dolomites.
The Problem: Meridian Distortion
The distance between degrees of longitude shrinks as you move away from the Equator. At 45°N (common in the Alps or Oregon), a degree of longitude is roughly 30% shorter than at the Equator. If your routing engine uses fixed multipliers, your total distance will be wrong, and your slope calculations will be purely fictional.
The Solution: The Haversine Formula
To defeat this distortion, BikeScout ignores the summary data provided by standard APIs and recalculates every single coordinate segment using the Haversine Formula. This calculates the great-circle distance between two points on a sphere given their longitudes and latitudes.
c = 2 ⋅ atan2( √a, √(1−a) )
d = R ⋅ c
Tactical Impact: The "Wall %" Credibility
Gradient (Slope) is the ratio between Vertical Gain and Horizontal Distance. By using Geodesic distance as our horizontal baseline, BikeScout eliminates the "flattening" effect of map projections. This is why our climb_category and avg_gradient metrics match the physical effort felt by the rider's legs, providing a higher level of tactical trust than generic GPS trackers.
Why it Matters for AI
Large Language Models (LLMs) cannot "feel" the terrain. They rely on the data we feed them. By providing Geodesically Accurate telemetry through the MCP protocol, BikeScout ensures the AI can accurately predict energy expenditure and technical difficulty without being misled by map distortion.