Too much Champagne?
-
I am just back from a 4 day trip to the Champagne region.
All went very well, except that Next went totally balistic in the centre of Epernay.
It must have been the Champagne fumes
-
@Drabslab Can you share your route so that we may perhaps be able to find out why the champagne bubbles interrupted your route.
-
well, it's a tiny route from hotel to Epernay and back, for a short evening trip from hotel to Epernay.
https://www.myrouteapp.com/en/social/route/7863435?mode=share
but i know the reason (i think)
A small piece of road, marked with the red line, was closed so I was forced to drive to the square marked in green, but of course, next sent me back to the closed bit because it tried to send me to waypoint 2.
So, I turned around again, back to the green square, and ignored the instruction to drive back to the red marked bit... and drove through Rue Gambetta
And Next got really cross with me and sent me on a wild trip through Epernay (or at least that was its intention).
-
@Drabslab You probably already know, but but a long press on RP5 would have skipped RPs 2,3 and 4.
-
@Drabslab At least you've seen something of the city that way (just kidding). Your red-marked street is not the only part where there would be a road closure. There is also a road closure visible on the route from waypoint 5 to waypoint 6 (according to the map, see the blue border in my image). Perhaps that's why MRA is also confused? I hope you enjoyed the champagne...
-
@Drabslab I wonder what you think should have happened here. I also wonder why waypoint 3 and 4 are in the route (2 I sort of get if you want to drive along the Avenue de Champagne, but 3 and 4 just seem useless).
I think the combination of:
- a road closure at a crucial point of the route (right after the only bridge in the vicinity and a rail crossing), with virtually no alternate routes available to start with
- lots of 1-way roads and due to that no alternatives to point 2, 3 and 4 that avoid both the closed road AND avoid going back and forth over the same road
- having to skip 3 waypoints to get to 5, which the system may be "reluctant" to do because it's 3 points, not just 1 and you are still very close to those points (I don't know what the algorithm for auto skipping takes into account, but I can imagine distance to the point(s) to skip is part of it)
made this into a "perfect storm" of non-navigableness (is that a word?), that I don't think is very easy to solve.
I can't really think of how I would solve this myself using a paper map. Other than just not having all those waypoints and going straight to 5 (which looks like the main focus of the route (shouldn't it have been a viapoint?).
-
@Nick-Carthew said in Too much Champagne?:
but a long press on RP5 would have skipped RPs 2,3 and 4.
Yes, but in the city with a heap of champagne lovers in big tin cans on the street, I was focussing on staying upright.
@Herko-ter-Horst said in Too much Champagne?:
non-navigableness (is that a word?),
"non-navigableness" is definitively a correct technical navigation term, I used it a lot later that evening back in the hotel after a small bottle of zjampain with a few other bikers
@Herko-ter-Horst said in Too much Champagne?:
going straight to 5 (which looks like the main focus of the route)
yep, it was a parking spot close to where intended to have dinner
lesson 1: don't cobble together a route in 5 minutes
lesson 2: Corjan should do somethign about "non-navigableness"
Lesson 3: Next did very well over 1200 km in 4 days, not bad at all, excellent typing!!!But the big test is August, with a small ride around Switserland.
-
@Drabslab said in Too much Champagne?:
@Nick-Carthew said in Too much Champagne?:
but a long press on RP5 would have skipped RPs 2,3 and 4.
Yes, but in the city with a heap of champagne lovers in big tin cans on the street, I was focussing on staying upright.
That is exactly my point i did to try tell some other folks. You don't want to skip manually points in these kind of situations. That is the task of the navigation software to figure this out.
In my opinion. The cause of this problem is the software. It isn't mature enough. It takes time to improve these kind of situations
In the early days of TomTom Go i did see similiar things happens but now the software is much more mature (many years later), it rarely happens anymore. -
Looking at the progress made by MRA the past year alone... they will definitively get there.
And bear in mind, the complete MRA package is probably now already the best complete travel route preparation and riding package available, and still iumproving