Scenic overestimates time required. By a lot. Bonus comment on routes that double back.
Quote from dasherpr on 15.06.2023, 18:23Hi, I am a long-time Scenic user (and fan of the app). Riding on long rides this week, I have noticed that Scenic overestimates the time required by a lot. Example - I just planned a 206 mile route on Google My Maps. Google thinks it will take me 5:05 to complete the loop. I imported it to Scenic, and it says 5:54. Almost an hour more. And it will likely take me less than 5 hours.
Is there a setting I'm missing, where you tell the app how much faster/slower than posted speed limits you normally ride? Maybe that's what's wrong.
Bonus comment: This time I have done some routes that require doubling back on the same line. For example, I was driving past a town but I wanted to check out some buildings inside the town, so I put a via point in town and then it doubled back out the way I came to continue my route. However, once I entered the "out and back" route, the app decided to skip the via point in town and just direct me to the next one along my route. This happened several times. FYI. It's as if it decides that my "out and back" is a spur that did not need to be part of the route.
Hi, I am a long-time Scenic user (and fan of the app). Riding on long rides this week, I have noticed that Scenic overestimates the time required by a lot. Example - I just planned a 206 mile route on Google My Maps. Google thinks it will take me 5:05 to complete the loop. I imported it to Scenic, and it says 5:54. Almost an hour more. And it will likely take me less than 5 hours.
Is there a setting I'm missing, where you tell the app how much faster/slower than posted speed limits you normally ride? Maybe that's what's wrong.
Bonus comment: This time I have done some routes that require doubling back on the same line. For example, I was driving past a town but I wanted to check out some buildings inside the town, so I put a via point in town and then it doubled back out the way I came to continue my route. However, once I entered the "out and back" route, the app decided to skip the via point in town and just direct me to the next one along my route. This happened several times. FYI. It's as if it decides that my "out and back" is a spur that did not need to be part of the route.
Quote from Guido on 15.06.2023, 18:47Thanks for the feedback
The duration overestimation is a known issue. More info here: https://scenic.app/forum/topic/arrival-time-inaccurate/#postid-2764
I’m working on a big update and will checkout the skipping of the double-back stretch. Probably what happens is that when a route contains the same stretch twice, it sometimes things you are on that stretch the 2nd time, while you are actually there the 1st time, removing all of the route between the 1st and 2nd time.
Thanks for the feedback
The duration overestimation is a known issue. More info here: https://scenic.app/forum/topic/arrival-time-inaccurate/#postid-2764
I’m working on a big update and will checkout the skipping of the double-back stretch. Probably what happens is that when a route contains the same stretch twice, it sometimes things you are on that stretch the 2nd time, while you are actually there the 1st time, removing all of the route between the 1st and 2nd time.
Quote from dasherpr on 15.06.2023, 18:56As always, thank you for your prompt and thoughtful replies! Unless you are traveling in America, it seems like you're burning (past) the midnight oil.
On the double-back, yes, that is exactly what it is doing, especially if on the 1st time on the same track I deviate in any small way (say stop to take a photo, or fuel).
Regards
As always, thank you for your prompt and thoughtful replies! Unless you are traveling in America, it seems like you're burning (past) the midnight oil.
On the double-back, yes, that is exactly what it is doing, especially if on the 1st time on the same track I deviate in any small way (say stop to take a photo, or fuel).
Regards
