Teaching Valhalla That Hiking Is Not Flat
A walking route across a city and a hiking route up a mountain should not share the same clock.
That sounds obvious until you ask a routing engine for an ETA. Most routing systems are good at distance, turn costs, access rules, and road classes. Hiking time is different. A two-kilometer trail can be easy, slow, dangerous, or all three depending on slope, descent, surface, visibility, and how the local trail network publishes reference times.
For Globus routing, this matters because we use Valhalla deeply. Valhalla already has the graph, the route shape, and elevation in the tiles. The question was whether we could use that information to make hiking ETAs less optimistic without breaking tile compatibility or inventing a regional formula that only works in one mountain range.
Over the last research pass, we built the corpus, tested the formulas, rejected several tempting models, used a deliberately expensive research hook to learn what worked, and then moved the result into production-shaped Valhalla code.
