Due to site maintenance, Forum interaction has been disabled until August 13. For support, please search existing forum posts or check the support page.
Disappointing experience
I've tried to use Scenic several times during my recent trip to Minnesota. I found serious issues with the routing algorithm. Here's a good example - a route from Prospect Hts, Illinois to Osseo, Wisconsin. Apple Maps keeps you on I-90, and the trip takes 4 hours. Scenic creates a much more complex route using state roads with an estimated time 5 hours.
Hopefully switching to HERE maps will address issues like this. On the other hand, another app that is using OSM created the same route as Apple Maps.
Do you have avoid highways checked?
No, I don't.
Try' Efficient' instead of 'Fast' as a routing setting. If that doesn't solve it then just use waypoints to make the route go the way you want. Best to use the route planner for that.
Efficient produces the same route.
I don't think waypoints is a solution. There's an obvious issue with the routing algorithm Scenic is using that needs to be addressed. There should be a certain level of confidence in the app before you can use it.
Just to humor myself, I created a route with the same destination using Apple Maps, Google Maps, TomTom, Harley-Davidson, InRoute and CoPilot apps. I think those 6 apps covered most if not all available maps - Google, TomTom, HERE, OSM, and Trimble. They all created the same route.
I think I figured out the problem. It's the Avoid Ferries switch. When this switch is on, it somehow impacts routing algorithm. When I turned the switch off, Scenic created an expected route. Also, time to destination was wildly inaccurate - 4 hr 49 min vs 3 hr 56 min calculated by other apps.
Well, this didn't fix the problem completely. Here's is the same route in Scenic and H-D. Notice the difference between waypoints 4 and 5. Both were created using routing mode Fast. When I changed it to Efficient, Scenic created the same route as H-D. If this is how it's designed, it's very confusing. But it feels more like a bug.
Just came back from a ride shown above. At some point the map got so much behind, it started missing turns.
Sorry for your bad experience.... and thank you for your thorough analyses and comparison with other map providers. Both issues (the routing and the position lag) are important reasons why I'm switching to a new provider in Scenic 3. The new provider has HERE maps, and includes the HERE routing algorithm.