Forum breadcrumbs - You are here:Scenic ForumUsing ScenicRouting Observations
Please or Register to create posts and topics.

Routing Observations

I used Scenic for the first time on one of my "bigger" rides.   8 days in West Virginia, Pennsylvania, New York, Vermont, New Hampshire and Maine.

My planning tool of choice is Furkot and I built an 8 day plan and imported into Scenic.   While in West Virginia, I ended up creating routes on the fly based on local recommendations.

What I found is routing compared to Google Maps is at times vastly different.   Like really really really different.    In West Virginia and Pennsylvania I spent all my time "off highway" and alot of time on very back roads.   Google Maps would give me good estimates on non-highway roads between cities while Scenic had a difficult time and would never route directly as possible even on "fastest" or "shortest".       Again when comparing Google Maps, Google would provide a fastest route, then a backup route that was a little bit slower.     Scenic would provide a route vastly longer in mileage every time, even on shortest.

On a day where I just wanted a 2-lane road that was "efficient" and kept me off the freeways, Google option was "avoid highways" and Scenic option was "avoid highways" and "balanced".    I had to rely on Google to keep me for example going north-east, while Scenic had wanted a route that went far north then east...like it did not know about the non-highway highway going north-east.    I had both running and Google and Scenic would eventually be on the same route, however Scenic would randomly try to route in various strange directions.

I assume this is a (limited) mapping data issue in my area?  Is there anything I can provide to help with these navigation "issues"?

I also want to say this was not a huge deal for me in this instance as I was on vacation and exploring and using the GPS to just get to my next destination...    and again, I am happy to help in any way to make this better!

 

** FYI - I do have the downloaded maps

 

That's a bit strange indeed. Typically Google Maps and Scenic will give you the same or very similar 'fast' and 'short' routes. There can be slight differences, but not as big as these ones if I understand correctly.

Having said that, Scenic uses HERE maps and the HERE routing algorithm, and Google Maps uses its own map data and algorithm obviously. There are bound to be differences in the map data as well as the routing algorithm. There could be a mapping data issue, indeed. The way to solve this is (1) first find out exactly what the error is and where (what road or junction it occurs), and then report that error to HERE maps: https://scenic.app/help/roads-not-on-the-map-errors-in-the-map-data/

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 ❤️

Thanks Guido, I am looking through my recorded rides and trying to piece together the reasons why Scenic was so different from Google and if I find out why I will let you know.    I definitely love Scenic as it has the features needed and is easier to use too.

Interesting, on the wego.here.com site, I did the same route search and it came up with 3 different routes.  The search was just a driving search with no options.

Search was:  St. Marys, PA to Latham, NY

Results were:

a.) all highway

b.) combo of highway/non-highway

c.) combo of highway/non-highway

What is interesting is the default result from  Here is option a.) and that result is longest in time AND distance.     The route I took was (from Google) but looks just like option b.)....    Option b.) was never shown on the Scenic app.   It only showed what I believe is option a.)           I just went into Power Planner and put in the same TO/FROM and no matter what routing algorithm I select is shows the "option a.)" route.

Am I doing anything wrong on the app or what do you think?

Here is a screenshot of wego.here.com

The WeGo here website is on a newer map framework. Im currently working on the big update from Scenic, which will adopt this new HERE map framework.

mcouture has reacted to this post.
mcouture
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 ❤️