ETA inaccurate
Quote from Kev450 on 21.07.2025, 16:55I did a ride last Saturday (July 19th 2025), one that I edited on July 17th to modify the planning, I didn't notice it when I edited it but the ETA was longer than what we actually did. Can't give you all the specifics but that is the day I noticed the problem.
Now if I go back in the rides I created, all recent ones automatically have their ETA's adjusted to be way longer than it actually is. To find when the problem started I went to all the created rides until I got to one that I created on July 12th 2025 and this one has the normal ETA but if I edit it, it will give it the "new" ETA which is far longer than the actual time it takes, around 1 hour extra in this case. I did a ride today that had a 4 hour estimate and it took 3 hours... So this problem started after July 12th 2025, now any ride I create will have this way overestimated ETA. According to the apple store, scenic had an update about 2 weeks ago so the problem may be from there.
![]()
I did a ride last Saturday (July 19th 2025), one that I edited on July 17th to modify the planning, I didn't notice it when I edited it but the ETA was longer than what we actually did. Can't give you all the specifics but that is the day I noticed the problem.
Now if I go back in the rides I created, all recent ones automatically have their ETA's adjusted to be way longer than it actually is. To find when the problem started I went to all the created rides until I got to one that I created on July 12th 2025 and this one has the normal ETA but if I edit it, it will give it the "new" ETA which is far longer than the actual time it takes, around 1 hour extra in this case. I did a ride today that had a 4 hour estimate and it took 3 hours... So this problem started after July 12th 2025, now any ride I create will have this way overestimated ETA. According to the apple store, scenic had an update about 2 weeks ago so the problem may be from there.

Quote from Guido on 22.07.2025, 02:00Yes...this is weird. The only possible explanation I can think of is that the datae for the duration calculation changed with the most recent map update. I've asked the map provider if they changed something, and will report back once I receive a response.
Yes...this is weird. The only possible explanation I can think of is that the datae for the duration calculation changed with the most recent map update. I've asked the map provider if they changed something, and will report back once I receive a response.
Quote from Kev450 on 24.07.2025, 15:29Quote from Guido on 22.07.2025, 02:00Yes...this is weird. The only possible explanation I can think of is that the datae for the duration calculation changed with the most recent map update. I've asked the map provider if they changed something, and will report back once I receive a response.
Any way for me to send you a private message? I created an itinerary for my weekend ride and detailed the comparison with the timeframe from Google Maps for example, might help to investigate, this one is almost 2 hours off..
Quote from Guido on 22.07.2025, 02:00Yes...this is weird. The only possible explanation I can think of is that the datae for the duration calculation changed with the most recent map update. I've asked the map provider if they changed something, and will report back once I receive a response.
Any way for me to send you a private message? I created an itinerary for my weekend ride and detailed the comparison with the timeframe from Google Maps for example, might help to investigate, this one is almost 2 hours off..
Quote from Kev450 on 20.09.2025, 13:07problem persists even in version 4.24 , just got back from a ride, Scenic ETA after creating the itinerary, 5 hours 49 minutes round trip, actual recorded time 4 hours 50 minutes, a full hour off in this case, that is horrible for planning!!
problem persists even in version 4.24 , just got back from a ride, Scenic ETA after creating the itinerary, 5 hours 49 minutes round trip, actual recorded time 4 hours 50 minutes, a full hour off in this case, that is horrible for planning!!



