Please or Register to create posts and topics.

Scenic 4 overestimating riding time (compared to Kurviger and Google Maps)

Hi Guido,

I am so sorry to bother you since you must be swamped with all the Version 4 work.

My issue might be Version 4 related though and could be quite important.

Im planning a trip to Thailand and want to do some routing ahead.

Work is all done on a Mac Mini M2

1. I find Scenic heavily overestimating the time for the same ride:

Scenic 132km 2h 57min

Kurviger 131km 1h 59min

Google maps 122km 2h 4min

 

Why could this be?

 

There is an error message – don’t know if it is relevant – screen shot added.

 

2. The next thing is not a big deal but obviously both Kurviger and Scenic takes an extra de-tour to make the famous Thai U-turn to avoid turning right (yes ride on the left side of the road ). Google maps doesn’t – it finds the little sneak passage not far away and guides the shortest way.

 

I fully understand that this is may be not your top priority for the moment….. but one day you or a smart guy in the forum hopefully can explain what is going on.

Thanks for your always great support

Paul

 

Hi Paul,

I’m working with the map provider to improve the duration estimate of routes. Will take a little while.

Regarding the u-turn. I don’t have time to look into this in detail, but it’s probably an error in the map data. Perhaps you can have a look yourself and report (or even fix) this error? Here is how: https://scenic.app/help/reporting-map-errors/

Best regards,

Guido

If you're enjoying Scenic and are happy with the support, please leave a nice rating in the App Store. It would mean a lot to me ❤️

Current travel times are overstated up to 83% limiting my practical use of Scenic to (1) a backup app for offline navigation and (2) checking unpaved roads. More roads are unpaved in Scenic than in reality, but Scenic lets easily review route planning, in particular with the recommendable street view function.

On a 60 km test leg, where I routinely achieve an average legal speed of 90 km/h, Michelin and TomTom are slightly speeding, InRoute, GoogleMaps  and Apple Map are realistic (⌀88 km/h), MyRoute (OSM), Sygic, Here WeGo and Kurviger are too conservative (⌀74 km/h) and Scenic and Guru Maps Pro are just too way off  (⌀48 km/h).

The U-turn issue is a common map issue in Thailand. Even Google or Apple may have several months delay until changes to U-Turns and roads are considered. In addition, OSM maps tend to be a few meters off and copying a coordinate may end up in the oncoming traffic lane.

Inaccurate travel times are not a big issue for me, but I had the opposite experience than Paul and Klonko on my recent trip to Scotland. Scenic was about 30% to optimistic (shorter) in terms of travel time compared to Google Maps or the BMW Navi App "Make Live A Ride" to which I export the Scenic route. This was true every day and on empty roads (no add-on from Google e.g. for traffic jams).

Thank you Guido,

Good to hear that you are not unaware of the issue and that you are working with the map provider.

Also thankful for the comments from Klonko and AstridM - it is so helpful to hear other peoples views.

Agree with Klonko's finding that roads sometimes are labelled un-paved when they in reality are not.

I was positively surprised to find the beautiful curvy roads next to the shore being paved when riding on Swedens biggest island Gotland out in the Baltic sea.

 

Great forum and great helpful community

/ Paul