An ETA that rides at your pace
Open TET sub-trail I-01 in Sardinia the other way round and the app used to say 14 hours 18 minutes for 169 km. Nobody rides it that slowly. Today the same trail plans at about 6 hours 40 minutes. While you ride, the estimate now learns how fast you actually go, and it remembers that for next time.
Why the estimate was so slow
The planned time is the router's time, road by road. Where OpenStreetMap has a posted speed limit, that limit is the speed; everywhere else the router uses a typical speed for that kind of road. That works well on tarmac. On unpaved tracks with no speed tag, the router's own figure is 5 to 7 km/h. I-01 has 83 km of those, and they alone accounted for more than 12 of its 14 hours.
AL-01 in Albania looked slow for a different reason: most of its gravel carries a real posted limit of 20 km/h in OpenStreetMap. That limit is kept.
Realistic times on unpaved tracks
Trips built from a GPX or a TET trail now time gravel and compacted roads at no less than 20 km/h, dirt at 15 km/h and paths at 10 km/h. A posted limit is never exceeded, and the route and its turns do not change, only the time:
| Trip | Before | Now |
|---|---|---|
| I-01 reversed, 169 km | 14 h 17 min | 6 h 37 min |
| I-01 native, 168 km | 14 h 27 min | 6 h 40 min |
| AL-01 reversed, 173 km | 7 h 45 min | 6 h 28 min |
The TET trails are rebuilt on the server over the next few nights; each one switches to the new time as soon as it is rebuilt, and your phone picks it up the next time you open the trail online.
The ETA learns your pace while you ride
A floor is the same for everybody, and gravel pace depends on the rider. So every 4 km the app now compares your moving time with the planned time for the same stretch, and re-estimates the rest of the route. It keeps two separate estimates, one for roads and one for tracks and gravel, so a fast motorway run never makes the trail look shorter. Traffic lights, photo stops and coffee breaks do not count. The remaining time, the arrival clock, the next-stop ETA and the CarPlay and Android Auto estimates all follow it, and a small your pace caption says so.
And it remembers
When navigation stops, the app remembers your pace for that vehicle. The next ride starts from it, halfway between your usual pace and the plan (a new trail or a wet day is slower than your average), until the first 4 km of that ride take over. Before you start, the planner shows both numbers, for example 7:45 h · ≈ 5:17 h at your pace.
Tap the ⓘ next to a planned route's time, or the pace caption in the HUD, for a short explanation. Everything can be turned off in Settings → Navigation → Adapt ETA to my pace, and Forget my pace clears what the app remembers.