Re: Routing errors (again) - any idea of a point of contact that may care ?
Posted: Wed Sep 15, 2021 3:54 pm
Thanks for that. The reason I asked is that I noticed that the caption underneath said the same thing no matter what the 3rd screen radio button said. Also that changing the settings when in Bike mode also changed the settings in car mode. Which is definitely wrong.
However, when I did a factory reset, everything was back as it should be.
I noticed when I was having problems with music and sound, that it only happened after I had been fiddling with the Explore website. After doing a reset, it behaved normally. I repeated this a number of times - each time I connected to Explore for the first time, the sound would be on off on off very rapidly. Sometimes it played v e r y s l o w l y.
I'm wondering if the same is happening with the Avoid Tolls.
I did a few tests. But I have to redo them as I forgot that doing a reset ticks all of myMaps - and I forgot to untick my OSM maps, which will probably have affected the results.
I tested your routes. My version of your routes created in BC and transferred (but with a correct positioning of Point B), and routes created on the XT Trip Planner using favourites with A-C, B-C, A-B-C, B2-C, A-B2-C.
Every version of each test behaved exactly the same as the every other version of the same test - both with Tolls allowed and tolls avoided. The inaccurate positioning of B makes no difference. The transfer from BAsecamp makes no difference. I even tried A to shaping point at B to C in case it was to do with Garmin's waypoints. So the XT version, the SN version and the JH version of each test produced identical results.
It seems that something is making it avoid certain roads around the are of Point B. So I got onto google street view, and looked at the roads. There are areas there that in 2015, the roads around Hambledon were closed.
So I did a simulation.
Try simulating the route. There are no speed limit signs on the Zumo screen - except near the A3 - but the simulation normally drives up to the speed limit on open roads. Watch what speed it sticks to. That might be a reason why it goes for main roads if it thinks it can do only 30-40mph on most of the rest of it. It doesn't explain it fully, but its getting closer.
I need to double check my results for the tests without OSM being ticked.
However, when I did a factory reset, everything was back as it should be.
I noticed when I was having problems with music and sound, that it only happened after I had been fiddling with the Explore website. After doing a reset, it behaved normally. I repeated this a number of times - each time I connected to Explore for the first time, the sound would be on off on off very rapidly. Sometimes it played v e r y s l o w l y.
I'm wondering if the same is happening with the Avoid Tolls.
I did a few tests. But I have to redo them as I forgot that doing a reset ticks all of myMaps - and I forgot to untick my OSM maps, which will probably have affected the results.
I tested your routes. My version of your routes created in BC and transferred (but with a correct positioning of Point B), and routes created on the XT Trip Planner using favourites with A-C, B-C, A-B-C, B2-C, A-B2-C.
Every version of each test behaved exactly the same as the every other version of the same test - both with Tolls allowed and tolls avoided. The inaccurate positioning of B makes no difference. The transfer from BAsecamp makes no difference. I even tried A to shaping point at B to C in case it was to do with Garmin's waypoints. So the XT version, the SN version and the JH version of each test produced identical results.
It seems that something is making it avoid certain roads around the are of Point B. So I got onto google street view, and looked at the roads. There are areas there that in 2015, the roads around Hambledon were closed.
So I did a simulation.
Try simulating the route. There are no speed limit signs on the Zumo screen - except near the A3 - but the simulation normally drives up to the speed limit on open roads. Watch what speed it sticks to. That might be a reason why it goes for main roads if it thinks it can do only 30-40mph on most of the rest of it. It doesn't explain it fully, but its getting closer.
I need to double check my results for the tests without OSM being ticked.